Grid Control jobs issue

Hi,
AIX, EMR3
Hi,
I'm testing a job scheduling from OEM - startups and shutdowns of monitored databases.
Immediate job execution works always, scheduled execution never works....
Any suggestions, troubleshooting ....
Thx,
Dobby

What errors do you get in the job status and what scheduled time does it show after the time has elapsed?

Similar Messages

Grid control switchover issue

Hi,
I have carried out the following
a 10g database install on 2 servers
enabled dataguard between them so I have a primary and a standby database.
I then installed Grid Control onto each server using the opetion to install into an existing database. this worked.
On the standby server opmnctl is shutdown and the database is a PHYSICAL STANDBY.
when I do a dataguard switchover I see the standby database is now the primary. I restart opmnctl and go to the web browser to look at Grid Control.
The issue I have is that Grid Control, even though it is on the standby server, points to the primary server. How can I change this behaviour
When I first started Grid Control I had to perform the following actions
[oracle@griddg bin]$ ./emctl status emkey
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key exists in the Management Repository, but is not configured properly or is corrupted in the file system.
Configure the Em Key by running "emctl config emkey -repos".
[oracle@griddg bin]$ ./emctl config emkey -repos
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key has been configured successfully.
after this gridcontrol was able to start but points to the wrong host.
rgds
alan

hi,
the steps I took are as follows
1 - precreate a database on the primary and standby.
2 - configure the tnsnames and listener files so that the databases can talk to each other
3 - create a standby control file from the primary database.
4 - copy all database files from the primary to the standby
5 - copy the standby controlfile to the standby
6 - start the primary database
7 - start the standby database but only mounted, check database_role from v$database; it should be physical standby
8 - install Grid Control on the primary server with the option to install onto an existing database. Complete this installation.
9 - Install Grid Control onto the standby server with the option to install onto an existing database. Complete the installation and then carry out an 'opmnctl stopall'
10 - all being well Grid Control should now show both hosts and databases.
11 - create a dataguard configuration from within GC
The standby database cannot be discovered correctly in GC and this must be because it is in a mount state, not sure what to do about this. This then meant that I had to carry out a switchover from the command line. I am just testing this now and will post back when complete.
regards
Alan

Grid Control access issue after ip change

Hi
The ip address of the server was changed. In this server there was repisotory database and OMS.
After that, I couldnt manage to start oms.
When I try:
opmnctl start all , I notice that it is hanging.
I also cannot display Grid Control url, however I can start repisotory database successfully.
Any recommendation?

I had the same problem, logged a TAR and waited several weeks, only to be told to resinstall OMS. That was 2 years ago with 10.2.0.3. There may be an article now on metalink which has the process. But I agree with the previous posts, the IP address is everywhere, so it's a real pain in the proverbial.

Dgutil.pl line 99 ERROR when creating 11.2.0.3 data guard via GRID CONTROL

Oracle Grid Control 11g Release 1 (11.1.0.1.0)
(64bit)
Oracle Enterprise Linux Server release 5.4 x86_64
Oracle Database 11.2.0.3 (64bit)
1. Grid Control>Targets>Databases
2.Click on pc01prmy (Primary)
3.Availability > Data Guard > Setup and Manage
4.Add Standby Database
5.Create a new physical standby database.
Fails with message:
38706 at /u01/app/oracle/agent11g/sysman/admin/scripts/db/dg/dgutil.pl line 99.
I can create a standby with a rman script without problems, but via the Grid Control page fails.
Have you seen this before?

