TECHALERT: Use of the dbutil command to check for an inconsistent FingerPrint cache can incorrectly indicate there is no data loss.

Article:TECH59027  |  Created: 2008-01-27  |  Updated: 2009-01-31  |  Article URL http://www.symantec.com/docs/TECH59027
Article Type
Technical Solution


Environment

Issue



TECHALERT: Use of the dbutil command to check for an inconsistent FingerPrint cache can incorrectly indicate there is no data loss.

Solution



Introduction:
When running the dbutil command on PureDisk 6.2, as indicated in related technote 300804 (see Related Documents below), the command can appear to run without errors.  In reality, the utility hasn't checked any records.  This only affects PureDisk 6.2.  See the following output (bold added for clarity):

# /opt/pdcr/bin/dbutil -lfs
Error: 17: Signal 'Child exited' intercepted, terminating
Info: Read-only mode enabled
Stage #1: Fast checking Segment DB
Stage #2: updating Segment DB
Segment Database Verification completed
0 records checked
0 records with errors
0 records OK

A correct output would look like the following (again, bold added for clarity):

# /opt/pdcr/bin/dbutil -lfs
Info: Read-only mode enabled
Stage #1: Fast checking Segment DB
Stage #2: updating Segment DB
Segment Database Verification completed
87417 records checked
0 records with errors
87417 records OK

What is Affected:
The environment is affected if ALL of the following conditions are met:
  • The environment must be running PureDisk Remote Office Edition 6.2.
  • PureDisk was installed using host names (fully qualified domain names) instead of IP addresses.
How to Determine if Affected:
To determine if the dbutil file in use is the correct version, run the following command.  If the output doesn't match what is shown, the binary should be updated.  

# md5sum /opt/pdcr/bin/.bin/dbutil
66e94034ef802c67819255647d2cd568  /opt/pdcr/bin/.bin/dbutil

Formal Resolution:
To resolve this issue:
1. Download the archive attached to this TechFile (click on the "Download Now", below, to do so).  
2. Uncompress the archive.
3. Place the new dbutil binary on all nodes in the /opt/pdcr/bin/.bin/ directory.  
4. Make the dbutil binary executable by running the following command: chmod +x /opt/pdcr/bin/.bin/dbutil
5. Run ldconfig to make sure all libraries are linked correctly

Common errors:
When running the dbutil -fls command, the most common error message is the "No such file or directory" message, as seen below:

# /opt/pdcr/bin/dbutil -fls
# /opt/pdcr/bin/dbutil: error while loading shared libraries: libcr.so.6: cannot open shared object file: No such file or directory

This message indicates the binary was copied to /opt/pdcr/bin directory, not to /opt/pdcr/bin/.bin/.  

To resolve this issue, place the binary in the correct location (as shown above) and rerun the ldconfig command.  

Workaround:
There are no known workarounds for this issue.  


Best Practices:
Symantec strongly recommends the following best practices:
1. Always perform a Full backup prior to and after any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.

How to Subscribe to Software Alerts:
If you have not received this TechNote from the Symantec Email Notification Service as a Software Alerts, please subscribe at the following link:
 http://maillist.entsupport.symantec.com/subscribe.asp




Attachments

puredisk_302042.zip (106 kBytes)


Legacy ID



302042


Article URL http://www.symantec.com/docs/TECH59027


Terms of use for this information are found in Legal Notices