APAR status
Closed as program error.
Error description
Maximo's DBManager class which handles user's session does not consider looking at GV$SESSION when killing long running connections, instead only looks at V$SESSION. STEPS TO REPRODUCE: -------------------------- Our customers use Oracle RAC as their distributed database and per the RAC's architecture, all the RAC participant users information is stored in GV$SESSION which has a special column INST_ID (Instance ID) which refers to the instance number from which the information comes from.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * All Maximo Usres * **************************************************************** * PROBLEM DESCRIPTION: * * Long running connections not closing inactive gv$session. * **************************************************************** * RECOMMENDATION: * * Upgrade to latest release. * **************************************************************** Maximo's DBManager class which handles user's session does not consider looking at GV$SESSION when killing long running connections, instead only looks at V$SESSION. STEPS TO REPRODUCE: -------------------------- Our customers use Oracle RAC as their distributed database and per the RAC's architecture, all the RAC participant users information is stored in GV$SESSION which has a special column INST_ID (Instance ID) which refers to the instance number from which the information comes from.
Problem conclusion
The gv$session table is used to check for long running connections for Oracle Real Application Cluster. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Fix Pack Release 7.5.0.8 TPAE
Temporary fix
Comments
APAR Information
APAR number
IV68045
Reported component name
SYSTEM CONFIG
Reported component ID
5724R46S1
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-12-18
Closed date
2015-01-28
Last modified date
2024-10-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
MAXIMO
Fix information
Fixed component name
SYSTEM CONFIG
Fixed component ID
5724R46S1
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 October 2024