First check to see if the /usr/lib/cms/Pname is empty or missing. If it is empty or missing, try one of the following to recover the file:
- If the file is empty or missing, check for the existence of /usr/lib/cms/Pname.rpmsave if this error occurs during an upgrade. The upgrade will save the existing files with a .rpmsave extension before creating a new file. If this happens, copy the /usr/lib/cms/Pname.rpmsave file to /usr/lib/cms/Pname.
- If the /usr/lib/cms/Pname is empty and no valid /usr/lib/cms/Pname file exists, check to see if this is a HA configuration. If it is a HA configuration and there is a valid /usr/lib/cms/Pname file on the Secondary CMS, copy the file from that server.
- If the /usr/lib/cms/Pname is empy or missing and there are no /usr/lib/cms/Pname.rpmsave files or a HA configuration, locate the last CMS ADM backup and copy the file using the cpio command listed in the CMS Maintenance and Troubleshooting guide to recover a specific file.
Once the /usr/lib/cms/Pname file is recovered using one of the steps above, rebuild the ACDs by running cmssvc > swsetup by following the steps below for all the ACDs administered:
1. Launch cmssvc
2. Enter choice 4) run_cms
3. Enter choice 2) Turn off CMS but Leave IDS running
4. Launch cmssvc
5. Enter choice 7) swsetup
6. Accept all default values
7. Launch cmssvc
8. Enter choice 4) run_cms
9. Enter choice 1) Turn on CMS
10. Launch su cms cms
11. Choose System Setup
12. Choose Data collection
13. Turn data collection On for all ACDs
Lastly reboot the CMS server.
