Upgrade of database with GC repository resides

Question

I have GC 10.2.0.3 running with the repository stored in a 9.2.0.8 database.
I would like to upgrade the database to 10.2.0.3 using dbua if possible. When the dbua sees an upgrade to 10.2 it creates a new SYSMAN schema, but I already have one that the Grid Control install created when I used the option "install into an existing database."
I've searched MetaLink on how to do this, and created a SR but am having trouble getting support to understand what I'm attempting.
I'm open to anything, create a new database, etc. The only thing I want to be sure of is to not loose the information that I've already established in Grid, and I'm assuming it's stored in the SYSMAN schema.

Answer 1

Totally fresh clean 10gR2 database on a different host and platform.
2.3 Export/Import
If the source and destination database is non-10g, then export/import is the only option for cross platform database migration.
For performance improvement of export/import, set higher value for BUFFER and RECORDLENGTH . Do not export to NFS as it will slow down the process considerably.
Direct path can be used to increase performance. Note – As EM uses VPD, conventional mode will only be used by Oracle on tables where policy is defined.
Also User running export should have EXEMPT ACCESS POLICY privilege to export all rows as that user is then exempt from VPD policy enforcement. SYS is always exempted from VPD or Oracle Label Security policy enforcement, regardless of the export mode, application, or utility that is used to extract data from the database.
2.3.1 Prepare for Export/Import
* Mgmt_metrics_raw partitions check
select table_name,partitioning_type type,
partition_count count, subpartitioning_type subtype from
dba_part_tables where table_name = 'MGMT_METRICS_RAW'
If MGMT_METRICS_RAW has more than 3276 partitions please see Bug 4376351 – This bug is fixed in 10.2. Old partitions should be dropped before export/import to avoid this issue – This will also speed up the export/import process.
To drop old partitions - run exec emd_maintenance.partition_maintenance
(This needs shutdown of OMS and set job_queue_processes to 0 during the time drop partitions is run) – Please refer to EM Performance Best practices document for more details on usage.
Workaround to avoid bug 4376351 is to export mgmt_metrics_raw in conventional mode – This is needed only if drop partition is not run. Note - drop old partitions run is highly recommended.
* Shutdown OMS instances and prepare for migration
Shutdown OMS, set job queue_processes to 0 and remove dbms jobs using commands
connect /as sysdba
alter system set job_queue_processes=0;
connect sysman/<password>
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_remove_dbms_jobs.sql
2.3.2 Export
Before running export make sure that NLS_LANG variable is same as database characterset. For example after running this query
SQL> select value from nls_database_parameters where PARAMETER='NLS_CHARACTERSET';
VALUE
WE8ISO8859P1
Then NLS_LANG environment variable should be set to AMERICAN_ AMERICA. WE8ISO8859P1
* Export data
exp full=y constraints=n indexes=n compress=y file=fullem102_1.dmp log=fullem102exp_1.log
Provide system username and password when prompted.
Verify the log file and make sure that no characterset conversion happens (this line should not be present in log file “possible charset conversion”)
* Export without data and with constraints
exp full=y constraints=y indexes=y rows=n file=fullem102_2.dmp log=fullem102exp_2.log
Provide system username and password when prompted
2.3.3 Import
Before running import make sure that NLS_LANG variable is same as database characterset.
* Run RepManager to drop target repository (if target database has EM repository installed)
cd ORACLE_HOME/ sysman/admin/emdrep/bin
RepManager repository_host repository_port repository_SID -sys_password password_for_sys_account -action drop
* Pre-create the tablespaces and the users in target database
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_create_tablespaces.sql
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_create_repos_user.sql
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_pre_import.sql
For first 2 scripts, we need to provide input arguments when prompted or you can provide them on command line for example
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_create_tablespaces.sql MGMT_TABLESPACE <path>/mgmt.dbf <size of mgmt.dbf> <aotoextend size> MGMT_ECM_DEPOT_TS <path>/mgmt_ecm_depot1.dbf <size of mgmt_ecm_depot1.dbf> <aotoextend size> MGMT_TABLESPACE <path>/mgmt.dbf <size of mgmt.dbf> <aotoextend size>
@/scratch/nagrawal/OracleHomes/oms10g/sysman/admin/emdrep/sql/core/latest/admin/admin_create_repos_user.sql sysman <sysman password> MGMT_TABLESPACE TEMP CENTRAL ON
* Import data -
imp constraints=n indexes=n FROMUSER=sysman TOUSER=sysman buffer=2097152 file=fullem102_1.dmp log=fullem102imp_1.log
* Import without data and with constraints -
imp constraints=y indexes=y FROMUSER=sysman TOUSER=sysman buffer=2097152 rows=n ignore=y file=fullem102_2.dmp log=fullem102imp_2.log
Verify the log file and make sure that no characterset conversion happens (this line should not be present in log file “possible charset conversion”)
2.3.4 Post Import EM Steps
* Please refer to Section 3.1 for Post Migration EM Specific Steps
3 Post Repository Migration Activities
3.1 Post Migration EM Steps
Following EM specific Steps should be carried out post migration -
* Recompile all invalid objects in sysman schema using
connect sysman/<password>
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_recompile_invalid.sql
* Run post plugin steps to recompile any invalids, create public synonyms, create other users, enable VPD policy, repin packages-
connect sysman/<password>
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_create_synonyms.sql
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_post_import.sql
Provide <ORACLE_HOME/sysman/admin/emdrep/sql for em_sql_root
SYSMAN for em_repos_user
MGMT_TABLESPACE for em_tablespace_name
TEMP for em_temp_tablespace_name
Note – The users created by admin_post_import will have same passwords as username.
Check for invalid objects – compare source and destination schemas for any discrepancy in counts and invalids.
* Following queues are not enabled after running admin_post_import.sql as per EM bug 6439035, enable them manually by running
connect sysman/<password>
exec DBMS_AQADM.START_QUEUE( queue_name=> 'MGMT_TASK_Q');
exec DBMS_AQADM.START_QUEUE( queue_name=> 'MGMT_PAF_RESPONSE_Q');
exec DBMS_AQADM.START_QUEUE( queue_name=> 'MGMT_PAF_REQUEST_Q');
exec DBMS_AQADM.START_QUEUE( queue_name=> 'MGMT_LOADER_Q');
* Please check for context using following query
connect sysman/<password>
select * from dba_context where SCHEMA='SYSMAN';
If any of following context is missing create them using
connect sysman/<password>
create or replace context storage_context sing storage_ui_util_pkg;
create or replace context em_user_context sing setemusercontext;
* Partition management
Check if necessary partitions are created so that OMS does not run into problems for loading into non-existent partitions (This problem can come only if there are gap of days between export and import) –
exec emd_maintenance.analyze_emd_schema('SYSMAN');
This will create all necessary partitions up to date.
* Submit EM dbms jobs
Reset back job_queue_processes to original value and resubmit EM dbms jobs
connect /as sysdba
alter system set job_queue_processes=10;
connect sysman/<password>
@ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_submit_dbms_jobs.sql
* Update OMS properties and startup OMS
Update emoms.properties to reflect the migrated repository - oracle.sysman.eml.mntr.emdRepConnectDescriptor
Update host name, port with the correct value and start the OMS.
* Relocate “Management Services and Repository” target
If “Management Services and repository” target needs to be migrated to the destination host, delete the old "Management Services and Repository" target. Add it again with same name "Management Services and Repository" on agent running on new machine.
* Run following sql to verify the repository collections are enabled for emrep target
SELECT
target_name,
metric_name,
task.task_id,
task.interval,
task.error_message,
trunc((mgmt_global.sysdate_utc-next_collection_timestamp )/1440) delay
from mgmt_collection_metric_tasks mtask,
mgmt_collection_tasks task,
mgmt_metrics met,
mgmt_targets tgt
where met.metric_guid = mtask.metric_guid AND
tgt.target_guid = mtask.target_guid AND
mtask.task_id = task.task_id(+) AND
met.source_type > 0 AND
met.source != ' '
AND tgt.target_type='oracle_emrep'
ORDER BY mtask.task_id;
This query should result same records in both source and destination database. If you find any of collections missing in destination database, run following to schedule them in destination database
DECLARE
traw RAW(16);
tname VARCHAR2(256);
ttype VARCHAR2(64);
BEGIN
SELECT target_name, target_type, target_guid
INTO tname, ttype, traw
FROM mgmt_targets
WHERE target_type = 'oracle_emrep';
mgmt_admin_data.add_emrep_collections(tname,ttype,traw);
END;
* Discover/relocate Database and database Listener targets
Delete the old repository database target and listener and rediscover the target database and listener in EM