Auto-declare fails when using Oracle 11g R2 and WebSphere Application Server 6.1

Auto-declare fails when using Oracle 11g R2 and WebSphere Application Server 6.1

Technote (troubleshooting)

Problem(Abstract)

Records cannot be automatically declared when you run IBM Records Manager with Oracle 11g R2 and WebSphere Application Server 6.1.

Symptom

Errors such as the following messages are written in the rmeserver.log. By default, the log file is in theIBMCMROOT/log/rme directory.

[MSG]: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.reflect.InvocationTargetException]
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:1000)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:705)
at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:2097)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1951)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1866)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1556)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1358)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:172)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
at com.ibm.rme.cmutils.dao.common.CommonDAO.isDatasourceCreated(CommonDAO.java:205)
at com.ibm.rme.repository.cm.RMECMRepositoryInterface.isWasDataSourceCreated(RMECMRepositoryInterface.java:2336)
at com.ibm.rme.init.RMEServerInit.init(RMEServerInit.java:222)
at com.ibm.rme.init.RMEServerInitThread.run(RMEServerInitThread.java:18)
at java.util.TimerThread.mainLoop(Timer.java:537)
at java.util.TimerThread.run(Timer.java:487)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:619)
at com.ibm.ejs.j2c.J2CUtilityClass.createMCFEntry(J2CUtilityClass.java:426)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.createMCFandPM(ConnectionFactoryBuilderServerImpl.java:557)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.processObjectInstance(ConnectionFactoryBuilderServerImpl.java:936)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:650)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:896)
... 
Caused by: java.lang.NoSuchMethodError: oracle/jdbc/driver/OracleLog.setLogVolume(I)V
at com.ibm.ws.rsadapter.dbutils.impl.OracleUtilityImpl.setLogVolume(OracleUtilityImpl.java:85)
at com.ibm.ws.rsadapter.spi.InternalOracleDataStoreHelper.setProperties(InternalOracleDataStoreHelper.java:142)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.<init>(WSRdbDataSource.java:911)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.setDataSourceProperties(WSManagedConnectionFactoryImpl.java:2239)

In addition, if you check the IBM Content Manager resource manager table RMEAUTODECLARE, the status column of the item to be declared is set to ERR.

Resolving the problem

To resolve this problem, verify that the IBM Content Manager Records Enabler data source is configured correctly in the WebSphere Application Server administrative console:

• In the Data store helper class name area of the data source configuration page, verify thatOracle10g data store helper is selected.
• On the configuration page for the oracle9iLogTraceLevel custom property of the data source, ensure that no value is specified in the Value field.

參考地址：http://www-01.ibm.com/support/docview.wss?uid=swg21627275