dm_oracle.pinlog Contained "ERROR: Could not find the /data/sequence_lock"
Last updated on SEPTEMBER 15, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.1 to 220.127.116.11.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.
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):
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.
Data Archiving State
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