Title: RE: oem2.2

Thank you very much.

li

    -----Original Message-----
    From:   Haskins, Ed [SMTP:[EMAIL PROTECTED]]
    Sent:   Tuesday, April 24, 2001 5:29 PM
    To:     Multiple recipients of list ORACLE-L
    Subject:        RE: oem2.2

    Did you go to MetaLink and do a search on the error?� This would likely point to the patch!

    I did...look what I found:

    Ed Haskins
    Oracle DBA
    Verizon Wireless


    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
    ����� Win32 (Windows 95, Windows 98, Windows NT, and Windows 2000)
    ����
    � Description
    � ~~~~~~~~~~~
    � After scheduling an Enterprise Report via the Console and a
    � Database Configuration or Database Status Report via DBA Studio,
    � file not found errors will occur as you navigate through the
    � generated database-specific HTML reports.�

    � Likelihood of Occurrence/Possible Symptoms
    � ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    � File not found errors will always 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�������������� IA_806_1356586.[TAR/JAR]
    ��������� 8.1.5.x�������������� IA_815_1356586.[TAR/JAR]
    ��������� 8.1.6.x�������������� IA_816_1356586.[TAR/JAR]
    ��������� 8.1.7.x�������������� IA_817_1356586.[TAR/JAR]�������

    � Scheduling of an Enterprise Report, Database Configuration Report,
    � or Database Status Report is not supported by any other version of
    � the Intelligent Agent.

    � Note:� These patches can be downloaded from the Oracle Support
    � Services website at http://metalink.oracle.com by navigating to the
    � 'Patches' download screen; selecting Oracle Enterprise Manager (for
    � the Management Server and Console/DBA Studio patches) or Oracle
    � Intelligent Agent (for the Intelligent Agent patches) from
    � the pull down menu under 'Product', and clicking the 'Submit' button.
    � From the list of available patches that are displayed, find
    � the patches referenced above.

    � To apply these patches, perform the steps outlined below.


    � Patch Application Instructions for Intelligent Agent
    � ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    � 1. Go to the machine 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 Patch
    ��������� 8.0.6.x�������������� IA_806_1356586.[TAR/JAR]
    ��������� 8.1.5.x�������������� IA_815_1356586.[TAR/JAR]
    ��������� 8.1.6.x�������������� IA_816_1356586.[TAR/JAR]
    ��������� 8.1.7.x�������������� IA_817_1356586.[TAR/JAR]

    � On Solaris, you can untar the file via the following
    � command:� tar -xvf IA_<version of Intelligent Agent>_1356586.TAR

    � On Windows platforms, you can unjar the file using WinZip
    � or via the following command: jar -xvf IA_<version of Intelligent
    Agent>_1356586.JAR

    � After untarring/unjarring, two subdirectories will be created
    � under the $ORACLE_HOME/network/agent/reports/ directory.

    � Note:� If the Intelligent Agent is version 8.0.6 for Windows NT then
    � the two subdirectories will be created under the
    � $ORACLE_HOME/net80/agent/reports/� directory.

    � 4. Restart the Intelligent Agent.


    � Patch Application Instructions for Management Server
    � ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    � 1. Go to the machine(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.�

    ���� 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.� Restart the Management Server.

    ��
    � Patch Application Instructions for Console and DBA Studio
    � ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    � 1. Go to the 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 1356586>:� HTX TEMPLATE FILES NOT CORRECTLY INSTALLED
    � @�� <Bug 1367712>:� ERROR WITH GENERATING OF REPORTS OF SERVICE NAMES IS
    � @������������������ QUOTED�
    � @�� <Bug 1473319>:� CAN'T VIEW EACH REPORT FOR DB, LISTENER,NODE DUE TO
    � @������������������ HTML NAME DIFFERENCE
    � @�� <Bug 1486038>:� DIFFERENCE IN FILENAMES BETWEEN THE DBA STUDIO AND
    � @������������������ SYSTEM REPORTS
    .

      -----Original Message-----
      From: Li, Xiangli [mailto:[EMAIL PROTECTED]]
      Sent: Tuesday, April 24, 2001 4:47 PM
      To: Multiple recipients of list ORACLE-L
      Subject: oem2.2

      Hi, all
      I want to create HTML report by using "generate enterprise report" under system menu in OEM 2.2, but got following error,

      ** Report **
      User: SYSMAN, Service: SYSMAN, Query: 0, Report: --INIT--
      ** Message **
      Unable to find template files files
      HTML generation files missing - Please apply the reports agent patch.
      ** Error **
      Intelligent Agent does not have the HTML generation files

      May I know which patch I should apply?

      thanks.
      li

Reply via email to