Metrics doesnt like my oracle 11g install

[hiddenkirby]

So i upgraded form oracle10g to oracle11g... and copied over the ojdbc5.jar to the correct directory. (there are now ojdbc14.jar and ojdbc5.jar in the same dir... if thats ok)

Any time i open a metrics package i get this error.

'no ocijdbc10 in java.library.path'
WHILE processing request for pid 'null'
WHILE Executing page 'null', from pageMap 'Unknown, since pid 'null' doesn't exist in any of the page maps', via request:

none of the existing cognos kb articles seem to have anything substantial for this issue. (or that i can find)

Any help would be greatly appreciated.

Cognos 8.3
Oracle11g client and DB Server


Thanks,
  Kirby

[hiddenkirby]

Cognos tells me to upgrade the ojdbc14.jar file to ojdbc5.jar... to releive that error msg. 

Though when i do i cannot start up services.

I  opened a separate SR with them .. and their answer is to update my JRE on the server.  (this does not seem right)

Thought under c8_location/bin/jre/ .. there is a 1.5 already there.     so whats the deal?

still waiting on Cognos Tech Support to get back to me but if anyone has any suggestions please shoot!

any help is appreciated.

[hiddenkirby]

Also the error i recieve when i place ojdbc5.jar in the c8\webapps\p2pd\WEB-INF\lib dir  is as follows.

The content store is on an oracle 11g RAC database.

[Content Manager database connection]
1. [ ERROR ] The database connection failed.
2. [ ERROR ] Content Manager failed to start because it could not load driver "oracle.jdbc.driver.OracleDriver".

[jriley]

From our discussion with Cognos support.  Oracle 10g Release 2 is the highest supported version of Oracle for a Metrics Store, please see the IBM Cognos BI 8.3 Software Environments page (direct link to Metrics Store http://www-01.ibm.com/support/docview.wss?rs=3442&uid=swg27013941#metricstore).

As to why you are unable to use the ojdbc5.jar file to connect to Oracle 11g, it appears that 8.3 RTM is meant to use the ojdbc14.jar file... in fact, I have come across an existing defect for this very issue (service won't start if using Oracle 11g and the odjbc5.jar file... the workaround is to use the ojdbc14.jar file).