OEM
The following Metalink article covers the EM Harvester utility: 1126022.1.
We followed this, and note 988063.1 which describes installing the latest OCM patch to the OMS home. To perform the de-installation of the previous version, we followed note 369619.1 (section “uninstalling/removal”) plus an additional undocumented step noted below (part of step 6).
A summary of all the steps is given below:
Reinstall OCM:
1. Stop the OCM utility from the OMS middle-tier oracle home thus:
$ORACLE_HOME/ccr/bin/emCCR stop
2. Connect to the EM repository database via SQL*Plus as SYSDBA, and execute the following steps (note that the scripts are found under the OMS middle-tier oracle home, NOT the database oracle home):
$ORACLE_HOME/ccr/admin/scripts/dropocm.sql
$ORACLE_HOME/ccr/admin/scripts/dropemrep_collect.sql
3. Stop the OCM scheduler from the OMS middle-tier oracle home thus:
$ORACLE_HOME/ccr/bin/deployPackages –d $ORACLE_HOME/ccr/inventory/core.jar
4. Remove any OCM crontab entries if they are present.
5. Rename the existing ccr directory under the OMS middle-tier oracle home to ccr_old (or something else appropriate).
6. Remove the state and config sub-directories from $ORACLE_CONFIG_HOME/sysman.
* Note: this is an undocumented step but is required, otherwise subsequent setupCCR commands will fail.
* Note: ORACLE_CONFIG_HOME is NOT the OMS middle-tier oracle home, but the grid-control installation oracle home.
7. From My Oracle Support dashboard click 'More..' subtab and select 'Collector'. Choose your platform and download 10.3.2 OCM Collector.
*** Note: this is now up to version 10.3.5.
8. Extract the downloaded zip file into the OMS middle-tier oracle home. This will create new ccr sub-directory.
9. Install and configure OCM Collector in the OMS middle-tier oracle home:
./setupCCR -s CSInumber email.address@company.com CountryCode
Thus:
./setupCCR -s 14284591 deepak.kachole@abc.com GB
| Overview of the GridControl Harvester as an EM Job [ID 1126022.1] | ||
| Modified 29-MAR-2011 Type FAQ Status PUBLISHED | ||
In this Document
Applies to:
Oracle Configuration Manager - Version: 10.3.2.0 to 10.3.2.0
Information in this document applies to any platform.
The Harvester is a new Grid Control EM job that was introduced in Enterprise Manager for Grid Control(EMGC) 10.2.0.5.0. This is another collection mechanism now available in EMGC10205 which is a subset of the external standalone OCM collector.
GridControl Harvester FAQ
The Harvester is a new Grid Control EM job that was introduced in Enterprise Manager for Grid Control(EMGC) 10.2.0.5.0. This is another collection mechanism now available in EMGC10205 which is a subset of the external standalone OCM collector. This new job is not accessible from within EMGC but runs in the background automatically once the Oracle Configuration Manager (OCM) collector(s) are configured in the OMS_HOME(s) in connected mode. This new EM job collects data from the EMGC repository. The data in the EMGC repository is collected by the EMGC agents on each host and uploaded to the EMGC repository already instead of having to configure OCM collectors in each Oracle Home. The EM job runs at 2:00 AM local time and the data is then stored in the $OMS_HOME/ccr/hosts/<hostname>/state/upload/external directory in 10 sub-directories, 1-10. This data is stored on the operating system via xml format so therefore data can be reviewed via a browser before it is uploaded to Oracle. This data is then uploaded as part of the data uploaded when the OCM collector makes its next scheduled collection and upload to Oracle. There is no manual method of running the Harvester job to force an upload to Oracle as with the OCM collector.
The data collected by the Harvester is uploaded to Oracle and it has time stamp that is checked and compared to the time stamp from any existing OCM collection data uploaded. If the OCM time stamp is less than 30 days it has precedence over the Harvester collection and that data is uploaded. Once the difference is greater than 30 days the Harvester data is uploaded.
Currently the Harvester only collects configuration data for the supported targets which are hosts, Oracle Homes, and all versions of Oracle Database and Oracle Application Server that are supported as EMGC managed targets.
A full deployment of EMGC includes the following components:
1. One or more Oracle Management Service (OMS) instances
2. An Oracle database used as the EMGC Repository
3. Management Agents deployed onto each host containing targets to be managed by EMGC
4. One Oracle Configuration Manager (OCM) collector per OMS instance configured in connected mode
The Harvester carries the advantage of simpler software deployment. The pure OCM model requires one instance of the OCM software in every Oracle Home. The EMGC infrastructure, on the other hand, requires one Management Agent on each host, thus potentially requiring many fewer deployments.
Stopping the OCM Collector stops the GCHarvestor data from being uploaded to Oracle. This can be done from the %OMS_Home/ccr/bin issuing the ‘emCCR stop’ command
No, Disconnected uploads are not supported by the Harvester Job.
Review the $OMS_HOME/ccr/hosts/<hostname>/log/collector.log file for failures to upload
Review the $OMS_HOME/sysman/log/emoms.trc file, search for harvester.
Follow the steps mentioned :
If the machine where OMS resides is connected to Internet, in order to configure OCM in connected mode run:
$ <OMS_ORACLE_HOME>/ccr/bin/setupCCR -s <CSI> <MyOracleSupportUserName> <Country-Code>
Fore more information about OCM, see:
'Oracle Configuration Manager Quick Start Guide' available at:
Yes, as of Grid Control Release 10.2.0.5 and later and OCM 10.3.2 and later, the GCHarvester data will be available for patch recommendations
The GC Harvester Errors with "installed version of Oracle Configuration Manager in the ORACLE_HOME is prior to 10.3.1. The Grid Control Configuration harvesting requires at a minimum, 10.3.1"
Reconfigure the OCM collector in the OMS Home
Follow the steps mentioned in Note 988063.1.
In the Management Services and Repository > Errors, you see the error below:
The file <OMS_HOME>/sysman/log/emoms.trc file shows:
<timestamp> [JobWorker 32180:Thread-29] ERROR gcharvester.GcCollectionMgr initOcm.? - GC OCM Harvester: Caught GC Harvester exception from GCInit.init(): Unexpected error in getting hostname
<timestamp> [JobWorker 35518:Thread-36] ERROR gcharvester.GCInit getHostname.? - Unexpected error java.io.IOException: java.io.IOException: /opt/oracle/oms10g/ccr/lib/emocmutl: cannot execute
at java.lang.UNIXProcess.(UNIXProcess.java:143)
The reason is <OMS_HOME>/ccr/lib/emocmutl file does not have execute permission so please ensure :
The executable bit is set for these files:
<OMS_HOME>/ccr/lib/emocmutl
<OMS_HOME>/ccr/lib/emlogger
<OMS_HOME>/ccr/lib/emCCRCollector
<OMS_HOME>/ccr/lib/getdbinfo
| How To Workaround The GCHarvester 30 Days Upload Grace Period [ID 1308224.1] | ||
| Modified 12-SEP-2011 Type HOWTO Status PUBLISHED | ||
In this Document
Applies to:
Oracle Configuration Manager - Version: 10.3.5.0.0 to 10.3.5.0.0
Information in this document applies to any platform.
Currently, if a standalone OCM collector is removed or dropped, the GCHarvester waits for 30 days until it starts to collect and mine the new target data. There is now a way to gently force the GCHarvester to restart a collection in a GC environment outside of this 30 days window.
As of OCM 10.3.5 and Grid Control release 11.1.0.1, the 'GC Force' option is now available. This option is not dependent on the release of the OCM Collector itself. However, OCM Collector 10.3.5 is the most current version as of this posting and should be used.
In order to introduce the GC Force option, the following steps need to be implemented in the GridControl Repository as the Sysman user :
begin
delete from mgmt_ocm_upl_props where name = 'is_gc_force';
insert into mgmt_ocm_upl_props (name,str_value) values('is_gc_force','true');
delete from mgmt_ocm_upl_props where name = 'changes_ts';
commit;
end;
/
Once that has completed successfully, each and every OMS in the GridControl environment will need to be restarted.
On the next scheduled GCHarvester EM Job run, the GCHarvester will upload all new targets with the flag IS_GC='GC_FORCE'.
No comments:
Post a Comment