Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: oem2.2
Did
you go to MetaLink and do a search on the error? This would likely point
to the patch!
<SPAN
class=278372120-24042001>
I
did...look what I found:
<SPAN
class=278372120-24042001>
Ed
Haskins
Oracle
DBA
<SPAN
class=278372120-24042001>Verizon Wireless
<SPAN
class=278372120-24042001>
<SPAN
class=278372120-24042001>
EM 2.2
File Not Found Errors Using Enterprise Reports and DB Config/Status
Reports
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Versions Affected ~~~~~~~~~~~~~~~~~ Oracle Enterprise Manager Release 2.2.0.0.0 Platforms Affected ~~~~~~~~~~~~~~~~~~Sun Solaris
generated database-specific HTML reports. Likelihood of Occurrence/Possible Symptoms ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ File not found errors willalways occur when you navigate through generated database-specifc HTML reports if you schedule an Enterprise Report via the Console and a Database Configuration or Database Status Report via DBA Studio. All services which have special characters in their names will appear in the overview pages, but will appear as broken links (HTTP 404) when trying to drill down. Thus will not be available through the normal navigation of the EM reports. Patches ~~~~~~~ Two patches that fix these problems must be applied, and both are available from Oracle MetaLink. One patch, named OMS_22_1486038.[TAR/JAR], must be applied to the Oracle Management Server Release 2.2 machine(s) as well as the Console/DBA Studio Release 2.2 machine(s). The second patch must be applied to the Intelligent Agent machine that executes the report job. Depending on the version of the Intelligent Agent being used, you should apply one of the following patches: Agent
Version Corresponding Patch 8.0.6.x
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Go to themachine which has the Intelligent Agent which will generate the Enterprise Report or the scheduled DBA Studio Report. 2. Shutdown the Intelligent Agent. 3. Depending on the version of the Intelligent Agent being used to execute the report job, untar/Unjar
the appropriate Intelligent Agent patch to the $ORACLE_HOME/ directory. Agent Version Corresponding
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Go to themachine(s) on which the Management Server runs. 2. Shutdown the Management Server. 3. Untar/Unjar OMS_22_1486038.[TAR/JAR] to the $ORACLE_HOME directory.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Go tothe machine(s) on which the Console and DBA Studio runs. 2. Exit the Console and/or DBA Studio. 3. Untar/Unjar OMS_22_1486038.[TAR/JAR] to the $ORACLE_HOME directory. On Solaris, you can untar the file via the following command: tar -xvf OMS_22_1486038.TAR On Windows platforms, you can unjar the file using WinZip or via the following command: jar -xvf OMS_22_1486038.JAR The existing VtcGenerateReportObject.class and TCLScriptString.class files will be properly overwritten. 4. Relaunch the Console and/or DBA Studio. References ~~~~~~~~~~ @ <Bug
@
@
@
![]() |
![]() |