SRDC - SOAP Interface error RESPONSE Trouble Shooting Information for OCUDR

Asset ID:	1-75-2214070.1
Update Date:	2016-12-15
Keywords:

Solution Type Troubleshooting Sure

Solution 2214070.1 : SRDC - SOAP Interface error RESPONSE Trouble Shooting Information for OCUDR

Applies to:

Oracle Communications User Data Repository - Version UDR 10.0 and later
Tekelec

Purpose

This Document will help the Administrator/User of "Customer Provisioning System" to take Corrective action for error codes received in Provisioning RESPONSE over SOAP interface

Troubleshooting Steps

What are SOAP Provisioning Interface main Functions?

The SOAP provisioning interface provides following data manipulation commands:
Subscriber/Pool:

• Profile create/retrieve/modify/delete
• Profile field add/retrieve/modify/delete
• Opaque data create/retrieve/modify/delete
o Quota, State, and Dynamic Quota
• Subscriber transparent data create/retrieve/modify/delete
o Quota, State and Dynamic Quota
• Reset of a row within Subscriber Quota transparent data

How Many Maximum Simultaneous SOAP Connection Are Supported in OCUDR?

100

Additional References

For more information, reference the UDR SOAP Provisioning Interface Specification Document by selecting the appropriate release at the Oracle Help Center, Communications Industry, and then select User Data Repository. (http://docs.oracle.com/en/industries/communications/user-data-repository/index.html)

ERROR SCENARIOS

In Typical Scenario 'Customer Provisioning Server' Will Going to Send a SOAP REQUEST and based on SOAP Request ,RESPONSE is returned from OCUDR,if that RESPONSE contain the Following Errors ,Customer Can take Preventive Action so there Request can be Processed Successfully Without Any Error.

Example Error Scenario-1

Request #1 from CUSTOMER PROVISIONING SERVER ----->

A subscriber is created, with an AccountId, MSISDN and IMSI keys. Another subscriber already exists with the given IMSI.

Response #1 from OCUDR <--------

The request fails. The error value indicates a subscriber already exists with the given IMSI, and the affected rows are 0.

<req name="insert" resonly="y">
<res error="70020" affected="0"/>
</req>

70020:Key Already Exists. A subscriber/pool already exists with the given key

Corrective Action : Resend the Request from "Customer Provisioning System" by changing the value of IMSI or delete the IMSI profile in OCUDR and resend the Request from CPS

Example Error Scenario-2

Request #2 from CUSTOMER PROVISIONING SERVER ---->

A request is made to create a data row in the QuotaEntity (Quota) data. The data row identifier field is name, and the value is Q3. The odk attribute is included requesting the data row be updated if it already exists. Two rows with the name of Q3 already exist in the Quota data. The request is not required in the response

<req name="insert" resonly="y" odk="yes">
<ent name="QuotaEntity"/>
<set>
<expr><attr name="MSISDN"/><value val="33123654862"/></expr>
<expr><attr name="name"/><value val="Q3"/></expr>
<expr><attr name="cid"/><value val="922337203685477777"/></expr>
<expr><attr name="time"/><value val="10:10"/></expr>
<expr><attr name="totalVolume"/><value val="55000"/></expr>
<expr><attr name="inputVolume"/><value val="50000"/></expr>
<expr><attr name="outputVolume"/><value val="5000"/></expr>
<expr><attr name="serviceSpecific"/><value val="serviceSpecific"/></expr>
<expr><attr name="nextResetTime"/>
<value val="1961-12-15T09:04:03"/></expr>
</set>
</req>

Response #2 from OCUDR <--------

The request fails. The error value indicates that multiple existing rows are found (i.e. more than one row has a name of Q3, and hence it is not possible to know which of the two rows to update), and the affected rows are 0. The original request is not included.

<req name="insert" resonly="y">
<res error="70035" affected="0"/>
</req>

70035:Multiple rows match the given criteria. When updating a row, only one row can exist that match the given row criteria

Corrective Action : Resend the Request from "Customer Provisioning System" after deleting the Row Q3 from OCUDR Database or Change the Row name from Q3 to Some other value.

SOAP Error Code Description

Error Codes:SOAP error codes are returned by the SOAP interface in the error attribute parameter of the <res> message The error parameter of a response message indicates the success or failure of a request.
The complete set of response error codes and their associated values are defined in the following table.
The “Type” column indicates if an error is permanent (“P”) or temporary (“T”), or indicates success (“S”). A request that results in a permanent error should be discarded and not sent again. A request that results in a temporary can be sent again at a different time, and may be successful.
Error codes that are marked with a “*” are permanent errors that can be fixed by means of configuration, such as configuring the entities/fields in the SEC etc.

^{Error Code}	^Value	^Type	^Description
NOT_PROCESSED	1	P	Not processed. The request was within a block transaction, and was not processed due to an error with another request within the same block transaction
INTF_ENTY_NOT_FOUND	70000	P*	Interface Entity Not Found
ENTY_DEF_NOT_FOUND	70002	P	Entity Definition Not Found
VER_BFS_NOT_FOUND	70003	P	Versioned Base Field Set for the Transparent Entity Not Found
NON_VER_BFS_NOT_FOUND	70004	P	Non Versioned Base Field Set for the Transparent Entity Not Found
MULT_VER_TAGS_FOUND	70005	P	Multiple Version Tags Found
FIELD_VAL_INVALID	70006	P*	Field Value Not Valid. The value for a given field is not valid based on the definition in the SEC
OCC_CONSTR_VIOLATION	70007	P*	Occurrence Constraint Violation. There are too many instances of a given field. Likely more than one instance of a non-repeatable field
INVAL_REPEATABLE_ELEM	70008	P	Invalid Repeatable Element
INVALID_XML	70009	P	Invalid Input XML
FLD_SET_NOT_FOUND	70010	P	Field Set Not Found
FLD_SET_EXISTS	70011	P	Field Set Already Exists
FIELD_NOT_FOUND	70012	P	Field Not Found
FIELD_EXISTS	70013	P	Field Already Exists
FLD_SET_UNDEFINED	70014	P	Field Set Not Defined
FIELD_UNDEFINED	70015	P	Field Not Defined. The given field is not a valid field within the entity as defined in the SEC
FIELD_NOT_UPDATABLE	70016	P	Field Cannot be Updated. The field is defined in the SEC as not be updatable
ENT_CANNOT_RESET	70017	P	Entity Cannot be Reset. The reset command cannot be used on the requested entity
DB_OPER_FAILED	70018	P	Database Operation Failed
KEY_NOT_FOUND	70019	P	Key Not Found. A subscriber/pool with the given key cannot be found
KEY_EXISTS	70020	P	Key Already Exists. A subscriber/pool already exists with the given key
SUB_IN_POOL	70021	P	Subscriber is Pool Member. The subscriber is a member of a pool. A subscriber cannot be deleted if they are a pool member
HAS_POOL_MEMBERS	70022	P	Has Pool Members. A pool cannot be deleted when it has member subscribers
ALREADY_POOL_MEMBER	70023	P	Already a Pool Member. The subscriber is already a member of a pool
NOT_POOL_MEMBER	70025	P	Not A Pool Member
OPER_NOT_ALLOWED	70026	P	Operation Not Allowed
REG_DATA_NOT_FOUND	70027	P	Register Data Not Found
REG_EXISTS	70028	P	This error code is utilized for two scenarios: 1) Register Already Exists 2) A property already exists and the “odk” flag was not set to indicate the insert request be converted to an update.
UNEXPECTED_ERROR	70029	P	Un-Expected Error
INV_SOAP_XML	70030	P	Invalid SOAP XML
SERVICE_UNAVAILABLE	70031	T	Service is unavailable. Provisioning has been disabled
ROW_NOT_FOUND	70032	P	Data row specified is not found
VALUE_EXISTS	70033	P	List value added already exists
FLD_NOT_MULTI	70034	P	Field is not a multi-value field. Add and remove from list operations can only be performed on a multi-value field, and the field supplied is not multi-value
MULTIPLE_ROWS_FOUND	70035	P	Multiple rows match the given criteria. When updating a row, only one row can exist that match the given row criteria
POOL_NOT_FOUND	70036	P	Pool does not exist. A subscriber cannot be added, retrieved or removed from a pool that does not exist
INVALID_KEY_VALUE	70037	P	The key value supplied is invalid, due to invalid characters/format etc.
DB_RETRY_EXHAUSTED	70038	T	Data could not be committed to database as the total number of retries to commit database transactions exhausted. NOTE: The client shall retry the command again
DURABILITY_DEGRADED	70039	T	Data could not be committed as Durability is degraded. NOTE: The client shall retry the command again
DURABILITY_TIMEOUT	70040	T	Data could not be made durable within the configured Durability Timeout. NOTE: The client shall retry the command again to get the data sent in the failed request to verify that it was stored by last request
TOO_BIG_MESSAGE	70041	P	The provisioning request size exceeded the maximum allowed size
MEMORY_FULL	70042	P	Free system memory is low. Request cannot be performed
MULTIPLE_KEYS_NOT_MATCH	70043	P	Multiple keys supplied do not refer to the same subscriber
ONE_KEY_REQUIRED	70044	P	At least one key is required for a subscriber
SYSTEM_CONGESTION	70045	T	Request rejected due to system congestion
CONNECTION_ERROR	70046	P	Request to be sent to different UDR instance could not be sent because no valid connection is available to send the request on

COMMAND LOGS

REST Request/Response Can be viewed in OCUDR system after login into NO VIP GUI

Navigate to UDR->Maintenace->Command Log

they Can also be Exported to External Export Server if Configured in OCUDR

Attachments

This solution has no attachment