When a user restores an NMS database using the data backed up from another NMS database holding a different version, an error message is displayed.
Fault locating:
1.This problem is generally caused by an inconsistency between the version of the NMS to be restored and the backup database. Therefore, the first step is to check whether the two NMS versions are the same. You can compare the server/patch directories of the two NMSs to check whether the CP versions are the same. The comparison result shows that the field backup database version is CP2312, whereas the version of the NMS to be restored is SPC201.
2.According to the feedback provided by frontline engineers, CP2312 has been installed on the NMS. However, after the CP2312 is installed, information about the CP2312 is still unavailable in the server/patch directory. After confirmation with frontline engineers on the procedure for loading the CP2312, it was discovered that the files in the old patch directory had not been cleared.
If the files in the old patch directory are not cleared, a patch conflict may occur, which leads to an environment exception and subsequently a patch loading failure.
Solution:
Perform rollback on the entries caused by repetitive patch loading.
Refer to the patch installation guide to perform environment cleanup so that the NMS version after the CP2312 is loaded is consistent with the backup database version.
Restore database data to the recovered NMS.
Experience sharing
Ensure the consistency between patch versions (specific to CP patch versions) during database backup and restoration.
Load the patch in strict compliance with the patch installation guide. Pay attention to the installation preparation part in the guide.
:
