OBIEE 12C - Agent issue

vai

We have currently migrated from 11.1.1.7 to 12.2.1.2, when i am trying to run agent , it throws an error.

I tried to deliver agent with different formats, but still facing the same issue.

Found below entries in obisch  log - i am not able to figure out the issue.

Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: Error loading Presentation Catalog.

Error Codes: MTKA9QGD

Location: saw.subsystems.admin.initServiceInstance, saw.securitysubsystem.checkauthentication.runimpl, saw.securitysubsystem.checkauthentication, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

Error Codes:

Location: saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

.

Error Codes: AGEGTYVF

, in call Create sessions...Trying main loop again.... Sleeping for 4 seconds.Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: Error loading Presentation Catalog.

Error Codes: MTKA9QGD

Location: saw.subsystems.admin.initServiceInstance, saw.securitysubsystem.checkauthentication.runimpl, saw.securitysubsystem.checkauthentication, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

Error Codes:

Location: saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

.

Error Codes: AGEGTYVF

, in call Create sessionsTerminal Error: Exceeded number of retries.

Joel

The error states an issue with loading the Presentation Catalog. Could you try loading the SampleApp catalog to rule out an issue with your upgraded catalog?

By the way, did you follow the Catalog Upgrade pre-requisite steps - Slide 6 3rd bullet point?

vai

very much thanks for your revert

I followed your points, it works fine with single server instance but,  when i clustered my environment, i am facing the same issue again.

Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: Error loading Presentation Catalog.

Error Codes: MTKA9QGD

Location: saw.subsystems.admin.initServiceInstance, saw.securitysubsystem.checkauthentication.runimpl, saw.securitysubsystem.checkauthentication, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

Error Codes:

Location: saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

.

Error Codes: AGEGTYVF

, in call Create sessions...Trying main loop again.... Sleeping for 3 seconds.Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: Error loading Presentation Catalog.

Error Codes: MTKA9QGD

Location: saw.subsystems.admin.initServiceInstance, saw.securitysubsystem.checkauthentication.runimpl, saw.securitysubsystem.checkauthentication, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

Error Codes:

Location: saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

.

Error Codes: AGEGTYVF

, in call Create sessionsTerminal Error: Exceeded number of retries.

Joel

Has the OBIEE Cluster ever worked properly? You may need to check that you have setup the Cluster correctly.

vai

Yes, the cluster works properly. I am able to open reports and other objects in the clustered environment.

Joel

Could you check the log files of the specific agent? They might provide some additional information. You can access these logs which are in the same location as the scheduler log file or alternatively you can access them via Job Manager. By the way, does this happen for all Agents?