7 HTTP Error Codes

NEF generates HTTP error codes in case of any request failure over Service Based Interface (SBI). The error descriptions contains the possible reason of the failure to facilitate proper troubleshooting.

The error description is provided in JSON format for the HTTP (POST/GET/DELETE) requests. The error code format is defined as follows:

OCNEF-<Service Name>-<Error Description>-<HTTP Response Code>-<Problem Code>

where,
  • <Service Name>: Specifies the name of the service that generates the error code.
  • <Error Description>: The reason or cause for the error.
  • <HTTP Response Code>: The HTTP Status Code for the error.
  • <Problem Code>: NEF defined 4 digit code for the error.

The following table describes each error code to help you understand why the error occurred and to provide a recovery procedure to help correct the condition that caused the error:

Table 7-1 HTTP Error Codes Supported on Service Based Interface (SBI)

Error Code Description Recovery Procedure
HTTP Response Code: 400 BAD_REQUEST
OCNEF-<svc_name>-<error>-400-1000 The value is not supported the for field: <fieldName>. Verify the parameter specifications for the request and provide a supported value to retry the operation.
OCNEF-<service name>-<error>-400-1001 The mandatory field is missing from the request body: <fieldName>. Verify the request specifications and provide the missing mandatory value to retry the operation.
OCNEF-<svc_name>-<error>-400-1002 Validation failed for the field with validation details: <fieldName> Update the field value as per the validation error and retry the operation.
OCNEF-<svc_name>-<error>-400-1003 Could not convert request JSON into valid object Verify the JSON format of the request and retry the operation.
OCNEF-<svc_name>-<error>-400-1004 Internal header parameter missing: <Parameter name> Contact My Oracle Support.
OCNEF-<svc_name>-<error>-400-1005 Duplicate Error : <Field details> Provide a unique value and retry the operation.
OCNEF-<svc_name>-<error>-400-1006 Message translation error Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-400-1007 Communication profile not found Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-400-1008 Empty Security method Contact My Oracle Support in case the issue persists.
HTTP Response Code: 404 NOT_FOUND
OCNEF-<svc_name>-<error>-404-1501 The record not available in OCNEF. Possible errors:
  • Subscription not found
  • Invoker not found
  • Group Id not found
 Verify the relevant value in the system. Contact My Oracle Support in case the issue persists.
HTTP Response Code: 401 UNAUTHORIZED
OCNEF-<svc_name>-<error>-401-1601 Possible errors:
  • Invoker onboarding related errors
  • Invalid Token
  • Invalid Invoker name
  • Mismatch between global capif configuration parameter "capifApiPrefix" and global nef configuration parameter "capifDetails.apiPrefix"
 Verify the relevant values in the system.
500 INTERNAL_SERVER_ERROR
OCNEF-<svc_name>-<error>-500-1701 Connectivity issue between NEF and UDM/GMLC Verify the connectivity between OCNEF and UDM/GMLC. Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-500-1702 Connectivity issue between Monitoring Event (ME) and 5GCAgent services Verify the connectivity between the ME service and 5GC Agent service. Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-500-1703 Connectivity issue between EG and ME services Verify the connectivity between the EG and ME service. Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-500-1704 Model D JSON to Object conversion error Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-500-1705 ME Subscription Service JSON to object conversion error Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-500-1706 NEF to Core connectivity failure using NRF Discovery Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-500-1707 Invalid communication model configuration Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-500-1708 Error during the following conversions:
  • QOS Service JSON to object conversion
  • Object to JSON conversion
 Contact My Oracle Support in case the issue persists.
HTTP Response Code: 503 SERVICE_UNAVAILABLE
OCNEF-<svc_name>-<error>-503-1801 Connectivity issue between NEF and the 5G core network Check the connectivity. Contact My Oracle Support in case the issue persists.
OCNEF-<svc_name>-<error>-503-1802 Connectivity issue between EG and ME services Verify the connectivity between the EG and ME service. Contact My Oracle Support in case the issue persists.
HTTP Response Code: 501 NOT_IMPLEMENTED
OCNEF-<svc_name>-<error>-501-1901 Method not supported : <Method Name> The requested HTTP Method not supported in the current release.
Diameter Error Code: 503 SERVICE_UNAVAILABLE
DIAMETER_INVALID_AVP_VALUE-5004 If scef-reference-id passed from MME is not found at ME end. Verify if scef-reference-id passed from MME is the correct one belonging to ME subscription.
DIAMETER_UNABLE_TO_COMPLY-5012 If there is Code Exception or Database is down or there is a Network Issue. Contact My Oracle Support in case the issue persists.