Error Enabling User Sysman For A Agent
Contents |
following sections: Reconfiguring the Oracle Management Agent Reconfiguring the Oracle Management Service 12.1 Reconfiguring the Oracle Management Agent The following sections describe reconfiguration and how to install oem 12c agent manually tuning changes you can make to the Management Agent after you
How To Configure Enterprise Manager In Oracle 11g Manually
have installed Enterprise Manager. Refer to the following sections for more information: Configuring the Management Agent to oms is locked. cannot unsecure the agent. Use a New Management Service Changing the Management Agent Port Controlling the Amount of Disk Space Used by the Management Agent About the Management Agent Watchdog Process Setting the emctl config agent addinternaltargets Management Agent Time Zone Adding Trust Points to the Management Agent Configuration 12.1.1 Configuring the Management Agent to Use a New Management Service When you install the Management Agent on a managed host, you associate the Management Agent with a particular Management Service. The Management Agent uses the Management Service URL address and port to identify and
Emctl Config Oms
communicate with the Management Service. After you install the Management Agent, you can later reconfigure the Management Agent so it is associated with a different Management Service. Reconfiguring the Management Agent requires no changes to the Management Service. The reconfigured Management Agent will begin communicating with the new Management Service after the Management Agent is restarted. To associate the Management Agent with a new Management Service after you have installed the Management Agent: Stop the Management Agent. See Also: "Controlling the Oracle Management Agent" Locate the emd.properties file in the Management Agent home directory: AGENT_HOME/sysman/config/emd.properties Use a text editor to open the file and locate the REPOSITORY_URL property. Modify the value for the REPOSITORY_URL property so it references the new Management Service. For example: REPOSITORY_URL=http://mgmthost2.acme.com:4889/em/upload Modify the value for the emdWalletSrcUrl and emdWalletDest properties so they reference the new Management Service and the new Oracle home path, respectively: For example, if the new Management Service is on a host called mgmthost2.acme.com and the new Oracle home is /
Cloud Control 12c, now I'll show how to add target hosts to our Enterprise Manager system. I assume that you're in a similar position (installed Cloud Control but haven't added any target oracle oem 12c firewall ports yet). As you know, we have to install Oracle Management Agent to the targets to oracle enterprise manager 12c default port be able to manage them via our Enterprise Manager. In OEM Cloud Control 12c, we can "Add Host Targets Wizard" which is
Environment Variable Oracle_unqname Not Defined. Please Set Oracle_unqname To Database Unique Name.
accessible from the web interface. We can manually enter required information of host or we can use auto-discovery method. If we'll use auto discovery, we need an active agent to discover targets in network. This agent https://docs.oracle.com/cd/B19306_01/em.102/b40002/postinstall_config.htm can scan local services or network. "Nmap" is used for scanning network. Nmap requires root privileges to be able to use raw sockets for "Syn Scanning" (a method to detect open ports through firewalls). So we need to configure "privilege delegation" in the host of our agent (which we'll use for scanning). Click "setup", "security" and then "privilege delegation". Currently I have only one active agent (it's the agent installed on OEM http://www.gokhanatil.com/2011/10/how-to-deploy-oracle-management-agent.html Cloud Control server), so I'll configure privilege delegation for it. Click "edit". Select "sudo", enter "/usr/bin/sudo -u %RUNAS% %COMMAND%" as sudo command. Click update. So we said that this host supports sudo for privilege delegation but in fact, we haven't configured sudo yet. Connect to the host (in this case it's our cloud control server), edit /etc/sudoers file, put remark sign before "Defaults requiretty" add a user (i.e. oracle): Shell vi /etc/sudoers #Defaults requiretty root ALL=(ALL) ALL oracle ALL=(ALL) ALL 123456 vi /etc/sudoers#DefaultsrequirettyrootALL=(ALL) ALLoracleALL=(ALL) ALL As soon as you save the changes, oracle will be added to sudoers and be able to run commands as root with sudo. Now we're ready to discovery new hosts using this host. Click "setup", "add target" and then "configure auto discovery". Click "configure" to set up IP scanning. Click "create" to create a new search. Click "add" to add agents which we'll use for scanning. Select the agent(s) for scanning. So you can use multiple agents to scan networks faster. Enter the target IP subnet and then click job details. Select "new" to be able to enter credentials of the user you added as sudoer, this information will be saved so you can use it later. You can give a meaningful name for it. Click "save and submit IP sc
Hostname without reinstalling Oracle Enterprise Manager. If you're trying to resolve an ORACLE_UNQNAME problem, check another post of mine for that answer. These http://blog.mclaughlinsoftware.com/oracle-architecture-configuration/changing-windows-hostname-and-oracle-enterprise-manager/ are the steps: 1. Change the %ORACLE_HOME%\network\admin\listener.ora file from an IP number to machine name. 2. Change the %ORACLE_HOME%\network\admin\tnsnames.ora file from an IP number to a machine name. 3. Change the C:\WINDOWS\System32\drivers\etc\hosts file by adding this line beneath the default localhost line (for the new Hostname value): 127.0.0.1 localhost 172.16.113.128 mclaughlin11g mclaughlin11g.techtinker.com 4. Change the Windows hostname by navigating: Start how to > Control Panel > System (classic view) from the random assignment of VMWare Fusion. 5. Reboot the machine to set the networking. Unlock the SYSMAN account because it ensures that emca can drop it and all dependencies. Then, drop the em configuration with the following commands. C:\Data> set ORACLE_SID=orcl C:\Data> emca -deconfig dbcontrol db -repos drop 6. You'll receive error enabling user the following prompts, enter the Oracle SID and Port number without double quotes but you must enter all passwords with double quotes (at least in Oracle Database 11g): Oracle Database 11gR1 STARTED EMCA at Jul 13, 2008 8:26:42 AM EM Configuration Assistant, Version 11.1.0.5.0 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID: orcl Listener port number: 1521 Password for SYS user: Password for SYSMAN user: Password for SYSMAN user: Do you wish to continue? [yes(Y)/no(N)]: y Oracle Database 11gR2 STARTED EMCA at Sep 3, 2012 7:40:07 PM EM Configuration Assistant, Version 11.2.0.0.2 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID: orcl Listener port number: 1521 Password for SYS user: Password for SYSMAN user: Do you wish to continue? [yes(Y)/no(N)]: y 7. If you failed to unlock the SYSMAN account in step #5, you should drop the SYSMAN user manually. If you don't drop the SYSMAN schema, you'll raise an error when you try to recreate it: CONFIG: ORA-20001: SYSMAN alread