Installation Checklist for EM 10g GC 10.2.0.1 to 10.2.0.2 OMS...-422062.1

rongshiyuan發表於2013-05-08
原文網址 : http://blog.itpub.net/17252115/viewspace-760179/
GC
Installation Checklist for EM 10g Grid Control 10.2.0.1 to 10.2.0.2 OMS and Repository Upgrades [ID 422062.1]

In this Document
Purpose
Scope and Application
Installation Checklist for EM 10g Grid Control 10.2.0.1 to 10.2.0.2 OMS and Repository Upgrades
Reducing the Upgrade Time:
Preparing the Repository Database:
Preparing for the Upgrade:
Post-processing After the Upgrade:

Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.2
Information in this document applies to any platform.

Purpose

This article is a quick checklist to follow when upgrading EM 10g 10.2.0.1 to EM 10g 10.2.0.2

Scope and Application

This article is intended for anyone needing to upgrade EM Grid Control from 10.2.0.1 to 10.2.0.2 by installing the 10.2.0.2 Grid Control patchset.

Installation Checklist for EM 10g Grid Control 10.2.0.1 to 10.2.0.2 OMS and Repository Upgrades

Reducing the Upgrade Time:


To speed up the data migration part, a couple of maintenance tasks should be performed on the repository prior to the upgrade.

NOTE: All statements below should be ran as the 'SYSMAN' user (Repository owner).

1. Run the partition maintenance routines:
In order to run the partition maintenance routines, the OMS's will
have to be stopped.
After all the OMS's have been shutdown, perform. the following steps:
    SQL> EXEC emd_maintenance.remove_em_dbms_jobs;
    SQL> ALTER SYSTEM SET job_queue_processes=0 SID='*';
    SQL> EXEC emd_maintenance.partition_maintenance;
    SQL> ALTER SYSTEM SET job_queue_processes=10 SID='*';
    SQL> EXEC emd_maintenance.submit_em_dbms_jobs;
2. Clean up all pending-delete ECM snapshots
Delete all pending-delete ECM snapshots, by running these two
PL/SQL routines:

    DECLARE
      pcb_params MGMT_PURGE_CALLBACK_PARAMS :=
        MGMT_PURGE_CALLBACK_PARAMS(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL);
    BEGIN
      ecm_ct.DELETE_SNAPSHOTS(pcb_params);
    END;
    /

    DECLARE
      pcb_params MGMT_PURGE_CALLBACK_PARAMS := 
        MGMT_PURGE_CALLBACK_PARAMS(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL);
    BEGIN
      ecm_ct.DELETE_HOST_CONFIG_SNAPSHOTS(pcb_params);
    END;
    /

3. After running all the cleanup, make sure the statistics on all the repository tables are accurate and up-to-date. Run this procedure to analyze the statistics on the repository tables:
    SQL> EXEC emd_maintenance.analyze_emd_schema('SYSMAN');


Preparing the Repository Database:

1. If the version of the repository database is 10.1.0.3 or 10.1.0.4, the following patch will need to get applied to the repository database prior to the upgrade:

Bug 4143213: VPD MISBEHAVIOUR CAUSES RANDOM FAILURES IN EM GRID JOB SYSTEM

2. If the version of the repository database is 10.1.0.4 or 10.1.0.5, the following patch will need to get applied to the repository database prior to the upgrade:

Bug 4329444: SKIP SCAN OF COMPRESSED INDEX ON INDEX-ORGANIZED TABLE (IOT) GIVES WRONG RESULTS
On Windows platforms, you will need to upgrade the 10.1.0.4 database to 10.1.0.5 using patch 5731187. The 10.1.0.5 patchset includes the patch 4329444.


3. If the version of the repository database is 10.2.0.1 to 10.2.0.3, the following patch will need to be applied to the repository database prior to upgrade:

Bug 5103126: INSERTS TAKEING 2 TO 3X LONGER IN 10.2.0.2 WITH PRESENCE OF
UNIQUE INDEX


Preparing for the Upgrade:

1. If Grid Control has been running with version 10.2.0.1 for a while, the table MGMT_JOB_STATE_CHANGES will have grown quite considerable in size.
To optimize the flow of jobs, and the dispatching of jobs with 10.2.0.2, this table should get truncated:
    SQL> TRUNCATE TABLE mgmt_job_state_changes;
2. Uninstall the 10.2.0.1 patch for Bug 5043773
5043773: PERF: MMR TRIGGER IS TOO HEAVY
If this patch is applied, the upgrade to 10.2.0.2 will fail.
     $ PATH=$ORACLE_HOME/OPatch:$PATH
     $ export PATH
     $ cd      $ opatch rollback -id 5043773

After the upgraded has completed, the 10.2.0.2 version of this patch can be applied:
Bug 5403839: MLR FOR BUGS 4712213 AND 5043773 ON TOP OF 10.2.0.2

3. Run the EMDiagKit and fix all of the found issues.
Certain problems in the repository can be found and fixed using the EMDiagkit. See Note.421053.1 Prior to running the upgrade of Grid Control, verify the repository by running the EMDiagKit:

To verify:
    SQL> EXEC mgmt_diag.VerifyAll(9);

To verify and Fix:
    SQL> EXEC mgmt_diag.VerifyAll(9,TRUE);



Post-processing After the Upgrade:

1. Check the status of the DBMS_JOBS.
After bringing up the repository, and with the OMS's all up-and-running, run this query, to verify the conditions of the DBMS_JOBS:

    SQL> SELECT COUNT(*) FROM user_jobs;

    COUNT(*)
    --------
          17

This query should return 17 on the migrated repository.

2. Since several tables got migrated and changed during the upgrade process, the statistics on these tables are not in sync anymore. To get accurate and up-to-date statistics on the repository, analyze the repository schema again:
    SQL> EXEC emd_maintenance.analyze_emd_schema('SYSMAN');

3. After the upgrade has completed, and the environment has been upgraded to 10gR2, verify the system again with the EMdiagkit:
    SQL> EXEC mgmt_diag.VerifyAll(9);


Critical patch list:
--------------------
This is the list of critical patches which is needed for 10.2.0.2:

4712213: PERF: OHSEM - FULL TABLE SCANS ON METRIC ERRORS PURGE
5055727: METRICS FOR RAC ARE SHOWING UP TWICE AFTER THRESHOLD CHANGE VIA TEMPLATE
5382668: EM_PURGE.APPLY_PURGE_POLICIES RUNNING FOR 4 DAYS
5448666: MISMATCH BETWEEN PING AND CURRENT AVAILABILITY FOR TARGETS
5709628: MLR FOR BUGS 4969057, 5108394, 5357916, 54038 ON TOP OF 10.2.0.2 FOR LINUX/INTEL
5725201: MLR FOR BUG-5690074 AND BUG-5661403 ON TOP OF 10.2.0.2 FOR LINUX/INTEL
5938050: JOB BACKLOG DUE TO REVERSE PING JOBS
5977153: TABLES MGMT_DELTA_ENTRY AND MGMT_DELTA_ENTRY_VALUES GROWING TOO FAST

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-760179/，如需轉載，請註明出處，否則將追究法律責任。

相關文章