Noticed an article on ReadWriteWeb a few weeks ago listing free SQL E-Books . Not all Oracle related but a couple seem interesting.
http://www.readwriteweb.com/hack/2011/06/free-e-books-on-sql.php
Thursday
Wednesday
Grid Control – Refreshing Weblogic Domains
WebLogic domains, especially SOA, tend to be very dynamic. Over time new applications may be deployed or others upgraded to the latest release, SOA partitions created/deleted, BPEL processes new/updated/deleted, etc. By default, Grid control is not aware of these changes. This can be a problem if you use grid control to centrally manage/monitor your environment. There are two options available to you:
1. Manually refresh the weblogic domain.
2. Enable Automatic Refresh
Manually refreshing a Weblogic Domain
One of the places this can be done is from the WebLogic Domain drop down menu, click on Refresh WebLogic Domain.
The following screen will appear, click on Continue.
After you click on continue target discovery will take place and a confirmation window will show how many targets were found:
After you click on close you’ll be brought to the assign agents screen. I’m not aware of any reason why you would want to reassign to a different agent, so I just continued by clicking on Add Targets.
Once you have made any changes, if necessary, above click on add targets to save the changes.
Automatically refreshing a Weblogic Domain
If your environment changes quite frequently you may want to enable an automatic refresh. To do this login to Grid Control, click on the Targets Table, Middleware section and select the domain you wish to make the change for.
Notice above that my domain was last refreshed Apr. 1st. Click on the timestamp next to WebLogic Domain Refreshed and the following window will appear:
After you click ok, a confirmation message will be displayed saying that it was successfully scheduled:
If you click on the timestamp above next to Weblogic Domain Refreshed again:
You can click on the job name and it will bring you to the Job Activity section of Grid Control. From here you can change the schedule of the refresh, etc.
Thats it, pretty simple. I prefer to use the manual method because it provides a summary of the new or modified targets, which you don't get by scheduling it automatically. I haven't checked the Grid Control job logs tho to see if that information is included there.
1. Manually refresh the weblogic domain.
2. Enable Automatic Refresh
Manually refreshing a Weblogic Domain
One of the places this can be done is from the WebLogic Domain drop down menu, click on Refresh WebLogic Domain.
The following screen will appear, click on Continue.
After you click on continue target discovery will take place and a confirmation window will show how many targets were found:
After you click on close you’ll be brought to the assign agents screen. I’m not aware of any reason why you would want to reassign to a different agent, so I just continued by clicking on Add Targets.
Once you have made any changes, if necessary, above click on add targets to save the changes.
Automatically refreshing a Weblogic Domain
If your environment changes quite frequently you may want to enable an automatic refresh. To do this login to Grid Control, click on the Targets Table, Middleware section and select the domain you wish to make the change for.
Notice above that my domain was last refreshed Apr. 1st. Click on the timestamp next to WebLogic Domain Refreshed and the following window will appear:
After you click ok, a confirmation message will be displayed saying that it was successfully scheduled:
If you click on the timestamp above next to Weblogic Domain Refreshed again:
You can click on the job name and it will bring you to the Job Activity section of Grid Control. From here you can change the schedule of the refresh, etc.
Thats it, pretty simple. I prefer to use the manual method because it provides a summary of the new or modified targets, which you don't get by scheduling it automatically. I haven't checked the Grid Control job logs tho to see if that information is included there.
Friday
Grid Control 11g–Blocked Agents
Today I noticed that one of my Grid Control agents was down. From the Grid Control homepage for the target:
I thought it had just crashed so I checked the status from the server:
[oracle@myserver bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home : /u01/app/oracle/product/grid11g/agent11g
Agent binaries : /u01/app/oracle/product/grid11g/agent11g
Agent Process ID : 29687
Parent Process ID : 29661
Agent URL : https://myserver:3872/emd/main/
Repository URL : https://myserver:4900/em/upload
Started at : 2011-06-23 02:06:56
Started by user : oracle
Last Reload : 2011-06-23 02:06:56
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 432
Size of XML files pending upload(MB) : 52.54
Available disk space on upload filesystem : 2.74%
Collection Status : Disabled by Upload Manager
Last attempted heartbeat to OMS : 2011-06-24 10:37:34
Last successful heartbeat to OMS : unknown
---------------------------------------------------------------
Agent is Running and Ready
Notice the “Last successful heartbeat to OMS” is unknown. If I try and force an upload it errors:
[oracle@myserver bin]$ ./emctl upload
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors.
Checking the agent logs ($GRID_HOME/agent11g/sysman/log/emagent.trc):
2011-06-24 10:40:03,074 Thread-1091160384 ERROR pingManager: Did not receive valid response to ping "ERROR-Agent is blocked. Blocked reason is: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console. Please contact EM adminstrator to unblock the agent"
So the agent is out of sync with with the repository and is now blocked. I remember back in the 9i days to clean up an agent was a bit of a pain but in 11g its pretty simple. Log back into Grid Control, click on the Setup link located in the top right hand corner. Next click on the Agents link in the blue bar, followed by the Misconfiguration Alerts and Blocked Agents tab.
If you click on the agent itself (instead of selecting it and clicking unblock) you will be brought to the agents page shown below:
To resynch it click on the Agent Resynchronization button.
Make sure the Unblock agent on successful completion… is selected and hit continue. Once completed you may notice that the agent is still showing as unreachable. If you check via the server again you’ll notice that its working fine. Notice the Last successful heartbeat and last successful upload rows.
[oracle@myserver bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
.
.
Last successful upload : 2011-06-24 10:44:36
Total Megabytes of XML files uploaded so far : 19.37
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 2.76%
Last successful heartbeat to OMS : 2011-06-24 10:44:04
---------------------------------------------------------------
Agent is Running and Ready
After a short period of time it will show as up in the Grid Control Console as well.
I thought it had just crashed so I checked the status from the server:
[oracle@myserver bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home : /u01/app/oracle/product/grid11g/agent11g
Agent binaries : /u01/app/oracle/product/grid11g/agent11g
Agent Process ID : 29687
Parent Process ID : 29661
Agent URL : https://myserver:3872/emd/main/
Repository URL : https://myserver:4900/em/upload
Started at : 2011-06-23 02:06:56
Started by user : oracle
Last Reload : 2011-06-23 02:06:56
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 432
Size of XML files pending upload(MB) : 52.54
Available disk space on upload filesystem : 2.74%
Collection Status : Disabled by Upload Manager
Last attempted heartbeat to OMS : 2011-06-24 10:37:34
Last successful heartbeat to OMS : unknown
---------------------------------------------------------------
Agent is Running and Ready
Notice the “Last successful heartbeat to OMS” is unknown. If I try and force an upload it errors:
[oracle@myserver bin]$ ./emctl upload
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors.
Checking the agent logs ($GRID_HOME/agent11g/sysman/log/emagent.trc):
2011-06-24 10:40:03,074 Thread-1091160384 ERROR pingManager: Did not receive valid response to ping "ERROR-Agent is blocked. Blocked reason is: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console. Please contact EM adminstrator to unblock the agent"
So the agent is out of sync with with the repository and is now blocked. I remember back in the 9i days to clean up an agent was a bit of a pain but in 11g its pretty simple. Log back into Grid Control, click on the Setup link located in the top right hand corner. Next click on the Agents link in the blue bar, followed by the Misconfiguration Alerts and Blocked Agents tab.
If you click on the agent itself (instead of selecting it and clicking unblock) you will be brought to the agents page shown below:
To resynch it click on the Agent Resynchronization button.
Make sure the Unblock agent on successful completion… is selected and hit continue. Once completed you may notice that the agent is still showing as unreachable. If you check via the server again you’ll notice that its working fine. Notice the Last successful heartbeat and last successful upload rows.
[oracle@myserver bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
.
.
Last successful upload : 2011-06-24 10:44:36
Total Megabytes of XML files uploaded so far : 19.37
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 2.76%
Last successful heartbeat to OMS : 2011-06-24 10:44:04
---------------------------------------------------------------
Agent is Running and Ready
After a short period of time it will show as up in the Grid Control Console as well.
Subscribe to:
Posts (Atom)