AERS Reports Server Stops Responding And The Reports Are No Longer Generated (Doc ID 577515.1)

Last updated on SEPTEMBER 03, 2014

Applies to:

Adverse Event Reporting System - Version: 4.5 and later   [Release: 4.5 and later ]
Information in this document applies to any platform.
***Checked for relevance on 12-FEB-2010***

***Checked for relevance on 10-AUG-2011***

Symptoms

On AERS 4.5, after one day of running, the AERS reports server stops responding and the reports are no longer generated.

The following errors are generated in the report server trace file:


[2008/4/22 3:10:20:718] Exception 50125 (oracle.ias.repository.schema.SchemaException: Unable to connect to Oracle Internet Directory Server. Please verify that the correct Oracle Internet Directory Server parameters are specified in D:\ORACLE\AS904\config\ias.properties. Make sure that the Oracle Internet Directory Server specified in OIDhost, OIDport is up and running. Base Exception : javax.naming.NamingException: [LDAP: error code 1 - User does not exist in directory for Proxy Switch]
at oracle.ias.repository.IASSchema.connectAs(IASSchema.java:1925)
at oracle.ias.repository.IASSchema.connectAs(IASSchema.java:1873)
at oracle.ias.repository.SchemaManager.connectAs(SchemaManager.java:1280)
at oracle.reports.utility.InfraConfigMgr.createDirContext(InfraConfigMgr.java:213)
at oracle.reports.utility.InfraConfigMgr.createOIDContext(InfraConfigMgr.java:128)
at oracle.reports.server.RWSecurity.start(RWSecurity.java:95)
at oracle.reports.server.SecurityHelper.start(SecurityHelper.java:85)
at oracle.reports.server.RWServer.startServer(RWServer.java:595)
at oracle.reports.server.RWServer.run(RWServer.java:229)
at java.lang.Thread.run(Thread.java:534)
): Internal error oracle.ias.repository.schema.SchemaException: Unable to connect to Oracle Internet Directory Server. Please verify that the correct Oracle Internet Directory Server parameters are specified in D:\ORACLE\AS904\config\ias.properties. Make sure that the Oracle Internet Directory Server specified in OIDhost, OIDport is up and running. Base Exception : javax.naming.NamingException: [LDAP: error code 1 - User does not exist in directory for Proxy Switch]
[2008/4/22 3:10:20:718] Debug 50103 (InfraConfigMgr:createDirContext): Failed to create OiD DirContext.
[2008/4/22 3:10:20:718] Debug 50103 (InfraConfigMgr:createDirContext): OiD DirContext created successfully. m_totalSize:0

[2008/4/23 7:50:2:937] State 56004 (EngineInfo:setState): Engine rwURLEng-0 state is: Initial
[2008/4/23 7:50:3:93] Exception 4068 (): ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package "PORTAL30.WWV_CORNERDB" has been invalidated
ORA-04065: not executed, altered or dropped package "PORTAL30.WWV_CORNERDB"
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "PORTAL30.WWV_RW_SB", line 129
ORA-06512: at "PORTAL30.WWV_RW_SB", line 55
ORA-06512: at line 1

exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=4068,
java.lang.String errorString="ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package "PORTAL30.WWV_CORNERDB" has been invalidated
ORA-04065: not executed, altered or dropped package "PORTAL30.WWV_CORNERDB"
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "PORTAL30.WWV_RW_SB", line 129
ORA-06512: at "PORTAL30.WWV_RW_SB", line 55
ORA-06512: at line 1
",
java.lang.String moduleName="SQL"
}}
}
at oracle.reports.utility.Utility.newRWException(Utility.java:604)
at oracle.reports.utility.DBConnection.handleSQLException(DBConnection.java:200)
at oracle.reports.server.WebDBIntegration.createScheduledJob(WebDBIntegration.java:413)
at oracle.reports.server.ConnectionImpl.runJob(ConnectionImpl.java:1109)
at oracle.reports.server.ConnectionPOATie.runJob(ConnectionPOATie.java:296)
at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:419)
at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:85)
at com.inprise.vbroker.poa.POAImpl.invoke(POAImpl.java:2355)
at com.inprise.vbroker.poa.ActivationRecord.invoke(ActivationRecord.java:104)
at com.inprise.vbroker.GIOP.GiopProtocolAdapter.doRequest(GiopProtocolAdapter.java:492)
at com.inprise.vbroker.IIOP.ServerProtocolAdapter.doRequest(ServerProtocolAdapter.java:64)
at com.inprise.vbroker.GIOP.GiopProtocolAdapter.dispatchMessage(GiopProtocolAdapter.java:653)
at com.inprise.vbroker.orb.TPDispatcherImpl$TPDispatcher.run(TPDispatcherImpl.java:99)
at com.inprise.vbroker.orb.ThreadPool$PoolWorker.run(ThreadPool.java:76)


Steps To Reproduce:
  1. Run opmnctl stopall on the middle tier;
  2. Run opmntcl stopall on database;
  3. Bounce the database;
  4. Delete the <reportserver>.dat file on the middle tier;
  5. Run opmnctl startall on database;
  6. If the report service is not in "Started" status before running 'opmnctl startall' on the middle tier, it will stay in blank status, but the reports will run until next day;
  7. If the report service is in "Started" status before running 'opmnctl startall' on the middle tier, it will be displayed with "Started" status.
  8. The reports can be ran throughout that day, but will stop during the next day.
If the steps 1-7 are not executed, the reports can not be run even if the report service is in "Started" status. In this case, the AERS reports are moved to 'Q' status.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms