Grid control patching log locations

I looked on oracle support. I am looking for the grid control logs for when I patch through the grid control gui.
The agent deploy logs are here:
/opt/app/oracle/product/10.2.0/oms10g/sysman/prov/agentpush
Where are the logs for Deploy -> Patch Agent ?
When a job fails for either patching an agent or a database, the error messages I get in the GUI are not real useful. I need the logs. I have been hunting for them and can't find them.

Check the job logs in the OMS since the real deploying/patching is done by a job.
See the tab Jobs. If you select Advanced Search, change Target Type to Targetless you may even see more jobs that ran on your OMS.
Select a job that ran. You can click Show All Details and even zoom in further, depending if it was multi step job.
Eric

Similar Messages

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

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.

Grid Control showing excessive amount of disk utilization.

Hi Folks,
I understand that Oracle doesn't support their products 100% on non Oracle VMs, but I thought I might take a stab at it.
I decided to stick with a simple installation of Oracle Grid Control running on a Windows 2003 R2 32 bit os, here are the steps I took.
1. Run Guest OS Windows 2003 R2 32 bit on a Windows 2008 x64 running Hyper-V (Yes I know why not EL5 running XEN, long story)
2. Install Grid Control with Database and Agent versions 10.2.0.2.1
3. Patch agent and oms to 10.2.0.5.0
4. Some minor issues, but managed to get by those.
- First off EM Website shows down, got to take a look at that, probably need to fix the beacon, not sure!
Problem:
- Grid shows that the host running em is over 100% disk utilization.
- According to Metalink this is a known bug in Windows 2000 Performance Counters (not 2003?)
- More specially Microsoft KB article Q310067.
- Metalink Doc Id: 303788.1
- Note, I'm running 2003 on a Hyper-V Guest, so anything can go wrong!
The specific error is:
Metric               Disk Device Busy (%)
Disk Device               0 C:
Severity               Critical
Alert Triggered          Jun 3, 2009 7:57:54 PM
Last Updated          Jun 4, 2009 3:48:48 PM
Acknowledged          No
Acknowledged By     n/a
Message               Disk Utilization for 0 C: is 587.86%, crossed warning (80) or critical (95) threshold.
More info:
- Guest is running on a Dual Quad Core Xeon System with 16 GB of RAM
- Guest has dedicated 4096MB of ram
- Guest has dedicated 2 CPUS
- Guest is configured with a Virtual Disk (specifically partition c:\) to be on local Hyper-V disk array
- Windows 2008 Hyper-V host disk array is in a RAID 5 configuration running 10k SAS drives
- Windows 2008 Hyper-V host utilization is literary at most 5% (current is 1%)
- Windows 2008 Hyper-V disk utilization according to graphs is showing 100KB/s usage (less than 1%)
Temporary solution is to turn off the metric, but not sure if that's such a good idea.
- Note that 11g EM and 10g EM running on Hyper-V server had the same issue.
- Note that 11g EM and 10g EM running without visualization had no issues.
Any thoughts?

It may be related to Bug 8677212: BACKUP INFORMATION FOR SOME DATABASES SHOWS INCORRECTLY
Although bug info says it for HP-UX, I've also seen the same problem on Grid Control 10.2.0.5 running on Solaris.
You may want to apply 10.2.0.5.4 Grid Control Patch Set Update (PSU) [ID 1139563.1] to fix it.
Best Regards,
Gokhan Atil
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

Grid Control architecture.

Can I have 64 bits primary and 32 bits standby logical server controlled by 32 bits Grid Control.
Primary server (64 bits) + Standby server (logical) 32 bits + Grid Control (32 bits)

Oliver,
Thanks for the comments. The article is based on practical experience. If one was to recommend a pool of 2 management servers for a large corporate with 1000 servers, what that would mean is that if 1 server was brought down for any maintenance reason (for eg. applying an EM patch), all the EM work load would be on the remaining management server. So it is better to have 3 management servers instead of 2 when the EM system is servicing so many targets. Otherwise, the DBAs would be a tad angry since only 1 remaining managment server would not be able to service them properly during the time of the maintainance fix on the first management server.
The article ends with these words: "You can easily manage hundreds or even *thousands* of targets with such an architecture. The large corporate which had deployed this project scaled easily up to managing 600 to 700 targets with a pool of just three management servers, and the future plan is to manage *2,000 or more* targets which is quite achievable." The 2000 or more is based on the same architecture of 3 managment servers.
So as per the best practice document, 2 management servers would be fine for 1000 servers, although I would still advise 3 servers in practice.
For your case of 200 servers, it depends on the level of monitoring you are planning to do, and the type of database managment activities that
will be done by the DBAs. For eg, if the Dbas are planning on creating standby databases now and then through Grid Control, running backups daily
via Grid Control, cloning databases in Grid Control, patching databases in Grid Control and so on, I would definitely advise a pool of 2 servers
in your case. 2 is always better than 1.
Regards,
Porus.
Edited by: Porushh on Feb 21, 2009 12:51 AM

