Do I need license to patch agent through grid control deployment wizard

In grid control, we have license to use database diagnostics pack and database tuning pack.
I know wihtout license for provision pack, I cannot patch database homes using grid control deployment tab. But I'm wondering if I can patch grid control agent through deployment page without license for the prvision pack.
thanks

There is no management pack license needed for patching the agent. You can get clear details what link needs what packs when you click on '+' symbol (Show Management Pack Information) right to the "About Oracle Enterprise Manager" at the extreme down on OEM screen.
When you click on "Show Management Pack Information", it will show what pack needed next to every link in paranthesis. If there is no pack information mentioned next to link means, there is no license needed for that link.

Similar Messages

Installing Oracle Agent through Grid Control!

Hi,
Can we install oracle agent on Solaris through Grid control which is located on Linux?
Thanks
Azam

before you can use the agents (the deployment will succeed) you need to apply 2 patches on OMS home.
Check metalink note: How to Deploy the Latest Database Plugin to the OMS and the Agent in 12C Cloud Control [ID 1388143.1]
it explains how you can apply the prerequisite patches and deploy the agents for Solaris and AIX (the current available agents).
Daniel.

How to delete archive log files from ASM through Grid Control

Hi
Anybody suggest me how to delete archive log files from ASM through Grid Control.
Thanks

It is important to specify both, the oracle version and os version when posting, so confusions can be avoided.
In this particular case, since you are referring to asm and grid control you could be talking about either 10gR1, 10gR2 or 11gR1; but I strongly suggest you to avoid us to be guessing. In either case, you sould go to the maintenance tab of the target database and program a scheduled 'delete noprompt obsolete;' procedure. This will purge the information stored at the Flash recovery area, which I assume you have declared inside the ASM.
~ Madrid
http://hrivera99.blogspot.com/

Monitor Linux Services through grid control 10g

Hi Experts,
Is there a way to monitor a linux service like samba/nfs/cups through grid control 10g. I mean if it could monitor status of these services and send a down alert if they re not running. I have large farm of linux servers being monitored by grid and most of them run these services so i was looking towards monitoring them through grid.
Let me know any ideas to accomplish this.
Thanks in advance.
Rohan

Hi Rob,
Thanks for the reply. I am new to GC. I cant find a setting while creating new metrics in grid to monitor a Linux service. Can you tell steps in brief to do this, or else is there any guide i can follow to create a plugin for grid control to discover a new type of target.
Thanks,
Rohan

How to delete a management agent from grid control completely?

I have installed oem grid control 10.2.0.4.0 on single host(oemlinux.oracle.com), and I removed agent10g, and reinstall a new management agent into a new location, but when I wanted to add a weblogic server to monitor, I got error as below:
More than one Enterprise Manager Agent was found for the host.oemlinux.oracle.com
I found there were 2 agents in em console, how to delete the old agent from em console,anybody can help me?

Click on the All targets tab, delete the agent.
Then confirm that the delete is in fact happening.
Click Setup, Management & Services Repository tab.
Deleted Targets link.
Time Deleted Completed must have a date in there...
If all that fails - do a quick search - I posted the sql you can run against the repository to wipe it clean of an agent :-)
Not too that if you are removing the O/S software - you need to use the runinstaller to remove the Oracle Home from the inventory.
If you don't do this - future auto installs using the agentDownload script of the agent will fail.
.Daryl

Problemm with access agent on grid control

Hi guys..
I successfully installed oracle 10g release 2 GC on sun solaris (sparc) 10. To access the console, if I do use http://192.168.0.1:4889/em, it doesnt work. Then when I use the machine name http://zone1.test.com:4889/em it did work. Since there isnt any DNS to resolve hostname from ip, had to add an entry in the etc/hosts before it works.
Now here comes the pb.
We have 8i db (on sparc solaris 8), 9i dbs (on sparc solaris 8, 9, 10; on windows Xp, and on windows 2003 server) and 10g dbs (on sparc solaris 8, 9, 10; on windows Xp, and on windows 2003 server). I would like to use the GC installed on the solaris above as my centralized server for monitoring all our dbs.
What I have to do is to install oracel GC agent on each machine running oracle. (but mai first question is which version to install? release 1 or release 2)??
So for a begining, I installed oracle 10g release 2 agent on a windows machine runing oracle 10g database. It asked me for the server name, port and password (as the server is running in secure mode). The installation went ok but when I did access the grid control on the server side, I cant see the host or db on the target.
Can any one let me know what happen or how ai could fix this?
does ai need to add the ip and name of the windows machine in the /etc/hosts of the GC server so that it can resolve it?
Any input is welcome.
Junior DBA in distress.

thanks for the reply mnazim.
where is the emagent.trc and emoms.trc found? it is
on the server or client (agent) side?
here is another question!
to start and stop all services on GC I saw from one
website that we do the following.
# Start everything
/u01/app/oracle/product/10.1.0/oms/bin/emctl start agent
You do not need to start agent from OMS_HOME
/u01/app/oracle/product/10.1.0/oms/opmn/bin/opmnctl startall
/u01/app/oracle/product/10.1.0/agent/bin/emctl start agent
The above two are OK
>
# Stop everything
/u01/app/oracle/product/10.1.0/agent/bin/emctl stop agent
/u01/app/oracle/product/10.1.0/oms/opmn/bin/opmnctl stopall
The above two are OK
/u01/app/oracle/product/10.1.0/oms/bin/emctl stop agent
You do not need to stop agent from OMS_HOME
now is this the same with
/u01/app/oracle/product/10.1.0/agent/bin/emctl start
oms (to start everything) and
/u01/app/oracle/product/10.1.0/agent/bin/emctl stop
oms (to end everything) ????
No it is not the same.

Topology diagram of installed agents on grid control

Hi,
Can anyone help. I have grid control with a number of clients (agents) installed. Does anyone know of a way to get a topology diagram out of grid which shows all the connected systems.
regards
Alan

