Page History
This section contains the following topics• Action
...
...
...
| Anchor | ||||
|---|---|---|---|---|
|
Some Tiers require action items to complete the un-installing or removal of the Tier. Usually, the action items are listed online, but some Tiers have detailed action items that are fully documented below.
| Anchor | ||||
|---|---|---|---|---|
|
Before you remove J2EE Tier Collectors, you should remove the Precise for J2EE configuration that was added when you performed post-installation tasks. To remove the configuration, shutdown the JVM, remove the configuration from the startup script, and then restart the JVM.
...
NOTE If you want to retain the instance or Tier history data, verify that the PMDB Maintenance (Weekly) process parameter is cleared. You are then able to view the data by installing a new instance using the same ID of the instance you deleted. For more information on the procedure for reusing an instance ID, see the Installing an uninstalled, old instance_id parameter section in the Precise CLI Utility Reference Guide.
| Anchor | ||||
|---|---|---|---|---|
|
After removing the Oracle Tier Collectors, you need to perform the following task.
...
-t oracle-port -v oracle-version
where oracle-version is 81, 90, or 100.
...
UNIX ./products/oracle/install/uninstall sys obj.sql
| Anchor | ||||
|---|---|---|---|---|
|
When the Siebel Tier Collectors have been removed, you can delete the Precise Interpoint Project from the Siebel Repository File (SRF). These tasks differ slightly depending on whether Interpoint is installed for a SQL Server or an Oracle database. See Deleting the Precise Interpoint project from the SRF (Oracle) on page 233 and Deleting the Precise Interpoint project from the SRF (SQL Server) on page 234.
...