Lengthen idle time in Grid Control

Grid control automatically logs out after period (about 10mins) of inactivity. Is there a way to lengthen the idle time in Grid Control? grid control version is 10.2.0.2.
thanks in advance.

Thanks. that worked. The line you suggested applied to every users in the Grid Control. Would it be possible to set the inactivity time differently for different users like the idle_time in the database profile?
thanks again.

Grid Control Architecture for Very Large Sites: New Article published

A new article on Grid Control was published recently:
Grid Control Architecture for Very Large Sites
http://www.oracle.com/technology/pub/articles/havewala-gridcontrol.html

Oliver,
Thanks for the comments. The article is based on practical experience. If one was to recommend a pool of 2 management servers for a large corporate with 1000 servers, what that would mean is that if 1 server was brought down for any maintenance reason (for eg. applying an EM patch), all the EM work load would be on the remaining management server. So it is better to have 3 management servers instead of 2 when the EM system is servicing so many targets. Otherwise, the DBAs would be a tad angry since only 1 remaining managment server would not be able to service them properly during the time of the maintainance fix on the first management server.
The article ends with these words: "You can easily manage hundreds or even *thousands* of targets with such an architecture. The large corporate which had deployed this project scaled easily up to managing 600 to 700 targets with a pool of just three management servers, and the future plan is to manage *2,000 or more* targets which is quite achievable." The 2000 or more is based on the same architecture of 3 managment servers.
So as per the best practice document, 2 management servers would be fine for 1000 servers, although I would still advise 3 servers in practice.
For your case of 200 servers, it depends on the level of monitoring you are planning to do, and the type of database managment activities that
will be done by the DBAs. For eg, if the Dbas are planning on creating standby databases now and then through Grid Control, running backups daily
via Grid Control, cloning databases in Grid Control, patching databases in Grid Control and so on, I would definitely advise a pool of 2 servers
in your case. 2 is always better than 1.
Regards,
Porus.
Edited by: Porushh on Feb 21, 2009 12:51 AM

Newbie - Installing Application Servers onto Grid Control

sorry for what may seem a basic question but we have 2 Application servers we wish to put onto our Grid Control.
Can someone point me to a page for installing/downloading the agent. I have tried installing the agent previously but this didn't seem to work.
We can access our DB EM pages in our grid control at present and also our RAC and ASM however i have been assigned the task of installing the agents for the Application servers.
Any assistance greatly appreciated

To ‘push’ the OEM agent from the OEM Grid Control patch 5455350 is needed. I found that after doing this I was still unable to fully deploy the agent by pushing it from the OEM GRID control. So take a different route
Download the proper agent installation file from http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
The GRID control agent installation zip file is extracted on the GRID control server and it should go to ORACLE_HOME/sysman/agent_download/<version>/<os>
set GRID control ORACLE_HOME
mkdir –p $ORACLE_HOME/sysman/agent_download/<version>
unzip /.../Win32_Grid_Control_agent_download_10_2_0_3_0.zip
opmnctl shutdown
opmnctl startall
WGET is needed for the installation of the OEM agent on Windows.
Download wget (complete package, except sources) from
http://gnuwin32.sourceforge.net/packages/wget.htm
and install it on to the Windows server.
edit the agent_download.rsp response file on the OMS host and change the:
s_OMSHost="..."
s_OMSPort="..."
scp over the agentDownload.... script to the target machine.
ecit the hosts file on the windows server and add the Windows machine IP and hostname and OMS machine IP and hostname.
on the windows server execute:
script.exe agentDownload.vbs b <agent home on windows server> m <OMS host name> r <port number>
secure the agent
emctl secure agent
I got most of this from Oracle whitepaper 10gr2_agent_deploy_bp.pdf (bp=best practices).

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.

No log on DBMS_DATAPUMP schedule on Grid Control

