Documente Academic
Documente Profesional
Documente Cultură
1. Check if the port is not busy for the system on which we are installing the agent.
For Dev OEM port is 1835
For Prod OEM, port is 1831
$ id oracle
If you are not able to telnet the respective ports, please open a ticket with Firewall team.
The installation will not be successful until this connection works.
If it is not set then set the PasswordAuthentication to yes and bounce the sshd daemon.
# stopsrc -s sshd
# startsrc -s sshd
5. Create a base directory for agent installation. If there are no /d01/oracle or /d02/oracle filesystems, request the
unix team to create one. Examples as follows –
Ex.
/d01/oracle/EM/agent
/d02/oracle/EM/agent
6. Edit or create the /etc/oratab and /etc/oraInst.loc. the owner for these files should be root:dba with rw
permissions for group.
Put following line in /etc/oratab. Examples as follows-
Ex.
AGENT: /d01/oracle/EM/agent/core/12.1.0.2.0:N
AGENT: /d02/oracle/EM/agent/core/12.1.0.2.0:N
8. Navigate as follows –
9. Click on add button. Fill in the hostname.domain for the server on which agent is to be installed in the Host field.
Select the correct platform in the Platform field. Click next.
10. Fill in the details as follows and click next.
Port for DEV OEM - 1835
Port for prod OEM – 1831
Instance directory will be generated itself depending on Installation Base Directory
Named Credentials is the OS login information. Select or create appropriately
Privileged Delegation Setting will be generated by itself
(put the credentials by clicking the + symbol & put the right credentials otherwise will get the user name &
password error at the time of initialization)
12. Agent installation will start. Review the errors if it fails and take the appropriate actions.
13. At last when it will prompt you need to run the root.sh script from the location which it will prompt.
14. After completing the agent installation check the status of the OEM agent in the agent_home/bin directory.
The successful installation page will appear as follows –
15. For PROD OEM – the agent installation fails at securing the agent because of some SLB issues. Please execute
following commands from the AGENT_HOME of target server on which agent is getting installed. During sercure
, it will prompt for the registration password. The password is is jdsudba.
Choose the oracle Database listener and Automatic Storage Management from the Drop down list.
Put the server name on the Host Location & Click Search
Select the server name which will be appear and then click on the select. & then Click NEXT
All the Targets Will be appear at this Location put the DBSNMP Password And add all the Targets to the Correct group
and click on the Test Connection and click Next all the Targets will be Added in the Agent
After Some time Go to targets -- > all targets ( it will show all the targets which are up and running in oem agent )
CREATE OEM AGENT BLACKOUT
Create the Blackout of the OEM Agent Enterprise Monitoring Blackouts
Put the Comments by which we can understand why black out created
Select on all the Targets from the Drop_down list and simple click select
Then Click Next
Next
Do not Click on the INDEFINATE from the Duration Column (we never take the indefinite in duration).
(Always click on the Immediately and then Length for how many hours you need to keep at agent in blackout)
Now Just Review it and Click on Finish
For the Some Minutes the Blackout Name will be appear in the Future ( Show -> Active , Future )
Do not start the activity until it comes in the Active area , because if it will be in future and you start the activity then the
Alert will still come , so wait for few minutes and let it be come in the Active Area . in the Show .
### Now OEM Agent is blackout And you can Proceed with your Activity ####