A PDBI Message Error Codes
This chapter lists the PDBI error codes and text.
PDBI Message Error Codes
Table A-1 lists the error codes, associated text generated by the PDBI, and recommended actions.
Table A-1 PDBI Message Error Codes
| Error Code | Text | Recommended Action |
|---|---|---|
|
0 |
PDBI_SUCCESS =0 |
No action necessary. This indicates a successful response from the PDBA. |
|
1001 |
PDBI_INTERNAL_ERROR = 1001 |
Contact Oracle. |
|
1002 |
PDBI_NOT_CONNECTED |
Establish an active connection before re-issuing this command. |
|
1003 |
PDBI_ALREADY_CONNECTED |
No action necessary. This is a redundant connection attempt. |
|
1004 |
PDBI_PARSE_FAILED |
Refer to the data section of the return message to determine the cause of the parse failure. |
|
1005 |
PDBI_WRITE_UNAVAIL |
Wait for write transaction to close before re-attempting this command. |
|
1006 |
PDBI_NO_WRITE_PERMISSION |
No action is necessary unless the IP address of this PDBI client should have WRITE access permissions. If that is the case, add WRITE permissions for the IP address of the PDBI client. |
|
1007 |
PDBI_NO_MATE |
Contact Oracle. This indicates that the Active PDB has lost contact with Standby. |
|
1008 |
PDBI_STANDBY_SIDE |
Connect to the Active PDBA for write operations. |
|
1009 |
PDBI_NO_ACTIVE_TXN |
Open a write transaction before retrying this command |
|
1010 |
PDBI_ACTIVE_TXN |
Wait for the transaction to complete before re-attempting the switchover. |
|
1011 |
PDBI_WRITE_IN_READ_TXN |
Reattempt this command after the read transaction is terminated and a write transaction is opened. |
|
1012 |
PDBI_INVALID_VALUE |
Re-enter the command using the correct value in the offending field returned in the data section. |
|
1013 |
PDBI_NOT_FOUND |
This error is dependent on the contents of the database. No action is required, unless it is known that the item in question should be in the database. If this is the case, contact Oracle. |
|
1014 |
PDBI_CONFLICT_FOUND |
Using the force parameter can override this check and eliminate the return of this error code for certain commands. |
|
1015 |
PDBI_ITEM_EXISTS |
No action necessary. The PDB already has the requested entry in the database. |
|
1016 |
PDBI_PARTIAL_SUCCESS |
No action necessary. This error indicates that more messages are to follow. PDBI_SUCCESS will be returned to indicate the last message has been sent. |
|
1017 |
PDBI_NO_UPDATES |
No action necessary. The PDB already has the requested entry in the database. |
|
1019 |
PDBI_BAD_ARGS |
There is a problem with the syntax of the command. Refer to the data section of the response message to determine what problem was encountered. |
|
1020 |
PDBI_TOO_MANY_CONNECTIONS |
One of the PDBI connections needs to be terminated before this client can gain a connection. |
|
1021 |
PDBI_NE_NOT_FOUND |
No action required unless it is known that the NE in question is/should be in the database. If that is the case, please contact Oracle. |
|
1022 |
PDBI_CONTAINS_SUBS |
To delete the NE in question, all subscription data must be removed from the NE. |
|
1023 |
PDBI_UNKNOWN_VERSION |
Use the correct version on the connect message. |
|
1025 |
PDBI_UNIMPLEMENTED |
Contact Oracle. |
|
1026 |
PDBI_MATE_BUSY |
Retry command checking to see if mate releases write transaction. |
|
1027 |
PDBI_IMSI_DN_LIMIT |
EPAP only supports assigning a maximum of 8 DNs to a single IMSI |
|
1028 |
PDBI_BAD_IMPORT_CMD |
Wrong command is written in the import file. Remove unsupported commands and try again. |
|
1029 |
PDBI_TXN_TOO_BIG |
Reduce the transaction size. |
|
1030 |
PDBI_DB_MAINT_REQD |
Contact Oracle |
|
1031 |
PDBI_DB_EXCEPTION |
The client program should retry the transaction. If the error persists, contact Oracle. |
|
1032 |
PDBI_MAX_IMSI_LIMIT |
Contact Oracle. Database capacity for IMSIs has been reached. |
|
1033 |
PDBI_MAX_DN_LIMIT |
Contact Oracle. Database capacity for DNs has been reached.. |
|
1034 |
PDBI_MAX_DNBLK_LIMIT | Contact Oracle. Database capacity for DN BLOCKs has been reached. |
|
1035 |
PDBI_MAX_NE_LIMIT | Contact Oracle. Database capacity for NEs has been reached. |
|
1036 |
PDBI_REPLICATING | Do not attempt the switchover until the replication is complete. |
|
1037 |
PDBI_CHECK_DIGIT_ERROR | The check digit must provided by the Customers Client Software does not match the EPAPs (via calculated algorithm). |
|
1038 |
PDBI_IMSI_NOT_FOUND | No action necessary. |
|
1039 |
PDBI_IMEI_IMSI_LIMIT | Limit has been reached. EPAP only supports assigning a maximum of 8 IMSIs to a single IMEI. |
|
1040 |
PDBI_MAX_IMEI_LIMIT | Contact Oracle. Database capacity for IMEIs has been reached. |
|
1041 |
PDBI_MAX_IMEI_BLK_LIMIT | Contact Oracle. Database capacity for IMEI BLKs has been reached. |
|
1042 |
PDBI_NO_LIST_FOR_IMEI | Provision at least one list type for IMEI object. Each IMEI object must have a list type attached. |
|
1043 |
PDBI_BAD_SWITCH_IN_APB | The PDBA status is controlled by the PDBA Proxy feature and cannot be changed manually. Call Oracle for more information. |
|
1044 |
PDBI_SUB_NE_LIMIT | Limit has been reached. DN or DN Block can have a maximum of 2 NE associations. |
|
1045 |
PDBI_CMD_LENGTH_EXCEEDED | Command length exceeded 247 characters. Remove unnecessary characters (including white space and parameters that are specified as the default value) or perform provisioning in two steps by using an enter command followed by an update command. |
|
1046 |
PDBI_MAX_ASD_LIMIT | Contact Oracle. Database capacity for ASD records has been reached. |
|
1047 |
PDBI_DN_NOT_FOUND | The DN specified by nsdn does not exist. |
|
1048 |
PDBI_MAX_ASSOCIATIONS | This request contains too many associations for a DN or DN Block. The error is raised when TIF Number Substitution is combined with other associations and distinct from SUB_NE_LIMIT. |
|
1049 |
PDBI_UNRESOLVED_DEPENDENCY | The record already refers to another record through TIF Number Substitution. The NSDN must be updated to none before a new association can be formed. |
|
1050 |
PDBI_INCOMPATIBLE_ST | The specified ST value conflicts with the ST value of NSDN. |
|
1051 |
PDBI_INCOMPATIBLE_ROP | The GRN ROP value conflicts with the GMT value for the specified ASD. |
|
1052 |
PDBI_DNB_SAME_PROPERTIES | The new DN Block requested by the operator is a subset of an existing block with same properties. |
|
1053 |
PDBI_MULTI_DNB_CONFLICT | The new DN Block could not be added to the database as multiple conflicting DN Blocks were found within given bdn-edn. |
|
1054 |
PDBI_DNB_SPLIT_NOT_ALLOWED | The new DN Block tries to split an existing DN Block that is not allowed to be split or a new individual DN is entered within an existing DN Block that is not allowed to be split. |
|
1055 |
PDBI_DNB_PARENT_PROPERTY
_MISMATCH |
Fragments of a master range have differing attributes. No automated resolution is possible to coalesce these records to satisfy a delete command. |
|
1056 |
PDBI_DNB_DLT_NOT_ALLOWED | Fragments of a master range cannot be deleted while subranges are present. |
|
1057 |
PDBI_TXN_TIMEOUT | Retry command checking to see if the write transaction does not timeout. Contact Oracle. |
|
1058 |
PDBI_IMSI_FULL | Cannot add new IMSI to the database. Adding new IMSI would exceed the supported SMxG card size. Contact Oracle. |
|
1059 |
PDBI_IMEI_FULL | Cannot add new IMEI to the database. Adding new IMEI would exceed the supported SMxG card size. Contact Oracle. |
|
1060 |
PDBI_DN_FULL | Cannot add new DN to the database. Adding new DN would exceed the supported SMxG card size. Contact Oracle. |
|
1061 |
PDBI_ASD_FULL | Cannot add new ASD to the database. Adding new ASD would exceed the supported SMxG card size. Contact Oracle. |
|
1062 |
PDBI_IMSI_ENT_NOT_ALLOWED | The RTDB is either down or incoherent. Contact Oracle. |
|
1063 |
PDBI_IMEI_ENT_NOT_ALLOWED | The RTDB is either down or incoherent. Contact Oracle. |