My DataBase is up and running, my config.xml is correctly configured:
<resource enabled="true">
<name>main-db</name>
<provider>jeeves.resources.dbms.DbmsPool</provider>
<config>
<user>geonetwork</user>
<password>geonetwork</password>
<driver>oracle.jdbc.driver.OracleDriver</driver>
<url>jdbc:oracle:thin:@geodby:1521:GIS10</url>
<poolSize>4</poolSize>
</config>
<activator class="org.fao.geonet.activators.McKoiActivator">
<configFile>WEB-INF/db/db.conf</configFile>
</activator>
</resource>

Geodby is the ServerName
GIS10 is the Oracle Istance.

But if I try to perform a search or try to login I get:

The requested operation could not be performed.

The Tomcat Console Write:
2006-03-16 07:44:22 | HTML Request (GET) : /geonetwork/srv/en/main.search
2006-03-16 07:44:22 | Dispatching : main.search
2006-03-16 07:44:22 | -> parameters are :
2006-03-16 07:44:22 | extended = off
2006-03-16 07:44:22 | hitsPerPage = 10
2006-03-16 07:44:22 | any =
2006-03-16 07:44:22 | attrset = geo
2006-03-16 07:44:22 | remote = off
2006-03-16 07:44:22 | [main.search] Exception when executing service
2006-03-16 07:44:22 | [main.search] (C) Exc : java.lang.NullPointerException
2006-03-16 07:44:22 | Raised exception while executing service
<error id="error">
<exception>
<message />
<string>java.lang.NullPointerException</string>
<stack>java.lang.NullPointerException&#xD;
at org.fao.geonet.services.main.Search.exec(Search.java:68)&#xD;
at jeeves.server.dispatchers.ServiceInfo.execService(ServiceInfo.java:23
8)&#xD;
at jeeves.server.dispatchers.ServiceInfo.execServices(ServiceInfo.java:1
Could You Help me?

Thanks
Paolo

We have the same problem (error on login/search: The requested operation could not be performed) with geonetwork using a postgresql database.
We installed and configured again and again with no success. Is there any more specific information available to solve this?

Thanks
Stefan

The error on metadata search (The requested operation could not be performed) seems to be tomcat related. Using the integrated jetty server geonetwork runs with a postgresql database. Running under tomcat leads to the error message above.