Updates Are Not Sent and Accumulated in Replication Tables with Reported Error "ORA-12012, PLS-00904" in Oracle Alert Logs
(Doc ID 1390937.1)
Last updated on OCTOBER 25, 2024
Applies to:
Oracle Communications Network Charging and Control - Version 3.1.0 and laterInformation in this document applies to any platform.
Symptoms
Replication updates are accumulating in the replication tables on the SMS (Service Management System) and are not sent to the replication clients, the SLCs (Service Logic Controllers) and the VWSs (Voucher and Wallet Servers).
Things to check:
1- Replication Tables:
rep_ora_event (Stores the new incoming replication events , waiting to be processed by their results)
rep_pending_queue (Contains a reference to the last event_id sent to every replication node)
rep_ora_renumbered (Contains the renumbered replication updates to be sent to the replication nodes)
Node_ID : Represent the ID of the replication node like (SLC,VWS). Table rep_cfn_node contains details information about the replication client's nodes.
ROE_EVENTID : Represent the last event_id was sent successfully to the replication node.
For more information about "Replication Table", please refer to SMS Technical Guide / Chapter 2/Section: Replication Overview. See <Document 1341844.1> for how to download documentation.
These commands should be run from the SMS. If the SMS is a cluster, run these commands from any of the nodes in the cluster:
Changes
The following or similar changes may be the cause of this problem:
1-Any manual modification of the Oracle Database replication JOBs during the initial setup or during any maintenance or optimization.
2-The installation of any patch modifying these Oracle Database JOBs, or require to manually modify these JOBs as a post-installation task.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Things to check: |
1- Replication Tables: |
2- Oracle alert logs: |
Changes |
Cause |
Replication Database- Brief Explanation |
Root Cause: |
Solution |
References |