Hello,
I'm trying to plan my own procedure lto make a datapump full of the instance with OEM Grid Control.
It's working but with no log in the job detail :
create or replace
PROCEDURE pr_expdp_full AS
Procedure permettant d'effectuer un export FULL
de l'instance avec la technologie DATAPUMP
Déclarer l'objet répertoire dans l'instance
CREATE DIRECTORY "DATAPUMP_DIR" AS '<Mon chemin réseau>'
JobHandle NUMBER; -- Data Pump job handle
JobStamp VARCHAR2(13); -- Date time stamp
InstanceName varchar2(30); -- Name of instance
ind NUMBER; -- Loop index
n_Exist NUMBER; -- count Job
JobHandle_Exist NUMBER; --JobHandle exist
percent_done NUMBER; -- Percentage of job complete
job_state VARCHAR2(30); -- To keep track of job state
le ku$_LogEntry; -- For WIP and error messages
js ku$_JobStatus; -- The job status from get_status
jd ku$_JobDesc; -- The job description from get_status
sts ku$_Status; -- The status object returned by get_status
BEGIN
-- TimeStamp File with system date
select to_char(SYSDATE,'DDMMRRRR-HH24MI') into JobStamp from dual ;
-- Instance Name to export
select rtrim(global_name) into InstanceName from global_name;
--Delete Job if exist
select count(*) into n_Exist from user_datapump_jobs where job_name = 'DAILY_EXPDP_'||InstanceName;
IF n_Exist > 0
THEN
JobHandle_Exist := DBMS_DATAPUMP.ATTACH('DAILY_EXPDP_'||InstanceName,'SYSTEM');
dbms_datapump.stop_job(JobHandle_Exist);
DBMS_DATAPUMP.DETACH (JobHandle_Exist);
execute immediate('DROP TABLE DAILY_EXPDP_'||InstanceName||'');
END IF;
-- Create a (user-named) Data Pump job to do a schema export.
JobHandle :=
DBMS_DATAPUMP.OPEN(
operation => 'EXPORT'
,job_mode => 'FULL'
,job_name => 'DAILY_EXPDP_'||InstanceName
,version => 'COMPATIBLE'
dbms_output.put_line('after OPEN');
-- Specify a single dump file for the job (using the handle just returned)
-- and a directory object, which must already be defined and accessible
-- to the user running this procedure.
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'FULL_EXPDP_'||InstanceName||'_'||JobStamp||'.dpf'
,directory => 'DATAPUMP_DIR'
,filetype => 1 );
dbms_datapump.set_parameter(handle => JobHandle, name => 'KEEP_MASTER', value => 0);
-- Specify a single log file for the job
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'FULL_EXPDP_'||InstanceName||'_'||JobStamp||'.log'
,directory => 'DATAPUMP_DIR'
,filetype => 3 );
dbms_datapump.set_parameter(handle => JobHandle, name => 'INCLUDE_METADATA', value => 1);
dbms_datapump.set_parameter(handle => JobHandle, name => 'DATA_ACCESS_METHOD', value => 'AUTOMATIC');
-- Start the job. An exception will be generated if something is not set up
-- properly.
DBMS_DATAPUMP.START_JOB(JobHandle);
-- The export job should now be running. In the following loop, the job
-- is monitored until it completes. In the meantime, progress information is
-- displayed.
percent_done := 0;
job_state := 'UNDEFINED';
while (job_state != 'COMPLETED') and (job_state != 'STOPPED') loop
dbms_datapump.get_status(JobHandle,dbms_datapump.ku$_status_job_error dbms_datapump.ku$_status_job_status dbms_datapump.ku$_status_wip,-1,job_state,sts);
js := sts.job_status;
-- If the percentage done changed, display the new value.
if js.percent_done != percent_done
then
dbms_output.put_line('*** Job percent done = ' ||
to_char(js.percent_done));
percent_done := js.percent_done;
end if;
-- If any work-in-progress (WIP) or error messages were received for the job,
-- display them.
if (bitand(sts.mask,dbms_datapump.ku$_status_wip) != 0)
then
le := sts.wip;
else
if (bitand(sts.mask,dbms_datapump.ku$_status_job_error) != 0)
then
le := sts.error;
else
le := null;
end if;
end if;
if le is not null
then
ind := le.FIRST;
while ind is not null loop
dbms_output.put_line(le(ind).LogText);
ind := le.NEXT(ind);
end loop;
end if;
end loop;
-- Indicate that the job finished and detach from it.
dbms_output.put_line('Job has completed');
dbms_output.put_line('Final job state = ' || job_state);
dbms_datapump.detach(JobHandle);
END pr_expdp_full;
I shcedule after :
BEGIN
SYSTEM.pr_expdp_full();
END;
But when i want to see the results of the execution in the details of job, i can't see anything.
When i do the same job using the direct link OEM : "Export Data" and after submission, i can see the DATAPUMP log in the job log details.
Can you tell me what is missing on the submission or what we can do to correct that.
Thanks in advance
Best regards.