Hi Alan,
You might find the following post is helpful. That's a introduction for a tool to show topology diagram for Oracle Application Server. FYI.
[http://www.oraclepoint.com/topic_600]
R.Wang
[http://www.oraclepoint.com]

Datapump through grid control 12C

hi,
I have created a schema in database which has exp_full_database privilege to run datapump jobs (verified by running a datapump API job too). I have a os user(non dba group) which has ability to run expdp command.
I also created an administrator in grid 12C which has connect to target privilege on database target and execute any command privilege on host. However when I submit a datapump job using these credentails, the submission of job fails with error message as "user doesn't have privilege for this operation".
I am able to execute datapump API successfully from within database schema; using the on dba group os user, I am able to execute expdp command too successfully..
What am i missing? please help.

It sounds like your Data Pump command is referencing the EM user instead of the schema owner. Look at the output log of the job; if you see "ORA-01031: insufficient privileges" then this is likely the case. The EM admin only needs sufficient privileges to exec the job; Data Pump is responsible for the database access and privileges.
Edited by: pschwart on Mar 14, 2013 5:59 PM

Creating physical standby db through grid control 11g fails with "default listener is not running"

On step 4/6, i am getting error like below
ErrorExamine and correct the following error(s), then re-try the operation.Default Listener in Grid Infrastructure - The default listener in the grid infrastucture is not running.
I have the listener running on grid user and grid home, 11.2 in both primary and standby.
During these steps till 4, its no where asked for grid user password.
Not sure how it will detect the grid home listener.
Listener is running with default port 1521 on both the servers primary and standby
On the step 4 screen the other option for default listener is non-default listener and its pointing to db home and not grid home.
So i guess oracle is looking for the listener to be up on the db home and not on grid home causing the issues,
if so how to fix this ?
I am using role separation, separate user for grid and oracle homes grid and oracle user and all are on 11.2.0.1 db + grid

Hello again;
Check the solution in this: ( and note the multiple versions of oracle it covers )
UNABLE TO FIND GRID INFRASTRUCTURE LISTENER (Doc ID 1483234.1)
Best Regards
mseberg

Creating standby database through Grid Control.

Hi,
I want to know if source database which we term as primary database goes down during Db creation process when given option of "Perform a live backup of primary database" during Add standby wizard in Grid Control. Please let me know if people have already tested it in their environments.
I appreciate you all for looking into my forum.
Regards,
Gaurav

No, one of the options for performing this task is to create from a Live db.
A couple of things to note here:
You must be using spfile
If you are not using the default port of 1521 then you must also have the local_listener parm set
I recommend using the "db_unique_name" option to make it easier to manager in OEM (for the target name)
Hope this helps,
Landon

Agent running but host unavailable in grid control

hi,
well yet another question, am having a bad day with grid control.
I have pushed an agent out to server xxx and the agent is now monitored through grid control however, the host remains unavailable. I have done agentca -d and -f, the agent is secure. Can anyone help out?
rgds
Alan

hi,
yes emctl status show everything is fine. Other targets have shown up in GC successfully.
At present I cannot find an emoms.trc file. I will post back if I can work out where it is.
rgds
Alan

Grid Control 에서 새 target node를 추가한 이후에 기존OMS와 새 Agent 간의 HeartBeat fail 해결방

Grid Control 에서 새 target node를 추가한 이후에 기존OMS와 새 Agent 간의 HeartBeat fail 해결방법
=========================================================================
다음은 Grid Control 을 설치한 이후에 node를 관리해 오다가 새로운 관리할 Target node를
추가한 이후에 Grid Control 이 있는 node의 OMS와 새로 추가한 node의 Agent가 HeartBeat 통신
실패 시에 해결책을 소개하고 있습니다.
Problem Description
Grid Control 에서 새로운 node를 추가한 다음에 그 새로운 node 에서
emctl status agent 명령 수행 시 다음과 같은 에러가 발생합니다.
Environment :
mesdev01 : 새로 추가한 Agent가 있는 node명
mesdev02 : 'Central Grid Agent' 존재 & 'Repository database가 존재하는 node'
새로 추가한 node에서 아래와 같이 emctl status agent 명령을 수행합니다.
그런데, OMS에 대한 HeartBeat fail 이 발생했음을 알 수 있습니다.
[mesdev01:/oracle/app/oracle/product/agent10g/bin] emctl status agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.3.0
Proto Version : 10.2.0.2.0
Agent Home : /oracle/app/oracle/product/agent10g
Agent binaries : /oracle/app/oracle/product/agent10g
Agent Process ID : 10526
Parent Process ID : 10511
Agent URL : http://mesdev01:3872/emd/main/
Repository URL : http://mesdev02:4889/em/upload/
Started at : 2007-12-28 10:36:59
Started by user : oracle
Last Reload : 2007-12-28 10:36:59
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 287
Size of XML files pending upload(MB) : 26.40
Available disk space on upload filesystem : 40.44%
Last attempted heartbeat to OMS : 2007-12-28 14:13:36
Last successful heartbeat to OMS : unknown <===
여기서 주목할 만한 에러는 Last successful heartbeat to OMS 체크 시 status가
unknown 으로 보인다는 것입니다.
에러 증상
emctl status agent 수행 시 Last successful heartbeat to OMS : unknown
또는 agent 에서 OMS의 Status를 알 수 없다는 아래의 에러가 보이는 경우임.
Note: "The OMS status is Unknown"
Explanation
이러한 에러는 주로 agent가 node에 새로(newly) install 된 경우 발생합니다.
원래 communication 이 정상적으로 보인다면 다음과 같이 수행 결과가 나와야 합니다.
다음은 Repository database가 존재하는 mesdev02 node에서 emctl status agent를 수행한 결과
성공적으로 보이는 결과입니다.
mesdev02:/u01/app/oracle/OracleHomes/agent10g/bin$ emctl status agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.3.0
Proto Version : 10.2.0.2.0
Agent Home : /u01/app/oracle/OracleHomes/agent10g
Agent binaries : /u01/app/oracle/OracleHomes/agent10g
Agent Process ID : 29307
Parent Process ID : 29300
Agent URL : https://mesdev02:3872/emd/main/
Repository URL : https://mesdev02:1159/em/upload
Started at : 2007-12-27 11:29:22
Started by user : oracle
Last Reload : 2007-12-27 17:57:18
Last successful upload : 2007-12-28 15:02:09
Total Megabytes of XML files uploaded so far : 48.78
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 38.29%
Last successful heartbeat to OMS : 2007-12-28 15:02:59 <====
Agent is Running and Ready
원인
이 에러가 발생하는 원인은 새로 추가한 database의 Agent process가 GRID Control 이
install된 main server의 OMS와 연결되지 않기 때문인데, 이렇게 새로운 node를 추가한 이후에
수행해줘야 할 절차가 있습니다.
OMS_HOME/sysman/log 의 secure.log 를 확인해 보면 OMS is "secure locked" 라는 에러가 보입니다.
The OMS is "secure locked", then the agent also needs to be secure.
[ 사전 check 사항 ]
1. 두 node 모두 DNS server에 등록되어 있는지 확인한다.
2. 두 node 모두 쌍방 간에 /etc/hosts file에 서로의 ip address와 hostname을 넣어준다.
위 두가지 check 사항이 충족된 경우에도 발생한다면 새로 추가한 node 쪽에서 자신의 정보를
OMS(즉, Repository node) 에게 정보를 upload하지 않았기 때문입니다.
Upload를 하는 방법은 간단하게 아래와 같은 emctl upload agent 라는 명령으로 가능합니다.
emctl upload agent
Upload를 하게 될 때 그 정보는 XML 형태로 중앙 Repository에 저장됩니다.
Solution Description
아래 절차 중에 1번만 Grid Control이 설치된 OMS server에서 수행을 하고,
2번~7번까지는 새로 추가한 Agent node에서 수행합니다.
1. On oms server: (Grid Control 이 설치된 서버에서 수행)
<OMS_HOME>/bin/emctl status oms -secure
OMS node인 mesdev02 node에서 우선 emctl status oms -secure 를 수행합니다.
mesdev02:/u01/app/oracle$$OMS_HOME/bin/emctl status oms -secure
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Checking the security status of the OMS at location set in /u01/app/oracle/OracleHomes/oms10g/sysman/config/emoms.properties... Done.
OMS is secure on HTTPS Port 1159
2. Stop Agent: Agent를 설치한 node에서 수행합니다.
<AGENT_HOME>/bin/emctl stop agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl stop agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Stopping agent ... stopped.
3. Verify no residue emagent processes running:
이와 같은 명령으로 남아 있는 emagent process가 있는지 확인합니다.
ps -ef|grep emagent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]ps -ef|grep emagent
oracle 4353 3125 0 16:19:34 pts/tb 0:00 grep emagent
4. If running secure please resecure agent on :
<AGENT_HOME>/bin/emctl secure agent
emctl secure agent 를 수행하는 목적은 모든 agent에 대해서 secure communication 을
하기 위해 필요합니다.
[ 주의사항 ]
emctl secure agent 명령은 Grid Control installation 과정에서
--> 'Specify Security Options' 단계에서
--> Management Service Security 항목에서
--> OMS와 함께 Secure Communication을 하고자 하는 agent에 password 설정을 하는데,
--> Require Secure Communication for all agents 를 check 표시하였다면
install 이후에 아래와 같이 emctl secure agent 명령을 수행하여야 합니다.
(기본적으로 Require Secure Communication for all agents는 enable되어야 함).
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl secure agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Enter Agent Registration password :
Agent is already stopped... Done.
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Done.
Requesting an Oracle Wallet and Agent Key from the OMS... Done.
Check if HTTPS Upload URL is accessible from the agent... Done.
Configuring Agent for HTTPS in CENTRAL_AGENT mode... Done.
EMD_URL set in /oracle/app/oracle/product/agent10g/sysman/config/emd.properties
Securing agent... Successful.
5. 4번 단계가 정상적으로 완료되면 이제 Agent를 기동합니다.
Start Agent
<AGENT_HOME>/bin/emctl start agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl start agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Starting agent ................................. started but not ready.
6. Then verify upload works
<AGENT_HOME>/bin/emctl upload agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl upload agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
EMD upload error: Upload timedout before completion
==> timedout 메시지는 warning으로 보이며, 운영에는 지장이 없습니다.
7. 다시 확인 차 emctl status agent 명령을 수행해 봅니다.
Then run status of agent
<AGENT_HOME>/bin/emctl status agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl status agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.3.0
Proto Version : 10.2.0.2.0
Agent Home : /oracle/app/oracle/product/agent10g
Agent binaries : /oracle/app/oracle/product/agent10g
Agent Process ID : 4618
Parent Process ID : 4609
Agent URL : https://mesdev01:3872/emd/main/
Repository URL : https://mesdev02:1159/em/upload
Started at : 2008-01-02 16:21:03
Started by user : oracle
Last Reload : 2008-01-02 16:21:03
Last successful upload : 2008-01-02 16:25:37
Total Megabytes of XML files uploaded so far : 54.28
Number of XML files pending upload : 40
Size of XML files pending upload(MB) : 0.97
Available disk space on upload filesystem : 37.22%
Collection Status : Disabled by Upload Manager
Last successful heartbeat to OMS : 2008-01-02 16:24:49 <== success!
Agent is Running and Ready
[mesdev01:/oracle/app/oracle/product/agent10g/bin]
8. 만약 Last successful heartbeat to OMS 에 위와 같은 success로 보이지 않으면
step 1부터 7까지 수행된 모든 output 을 수집하여 문의를 합니다.
9. 그리고, debugging을 위해 다음의 log 화일들을 보관하시기 바랍니다.
<OMS_HOME>/sysman/log
<OMS_HOME>/sysman/log 의 secure.log가 특히 중요합니다.
<AGENT_HOME>/sysman/log
References
Note 458033.1
Title:Problem: Agent Upload Fails: OMS Is Locked and Agent not Secured

EM Grid Control - Licensing

Hello,
I've read the licensing and understand that the grid control/repository is free. What I did not find is how one can use this.
In example, if I have several clients who have production database. Can I setup a grid in my company and just setup the agents to my clients database servers and have them feed my grid control? As in the scenario is there a difference between a 1 man company(consultant) and a service company with many dba?
Or is the licensing orientated around the concept of 1 company, many internal database,1 internal grid control?
Thanks
/Jan

I believe the use of Grid Control itself is free, but you have to buy the extra packs if you use them (e.g. change management, configuration management and tuning packs).
As for the repository:
A separate Oracle Database can be installed and used as a Oracle Enterprise Manager Grid Control (OEM Grid Control) repository without additional license requirements, provided that all the targets (databases, applications, and so forth) managed in this repository are correctly licensed. This database may also be used for the RMAN repository. It may not be used or deployed for other uses.
http://download.oracle.com/docs/cd/E11882_01/license.112/e10594/editions.htm#BABDJGGI
In your case, the orientation is on the company for which the Grid control is monitoring the databases for (in your case per customer).
When you choose the setup you describe, you end up paying for your own Oracle Database Enterprise Edition license for using OEM (as this is your 'property').
You might also consider good firewalling in this, as i don't think customers like it when they can see each others servers / network... ;)

Installing Grid Control and its agents in RAC

Hi
I have a RAC of 2 nodes in 10.2.0.5 . I need to install Grid Control in another server to manage the RAC.
I have several questions....
The agent and grid control to be install has to be in 10.2.0.5 as well ? or must be higher...
I have to install the agent in all nodes of the RAC ? and after the grid control in another server ?
Thanks

WAIT...
I was thinking same that Grid Installer will create the databasse or you can use the one if exists..
but when I was reading a similar thread.. The Grid control installer has inside an Oracle Server ?
someone mentioned that Grid Installer will not create repository database.
It is better if you refer the document before make any further comments.

Unable to discover agent in grid!

Hi,
We have Oracle 11g grid up and running. I was installing agent on the target servers using `agent push` method (using deployment wizard of grid). At the end of the installation I got an error "Install: failed" but when I navigated to HOME tab in the grid, I could see the new server. Great!!! Then I installed agent using same method on other server(i will call it X). Again install failed but this time server X did not appear in the discovered targets list. Both the servers i.e. grid and server X are in two different network(i guess). OS and db version on both the servers are same. Below is the ip address of both servers:
grid : 10.101.248.123
server X : 10.106.8.117
Is this an issue? Any suggestions?
-Onkar

If "AGENT_BASE_DIR" is empty, that means the Agent push failed at the initial stage of copying the binaries from
OMS host to Agent Host and so empty folder. Agent may need to be installed again using below document to install 11g Agent with Silent method.
http://docs.oracle.com/cd/E11857_01/install.111/e16847/install_agent_usng_rsp.htm#CEGGACJE
All the prerequisties must be checked carefully and make sure that the system satisfy all of them and then proceed with the installation.
The prerequisite are listed :
http://docs.oracle.com/cd/E11857_01/install.111/e16847/install_agent_usng_rsp.htm#CEGIAADH
The silent installation may failed if "OMS_PORT set to the secure upload port (HTTPS) instead of unsecure upload port (HTTP)
in the response file."
To resolve the issue, kindly follow the below steps:
[*] Change OMS_PORT to the unsecure (HTTP) upload port in the response file.
This can be obtained from the output of :
<OMS_HOME>/bin/emctl status oms -details[*] Keep all the parameters value with-in double quotes ("") except for Boolean values (True / False).
For example:
OMS_HOST="<OMS Host server name>"
OMS_PORT="4900"
AGENT_REGISTRATION_PASSWORD="<password>"After installation, agent should be discovered in the grid if not then
* From OMS machine [grid1.company.com] to Agent machine [machine1.company.com]:
ping <full host where agent is installed ex. machine1.company.com>
ping machine1
ping <IP Address of machine1.company.com>
nslookup <full host where agent is installed ex. machine1.company.com>
nslookup machine1
nslookup <IP Address of machine1.company.com>[+] From Agent machine [machine1.company.com] to OMS machine [grid1.company.com]:
ping <full host name where OMS is installed ex: grid1.company.com>
ping grid1
ping <IP Address of grid1.company.com>
nslookup grid1.company.com
nslookup grid1
nslookup <IP Address of grid1.company.com>
telnet grid1.company.com 4889
telnet grid1 4889
telnet <IP Address of grid1.company.com> 4889If all the connection seems to be correct, then kindly make the changes in additional_agent.rsp file as:
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=trueand then re-try the silent installation.
It worked for me.

Do I need license to patch agent through grid control deployment wizard

Similar Messages

Maybe you are looking for