2.2.2 Procedure for canceling setup
This subsection describes how to cancel setup of PFM - Agent for Oracle.
- Organization of this subsection
(1) Canceling setup of an instance environment
Canceling setup of an instance environment involves the tasks listed below. To cancel setup of multiple instance environments, you must repeat the procedure for each environment.
-
Deleting an instance environment
-
Deleting the objects registered in the Oracle Database
The following describes the above tasks.
(a) Deleting an instance environment
Check the instance name and delete the instance environment. Deletion of an instance environment is performed from a PFM - Agent host.
To check the instance name, use the jpcconf inst list command. To delete an instance environment that has been created, use the jpcconf inst unsetup command.
To delete an instance environment:
-
Check the instance name.
Execute the jpcconf inst list command specified with the service key that indicates PFM - Agent for Oracle. The following shows the command format:
jpcconf inst list -key Oracle
For example, if the instance name is SDC, the command displays SDC.
-
Stop all active PFM - Agent services in the instance environment.
For details about how to stop services, see the chapter on starting and stopping Performance Management in the JP1/Performance Management User's Guide.
-
Delete the instance environment.
Execute the jpcconf inst unsetup command specified with the service key that indicates PFM - Agent for Oracle and the instance name.
For example, if the instance name is SDC, use the following command line:
jpcconf inst unsetup -key Oracle -inst SDC
If execution is successful, the folders created as the instance environment are deleted, as well as the service IDs and Windows services.
- Note:
-
Canceling setup of an instance environment does not delete the service information that is displayed with the jpctool service list command. Use the jpctool service delete command to delete service information.
If you want to update the PFM - Web Console host to reflect the deletion of instance environment, you need to execute the jpctool service sync command to synchronize the agent information of the PFM - Manager host and that of the PFM - Web Console host.
After executing the command, restart PFM - Manager.
The following shows sample conditions and a command line applicable for the conditions.
-
Instance name: SDC
-
Host name: host03
-
Service ID of the Agent Collector service: OA1SDC[host03]
-
Service ID of the Agent Store service: OS1SDC[host03]
jpctool service delete -id O?1SDC[host03] -host host03
-
For details about the command, see the chapter on commands in the manual JP1/Performance Management Reference.
(b) Deleting the objects registered in the Oracle Database
This subsection describes the procedure for deleting the table and packages that were created in the Oracle Database being monitored. To execute this procedure, you must use the same Oracle account that you used when you registered the objects in the Oracle Database. Note that this procedure must be used only once for each account that is used to monitor the Oracle Database instance.
To delete the objects registered in the Oracle Database:
-
Set up an environment where the Oracle sqlplus command can be executed.
For details about Oracle environment setup, see your Oracle documentation.
-
Navigate to the following folder that contains the sp_drop.sql script provided by the PFM - Agent for Oracle:
installation-folder\agto\agent\sql
-
Execute the sp_drop.sql script on the Oracle Database being monitored.
PFM - Agent for Oracle deletes monitoring procedures, work tables, and other objects that are required to monitor Oracle from Oracle.
Example:
sqlplus Oracle-account@net-service-name-of-the-monitoring-target-database/password-for-the-Oracle-account @sp_drop.sql
-
sqlplus is a command provided by Oracle Corporation.
-
Oracle-account is the same Oracle account that was used to register the objects in the database.
For Oracle 10g or later, LSC_13_PLAN_TABLE is placed in DBA_RECYCLEBIN and is not deleted completely. If you want to delete LSC_13_PLAN_TABLE completely, execute the PURGE TABLE LSC_13_PLAN_TABLE; command.
Note that if the Oracle account is sys, LSC_13_PLAN_TABLE is not stored in DBA_RECYCLEBIN. Therefore, you do not need to execute the PURGE TABLE LSC_13_PLAN_TABLE; command.
-
-
Reset the value of the TIMED_STATISTICS Oracle initialization parameter.
If the value of the TIMED_STATISTICS Oracle initialization parameter has been changed in order to collect records of PFM - Agent for Oracle, reset the value, if necessary.
(2) Deleting an Oracle account used in PFM - Agent for Oracle
Oracle accounts used in PFM - Agent for Oracle are authorized to change the objects of other schemas freely in order to monitor the Oracle Database. For this reason, unnecessary Oracle accounts must be deleted. If the tablespaces that were used by a deleted account are unnecessary, also delete the tablespaces.
(a) Deleting an Oracle account
To delete an Oracle account, issue the DROP USER statement in an environment where the sqlplus Oracle command can be executed. Before issuing the statement, make sure that your Oracle account has the DROP USER system privilege.
To delete an Oracle account:
-
Issue the DROP USER statement.
Example:
DROP USER Oracle-account CASCADE;
If you add the CASCADE option, you can also delete the objects owned by the account.
For details about the DROP USER statement, see your Oracle documentation.
(b) Deleting the tablespaces used by a deleted Oracle account
When an Oracle account is deleted, the tablespaces used by the Oracle account become unnecessary. To delete these tablespaces, issue the DROP TABLESPACE statement in an environment where the sqlplus Oracle command can be executed. Before issuing the statement, make sure that your Oracle account has the DROP TABLESPACE system privilege.
To delete tablespaces:
-
Issue the DROP TABLESPACE statement.
For details about the DROP TABLESPACE statement, see your Oracle documentation.