Losing Replication Updates with "ORA-20016: User's terminal is not defined." and "ORA-06512: at "SMF.SMF_SECURITY_INTL""

(Doc ID 1263407.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 09-Dec-2013***

Symptoms

Replication of updates from the SMS (Service Management Server) fails with the following errors, which may also be passed to an external alarm management system. These errors are seen in /var/adm/messages and /IN/service_packages/SMS/tmp/smsMaster.log on the SMS:

Nov 3 18:52:15 xxxx smsMaster: [ID 438867 user.warning] smsMaster(23069) WARNING OEXEC, OEXN=20016 oraUpdateLoader.c@480: ORA-20016: User's terminal is not defined.
Nov 3 18:52:15 xxxx ORA-06512: at "SMF.SMF_SECURITY_INTL", line 60
Nov 3 18:52:15 xxxx ORA-06512: at "SMF.ACS_CUSTOMER_SN_ABT", line 8
Nov 3 18:52:15 xxxx ORA-04088: error during execution of trigger 'SMF.ACS_CUSTOMER_SN_ABT'
Nov 3 18:52:15 xxxx smsMaster: [ID 839465 user.notice] smsMaster(23069) NOTICE: Update Lost: ACS_CUSTOMER_SN(ID):+00000000000000000000000000000000095614

 

Note that the database object and the nature of the update lost may be different from this example.


These sort of error on the replication node (not SMS) may also be an indication of the same problem:

May 26 14:59:32.042008 smsCompareResyncClient(3162) ERROR: OCI Error - (OCIAttrGet) Get Of Attribute Failed
May 26 14:59:32.043697 smsCompareResyncClient(3162) ERROR: Meta Data Extraction Error For Statement SELECT /*+ RULE */ ID, ACS_CUST_ID, BALANCE_TYPE, CREDIT_THRESHOLD, NAME, NEW_STATE, NOTIFICATION_TYPE, OLD_STATE, REFERENCE, SMS_TEMPLATE_ID, SUPPRESS_DAP_FIELD_TAG, SUPPRESS_SMS_FIELD_TAG, TEMPLATE, THRESHOLD, UNRESERVED_THRESHOLD, WALLET_TYPE FROM CCS_NOTIFICATION_DEF Likely reasons for this error is the table or column is not found for this user. Error was ORA-24338: statement handle not executed

 

Note: These errors are more likely to be caused by tables in the replication config that do not exist on the replication node.



The updateLoader log file on the replication node can also report ORA-20016/ORA-06512 errors:

ERR: Wed Dec 21 12:04:31 2011: Row 10 was not stored in the database properly because of the error: ORA-1, ORA-20016: User's terminal is not defined.
ORA-06512: at "SMF.SMF_SECURITY_INTL", line 60
ORA-06512: at "SMF.SMF_STATISTICS_DEFN_ABT", line 2
ORA-04088: error during execution of trigger 'SMF.SMF_STATISTICS_DEFN_ABT'



Services relying on the propagation of database updates via the replicationIF to the SMS may also be affected. This would include control plans that make use of the "Activate Call Plan" or "Copy" nodes. In this scenario these nodes will succeed because they have sent the update to the SMS, but it then fails to replicate back to the UAS nodes.

Other processes could report the same ORA-20016 error for the similar reasons but the impact may be different.



Changes

Installation of any NCC patch that changes packages, triggers and stored procedures within the SMS database.

OR

Changes have been made to SMS/etc/replication.def on one or more replication nodes.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms