3 Deinstalling Oracle Data Quality Products

This chapter describes how to deinstall Oracle Data Quality products using the Deinstaller. Manual deinstallation procedures are also provided.

Section 3.1, "Starting the Deinstaller"
Section 3.2, "Removing the ODQ Home"
Section 3.3, "Removing Entries from Services File on UNIX Operating Systems"
Section 3.4, "Removing Entries from inetd.conf File on UNIX Operating Systems"

3.1 Starting the Deinstaller

For Oracle Data Quality products, go to the ODQ_HOME/oui/bin (on UNIX operating systems) or ODQ_HOME\oui\bin (on Windows operating systems) directory and start the Deinstaller.

On UNIX operating systems:
```
./runInstaller.sh -deinstall
```
On Windows operating systems:
```
setup.exe -deinstall
```
On Windows operating systems, you can also start the Deinstaller from the Start menu by selecting Programs > Oracle Home - ODQ_HOME > Uninstall.

Caution:
You must reboot your Windows operating system after running the Deinstaller. Failure to do so may result in an incomplete deinstallation.

Follow the instructions in Table 3-1 to remove the ODQ_HOME.

3.2 Removing the ODQ Home

After starting the Deinstaller, follow the instructions in Table 3-1 to remove your ODQ_HOME.

Note:

If you plan to reinstall Oracle Data Quality and use the same port numbers, you must modify the services file and the inetd.conf file after the deinstallation. See Section 3.3, "Removing Entries from Services File on UNIX Operating Systems" and Section 3.4, "Removing Entries from inetd.conf File on UNIX Operating Systems".

Table 3-1 Removing Your Oracle Data Quality Home

Number	Screen	Description and Action Required
1		Click Next to continue.
2		Select Deinstall Oracle Home. Verify the Oracle home directory that is about the be deinstalled. Click Deinstall to continue.
3		This screen shows the progress and status of the deinstallation.
4		Click Finish to dismiss the screen.

3.3 Removing Entries from Services File on UNIX Operating Systems

When you installed Oracle Data Quality, two entries were added to the bottom of the services file found in the /etc directory. These entries must be removed before you attempt to reinstall the Oracle Data Quality products.

To remove entries in the Services file

After removing Oracle Data Quality binaries and metabases as described in Section 3.1 and Section 3.2, log in as root and change directories to the directory /etc.
Locate the file named services and make a backup.
Open the services file for editing and go to the end of the file. You will see three lines inserted into the file as shown below:
```
#  These lines are entered for TSS 12 - Metabase Server
dscserv1_rel1200 8500/tcp
dscserv1_lm_rel1200 8501/tcp
```
Delete these three lines from the services file.
Save your changes and close the file.

3.4 Removing Entries from inetd.conf File on UNIX Operating Systems

When you installed Oracle Data Quality, an entry was added to the bottom of the inetd.conf file found in the /etc directory. This entry must be removed before you attempt to reinstall the Oracle Data Quality products.

To remove entries from inetd.conf

After modifying the services file as described in Section 3.3, locate the file named inetd.conf. (You should still be in the directory /etc. You must be logged in as root to perform this task.)
Locate the file named inetd.conf and make a backup.

NOTE: On Linux operating systems the file is named TSDiscovery and is located in the hidden directory /etc/xinetd.d.

Open inetd.conf for editing and go to the end of the file. You will see one line inserted into the file as shown below:

# These lines are entered for TSS 12 - Metabase Server
dscserv1_rel1200 stream tcp nowait systest /usr/bin/env -i HOME=/home systest
.LOGNAME=systest /home/system/rel1200_doc/metabase/bin/mtb_server

Delete the line from the inetd.conf file.
Save your changes and close the file.
Restart inetd in order to release the ports. While logged in as root, use the following command:
```
kill -HUP $(ps -e|grep inetd|head -1|awk '{print$1}')
```
This command will stop and restart inetd. Check with your UNIX administrator to ensure that this command will not cause problems in your environment.