Troubleshooting
Problem
Users of IBM Maximo Application Suite might see an error when they run Maximo Application Suite on Amazon Relational Database Service (RDS) Oracle system.
The error can be replicated using the following process:
1. Install IBM Maximo Application Suite on an Amazon RDS Oracle system.
2. Open any Internet browser and enter the following URL:
<mas servername>/maximo/api/members/thisserver/pingdb
Note: In the URL, <mas servername> is the server address that you are using.
The MAS logs display the following error:
ping db connection error -- ORA-00942: table or view does not exist
Symptom
When you check Maximo Application Suite logs by using the RedHad OpenShift web console, the pingDB call generates a series of log messages like the following:
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [ERROR] [MXServer] [CID-MXOSLC-160318] ping db connection error -- ORA-00942: table or view does not exist
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [INFO] [MXServer] [CID-MXOSLC-160318] Correlation started, correlation data added: ResponseResourceSize:2
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [INFO] [MXServer] [CID-MXOSLC-160318] Correlation started, correlation data added: ResponseResourceSize:2 SendResponseTime:0
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [INFO] [MXServer] [CID-MXOSLC-160318] Correlation started, correlation data added: ResponseResourceSize:2 RequestURI:/maximo/api/members/thisserver/pingdb SendResponseTime:0 I have looked at the Logging configuration and it is calling this piece of code: com.ibm.tivoli.maximo.oslc.provider.bus.PingDBRouteHandler
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [ERROR] [MXServer] [CID-MXOSLC-160318] ping db connection error -- ORA-00942: table or view does not exist
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [INFO] [MXServer] [CID-MXOSLC-160318] Correlation started, correlation data added: ResponseResourceSize:2
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [INFO] [MXServer] [CID-MXOSLC-160318] Correlation started, correlation data added: ResponseResourceSize:2 SendResponseTime:0
[7/6/23 7:49:43:217 BST] 000015cc SystemOut O 06 Jul 2023 07:49:43:217 [INFO] [MXServer] [CID-MXOSLC-160318] Correlation started, correlation data added: ResponseResourceSize:2 RequestURI:/maximo/api/members/thisserver/pingdb SendResponseTime:0 I have looked at the Logging configuration and it is calling this piece of code: com.ibm.tivoli.maximo.oslc.provider.bus.PingDBRouteHandler
Cause
Issue 1:
The V$ACTIVE_SESSION_HISTORY view is invalid for Oracle databases that are hosted by using the AWS RDS technology.
Issue 2:
The standard Maximo Application Suite installation does not grant access to the following views by default:
v$sqlstats
V$ACTIVE_SESSION_HISTORY
The V$ACTIVE_SESSION_HISTORY view is invalid for Oracle databases that are hosted by using the AWS RDS technology.
Issue 2:
The standard Maximo Application Suite installation does not grant access to the following views by default:
v$sqlstats
V$ACTIVE_SESSION_HISTORY
Environment
The error only occurs on Amazon RDS (Relational Database Service) Oracle system.
Resolving The Problem
Resolve the problem by following the steps:
- Create a public synonym to map the V$ACTIVE_SESSION_HISTORY view to the V_$ACTIVE_SESSION_HISTORY.
- Grant explicit access to the following views:
- v$sqlstats
- grant select on V$ACTIVE_SESSION_HISTORY to the Maximo user
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite-\u003EMAS Applications-\u003EManage"}],"ARM Case Number":"TS013541892","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
16 August 2023
UID
ibm17023172