Moreover, there are two types of targets:<\/p>\n
- \n
- Repository Side targets<\/li>\n
- Agent Side targets<\/li>\n<\/ul>\n
To query the Repository Side targets, use the following SQL\u00a0inside your EM repository:<\/p>\n
SELECT ENTITY_TYPE,\r\n TYPE_DISPLAY_NAME,\r\n ENTITY_NAME,\r\n DISPLAY_NAME\r\nFROM SYSMAN.EM_MANAGEABLE_ENTITIES\r\nWHERE MANAGE_STATUS = 2\r\nAND REP_SIDE_AVAIL = 1\r\nORDER BY 1,2;<\/pre>\n
To query the Agent Side targets, use the following SQL\u00a0inside your EM repository:<\/p>\n
SELECT ENTITY_TYPE,\r\n TYPE_DISPLAY_NAME,\r\n ENTITY_NAME,\r\n DISPLAY_NAME,\r\n EMD_URL\r\nFROM SYSMAN.EM_MANAGEABLE_ENTITIES\r\nWHERE MANAGE_STATUS = 2\r\nAND REP_SIDE_AVAIL = 0\r\nAND EMD_URL IS NOT NULL\r\nORDER BY 1,2,3;<\/pre>\n
The agent side targets are stored also inside your target host. You can list\u00a0them executing\u00a0the following script\u00a0(as the EM Agent user):<\/p>\n
[root@evabddrjs001 ~]# su - emc12\r\n[emc12@evabddrjs001 ~]$ $AGENT_HOME\/bin\/emctl config agent listtargets\r\nOracle Enterprise Manager Cloud Control 12c Release 2\r\nCopyright (c) 1996, 2012 Oracle Corporation. All rights reserved.\r\n[10.221.63.104, host]\r\n[10.221.63.104:3872, oracle_emd]\r\n[agent12c1_2_evabddrjs001, oracle_home]\r\n[COLISEU_104, oracle_database]\r\n[OraDb10g_home1_1_evabddrjs001, oracle_home]\r\n[COLISEU_10.221.63.104, oracle_listener]\r\n[emc12@evabddrjs001 ~]$<\/pre>\n
First, let’s see an example of how to rename Repository side targets:<\/p>\n
Rename Repository Side Targets<\/h2>\n
What you need to know:<\/p>\n
- \n
- These targets are not<\/strong> monitored by the Cloud Control Agent.<\/li>\n
- These targets are not<\/strong> present in the Cloud Control Agent files “$AGENT_BASE\/sysman\/emd\/targets.xml”<\/li>\n
- These targets are only present in the Cloud Control repository and they are mainly known as “System” targets or aggregate targets (like groups).<\/li>\n<\/ul>\n
The “Display Name” and the “Target Name” are usually the same on Repository Side targets.<\/p>\n
It is possible to rename Repository Side targets. First, execute the following emcli command as oracle user inside your EMc server:<\/p>\n
[root@ec12mntrjr001 ~]# su - oracle\r\n[oracle@ec12mntrjr001 ~]$ emcli login -username=sysman\r\nEnter password :\r\n\r\nLogin successful\r\n[oracle@ec12mntrjr001 ~]$ emcli sync\r\nSynchronized successfully<\/pre>\n
Target Name<\/h3>\n
To rename the “Target Name” of the target, use the following query:<\/p>\n
-target_name=<the actual target name>
\n-new_target_name=<the new target name><\/p>\nEg: Renaming a target name from “oracbddrjs_cluster”<\/strong><\/em><\/span> to “oracbddrjs-cluster”<\/strong><\/em><\/span>.<\/p>\n
[oracle@ec12mntrjr001 ~]$ emcli rename_target -target_type=\"cluster\" -target_name=\"oracbddrjs_cluster\" -new_target_name=\"oracbddrjs-cluster\"<\/pre>\n
Now check with the “Repository Side Targets” SQL\u00a0above if the Target name and Display name were modified.<\/p>\n
If only the target name was changed, proceed to the next step.<\/p>\n
Display Name<\/h3>\n
To rename the “Display Name” of the target, use the query:<\/p>\n
-name=<the target name> # Note that I use the new name because I renamed it in the step before.
\n-display_name=<new display name><\/p>\nEg: Renaming a display\u00a0name to “oracbddrjs-cluster”<\/em><\/span><\/strong>.<\/p>\n
[oracle@ec12mntrjr001 ~]$ emcli modify_target -name=\"oracbddrjs-cluster\" -type=\"cluster\" -display_name=\"oracbddrjs-cluster\"\r\nTarget \"oracbddrjs-cluster:cluster\" modified successfully\r\n[oracle@ec12mntrjr001 ~]$<\/pre>\n
Now, let’s see an example of how to rename Agent side targets:<\/p>\n
Rename Agent Side Targets<\/h2>\n
What you need to know:<\/p>\n
- \n
- These targets are<\/strong> monitored by the Cloud Control Agent.<\/li>\n
- These targets are<\/strong> present in the Cloud Control Agent files “$AGENT_BASE\/sysman\/emd\/targets.xml”<\/li>\n<\/ul>\n
The “Display Name” and the “Target Name” may be different for Agent Side targets.
\nThe “Target Name” for an Agent Side target is the name of the target in the EM Cloud Control Agent file “$AGENT_BASE\/sysman\/emd\/targets.xml”.
\n(Which can be retrieved with the EM Cloud Control Agent command “emctl config agent listtargets”).<\/p>\nDisplay Name<\/h3>\n
To change the “Display Name” of an Agent Side target, you can use the following command:<\/p>\n
Eg: Renaming the listener display\u00a0name from “COLISEU_10.221.63.104”<\/span>\u00a0<\/em><\/strong>to\u00a0“LISTENER_10.221.63.104”<\/em><\/strong><\/span>.<\/p>\n
[root@ec12mntrjr001 ~]# su - oracle\r\n[oracle@ec12mntrjr001 ~]$ emcli login -username=sysman\r\nEnter password :\r\n\r\nLogin successful\r\n[oracle@ec12mntrjr001 ~]$ emcli modify_target -name=\"COLISEU_10.221.63.104\" -type=\"oracle_listener\" -display_name=\"LISTENER_10.221.63.104\" -on_agent\r\nTarget \"COLISEU_10.221.63.104:oracle_listener\" modified successfully<\/pre>\n
Checking on target side:<\/p>\n
[emc12@evabddrjs001 ~]$ emctl config agent listtargets\r\nOracle Enterprise Manager Cloud Control 12c Release 2\r\nCopyright (c) 1996, 2012 Oracle Corporation. All rights reserved.\r\n[10.221.63.104, host]\r\n[10.221.63.104:3872, oracle_emd]\r\n[agent12c1_2_evabddrjs001, oracle_home]\r\n[COLISEU_104, oracle_database]\r\n[OraDb10g_home1_1_evabddrjs001, oracle_home]\r\n[COLISEU_10.221.63.104, oracle_listener]\r\n[emc12@evabddrjs001 ~]$<\/pre>\n
The target name didn’t change, but the Display name on EM is now modified as the picture below:<\/p>\n
![\"\"](\"http:\/\/www.dbarj.com.br\/wp-content\/uploads\/2013\/10\/img_5259df16219d0.png\")
<\/p>\nTarget Name<\/h3>\n
Attention: Do this at your own risk. Oracle does not support it yet and it will be necessary to do manual changes on SYSMAN packages.<\/p>\n
In this example, we will rename the listener target\u00a0name from\u00a0“COLISEU_10.221.63.104”<\/em><\/span> to “LISTENER_10.221.63.104”<\/span><\/em>. Note that the display name<\/span> was already changed in the step before.<\/strong><\/p>\n
First of all, stop the agent on the target host, edit the “$AGENT_BASE\/sysman\/emd\/targets.xml” with the desired target name and start the agent again:<\/p>\n
[emc12@evabddrjs001 ~]$ emctl stop agent\r\nOracle Enterprise Manager Cloud Control 12c Release 2\r\nCopyright (c) 1996, 2012 Oracle Corporation. All rights reserved.\r\nStopping agent ..... stopped.\r\n[emc12@evabddrjs001 ~]$ vim $AGENT_BASE\/sysman\/emd\/targets.xml<\/pre>\n
Before:<\/p>\n
[emc12@evabddrjs001 ~]$ cat $AGENT_BASE\/sysman\/emd\/targets.xml<\/pre>\n
...\r\n<Target TYPE=\"oracle_listener\" NAME=\"COLISEU_10.221.63.104\" DISPLAY_NAME=\"LISTENER_10.221.63.104\" ON_HOST=\"\" EMD_URL=\"https:\/\/10.221.63.104:3872\/emd\/main\/\" TIMEZONE_REGION=\"\" IDENTIFIER=\"TARGET_GUID=0AD03AC01B183A0E9762470BD2A4799E\">\r\n<Property NAME=\"Machine\" VALUE=\"10.221.63.104\"\/>\r\n<Property NAME=\"Port\" VALUE=\"1521\"\/>\r\n<Property NAME=\"ListenerOraDir\" VALUE=\"\/software\/app\/oracle\/product\/network\/admin\"\/>\r\n<Property NAME=\"OracleHome\" VALUE=\"\/software\/app\/oracle\/product\"\/>\r\n<Property NAME=\"LsnrName\" VALUE=\"LISTENER\"\/>\r\n<\/Target>\r\n...<\/pre>\n
After:<\/p>\n
[emc12@evabddrjs001 ~]$ cat $AGENT_BASE\/sysman\/emd\/targets.xml<\/pre>\n
\u00a0...\r\n<Target TYPE=\"oracle_listener\" NAME=\"LISTENER_10.221.63.104\" DISPLAY_NAME=\"LISTENER_10.221.63.104\" ON_HOST=\"\" EMD_URL=\"https:\/\/10.221.63.104:3872\/emd\/main\/\" TIMEZONE_REGION=\"\" IDENTIFIER=\"TARGET_GUID=0AD03AC01B183A0E9762470BD2A4799E\">\r\n<Property NAME=\"Machine\" VALUE=\"10.221.63.104\"\/>\r\n<Property NAME=\"Port\" VALUE=\"1521\"\/>\r\n<Property NAME=\"ListenerOraDir\" VALUE=\"\/software\/app\/oracle\/product\/network\/admin\"\/>\r\n<Property NAME=\"OracleHome\" VALUE=\"\/software\/app\/oracle\/product\"\/>\r\n<Property NAME=\"LsnrName\" VALUE=\"LISTENER\"\/>\r\n<\/Target>\r\n...<\/pre>\n
[emc12@evabddrjs001 ~]$ emctl start agent\r\nOracle Enterprise Manager Cloud Control 12c Release 2\r\nCopyright (c) 1996, 2012 Oracle Corporation. All rights reserved.\r\nStarting agent .................. started.\r\n[emc12@evabddrjs001 ~]$ vim $AGENT_BASE\/sysman\/emd\/targets.xml\r\n[emc12@evabddrjs001 ~]$ emctl config agent listtargets\r\nOracle Enterprise Manager Cloud Control 12c Release 2\r\nCopyright (c) 1996, 2012 Oracle Corporation. All rights reserved.\r\n[10.221.63.104, host]\r\n[10.221.63.104:3872, oracle_emd]\r\n[agent12c1_2_evabddrjs001, oracle_home]\r\n[COLISEU_104, oracle_database]\r\n[OraDb10g_home1_1_evabddrjs001, oracle_home]\r\n[LISTENER_10.221.63.104, oracle_listener]\r\n[emc12@evabddrjs001 ~]$<\/pre>\n
The target name on the client changed. However, only those changes are not enough. If we check on EM, we will see that the target name is still unchanged.<\/p>\n
Now, we have 2 different methods<\/span> with same results to finish our target rename:<\/p>\n
Method 1:<\/h4>\n
If you try to change the target name as we did on “Repository Managed Targets”, you will get the following error:<\/p>\n
[oracle@ec12mntrjr001 ~]$ emcli rename_target -target_type=\"oracle_listener\" -target_name=\"COLISEU_10.221.63.104\" -new_target_name=\"LISTENER_10.221.63.104\"\r\nRename not supported for given Target Type.<\/pre>\n
This command line implicit calls the procedure\u00a0SYSMAN.EM_TARGET.RENAME_TARGET.<\/p>\n
Unfortanelly, if we check the procedure code inside the package body, there is a comment:<\/p>\n
-- we will implement rename of agent side targets when it is fully\r\n-- supported by agent<\/pre>\n
However, we have already done this manual agent name change.<\/p>\n
To accomplish\u00a0this, you will need to edit the PACKAGE BODY SYSMAN.EM_TARGET. Make a backup of the code and apply the changes:<\/p>\n
From:<\/p>\n
-- we will implement rename of agent side targets when it is fully\r\n -- supported by agent\r\n IF ( l_trec.manage_status = MANAGE_STATUS_MANAGED AND\r\n l_trec.emd_url IS NOT NULL) \r\n THEN\r\n raise_application_error(MGMT_GLOBAL.INVALID_PARAMS_ERR,\r\n MGMT_GLOBAL.INVALID_PARAMS_ERR||' Not allowed') ;\r\n END IF ;<\/pre>\n
To:<\/p>\n
-- we will implement rename of agent side targets when it is fully\r\n -- supported by agent\r\n IF ( l_trec.manage_status = MANAGE_STATUS_MANAGED AND\r\n l_trec.emd_url IS NOT NULL) \r\n THEN\r\n --raise_application_error(MGMT_GLOBAL.INVALID_PARAMS_ERR,\r\n -- MGMT_GLOBAL.INVALID_PARAMS_ERR||' Not allowed') ;\r\n\t null;\r\n END IF ;<\/pre>\n
Now recompile the package and any dependent invalid object:<\/p>\n
SQL> EXEC sys.UTL_RECOMP.recomp_serial('SYSMAN');\r\n\r\nPL\/SQL procedure successfully completed.<\/pre>\nLet’s try again.<\/p>\n
[oracle@ec12mntrjr001 ~]$ emcli rename_target -target_type=\"oracle_listener\" -target_name=\"COLISEU_10.221.63.107\" -new_target_name=\"LISTENER_10.221.63.107\"\r\nORA-04068: existing state of packages has been discarded\r\nORA-04061: existing state of package body \"SYSMAN.EM_TARGET\" has been invalidated\r\nORA-04065: not executed, altered or dropped package body \"SYSMAN.EM_TARGET\"\r\nORA-06508: PL\/SQL: could not find program unit being called: \"SYSMAN.EM_TARGET\"\r\nORA-06512: at \"SYSMAN.MGMT_TARGET\", line 3373\r\nORA-06512: at line 1<\/pre>\n
If you get this error, just reconnect or resync the session that was opened before you made the package change, and try again:<\/p>\n
[oracle@ec12mntrjr001 ~]$ emcli sync\r\nSynchronized successfully\r\n[oracle@ec12mntrjr001 ~]$ emcli rename_target -target_type=\"oracle_listener\" -target_name=\"COLISEU_10.221.63.107\" -new_target_name=\"LISTENER_10.221.63.107\"\r\nTarget COLISEU_10.221.63.107 successfully renamed to LISTENER_10.221.63.107.<\/pre>\n
Great. Now restore the package body backup that you have made putting back the commented line.<\/p>\n
Method 2:<\/h4>\n
We have also another way to change the target name inside EMc 12c Metadata. We can directly call the procedure that we changed on “Method 1”:<\/p>\n
SQL> exec sysman.em_target.rename_target('oracle_listener','COLISEU_10.221.63.104','LISTENER_10.221.63.104');\r\n\r\nbegin sysman.em_target.rename_target('oracle_listener','COLISEU_10.221.63.104','LISTENER_10.221.63.104'); end;\r\n\r\nORA-20233: -20233 Not allowed\r\nORA-06512: at \"SYSMAN.EM_TARGET\", line 5040\r\nORA-06512: at line 2<\/pre>\nI got the error above because I need to comment the Package Body lines exactly the same way I did in “Method 1”. So, backup it, comment them, recompile the dependencies and try again:<\/p>\n
SQL> exec sysman.em_target.rename_target('oracle_listener','COLISEU_10.221.63.104','LISTENER_10.221.63.104');\r\n\r\nbegin sysman.em_target.rename_target('oracle_listener','COLISEU_10.221.63.104','LISTENER_10.221.63.104'); end;\r\n\r\nORA-04068: existing state of packages has been discarded\r\nORA-04061: existing state of package \"SYSMAN.EM_TARGET\" has been invalidated\r\nORA-04065: not executed, altered or dropped package \"SYSMAN.EM_TARGET\"\r\nORA-06508: PL\/SQL: could not find program unit being called: \"SYSMAN.EM_TARGET\"\r\nORA-06512: at line 2<\/pre>\nIf you get this error, just reconnect the session that was opened before you made the package change, and try again:<\/p>\n
SQL> exec sysman.em_target.rename_target('oracle_listener','COLISEU_10.221.63.104','LISTENER_10.221.63.104');\r\n\r\nPL\/SQL procedure successfully completed\r\n\r\nSQL> commit;\r\n\r\nCommit complete\r\n\r\nSQL><\/pre>\nGreat, now let’s check on EM screen:<\/p>\n
![\"\"](\"http:\/\/www.dbarj.com.br\/wp-content\/uploads\/2013\/10\/img_5259df864dd59.png\")
<\/p>\nEverything is working fine. Don’t forget to\u00a0restore the package body backup that you have made, putting back the commented line.<\/p>\n
Now you finally have your target renamed.<\/p>\n
This article was based on Metalink document Doc ID 1515413.1, with many, many adaptations.<\/strong>
\n
\nHave you enjoyed? Please leave a comment or give a \ud83d\udc4d!<\/b><\/p>\n - These targets are<\/strong> present in the Cloud Control Agent files “$AGENT_BASE\/sysman\/emd\/targets.xml”<\/li>\n<\/ul>\n
- These targets are not<\/strong> present in the Cloud Control Agent files “$AGENT_BASE\/sysman\/emd\/targets.xml”<\/li>\n
- These targets are not<\/strong> monitored by the Cloud Control Agent.<\/li>\n
