Last updated on DECEMBER 22, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 6.0.0 [Release 4.3 to 6.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), an Oracle Database Management System (DBMS) job installed with the NCC/OC3C software can lock objects for an excessive duration resulting in unresponsive applications which are blocking waiting to access the locked object.
The DBMS job in question is the SMS_DEFRAG_REP_IOT job which is scheduled to run every 10s.
This job will check the REP_ORA_RENUMBERED and REP_ORA_EVENT Index Organized Tables (IOTs) and rebuild them if they are fragmented. This is to ensure the speed of replication remains consistently fast over time.
If this job fails to rebuild the IOTs for a long period of time (likely due to being unable to obtain a lock on the table), then the IOTs will become further fragmented. When the job does manage to get a lock on the table, it will spend significantly longer to rebuild the IOTs and lock them for longer, potentially affecting applications.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms