Using PATROL Configuration Manager to change the default database password
You can use PATROL Configuration Manager to change the PATROL database monitoring user without using the Instance Modify menu command. Using PATROL Configuration Manager, you can retrieve the existing variables from each PATROL Agent and extract only those variables that relate to the instances you want to change. You can then enter the new password in text format and it will change to the encrypted format.
The naming convention for instances in the PATROL for Oracle KM is as follows:
/AgentSetup/ORACLE_<application class>.<sidname>.defaultAccount
For example, the following are some default account variables in PATROL for Oracle for an instance named neo924s1:
"/AgentSetup/ORACLE_AVAILABILITY.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_CAPACITY.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_COLLECTORS.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_DB_LINKS.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_ENVIRONMENT.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_INSTANCE.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_JOBS.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_LOG.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_MTS.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_NETWORK.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
"/AgentSetup/ORACLE_PERFORMANCE.neo924s1.defaultAccount" = { REPLACE = "tv8700/FFDE7E11676E2C83" },
The variables in the example above are instance specific. Therefore, you must create a change rule for each entry and save the extracted details as independent rule sets for each PATROL Agent. Save the rule sets in an editable .cfg file at PATROLInstallationDirectory/pconfmgr/rulesets.
After setting up the rule sets, run a process that replaces the existing password with the new encrypted password. You can then use PATROL Configuration Manager to apply the new rules. By using PATROL Configuration Manager, you also benefit from having backups of the change and a record of the actions taken.
Note
The example above applies only to the basic Oracle configuration that uses the ORACLE.kml files.
Comments
Log in or register to comment.