IJ36469: DB CONNECTION TIMEOUTS - DBMANAGER CODE DOES NOT WORK CORRECTLY WITH ORACLE RAC

APAR status

• Closed as program error.

Error description

• When the customer has the 3 nodes active in the cluster oracle
  RAC on Exadata, he sees many errors BMXAA6713E - The MBO fetch
  operation failed in the mboset with the SQL error code 17008
  And the Maximo server becomes slow and stops responding.
  
  
  DBManager identify if this is Oracle RAC (Real Application
  Clusters) or not by the following lines of code:
  
  ----------------------------------
  
  				dbProductVersion =
  con.getMetaData().getDatabaseProductVersion();
  
  
  
  				if (dbProductName.toUpperCase().indexOf("ORACLE") >= 0)
  
  				{
  
  					dbPlatform = UpgConstants.ORACLE;
  
  					if (dbProductVersion.indexOf("Real Application Clusters")
  >= 0)
  
  						isRAC = true;
  
  				}
  
  --------------------------------
  
  It seems we do need an additional or different approach to check
  if this is oracle instance is part of a RAC.
  
  The most adequate option is using  recommendation: select name,
  value from v$parameter where name='cluster_database';
  
  
  However, this will impact all maximo clients as it would require
  an additional SELECT permission granted to maximo schema owner
  on V$PARAMETER table.
  
  As the existing Java core method that obtain the database
  information does not return sufficient information to identify
  Oracle RAC, this will be fixed through introducing a new MAXIMO
  property to identify the database as an Oracle RAC. The client
  will have to set this new property to true/ 1 and the code will
  be modified to proceed based on its value.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When maximo application is deployed on an Oracle database,   *
  * maximo identifies whether the database is a standalone or an *
  * Oracle Real Application Clusters (RAC) based on a standard   *
  * Java method. However, this method may not be able to provide *
  * sufficient information for identification resulting in       *
  * additional database connections not being released at the    *
  * database level.                                              *
  ****************************************************************
  

Problem conclusion

• A new maximo property "mxe.db.isOracleRAC" has been introduced
  for identifying Oracle Real Application Clusters(RAC)
  deployment. If the property is set to its default value (0),
  maximo will manage the database sessions based on a non RAC
  database. On the other hand, if the property value is set to 1,
  maximo will manage the database sessions based on the database
  being deployed as an Oracle RAC. NOTE, maximo schema owner needs
  to be granted access to V$SESSION in an Oracle non RAC
  environment and both V$SESSION and GV$SESSION for Oracle RAC
  environment.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels