Installation Checklist for EM 10g GC 10.2.0.1 to 10.2.0.2 OMS...-422062.1-程序员宅基地

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/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/17252115/viewspace-760179/

本文链接：https://blog.csdn.net/cuilian2013/article/details/100401738

原作者删帖不实内容删帖广告或垃圾文章投诉

智能推荐

c# 调用c++ lib静态库_c#调用lib-程序员宅基地

文章浏览阅读2w次，点赞7次，收藏51次。四个步骤1.创建C++ Win32项目动态库dll 2.在Win32项目动态库中添加外部依赖项 lib头文件和lib库3.导出C接口4.c#调用c++动态库开始你的表演...①创建一个空白的解决方案，在解决方案中添加 Visual C++ , Win32 项目空白解决方案的创建：添加Visual C++ , Win32 项目这......_c#调用lib

deepin/ubuntu安装苹方字体-程序员宅基地

文章浏览阅读4.6k次。苹方字体是苹果系统上的黑体，挺好看的。注重颜值的网站都会使用，例如知乎：font-family: -apple-system, BlinkMacSystemFont, Helvetica Neue, PingFang SC, Microsoft YaHei, Source Han Sans SC, Noto Sans CJK SC, W..._ubuntu pingfang

html表单常见操作汇总_html表单的处理程序有那些-程序员宅基地

文章浏览阅读159次。表单表单概述表单标签表单域按钮控件demo表单标签表单标签基本语法结构<form action="处理数据程序的url地址“ method=”get|post“ name="表单名称”></form><!--method将表单中的数据传送给服务器处理，get方式直接显示在url地址中，数据可以被缓存，且长度有限制；而post方式数据隐藏传输，_html表单的处理程序有那些

PHP设置谷歌验证器（Google Authenticator）实现操作二步验证_php otp 验证器-程序员宅基地

文章浏览阅读1.2k次。使用说明:开启Google的登陆二步验证（即Google Authenticator服务）后用户登陆时需要输入额外由手机客户端生成的一次性密码。实现Google Authenticator功能需要服务器端和客户端的支持。服务器端负责密钥的生成、验证一次性密码是否正确。客户端记录密钥后生成一次性密码。下载谷歌验证类库文件放到项目合适位置(我这边放在项目Vender下面)https://github.com/PHPGangsta/GoogleAuthenticatorPHP代码示例://引入谷_php otp 验证器

【Python】matplotlib.plot画图横坐标混乱及间隔处理_matplotlib更改横轴间距-程序员宅基地

文章浏览阅读4.3k次，点赞5次，收藏11次。matplotlib.plot画图横坐标混乱及间隔处理_matplotlib更改横轴间距

docker — 容器存储_docker 保存容器-程序员宅基地

文章浏览阅读2.2k次。①Storage driver 处理各镜像层及容器层的处理细节，实现了多层数据的堆叠，为用户提供了多层数据合并后的统一视图②所有 Storage driver 都使用可堆叠图像层和写时复制（CoW）策略③docker info 命令可查看当系统上的 storage driver主要用于测试目的，不建议用于生成环境。_docker 保存容器

随便推点

网络拓扑结构_网络拓扑csdn-程序员宅基地

文章浏览阅读834次，点赞27次，收藏13次。网络拓扑结构是指计算机网络中各组件（如计算机、服务器、打印机、路由器、交换机等设备）及其连接线路在物理布局或逻辑构型上的排列形式。这种布局不仅描述了设备间的实际物理连接方式，也决定了数据在网络中流动的路径和方式。不同的网络拓扑结构影响着网络的性能、可靠性、可扩展性及管理维护的难易程度。_网络拓扑csdn

JS重写Date函数，兼容IOS系统_date.prototype 将所有 ios-程序员宅基地

文章浏览阅读1.8k次，点赞5次，收藏8次。IOS系统Date的坑要创建一个指定时间的new Date对象时，通常的做法是：new Date("2020-09-21 11:11:00")这行代码在 PC 端和安卓端都是正常的，而在 iOS 端则会提示 Invalid Date 无效日期。在IOS年月日中间的横岗许换成斜杠，也就是new Date("2020/09/21 11:11:00")通常为了兼容IOS的这个坑，需要做一些额外的特殊处理，笔者在开发的时候经常会忘了兼容IOS系统。所以就想试着重写Date函数，一劳永逸，避免每次ne_date.prototype 将所有 ios