Hyperion 188.8.131.52 Migration Error within Shared Services: “CLU Process exited without updating MSR report.”
May 20, 2012 Oracle Hyperion EPM 184.108.40.206 0 Comments
I have been running into an error everytime that I tried doing a Lifecycle migration from within Shared Services (not for the 220.127.116.11 upgrade). I constantly was getting this error: CLU Process exited without updating MSR report.
I finally resolved this error by finding that my Native Directory LDAP had an incorrect port number, perhaps from the many upgrades that this server has been through. I fixed it by doing the following. Before starting, verify the correct port number by running the following at the command line (this is on Linux; find the similar folder and executable for Windows – epmsys_registry.bat):
cd /home/hyperion/Hyperion/common/config/18.104.22.168 /epmsys_registry.sh VIEW SHARED_SERVICES_PRODUCT/NATIVE_PROVIDER
COMPONENTS MATCHING THE TREE EXPRESSION COMPONENT - 1 NAME - NATIVE_PROVIDER:examplename.example.com ID - 11d1def534ea1be028b6a6ad121b6ad3207faf TYPE - NATIVE_PROVIDER HOST - examplename.example.com HYPERION HOME - /home/hyperion/Hyperion PROPERTIES - version = 22.214.171.124 port = 58089 FILES - NONE PARENT COMPONENTS - Parent 1 NAME - HOST:examplename.example.com ID - 11d1def534ea1be028b6a6ad121b6aaf3207ffe TYPE - HOST Parent 2 NAME - SHARED_SERVICES_PRODUCT ID - 62f13ac4eab91fa0562age2f41142b0914018005 TYPE - SHARED_SERVICES_PRODUCT CHILD COMPONENTS - NONE
- View the listed information to verify the correct port number: “port = 58089”
- In Shared Services, go to Application Groups, Foundation and Deployment Metadata.
- Expand Shared Services Registry, Foundation Services, Shared Services, and Native Provider….
- Right-Click on the Properties file, and choose Export for Edit.
- Open the downloaded file in a text editor (notepad), and then modify the port number to the correct port. This file was correct on my system: port=58089
- Save and Upload the file if changes were needed, by right-clicking on the Properties file in Shared Services, and choosing Import after Edit. Find your file and click Finish.Now check the next file:
- In the Shared Services folder from above, right click on the CSSConfig file.
- Choose Export for Edit.
- Check the downloaded files for any error in the port number. My file had the port number of 28089 listed, which was apparently carried over from version 9.2.
- Upload the changed file back by right-clicking on the CSSConfig file again and choosing Import after Edit. Find you file and click Finish.
- Restart Shared Services and try your Migration again.
I hope this helps someone else, and they don’t ignore it for months like I did.