Legacy ID:KA426129
Cause
The cmapolicymigration tool will print in the command prompt the policies which exported successfully, but if a problem is found with one of the policies the export process will stop creating the output export policy files, and no reference to the policy name will be given (RFE QM001879925 has been created to improve this) in the screen, only in datamigrator.log file will be seen errors as below:
+++
INFO 11 May 2015 15:17:478161 [main] com.bmc.sas.dm.wsclient.PolicyWebserviceHelper BMC_DM8I Retrieving policy with id : 5b60ae2e-b8de-4eb9-938c-41e2d90e134d
DEBUG 11 May 2015 15:17:478161 [main] com.bmc.sas.dm.wsclient.BPPMClientWrapper Invoking operation unifiedadmin/Policy/5b60ae2e-b8de-4eb9-938c-41e2d90e134d/list HTTP Request GET
DEBUG 11 May 2015 15:17:478161 [main] com.bmc.sas.dm.wsclient.BPPMClientWrapper request params :idType=id
DEBUG 11 May 2015 15:17:478161 [main] com.bmc.sas.dm.wsclient.BPPMClientWrapper body :null URL: unifiedadmin/Policy/5b60ae2e-b8de-4eb9-938c-41e2d90e134d/list
ERROR 11 May 2015 15:17:489174 [main] com.bmc.sas.dm.wsclient.BPPMClientWrapper BMC_DM6E Exception:Error while executing web service request with URL unifiedadmin/Policy/5b60ae2e-b8de-4eb9-938c-41e2d90e134d/list
com.bmc.bppm.wsclient.exception.ServerException: Call to Server failed : Response Status: 500 Message returned from server: rO0ABXNyACxjb20uYm1jLnNtcy53c2NvbW1vbi5jbGllbnQuQ2xpZW50UmVzcG9uc2VUTwAAAAAAAAABAgAHSgARcmVzcG9uc2VUaW1lU3RhbXBMAAxlcnJvck1lc3NhZ2V0ABJMamF2YS9sYW5nL1N0cmluZztMAAZlcnJvcnN0ABBMamF2YS91dGlsL0xpc3Q7TAAKc3RhdHVzQ29kZXEAfgABTAALc3RhdHVzQ29kZXNxAH4AAkwADnN0YXR1c01lc3NhZ2VzcQB+AAJMAAlzdGF0dXNNc2dxAH4AAXhwAAABTUKx85Bwc3IAE2phdmEudXRpbC5BcnJheUxpc3R4gdIdmcdhnQMAAUkABHNpemV4cAAAAAF3BAAAAAF0AEdGYWlsZWQgdG8gcmV0cmlldmUgUG9saWN5IHdpdGggSUQ6IDViNjBhZTJlLWI4ZGUtNGViOS05MzhjLTQxZTJkOTBlMTM0ZHh0AA5CUFBNLUNNQTUwMDAxRXBwdAALQmFkIFJlcXVlc3Q=
at com.bmc.bppm.wsclient.impl.BPPMServerConnUsingSAPService.executeRequest(BPPMServerConnUsingSAPService.java:607)
at com.bmc.bppm.wsclient.impl.BPPMServerConnUsingSAPService.executeGetService(BPPMServerConnUsingSAPService.java:138)
at com.bmc.sas.dm.wsclient.BPPMClientWrapper.executeRequest(BPPMClientWrapper.java:184)
at com.bmc.sas.dm.wsclient.BPPMClientWrapper.invokeOperation(BPPMClientWrapper.java:156)
at com.bmc.sas.dm.wsclient.PolicyWebserviceHelper.getPolicy(PolicyWebserviceHelper.java:43)
at com.bmc.sas.dm.exporter.PolicyDataExporter.exportData(PolicyDataExporter.java:42)
at com.bmc.sas.dm.PEExporter.export(PEExporter.java:59)
at com.bmc.sas.dm.exporter.PolicyEngineExporter.exportPolicies(PolicyEngineExporter.java:60)
at com.bmc.sas.dm.exporter.PolicyEngineExporter.exportAllData(PolicyEngineExporter.java:55)
at com.bmc.sas.dm.CmdDataMigration.execute(CmdDataMigration.java:302)
at com.bmc.sas.dm.CmdDataMigration.main(CmdDataMigration.java:117)
ERROR 11 May 2015 15:17:489176 [main] com.bmc.sas.dm.PEExporter ERROR_IN_EXPORTING_DATA Error in exporting data null
com.bmc.sas.dm.ImportExportException: Exception while communicating with WS:Error while executing request
at com.bmc.sas.dm.wsclient.BPPMClientWrapper.invokeOperation(BPPMClientWrapper.java:159)
at com.bmc.sas.dm.wsclient.PolicyWebserviceHelper.getPolicy(PolicyWebserviceHelper.java:43)
at com.bmc.sas.dm.exporter.PolicyDataExporter.exportData(PolicyDataExporter.java:42)
at com.bmc.sas.dm.PEExporter.export(PEExporter.java:59)
at com.bmc.sas.dm.exporter.PolicyEngineExporter.exportPolicies(PolicyEngineExporter.java:60)
at com.bmc.sas.dm.exporter.PolicyEngineExporter.exportAllData(PolicyEngineExporter.java:55)
at com.bmc.sas.dm.CmdDataMigration.execute(CmdDataMigration.java:302)
at com.bmc.sas.dm.CmdDataMigration.main(CmdDataMigration.java:117)
Caused by: com.bmc.bppm.wsclient.exception.ServerException: Call to Server failed : Response Status: 500 Message returned from server: rO0ABXNyACxjb20uYm1jLnNtcy53c2NvbW1vbi5jbGllbnQuQ2xpZW50UmVzcG9uc2VUTwAAAAAAAAABAgAHSgARcmVzcG9uc2VUaW1lU3RhbXBMAAxlcnJvck1lc3NhZ2V0ABJMamF2YS9sYW5nL1N0cmluZztMAAZlcnJvcnN0ABBMamF2YS91dGlsL0xpc3Q7TAAKc3RhdHVzQ29kZXEAfgABTAALc3RhdHVzQ29kZXNxAH4AAkwADnN0YXR1c01lc3NhZ2VzcQB+AAJMAAlzdGF0dXNNc2dxAH4AAXhwAAABTUKx85Bwc3IAE2phdmEudXRpbC5BcnJheUxpc3R4gdIdmcdhnQMAAUkABHNpemV4cAAAAAF3BAAAAAF0AEdGYWlsZWQgdG8gcmV0cmlldmUgUG9saWN5IHdpdGggSUQ6IDViNjBhZTJlLWI4ZGUtNGViOS05MzhjLTQxZTJkOTBlMTM0ZHh0AA5CUFBNLUNNQTUwMDAxRXBwdAALQmFkIFJlcXVlc3Q=
at com.bmc.bppm.wsclient.impl.BPPMServerConnUsingSAPService.executeRequest(BPPMServerConnUsingSAPService.java:607)
at com.bmc.bppm.wsclient.impl.BPPMServerConnUsingSAPService.executeGetService(BPPMServerConnUsingSAPService.java:138)
at com.bmc.sas.dm.wsclient.BPPMClientWrapper.executeRequest(BPPMClientWrapper.java:184)
at com.bmc.sas.dm.wsclient.BPPMClientWrapper.invokeOperation(BPPMClientWrapper.java:156)
... 7 more
+++
Solution
1. To identify the policy name that failed to export and produced the tool to stop working, analyze the datamigrator.log file to get the id of the policy failing. Search for string similar to "BMC_DM6E Exception:Error while executing web service request" like in below message:
ERROR 11 May 2015 15:17:489174 [main] com.bmc.sas.dm.wsclient.BPPMClientWrapper BMC_DM6E Exception:Error while executing web service request with URL unifiedadmin/Policy/5b60ae2e-b8de-4eb9-938c-41e2d90e134d/list
com.bmc.bppm.wsclient.exception.ServerException: Call to Server failed : Response Status: 500 Message returned from server:
2. Take the policy ID from the error message. This is the long value between "/Policy/" and "/list", that is, 5b60ae2e-b8de-4eb9-938c-41e2d90e134d
3. Execute below SQL statement in your BPPM server to get the name of the Policy assiociated to that ID (value of the oname column):
runjava scripts.runsqli "select * from pepolicy where id ='5b60ae2e-b8de-4eb9-938c-41e2d90e134d'"
4. Trying to export only this particular policy name with the cmapolicymigration tool from the command line should also fail.
The reasons for the policy to fail during export are difficult to say at this stage but below are some recommended steps:
a. Edit the policy from CMA console and review every configuration section to ensure nothing got wrong or corrupted (for instance, if Single Integration Service value is set, ensure only one ISN name is provided in the value field).
b. A restart of BPPM server to sync up data within BPPM DB may help.
c. If restarting is not possible or it doesn't fix it, deleting the specific policy and recreating it again may also help to ensure the policy is properly created.
Additional Information
[remove if no additional clarification or reference is required.]
Related Products:
- BMC ProactiveNet Performance Management Suite