I contact Oracle Support on this issue, here are the details.
Generic Note
Hi Marcelo, the note you sited Creating Standby Database With Enterprise Manager Failing [ID 1400482.1
Says something a little different than what you tried.
You did RECOVER DATABASE for manual recover and the error says use backup control file.
For a standby to do manual recovery it's
*alter database recover standby database ;*
It may behave better.
But the note implies to just apply enough redo to have the standby consistent enough to turn on flashback.
This can be done by starting managed recovery and applying some redo log sequences.
So the flashback being turned on is too soon, but should have worked anyway. I think it would turn on managed recovery though.
This also happens since the job doesn't use dorecover since recovery can be done with managed recovery.
So most likely there isn't enough activity on the primary and the online redo has not been archived yet.
So some log switches on the primary will send enough redo to get consistent so you can turn on flashback and finish it.
*So why did it happen?*
Possibly
Bug 13250486 - ADD STANDBY DATABASE FOR TARGET WITH FLASHBACK ON FAILS WITH ERROR
Base bug 12923814 FLASHBACK AND ARL DELETION OPTIONS IGNORED IN ADD STANDBY DATABASE WIZARD
fixed in Grid Control 12.1c
There is currently no patch available for 11.1.0.1 Grid Control. We would have to open a bug to confirm you hit this in 11.1.0.1 and get a patch.
*A workaround would be to turn off flashback at the primary then try to create the standby.*
*Once the standby is created you can turn flashback back on for the primary and if required, the standby.*
You can try again to see, or finish the standby manually as I stated above.
I will still need the diagnostic information below.
Action Plan
=========
The product verion in this SR is for 12.1.0.1 Grid Control. I assume it should be 11.1 since you stated it is.
Grid Control job log that shows the errors.
alert logs from the primary and standby.
Please run these two diagnostic scripts and upload the output.
Script to Collect Data Guard Primary Site Diagnostic (Doc ID 241374.1)
Script to Collect Data Guard Physical Standby Diagnostic (Doc ID 241438.1)
Edited by: Marcelo Marques - ESRI on Mar 24, 2012 9:51 AM

Oracle Grid Scheduled jobs disappear from active tab?

Thread was posted before as a similar situation.
Grid Control jobs disappeared from schedule
But was never answered;
For Grid control v10.2.0.3 Unix box.
I was wondering if this is a bug within OGC. Some of the scheduled jobs disappear from the active tab and have to be re-submitted. Does anyone or has anyone experienced this? Agents are in synch, and the only thing that was done was a bounce of the database and possibly the box itself.
Thanks,
Mark S.

Hi,
I have upgraded Discoverer 4i EUL to 10g EUL by using auto upgrade utility which comes with the Disocverer 10.1.2 and installed the Discoverer 10g Admin Edition on my PC. And I executed the batchusr_app.sql and assigned a user DISCREP(other than APPS). We are in APPS mode EUL. The script execution completed fine and the EUL5 packages were created under the DISCREP owner. When I log into the Discoverer Admin and select Tools/Privileges and at the point of assigning the result tables to a schema which is DISCREP, I am getting a message saying that 'EUL5_BATCH_REPOSITORY' package is wrong version and batchusr.sql script needs to be run. I ran the batchusr.sql script and when tried to assign the schema to own result tables it gave me the same message.
Any ideas. You may have gone through this during your upgrades or installation.
Thanks,
Sabbani

Problem in deleting backup job in Grid Control

Hi,
The topology and versions are as follows:
1 windows 2003 server with Oracle Grid Control 10.2.0.4.0.
1 windows 2003 server with Oracle Databases 10.2.0.3.
1 windows 2003 server with Oracle Databases 10.2.0.3 - Data Guard setup
I have tried to stop (and delete) some scheduled fullbackup jobs from Grid Control.
The job has now status SUSPEND. I have tried to stop and delete the job, but I get the message:
All executions of the job were stopped successfully. Currently running steps will not be stopped.
I cannot delete the job and the job is not running.
I have run this procedure in order to delete the job:
DECLARE
jguid RAW;
BEGIN
SELECT job_id
INTO jguid
FROM mgmt_job
WHERE job_name = '<name of your job>'
AND job_owner = '<owner of your job>';
mgmt_job_engine.stop_all_executions_with_id(jguid,TRUE);
COMMIT;
END;
With no effect. The job is still shown in Grid Control with status SUSPEND.
I have restarted all servers and all the components in Grid Control, but the jobs will not disappear from Grid Control although they have been deleted.
I am struggling with this for about 2 days now.
I have search in Metalink and the internet, but I have not found anything that provides a solution.
Any help will be very much appreciated.

hi,
I have in the past used the following from metalink
Do you have a metalink account?
SET verify OFF
SET linesize 255
SET pagesize 128
SET trimout ON
SET trimspool ON
SPOOL jobdump.log
ALTER SESSION SET nls_date_format='MON-DD-YYYY hh:mi:ss pm';
COLUMN status format a15
COLUMN job_name FORMAT a64
COLUMN job_type FORMAT a32
COLUMN job_owner FORMAT a32
COLUMN job_status format 99
COLUMN target_type format a64
COLUMN frequency_code format a20
COLUMN interval format 99999999
VARIABLE JOBID VARCHAR2(64);
PROMPT *********************** JOB INFO ********************************
REM Get the job id
SET serveroutput on
BEGIN
SELECT job_id INTO :JOBID
FROM MGMT_JOB
WHERE job_name='&&jobName'
AND job_owner='&&jobOwner'
AND nested=0;
EXCEPTION
WHEN NO_DATA_FOUND THEN
BEGIN
DBMS_OUTPUT.put_line('JOB NOT FOUND, TRYING NAME ONLY');
SELECT job_id INTO :JOBID
FROM MGMT_JOB
WHERE job_name='&&jobName'
AND nested=0
AND ROWNUM=1;
EXCEPTION
WHEN NO_DATA_FOUND THEN
DBMS_OUTPUT.put_line('JOB NOT FOUND');
END;
END;
SELECT job_name, job_owner, job_type, system_job, job_status, target_type
FROM MGMT_JOB
WHERE job_id=HEXTORAW(:JOBID);
PROMPT *********************** JOB SCHEDULE ****************************
SELECT DECODE(frequency_code,
1, 'Once',
2, 'Interval',
3, 'Daily',
4, 'Day of Week',
5, 'Day of Month',
6, 'Day of Year', frequency_code) "FREQUENCY_CODE",
start_time, end_time, execution_hours, execution_minutes,
interval, months, days, timezone_info, timezone_target_index,
timezone_offset, timezone_region
FROM MGMT_JOB_SCHEDULE s, MGMT_JOB j
WHERE s.schedule_id=j.schedule_id
AND j.job_id=HEXTORAW(:JOBID);
PROMPT ********************** PARAMETERS ********************************
SELECT parameter_name,
decode(parameter_type,
0, 'Scalar',
1, 'Vector',
2, 'Large', parameter_type) "PARAMETER_TYPE",
scalar_value, vector_value
FROM MGMT_JOB_PARAMETER
WHERE job_id=HEXTORAW(:JOBID)
AND execution_id=HEXTORAW('0000000000000000')
ORDER BY parameter_name;
PROMPT ********************** TARGETS ********************************
SELECT target_name, target_type
FROM MGMT_JOB_TARGET jt, MGMT_TARGETS t
WHERE job_id=HEXTORAW(:JOBID)
AND execution_id=HEXTORAW('0000000000000000')
AND jt.target_guid=t.target_guid
ORDER BY target_type, target_name;
PROMPT ********************** FLAT TARGETS ********************************
SELECT target_name, target_type
FROM MGMT_JOB_FLAT_TARGETS jft, MGMT_TARGETS t
WHERE job_id=HEXTORAW(:JOBID)
AND jft.target_guid=t.target_guid
ORDER BY target_type, target_name;
PROMPT ************************ EXECUTIONS *******************************
SELECT execution_id,
DECODE(status,
1, 'SCHEDULED',
2, 'RUNNING',
3, 'FAILED INIT',
4, 'FAILED',
5, 'SUCCEEDED',
6, 'SUSPENDED',
7, 'AGENT DOWN',
8, 'STOPPED',
9, 'SUSPENDED/LOCK',
10, 'SUSPENDED/EVENT',
11, 'SUSPENDED/BLACKOUT',
12, 'STOP PENDING',
13, 'SUSPEND PENDING',
14, 'INACTIVE',
15, 'QUEUED',
16, 'FAILED/RETRIED',
17, 'WAITING',
18, 'SKIPPED', status) "STATUS",
scheduled_time, start_time, end_time
FROM MGMT_JOB_EXEC_SUMMARY e
WHERE job_id=HEXTORAW(:JOBID)
ORDER BY scheduled_time;
UNDEFINE jobName
UNDEFINE jobOwner
UNDEFINE JOBID
SPOOL OFFAlan

RHEL4U4 EM64T Grid Control agent install issue

I've installed a 2 node Oracle 10G R2 RAC on RHEL4 U4 EM64T and it is working fine on Dell PE2850 servers. But I couldn't get the grid control agent installed on these RHEL4U4 EM64T PE2850 servers. The OMS server is running 32 bit Oracle 10g R2 on RHEL4. The issue is with the OMA (agent) install on EM64T and I've tried several different options (local install and push from the OMS server). I end up with the following error. Any feedback is appreciated. Thanks.
Raj
<<installActions2006-12-07_11-22-39AM.log>>
This is error we got from both the install on the local node and tried a push from the OMS server as well.
INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:
INFO: /opt/oracle/product/10.2.0/agent10g/bin/genclntsh
INFO: /usr/bin/ld: skipping incompatible /opt/oracle/product/10.2.0/agent10g/lib/libxml10.a when searching for -lxml10
/usr/bin/ld: cannot find -lxml10
INFO: collect2: ld returned 1 exit status
INFO: genclntsh: Failed to link libclntsh.so.10.1
INFO: make: *** [client_sharedlib] Error 1
INFO: End output from spawned process.
INFO: ----------------------------------
INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'client_sharedlib' of makefile '/opt/oracle/product/10.2.0/agent10g/network/lib/ins_net_client.mk'. See '/opt/oracle/oraInventory/logs/installActions2006-12-07_11-22-39AM.log' for details.
Exception Severity: 1

Hi,
Did you run cvu to check if all OS Patches are installed ??
Best Regards,
Paulo.

Patching Grid Control OMS and Agent to 10.2.0.5 issue

Oracle 11gR1 RHEL5 - Grid Control 10.2.0.5
Hi All,
I have been stuck on this issue for over a month (was relying on Oracle supports help and they just would not reply) and I can't figure it out. Basically, what happened is that my 10.2.0.5 patch set failed partiallty when I was applying it to the OMS. Here is what is going on right now:
Database Repository (EMREP) - 11gR1 (11.1.0.6) - /opt/app/oracle/product/11.1.0/db_1
OMS - 10.2.0.5 - /opt/app/oracle/product/10.2.0/grid_1/oms10g
Agent - 10.2.0.5 - /opt/app/oracle/product/10.2.0/grid_1/agent10g
When I was almost done with the 10.2.0.5 patch on the OMS, OUI gave me the following error:
SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration
assistants at this time. Not successfully running any "Recommended" assistants
means your system will not be correctly configured.
*1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the*
failures.
*2. Fix the errors causing these failures.*
*3. Select the failed assistants and click the 'Retry' button to retry them*
When I checked the logs I found the following messages (Here is a part of it...I think before it started to fail):
Finished deleting the above files...
INFO: Configuration assistant "OMS Oneoff Patch Application" succeeded
INFO: Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
Repository Upgrade is failed with errors. Restore the database, rectify the errors and retry the install.
For more details :
-For configuration issues, look at the log files present in following location:
/opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/cfgfw
-For repository failures, look at the log files
/opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.
2.0.5.0
/opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors
-If not able to identify the repository issues, contact ORACLE Support.
-After the Repository issues are rectified and upgraded successfully, execute the below runConfig command to run remaining config tools.
Goto /opt/app/oracle/product/10.2.0/grid_1/oms10g/oui/bin directory and run below command.
For UNIX :
./runConfig.sh ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
For Windows :
runConfig.bat ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade has failed
Exception : java.lang.Exception: Command: /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rhel-grid)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep))) -action upgrade -no_transx -no_verify -verbose -repos_user sysman -output_file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 failed. Exit code: expected [0 ], but got 45
INFO: Configuration assistant "Repository Upgrade" failed
*** Starting OUICA ***
Oracle Home set to /opt/app/oracle/product/10.2.0/grid_1/oms10g
Configuration directory is set to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs. All xml files under the directory will be processed
Parsing configuration file config.xml ....
Ended Parsing configuration file config.xml
Start Processing configuration tool Oracle Internet Directory Patch Configuration Assistant....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Buffer size for copying file is set to 2048
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log from the file path expanding...
WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log could not be found. Nothing will be copied for this file
Number of file(s) copied is 0
Number of directories copied is 0
End Processing configuration tool Oracle Internet Directory Patch Configuration Assistant
Start Processing configuration tool Directory Integration Platform Configuration Assistant....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log from the file path expanding...
WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log could not be found. Nothing will be copied for this file
Number of file(s) copied is 0
Number of directories copied is 0
End Processing configuration tool Directory Integration Platform Configuration Assistant
Start Processing configuration tool OC4J Instance Configuration Assistant....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/*
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/home_default_island_1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/operations from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/log.xml from the file path expanding...
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/log.xml to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/log.xml
Number of file(s) copied is 1
Number of directories copied is 0
End Processing configuration tool OC4J Instance Configuration Assistant
Start Processing configuration tool OPMN Configuration Assistant - start HTTP server....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/*
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 from the file path expanding...
Number of directories copied is 0
End Processing configuration tool OPMN Configuration Assistant - start OCA Instance
Start Processing configuration tool Wireless Configuration Assistant....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out from the file path expanding...
WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out could not be found. Nothing will be copied for this file
Number of file(s) copied is 0
Number of directories copied is 0
End Processing configuration tool Wireless Configuration Assistant
Start Processing configuration tool Wireless Metadata Repository Update....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out from the file path expanding...
WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out could not be found. Nothing will be copied for this file
Number of file(s) copied is 0
Number of directories copied is 0
End Processing configuration tool Wireless Metadata Repository Update
Start Processing configuration tool Portal Metadata Repository Update....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log from the file path expanding...
WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log could not be found. Nothing will be copied for this file
Number of file(s) copied is 0
Number of directories copied is 0
End Processing configuration tool Portal Metadata Repository Update
Start Processing configuration tool OPMN Configuration Assistant....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/*
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EM~default_island~1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/dcm-daemon~dcm-daemon~dcm~1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ons.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCache~1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EMPROV~default_island~1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/states from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~home~default_island~1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/opmn.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/HTTP_Server~1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ipm.log from the file path expanding...
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/WebCache~WebCacheAdmin~1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EM~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~OC4J_EM~default_island~1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/dcm-daemon~dcm-daemon~dcm~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/dcm-daemon~dcm-daemon~dcm~1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ons.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/ons.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCache~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/WebCache~WebCache~1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EMPROV~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~OC4J_EMPROV~default_island~1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~home~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~home~default_island~1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/opmn.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/opmn.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/HTTP_Server~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/HTTP_Server~1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ipm.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/ipm.log
Number of file(s) copied is 10
Number of directories copied is 0
End Processing configuration tool OPMN Configuration Assistant
Start Processing configuration tool Application Server Control Configuration Assistant....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/*
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.10 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.trc from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.4 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.7 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/nfsPatchPlug.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-application.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.9 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.8 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.trc from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emctl.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/server.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/secure.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.6 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em.nohup from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-web-access.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/pafLogs from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emias.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.5 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0.errors from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.3 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.trc from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/rmi.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.2 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emca_repos_out_of_box12_56_33.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.log from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log.1 from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.transx from the file path expanding...
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.10 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.10
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emdctl.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.4.0
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagentfetchlet.trc
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.4 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.4
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.7 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.7
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/nfsPatchPlug.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/nfsPatchPlug.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-application.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em-application.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.9 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.9
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.8 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.8
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emdctl.trc
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emctl.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emctl.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/server.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/server.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/secure.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/secure.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.6 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.6
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em.nohup to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em.nohup
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0.errors
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-web-access.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em-web-access.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emias.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emias.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.5 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.5
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0.errors to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.4.0.errors
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.3 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.3
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagent.trc
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/rmi.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/rmi.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagent.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.2 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.2
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emca_repos_out_of_box12_56_33.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emca_repos_out_of_box12_56_33.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagentfetchlet.log
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log.1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.log.1
Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.transx to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0.transx
Number of file(s) copied is 34
Number of directories copied is 0
End Processing configuration tool Application Server Control Configuration Assistant
Start Processing configuration tool DCM Repository Update Assistant ....
Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/*
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/dcmctl_logs from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/emd_logs from the file path expanding...
Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/daemon_logs from the file path expanding...
Number of file(s) copied is 0
Number of directories copied is 0
End Processing configuration tool DCM Repository Update Assistant
INFO: The "/opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.
INFO: Since the option is to overwrite the existing /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands file, backing it up
INFO: The backed up file name is /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands.bak.1
SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration assistants at this time. Not successfully running any "Recommended" assistants means your system will not be correctly configured.
1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.
2. Fix the errors causing these failures.
3. Select the failed assistants and click the 'Retry' button to retry them.
INFO: User Selected: Yes/OK
INFO: Starting to execute configuration assistants
INFO: Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
Repository Upgrade is failed with errors. Restore the database, rectify the errors and retry the install.
For more details :
-For configuration issues, look at the log files present in following location:
/opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/cfgfw
-For repository failures, look at the log files
/opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0
/opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors
-If not able to identify the repository issues, contact ORACLE Support.
-After the Repository issues are rectified and upgraded successfully, execute the below runConfig command to run remaining config tools.
Goto /opt/app/oracle/product/10.2.0/grid_1/oms10g/oui/bin directory and run below command.
For UNIX :
./runConfig.sh ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
For Windows :
runConfig.bat ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade has failed
Exception : java.lang.Exception:
REPOSITORY UPGRADE STATUS : 3
INFO: Configuration assistant "Repository Upgrade" failed
I would appreciate any help on this as I have been stuck on it since April :( Not too happy with Oracle Support.
Thanks much to all!
JrOraDBA

Here is the output for when I applied the patch:
opatch apply
Invoking OPatch 10.2.0.3.0
Oracle interim Patch Installer version 10.2.0.3.0
Copyright (c) 2005, Oracle Corporation. All rights reserved..
Oracle Home       : /opt/app/oracle/product/10.2.0/grid_1/db10g
Central Inventory : /opt/app/oracle/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 10.2.0.3.0
OUI version       : 10.2.0.3.0
OUI location      : /opt/app/oracle/product/10.2.0/grid_1/db10g/oui
Log file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/opatch2009-04-22_12-07-14PM.log
ApplySession applying interim patch '4329444' to OH '/opt/app/oracle/product/10.2.0/grid_1/db10g'
Invoking fuser to check for active processes.
Invoking fuser on "/opt/app/oracle/product/10.2.0/grid_1/db10g/bin/oracle"
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
*(Oracle Home = '/opt/app/oracle/product/10.2.0/grid_1/db10g')*
Is the local system ready for patching?
*Do you want to proceed? y*
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '4329444' for restore. This might take a while...
Backing up files affected by the patch '4329444' for rollback. This might take a while...
Patching component oracle.rdbms, 10.1.0.4.0...
Updating archive file "/opt/app/oracle/product/10.2.0/grid_1/db10g/lib/libserver10.a" with "lib/libserver10.a/qerix.o"
ApplySession adding interim patch '4329444' to inventory
Verifying the update...
Inventory check OK: Patch ID 4329444 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 4329444 are present in Oracle Home.
Running make for target ioracle
The local system has been patched and can be restarted.
OPatch succeeded.
However, the weird thing is that I don't see it in the lsinventory:
*/opt/app/oracle/product/10.2.0/grid_1/db10g/OPatch/opatch lsinventory*
Invoking OPatch 10.2.0.3.0
Oracle interim Patch Installer version 10.2.0.3.0
Copyright (c) 2005, Oracle Corporation. All rights reserved..
Oracle Home       : /opt/app/oracle/product/10.2.0/grid_1/db10g
Central Inventory : /opt/app/oracle/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 10.2.0.3.0
OUI version       : 10.2.0.3.0
OUI location      : /opt/app/oracle/product/10.2.0/grid_1/db10g/oui
Log file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/opatch2009-06-09_09-37-54AM.log
Lsinventory Output file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/lsinv/lsinventory2009-06-09_09-37-54AM.txt
Installed Top-level Products (2):
Oracle Database 10g Patch Set 3                                      10.1.0.5.0
Oracle Enterprise Manager Repository Database                        10.2.0.3.0
There are 2 products installed in this Oracle Home.
Interim patches (1) :
Patch 5632264      : applied on Thu Apr 23 12:23:10 CDT 2009
Created on 8 Feb 2007, 00:38:09 hrs PST8PDT
Bugs fixed:
*5632264*
OPatch succeeded.
Do you think I should restore the backup (and I only have the database backup, not the Oracle Home backup)?
THanks.

