MSR4099 ErrorXmlCaughtByParser Error Observed In Failed Provisioning Requests

Asset ID:	1-71-2126675.1
Update Date:	2018-05-06
Keywords:

Solution Type Technical Instruction Sure

Solution 2126675.1 : MSR4099 ErrorXmlCaughtByParser Error Observed In Failed Provisioning Requests

Applies to:

Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.3 and later
Tekelec

Goal

Provisioning errors <error code="MSR4099">ErrorXmlCaughtByParser</error> reported while provisioning in SPR

[root@xxx]# curl -X GET http://10.132.61.27:8787/rs/msr/sub/MSISDN/+33659899013
<?xml version="1.0" encoding="UTF-8"?>
<error code="MSR4099">ErrorXmlCaughtByParser</error>

Solution

WebCI/BlueCli on both the blades was not accessible. It was reporting following error :-

----------

[root@xxx ~]# BlueCli -u admin
BlueCli Copyright (C) 2010, 2013, Oracle and/or its affiliates. All rights reserved.
Version:
Build: 0

Invalid Reply from the OampManager
Error: Failed to connect to the Oamp Manager

-----------

Further investigation revealed that DAS(DataAccessServer) process was cored in spr during that time.Tried to restart DataAccessServer and Oamp manager process in SPR active backend blade but it didn’t helped. Patch level found on system was 9.3.1 patch 9.

Problem was resolved after restarting blue service on both BE blades.
After analyzing the core dump and DAS code, it was found that core was generated due to memory corruption caused by issue fixed in 9.3.1 patch 10.

References

<BUG:21777581> - DAS RESTARTING SEVERAL TIMES - NO PROVISIONING POSSIBLE

Attachments

This solution has no attachment