Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Magic Number MisMatch
- Thread starter yahdin
- Start date
The only reference I could find on this was in the Troubleshooting Guide in the "Device Management Status Codes"
The status codes appear in exit status and command output for the ltid, tpclean, tpreq, and tpunmount commands, and in system or debug logs. These codes are also presented by programs that call those commands, such as media and device management user interfaces and the vmoprcmd command.
Device Management Status Code: 29
Message: Magic Number MisMatch
Explanation: An attempt was made to read the drive database, but it was found to be of an unknown format or version. The database is corrupt or there has been a mismatch of software components.
Recommended Action: Check integrity of the drive database file ltidevs, located in the directory /usr/openv/volmgr/database (UNIX) or in the folder install_path\Volmgr\database (Windows). Display the device configuration to determine whether or not the database is corrupt, and restore a saved copy of the database file
Bob Stump
Just because the Veritas documentation states a certain thing does not make it a fact
The status codes appear in exit status and command output for the ltid, tpclean, tpreq, and tpunmount commands, and in system or debug logs. These codes are also presented by programs that call those commands, such as media and device management user interfaces and the vmoprcmd command.
Device Management Status Code: 29
Message: Magic Number MisMatch
Explanation: An attempt was made to read the drive database, but it was found to be of an unknown format or version. The database is corrupt or there has been a mismatch of software components.
Recommended Action: Check integrity of the drive database file ltidevs, located in the directory /usr/openv/volmgr/database (UNIX) or in the folder install_path\Volmgr\database (Windows). Display the device configuration to determine whether or not the database is corrupt, and restore a saved copy of the database file
Bob Stump
Just because the Veritas documentation states a certain thing does not make it a fact
- Status
Similar threads
