Troubleshooting database commands errors
The following table provides solutions for troubleshooting loaddb commands.
| Issue | Solution/Information |
|---|---|
| Wrong port (http protocol, local) I get the following error message when running loaddb CHECKDB from a non-secure system. loaddb -Dlc.port=8081 -Dlc.zip=yes -Dlc.backup=yes CHECKDB (where | The port number you entered must match the port defined in $tomcat\conf\server.xml
|
| Wrong port (https protocol, local) I get the following error message when running loaddb CHECKDB from a secure system. loaddb -Dlc.port=8444 -Dlc.protocol=https -Dlc.host=companyserver.corp -Dlc.zip=yes -Dlc.backup=yes CHECKDB
| The port number you entered must match the ports defined in $tomcat\conf\server.xml
|
| Wrong port (https protocol, remote) I get the following error message when running loaddb CHECKDB from a secure system. loaddb -Dlc.port=8444 -Dlc.protocol=https -Dlc.host=example.com -Dlc.zip=yes -Dlc.backup=yes CHECKDB
| The port number you entered must match the ports defined in $tomcat\conf\server.xml
|
| Missing port (https protocol, local) I get the following error message when running loaddb CHECKDB from a secure system.
loaddb -Dlc.protocol=https -Dlc.host=companyserver.corp -Dlc.zip=yes -Dlc.backup=yes CHECKDB
| You must specify a Dlc.port argument. |
Missing cacerts from cacerts keystore I get the following error message when running : loaddb CHECKDB from a secure system.
loaddb -Dlc.port=8443 -Dlc.protocol=https -Dlc.host=example.com -Dlc.zip=yes -Dlc.backup=yes CHECKDB
| You must specify a valid cert path. The cert must exist in Java's cacerts keystore from where you initiate loaddb. |
| Missing CAcert from cacerts keystore when backing up remotely. I get the following error message when running from a secure system. loaddb -Dlc.port=8443 -Dlc.protocol=https -Dlc.host=example.com -Dlc.zip=yes -Dlc.backup=yes CHECKDB | You must specify a valid cert path. The cert must exist in Java's cacerts keystore from where you initiate loaddb. |