Document Type | Troubleshooting
Category | Administration
Applicable Product Version | 6FS07
Document Number | TADTS016
Issue
This is an issue where resources related to Tibero DB such as engine and logs cannot be checked.
This issue occurs in two virtual machines configured in an Active-Standby structure using an HA (High Availability) solution, mainly resulting in inability to access Tibero DB engine, logs, and other resources.
- tbboot: command not found
- Unable to verify db engine path and log path
- When checking the results of the df -hT command on both nodes, all mount points cannot be confirmed
- No information about the external volume where Tibero is deployed can be found in the /etc/fstab file
Cause
After configuring the HA solution, the configuration for the volume was not set.
Due to VM reboot, the mount of the directory containing Tibero-related files has been released, and since the external volume cannot be detected on the server side, it is impossible to execute Tibero-related commands or check logs.
Solutions
Mount the external volume and then start Tibero normally.