Open topic with navigation

Identifying and Removing Orphaned Tables

Occasionally, the development and testing of processes may cause some database objects to become 'orphaned'. That is, the entities that used to depend upon them are no longer present, and so the objects themselves are no longer linked to, or required by, any other part of the system.

The jmxtools command line tool can be used to identify and remove orphaned tables from the database. The jmxtools.jar file is installed in the tools directory of the OEDQ installation, and to run the following commands, you should start by changing your command line working directory to the tools directory of your OEDQ installation.

Identifying orphaned database objects

Orphaned database objects can be identified using the following command:

java -jar jmxtools.jar listorphans -u [username] -p [password] [ApplicationServerHostName]:[PortNumber]

where:

• [username] is the user name that the script should run under;
• [password] is the password belonging to the user identified by [username];
• [ApplicationServerHostName] is the name of the server which is running the application service, and
• [PortNumber] is the number of the JMX port for the installation (by default, this is 9005).

This command generates a newline-separated list of orphaned database objects.

Removing orphaned database objects

Orphaned database objects can be removed from the database using the following command:

java -jar jmxtools.jar droporphans -u [username] -p [password] [ApplicationServerHostName]:[PortNumber]

where:

• [username] is the user name that the script should run under;
• [password] is the password belonging to the user identified by [username];
• [ApplicationServerHostName] is the name of the server which is running the application service, and
• [PortNumber] is the number of the JMX port for the installation (by default, this is 9005).

This command runs non-interactively and removes the database objects identified by the listorphans script.