Hello,
I'm trying to plan my own procedure lto make a datapump full of the instance with OEM Grid Control.
It's working but with no log in the job detail :
create or replace
PROCEDURE pr_expdp_full AS
Procedure permettant d'effectuer un export FULL
de l'instance avec la technologie DATAPUMP
Déclarer l'objet répertoire dans l'instance
CREATE DIRECTORY "DATAPUMP_DIR" AS '<Mon chemin réseau>'
JobHandle NUMBER; -- Data Pump job handle
JobStamp VARCHAR2(13); -- Date time stamp
InstanceName varchar2(30); -- Name of instance
ind NUMBER; -- Loop index
n_Exist NUMBER; -- count Job
JobHandle_Exist NUMBER; --JobHandle exist
percent_done NUMBER; -- Percentage of job complete
job_state VARCHAR2(30); -- To keep track of job state
le ku$_LogEntry; -- For WIP and error messages
js ku$_JobStatus; -- The job status from get_status
jd ku$_JobDesc; -- The job description from get_status
sts ku$_Status; -- The status object returned by get_status
BEGIN
-- TimeStamp File with system date
select to_char(SYSDATE,'DDMMRRRR-HH24MI') into JobStamp from dual ;
-- Instance Name to export
select rtrim(global_name) into InstanceName from global_name;
--Delete Job if exist
select count(*) into n_Exist from user_datapump_jobs where job_name = 'DAILY_EXPDP_'||InstanceName;
IF n_Exist > 0
THEN
JobHandle_Exist := DBMS_DATAPUMP.ATTACH('DAILY_EXPDP_'||InstanceName,'SYSTEM');
dbms_datapump.stop_job(JobHandle_Exist);
DBMS_DATAPUMP.DETACH (JobHandle_Exist);
execute immediate('DROP TABLE DAILY_EXPDP_'||InstanceName||'');
END IF;
-- Create a (user-named) Data Pump job to do a schema export.
JobHandle :=
DBMS_DATAPUMP.OPEN(
operation => 'EXPORT'
,job_mode => 'FULL'
,job_name => 'DAILY_EXPDP_'||InstanceName
,version => 'COMPATIBLE'
dbms_output.put_line('after OPEN');
-- Specify a single dump file for the job (using the handle just returned)
-- and a directory object, which must already be defined and accessible
-- to the user running this procedure.
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'FULL_EXPDP_'||InstanceName||'_'||JobStamp||'.dpf'
,directory => 'DATAPUMP_DIR'
,filetype => 1 );
dbms_datapump.set_parameter(handle => JobHandle, name => 'KEEP_MASTER', value => 0);
-- Specify a single log file for the job
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'FULL_EXPDP_'||InstanceName||'_'||JobStamp||'.log'
,directory => 'DATAPUMP_DIR'
,filetype => 3 );
dbms_datapump.set_parameter(handle => JobHandle, name => 'INCLUDE_METADATA', value => 1);
dbms_datapump.set_parameter(handle => JobHandle, name => 'DATA_ACCESS_METHOD', value => 'AUTOMATIC');
-- Start the job. An exception will be generated if something is not set up
-- properly.
DBMS_DATAPUMP.START_JOB(JobHandle);
-- The export job should now be running. In the following loop, the job
-- is monitored until it completes. In the meantime, progress information is
-- displayed.
percent_done := 0;
job_state := 'UNDEFINED';
while (job_state != 'COMPLETED') and (job_state != 'STOPPED') loop
dbms_datapump.get_status(JobHandle,dbms_datapump.ku$_status_job_error dbms_datapump.ku$_status_job_status dbms_datapump.ku$_status_wip,-1,job_state,sts);
js := sts.job_status;
-- If the percentage done changed, display the new value.
if js.percent_done != percent_done
then
dbms_output.put_line('*** Job percent done = ' ||
to_char(js.percent_done));
percent_done := js.percent_done;
end if;
-- If any work-in-progress (WIP) or error messages were received for the job,
-- display them.
if (bitand(sts.mask,dbms_datapump.ku$_status_wip) != 0)
then
le := sts.wip;
else
if (bitand(sts.mask,dbms_datapump.ku$_status_job_error) != 0)
then
le := sts.error;
else
le := null;
end if;
end if;
if le is not null
then
ind := le.FIRST;
while ind is not null loop
dbms_output.put_line(le(ind).LogText);
ind := le.NEXT(ind);
end loop;
end if;
end loop;
-- Indicate that the job finished and detach from it.
dbms_output.put_line('Job has completed');
dbms_output.put_line('Final job state = ' || job_state);
dbms_datapump.detach(JobHandle);
END pr_expdp_full;
I shcedule after :
BEGIN
SYSTEM.pr_expdp_full();
END;
But when i want to see the results of the execution in the details of job, i can't see anything.
When i do the same job using the direct link OEM : "Export Data" and after submission, i can see the DATAPUMP log in the job log details.
Can you tell me what is missing on the submission or what we can do to correct that.
Thanks in advance
Best regards.