Linux OEM Grid Control 10.2.0.1.0 installation issue

Just a heads up to anyone installing Linux OEM Grid Control 10.2.0.1.0
If you are doing a full install, the "product specific prerequisite checks" page will show an error on the following packages even if you have them installed.
compat-libstdc++-296-2.96-132.7.2 (failed)
libstdc++devel-3.4.3-22.1 (failed)
openmotif-21-2.1.30-11 (failed)
Note that the installation works fine if you ignore the "missing" prerequisites. I believe the check itself is flawed. The openmotif check should be openmotif21-**** (extra hyphen incorrect in check - the old install was openmotif, now openmotif21), the libstdc++ needs a hypen added before the devel, and the compat-libstdc++ has yet another issue.
This is something the developers at oracle will have to fix.
Steve

Yes, you must download and install the 10.2.0.1 version and then patch it up to the 10.2.0.4 version.
http://www.oracle.com/technology/obe/obe10gem/install/index.html
The above link shows you the install routine when using a new database, the steps for the existing database are only slightly different, all you need are the connection details for that existing database and you should be ok.
As for taking full backups of the Grid Control repository, I know many choose not to, space is always a big concern, but this depends on how critical your repository is to you. If you need it for the auditors, well then I'd suggest acquiring some more hard disks to up your space.

