dm_oracle.pinlog Contained "ERROR: Could not find the /data/sequence_lock"

(Doc ID 763154.1)

Last updated on SEPTEMBER 15, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 6.7.0.0.1 to 6.7.0.0.1 [Release 6.7.0]
Information in this document applies to any platform.
***Checked for relevance on 07-Feb-2014***
Checked for relevance on 09-Feb-2016.
Checked for relevance on 15-Sep-2017.

Goal

After upgraded from Infranet 6.7 FP1 to BRM 7.3.1, the following error got recorded in the dm_oracle.pinlog when trying to create an account (although this may not actually prevent account creation):

W Fri Dec 05 22:09:31 2008 xxxxxxx dm:25356 dm_subr.c(116):1007 1:xxxxxxx:cm:25398:1:9:1228514971:1
ORACLE error: get_new_poid_id_range: PINStmtExecute: code 20016, op 0
=ORA-20016: ERROR: Could not allocate a new poid id range - i_quantity: 1000 i_pad_range: 1
ORA-06512: at "PIN.PIN_SEQUENCE", line 612
ORA-20001: ERROR: Could not find the /data/sequence_lock object with name: POID_IDS2
ORA-06512: at "PIN.PIN_SEQUENCE", line 263
ORA-01403: no data found
ORA-06512: at line 1

The following query showed which NAME values were present in the DATA_T table.

SQL> select distinct name from data_t order by name;
NAME
----------------------------
Data Archiving State
PIN_SEQUENCE_TYPE_ACCOUNT
PIN_SEQUENCE_TYPE_ADJUSTMENT
PIN_SEQUENCE_TYPE_BILL_NO
PIN_SEQUENCE_TYPE_DISPUTE
PIN_SEQUENCE_TYPE_FIAS_ID
PIN_SEQUENCE_TYPE_PACKAGE_ID
PIN_SEQUENCE_TYPE_PAYMENT
PIN_SEQUENCE_TYPE_REFUND
PIN_SEQUENCE_TYPE_SETTLEMENT
PIN_SEQUENCE_TYPE_TRANS_ID
PIN_SEQUENCE_TYPE_WRITEOFF
billing transid
reg loginid
top DATA

 

Solution

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