Apply CPU /PSU patches through Enterprise Manager Grid Control.

How to apply PSU patches from 10.2.0.5 GRID Grid Control to my test/development/qa environment.
Are there any step by step documents availible. Did any one applied these patches using Oracle Enterprise Manager Grid control.

Please read
Oracle® Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching
10g Release 5 (10.2.0.5.0)
3 Infrastructure Requirements
http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e14500/infrastructure_setup.htm#BABEIFBC
For the correct setup to do you patching.
Regards
Rob
http://oemgc.wordpress.com

Please provide the patch set for Oracle Enterprise Manager Grid Control 10

Hi,
please provide the patch set for Oracle Enterprise Manager Grid Control 10.2.0.1 and 10.2.0.5 for AIX 5.3
patch set for Oracle Enterprise Manager Grid Control for 11.2.0.2 OS AIX 5.3
Thanks,
Vishal Hande.

user12009184 wrote:
Hi,
please provide the patch set for Oracle Enterprise Manager Grid Control 10.2.0.1 and 10.2.0.5 for AIX 5.3
patch set for Oracle Enterprise Manager Grid Control for 11.2.0.2 OS AIX 5.3
Thanks,
Vishal Hande.you must obtain all patches directly from
http://support.oracle.com

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/

Alert Log File Monitoring of 8i and 9i Databases with EM Grid Control 10g

Is it possible to monitor alert log errors in Oracle 8i/9i Databases with EM Grid Control 10g and EM 10g agents? If yes, is it possible to get some kind of notification?
I know that in 10g Database, it is possible to use server generated alerts, but what about 8i/9i?
Regards,
Martin

Hello
i am interested in a very special feature: is it possible to get notified if alerts occur in alert logs in an 8i/9i database when using Grid control and the 10g agent on the 8i/9i systems?
Moreover, the 10g agent should be able to get Performance Data using the v$ views or direct sga access without using statspack, right?
Do you know where I can find documentation about the supported features when using Grid Control with 8i/9i databases?

Process Flow ignores name and location for Control- and Log-Files

Hi!
Our OWB Version is 10.1.0.3.0 - DB Version 9.2.0.7.0 - OWF Version 2.6.2
Clients and server are running on Windows. Database contains target schemas as well as OWB Design and Runtime, plus OWF repositories. The source files to load reside on the same server as the database.
I have for example a SQL*Loader Mapping MAP_TEXT which loads one flat file "text.dat" into a table stg_text.
The mapping MAP_TEXT is well configured and runs perfect. i.e. Control file "text.ctl" is generated to location LOC_CTL, flat file "text.dat" read from another location LOC_DATA, bad file "text.bad" is written to LOC_BAD and the log file "text.log" is placed into LOC_LOG. All locations are registered in runtime repository.
When I integrate this mapping into a WorkFlow Process PF_TEXT, then only LOC_DATA and LOC_BAD are used. After deploying PF_TEXT, I execute it and found out, that Control and Log file are placed into the directory <OWB_HOME>\owb\temp and got generic names <Mapping Name>.ctl and <Mapping Name>.log (in this case MAP_TEXT.ctl and MAP_TEXT.log).
How can I influence OWB to execute the Process Flow using the locations configured for the mapping placed inside?
Has anyone any helpfull idea?
Thx,
Johann.

I didn't expect to be the only one to encounter this misbehaviour of OWB.
Meanwhile I found out what the problem is and had to recognize that it is like it is!
There is no solution for it till Paris Release.
Bug Nr. 3099551 at Oracle MetaLink adresses this issue.
Regards,
Johann Lodina.

Grid control patching log locations

Similar Messages

Maybe you are looking for