Scheduling an Export Job Using Grid Control

Hi,
I got a requirement to schedule export jobs in Oracle Grid Control 10.2.0.5 (Windows). Is this possible and have any one done this? If so please share the steps. The idea is to get alerts if the job fails.
Thanks.
GB

Here is the easy steps (There might be slight differences as I am posting it based on 11g screen)
1. On grid control console, click on the relevant database
2. click on 'Data Movement' tab
3. Click on 'Export to Export Files'
4. chose the Export type (Database / Schema / Tables/ Tablespace)
5. Provide Host credentials (OS username and Password) and click on 'Continue'. You will get a new screen called 'Export: Options'
6. Click the checkbox called 'Generate Log File' and select the Directory object where you wants to create the dump files. (You need to create a directory object in database, if you don't have one)
7. Chose the contents option as you required, and click '*Next*'. You will get a new page called 'Export: Files'
8. Select the directory object from the drop-down box and provide a name format for file name, and click 'Next'
9. Here you provide the Job name and description, and chose repeat options (daily, weekly etc), and click 'Next'
10. You will get a summary screen called 'Export: Schedule'. review your job details and click on 'Submit'.
This is the solution, and it works well.

SQL script with host command job in Enterprise Manger Grid Control

I use Enterprise Manger Grid Control 10.2.0.5 and need to create SQL script job on database instance target on unix/linux platform.
I have problem with os command inside sqlplus script.
For example for the simple command: SQL> host ls
I get the message in output log: SQL> SQL> SQL> SQL> SQL> SQL> /bin/bash: ls: command not found
Can anyone help me?
Thank you.

Hi,
Make sure you have granted all necessary rights (log on as a batch job etc.) to the user used in the prefered credentials.
Cheers,
Kenneth

Can we schedule Loader Jobs (SQL Loader) using Grid Control ?

Can we schedule SQL Loaders jobs/process using Grid Control for 11g database ?
Or
Is it good to schedule it as external jobs using DBMS_SCHEDULER ?
OS is LINUX. Database is 11g R1 Grid Control will be the latest, I believe 10gR3.
Any other suggestions... (I know it can be done using OS utilities like cron and others but that is not an option for now.)
Thanks in advance.

Try this
-> Create a shell script to execute sqlldr
-> On Grid, create an "OS COMMAND" job and pass this script as parameters. You'll have options to schedule this job.
Let us know how it works.

Issue with OEM grid control.

I created a stream replication for scott schema on 10gR2 using maintain_tables.
Everything is working fine and for initail two days there was no issue when i checked the diffrent processes using OEM grid control. After two days, OEM is not showing anything under the "propagation" process and instead showing "no data found". I checked the dba_propagation and there is a propagation process in that. Even the replication is working fine. So is that an issue/Bug in OEM? Any cure for this?
Kapil

I created a stream replication for scott schema on 10gR2 using maintain_tables.
Everything is working fine and for initail two days there was no issue when i checked the diffrent processes using OEM grid control. After two days, OEM is not showing anything under the "propagation" process and instead showing "no data found". I checked the dba_propagation and there is a propagation process in that. Even the replication is working fine. So is that an issue/Bug in OEM? Any cure for this?
Kapil

No emails being issued by grid control

I am trying to configure GC to send emails. From the preferences page I have added an email address. I have also added an email in the setup, notification methods page.
When I test these I get an email as expected.
I then set up a test with the archive metric. I set the threshold down to 2%
I then set up the relevent notification rule and check the email tab.
then I force the archive area over the 2% threshold and wait for an email. I can see the error on the database page on grid control but do not get an email.
I have set the metric to email on critical and warning
regards
Alan

Check the plan action
Go to Grid control and select the database target
In the home page of databse go down and search Metrics and Polycy settings . Select this
In the page of metrics enable ALL METRICS and search the metric of ARCHIVE AREA used or ARCHIVE AREA FREE % . Put values in CRITICAL and WARNING THERESHOLDS.
When you finish apply the changes
Go to the PREFERENCES page and CREATE A NOTIFICATION RULE
Give NAME to rule and description -- Archiver Rule
In the targets select the database of first step
In the metrics section press the add button
Select the metrics of ARCHIVE AREA monitoring and enable the CRITICAL and WARNING checkbox if yo want notifications for both events
Not select jobs and in the last page enable the checkbox of mail sender
Remember that the metrics in the database must be critical and warning thresholds. The rule not send mail of metrics that not have values . But if you see the alert in grid control console and you dont receive mail, the procedure is create a rule or edit any that exists and add the metrics for archiver monitoring
Regards

Cleanup job to remove archive logs automatically through OEM Grid control

Hi All,
I am working on 11gR2 3node RAC database. we have enabled archivelog mode for the databases and don't have any backup processes (like rman) and not using ASM.
Please let me know how to cleanup the old archivelogs automatically through oem Grid control.
I have some idea how to do it in standalone database, but not sure how it works in RAC environment through OEM. Please let me know.
Thanks in advance.

Hari wrote:
Thanks for your reply and The requirement is, put the DB in archive log mode and cleanup the old archive logs which is more than 5days. We are doing this because of space issue and don't have backup for these files and the DB must be in archive log mode.
I have few question here.
1. Is it must to take the backup of the archive log files and before delete them?No, but if you aren't backing up, why create the archivelogs in the first place?
2. If i delete them without backup, what is the negative impact?If you aren't backing up the database in the first place (as you stated in an earlier post) then it really doesn't matter what you do with the archivelogs as they are worthless anyway.
3. What is the recommended process to do it?My recommendation is you first start using rman to backup the database
4. I need to setup this process through OEM grid control.
Please let me know.
Thanks,
HariIt all begs the question which has already been asked and you avoided answering . . . if you are not taking backups, why bother archiving? The archive logs have ZERO VALUE outside of a consistent backup strategy. So how is it you have a 'requirement' to run in archivelog mode but no requirement for backups?
Edited by: EdStevens on Dec 2, 2011 9:30 PM

Grid Control jobs issue

Similar Messages

Maybe you are looking for