Troubleshooting HCL OneDB

Several troubleshooting techniques, tools, and resources are available for resolving problems that you encounter in your HCL OneDB™ database server environment.

Use this general approach for troubleshooting problems:

1. Determine if the problem is a known software defect...
Check the HCL Support Portal for HCL OneDB.
  • Search for keywords related to your problem to find problem reports, workarounds, patches, or fix packs.
2. If the problem is not a known software defect, diagnose the problem...

Check the HCL OneDB online log.

The log file is in $ONEDB_HOME/tmp/online.log by default, or in the location set by MSGPATH. The log contains messages about the database server status and errors.
  • Verify that normal operations are logging successfully (startup, checkpoints, shut down).
  • Look for messages about problems that occurred (for example, process aborted abnormal).
  • Run the finderr command with the message number to find information about that message and follow the recommendations (for example, restart the database server, run a particular command or utility).
Monitor the database server.
3. If the problem cannot be resolved, contact HCL Software Support
Define the problem, gather background information, and determine the severity of the problem.
  • End-to-end Network Management with HCL's Flexible and Secure Solution Suite Product Support (Product Support Services).
To avoid future problems, review the troubleshooting resources and take these preventive steps:
  • Review online logs regularly.
  • Run and analyze system statistics regularly.
  • Keep up to date with product fix packs.
  • Validate changes on a test system before changing the production system.
  • Follow backup and restore practices.
  • Set up event alarms for error handling.