Please enter search query.
Search <product_name> all support & community content...
Article: 100018317
Last Published: 2009-01-29
Ratings: 0 0
Product(s): NetBackup & Alta Data Protection
Problem
VxUL Unified Logging command "vxlogview" responds with "corrupted log records" message.Error Message
V-1-1-12 There are no records to be displayed.V-1-1-13 NOTE: There were xxxxx corrupted log records.
Solution
Overview:
When running a command to extract logmessages from raw logs, a message like thisappears
V-1-1-13 Note: There were 1,198 corrupted logrecords.
Solutions / Workaround:
This message can occur forseveral reasons:
1. The version of NetBackup running on the machinewhere
Solution 1: On the host being used for processing theraw logs, upgrade NetBackup to at least the version that was used to create thelogs or to the most recent available version.
2. There is aknown issue with
Solution 2: Run
Note: There are plans to address this
3. If the log file truly containscorrupt entries, then the
Solution3: There is a new
Note: Run
Note: This newswitch will not work to resolve the character interpretation problem on Windowsas documented in item 2 above.
-c,--showcorrupt Show corruptmessages.
Example:
C:\Program Files\VERITAS\NetBackup\bin> vxlogview -p 51216 -d all -c>d:\logging\out.txt
or
C:\Program Files\VERITAS\NetBackup\bin> vxlogview -p 51216 -d all --showcorrupt>d:\logging\out.txt
When running a command to extract logmessages from raw logs, a message like thisappears
C:\ProgramFiles\VERITAS\NetBackup\bin>
vxlogview -p 51216 -d all>d:\logging\out.txt
V-1-1-13 Note: There were 1,198 corrupted logrecords.
Solutions / Workaround:
This message can occur forseveral reasons:
1. The version of NetBackup running on the machinewhere
vxlogview is being run, is lowerthan the NetBackup version used to create the unified logs that are beingprocessed.
Solution 1: On the host being used for processing theraw logs, upgrade NetBackup to at least the version that was used to create thelogs or to the most recent available version.
2. There is aknown issue with
vxlogview when run froma
Windows host. Sometimes, if OID 156 has been logging at Verbose 4or higher, it can generate a log character that the
Windows version of
vxlogview can not interpretcorrectly. It is not a log corruption in the strictest sense, but afailure of
vxlogview to interpret thecharacter correctly.
Solution 2: Run
vxlogview against the logs from a
Unix host. The
Unix version of
vxlogview can correctly interpret thetroublesome character.
Note: There are plans to address this
vxlogview shortcoming in the nextrelease of NetBackup.
3. If the log file truly containscorrupt entries, then the
"corrupted logrecords" error will display regardless if using the
Unix or
Windows version of
vxlogview .
Solution3: There is a new
vxlogview switch starting in NetBackup 6.5.3 and higher. It is called
"--showcorrupt" or
"-c" . Addthis new switch to your
vxlogview command syntax.
Note: Run
vxlogview-h to see a complete list of
vxlogview syntax.
Note: This newswitch will not work to resolve the character interpretation problem on Windowsas documented in item 2 above.
-c,--showcorrupt Show corruptmessages.
Example:
C:\Program Files\VERITAS\NetBackup\bin> vxlogview -p 51216 -d all -c>d:\logging\out.txt
or
C:\Program Files\VERITAS\NetBackup\bin> vxlogview -p 51216 -d all --showcorrupt>d:\logging\out.txt
References
Etrack : 1843112
Etrack : 1388063
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.