=============================

Transcription

1 Cross-Platform Transportable Database: ====================================== RMAN CONVERT DATABASE from Windows to Solaris using RMAN, and upgrade the same from to ================================================================================== The RMAN CONVERT DATABASE command is used to automate the movement of an entire database From one platform (the source platform) to another (the destination platform). Provided that the source and destination platforms are of the same endian format, RMAN automates most of the steps of creating a new database on the destination platform, Which contains the same data as the source database, and which has, with a few exceptions, the same settings as the source database. Windows: Win-7 32 bit: Source ============================= set pages 50 select * from v$transportable_platform order by 2; PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT AIX-Based Systems (64-bit) Big 16 Apple Mac OS Big 15 HP Open VMS Little 5 HP Tru64 UNIX Little 3 HP-UX (64-bit) Big 4 HP-UX IA (64-bit) Big 18 IBM Power Based Linux Big 9 IBM zseries Based Linux Big 13 Linux 64-bit for AMD Little 10 Linux IA (32-bit) Little 11 Linux IA (64-bit) Little 12 Microsoft Windows 64-bit for AMD Little 7 Microsoft Windows IA (32-bit) Little (our Source) 8 Microsoft Windows IA (64-bit) Little 17 Solaris Operating System (x86) Little (our Target) 1 Solaris[tm] OE (32-bit) Big 2 Solaris[tm] OE (64-bit) Big 17 rows selected. col PLATFORM_NAME for a50 select d.platform_name, endian_format from v$transportable_platform tp, v$database d where tp.platform_name = d.platform_name ; PLATFORM_NAME ENDIAN_FORMAT Microsoft Windows IA (32-bit) Little 1 P a g e

2 show parameter compatible NAME TYPE VALUE compatible string Solaris: (Target) =================== -bash-3.00$ uname -a SunOS orasolaris Generic_ i86pc i386 i86pc -bash-3.00$ cat /etc/release Oracle Solaris 10 9/10 s10x_u9wos_14a X86 Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. Assembled 11 August bash-3.00$ isainfo -kv 32-bit i386 kernel modules You can check the Platform from one of the existing DB s on Target as below. col PLATFORM_NAME for a50 select d.platform_name, endian_format from v$transportable_platform tp, v$database d where tp.platform_name = d.platform_name ; PLATFORM_NAME ENDIAN_FORMAT Solaris Operating System (x86) Little Windows: Source ============================= select name from v$database; NAME Q041 set line 200 select round(df.total/1024/1024/1024,2) "DataFile Size GB", round(log.total/1024/1024/1024,2) "Redo Log Size GB", round(control.total/1024/1024,2) "Control File Size MB", round((df.total + LOG.TOTAL + CONTROL.TOTAL)/ ,2) "Total Size Mb", round((df.total + LOG.TOTAL + CONTROL.TOTAL)/ /1024,2) "Total Size Gb" from dual, (select sum(a.bytes) TOTAL from dba_data_files a) DF, (select sum(b.bytes) TOTAL from v$log b) LOG, (select sum((cffsz+1)*cfbsz) TOTAL from x$kcccf c) CONTROL; 2 P a g e

3 DataFile Size GB Redo Log Size GB Control File Size MB Total Size Mb Total Size Gb create table mtest(nam varchar2(20)); Table created. insert into mtest values('cross Plat Mig'); 1 row created. commit; Commit complete. Check Pre-requisite on Source DB: =================================== set serveroutput on declare db_ready boolean; begin db_ready := dbms_tdb.check_db('solaris Operating System (x86)'); end; / Database is not open in READ-ONLY mode. Open the database in READ-ONLY mode and retry. PL/SQL procedure successfully completed. set serveroutput on declare external boolean; begin /* value of external is ignored, but with SERVEROUTPUT set to ON * dbms_tdb.check_external displays report of external objects * on console */ external := dbms_tdb.check_external; end; / The following directories exist in the database: SYS.DATA_PUMP_DIR PL/SQL procedure successfully completed. Make the Source DB as Read only: ==================================== shut immediate Database closed. Database dismounted. ORACLE instance shut down. 3 P a g e

4 startup mount; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. alter database open read only; Database altered. set line 200 select NAME,DB_UNIQUE_NAME,OPEN_MODE,CONTROLFILE_TYPE,DATABASE_ROLE,LOG_MODE,PROTECTION_MO DE from v$database; NAME DB_UNIQUE_NAME OPEN_MODE CONTROL DATABASE_ROLE LOG_MODE PROTECTION_MODE Q041 q041 READ ONLY CURRENT PRIMARY ARCHIVELOG MAXIMUM PERFORMANCE select distinct substr(name,1,instr(name,'\',-1)-1) PATH from v$datafile; PATH ======================== C:\ORACLE\ORADATA\Q041 Now Covert the Source DB(q041): ================================= c:\oracle>set oracle ORACLE_HOME=c:\oracle\product\10.2.0\db_1 oracle_sid=q041 rman target / CONVERT DATABASE NEW DATABASE 'test' transport script 'C:\VMDisks\winshare\orabkp\migtest\trans.sql' to platform 'Solaris Operating System (x86)' db_file_name_convert 'C:\ORACLE\ORADATA\Q041' 'C:\VMDisks\winshare\orabkp\migtest' ; c:\oracle>rman target / Recovery Manager: Release Production on Sun Sep 27 12:12: Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: Q041 (DBID= ) RMAN> CONVERT DATABASE NEW DATABASE 'test' 2> transport script 'C:\VMDisks\winshare\orabkp\migtest\trans.sql' 3> to platform 'Solaris Operating System (x86)' 4> db_file_name_convert 'C:\ORACLE\ORADATA\Q041' 'C:\VMDisks\winshare\orabkp\migtest' 5> ; 4 P a g e

5 Starting convert at 27-SEP-13 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=154 devtype=disk Directory SYS.DATA_PUMP_DIR found in the database User SYS with SYSDBA and SYSOPER privilege found in password file channel ORA_DISK_1: starting datafile conversion input datafile fno=00001 name=c:\oracle\oradata\q041\system01.dbf converted datafile=c:\vmdisks\winshare\orabkp\migtest\system01.dbf channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:15 channel ORA_DISK_1: starting datafile conversion input datafile fno=00002 name=c:\oracle\oradata\q041\undotbs01.dbf converted datafile=c:\vmdisks\winshare\orabkp\migtest\undotbs01.dbf channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:07 channel ORA_DISK_1: starting datafile conversion input datafile fno=00003 name=c:\oracle\oradata\q041\sysaux01.dbf converted datafile=c:\vmdisks\winshare\orabkp\migtest\sysaux01.dbf channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:07 channel ORA_DISK_1: starting datafile conversion input datafile fno=00004 name=c:\oracle\oradata\q041\users01.dbf converted datafile=c:\vmdisks\winshare\orabkp\migtest\users01.dbf channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:01 Run SQL script C:\VMDISKS\WINSHARE\ORABKP\MIGTEST\TRANS.SQL on the target platform to create database Edit init.ora file C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\INIT_00OL2HTU_1_0.ORA. This PFILE will be used to create the database on the target platform To recompile all PL/SQL modules, run utlirp.sql and utlrp.sql on the target platform To change the internal database identifier, use DBNEWID Utility Finished backup at 27-SEP-13 RMAN> Manually create pfile to converted location, though it s not required. ======================================================================== create pfile='c:\vmdisks\winshare\orabkp\migtest\pfile.ora' from spfile; OR Edit init.ora file C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\INIT_00OL2HTU_1_0.ORA, and set values as per your new environment.this PFILE will be used to create the database on the target platform. # Please change the values of the following parameters: control_files _00OKUCLB" audit_file_dest background_dump_dest user_dump_dest core_dump_dest db_name = "C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\CF_D-TEST_ID- = "C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\ADUMP" = "C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\BDUMP" = "C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\UDUMP" = "C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\CDUMP" = "TEST" 5 P a g e

6 Modified values ================== *.audit_file_dest='/u01/app/oracle/admin/test/adump' *.background_dump_dest='/u01/app/oracle/admin/test/bdump' *.control_files='/oradata1/test/control01.ctl' *.core_dump_dest='/u01/app/oracle/admin/test/cdump' *.user_dump_dest='/u01/app/oracle/admin/test/udump' *.db_name="test" *.compatible=' ' ftp/scp/transfer the converted files to Solaris target host: ========================================================= This ftp can be avoided if this filesystem is shared between Windows and Solaris as in my case below. C:\VMDisks\winshare\orabkp\migtest\* C:\Windows\System32>dir C:\VMDisks\winshare\orabkp\migtest\* Volume in drive C is Root Volume Serial Number is BCFF-7226 Directory of C:\VMDisks\winshare\orabkp\migtest :13 <DIR> :13 <DIR> :13 125,837,312 SYSAUX01.DBF :12 314,580,992 SYSTEM01.DBF :13 2,834 TRANS.SQL :13 209,723,392 UNDOTBS01.DBF :13 5,251,072 USERS01.DBF 5 File(s) 655,395,602 bytes 2 Dir(s) 116,189,528,064 bytes free -bash-3.00$ df -h grep win winshare 225G 117G 108G 52% /mnt/sf_winshare -bash-3.00$ cd /mnt/sf_winshare/orabkp/migtest -bash-3.00$ ls -ltrh total rwxrwxrwx 1 root vboxsf 300M Sep 29 12:12 SYSTEM01.DBF -rwxrwxrwx 1 root vboxsf 200M Sep 29 12:13 UNDOTBS01.DBF -rwxrwxrwx 1 root vboxsf 120M Sep 29 12:13 SYSAUX01.DBF -rwxrwxrwx 1 root vboxsf 5.0M Sep 29 12:13 USERS01.DBF -rwxrwxrwx 1 root vboxsf 2.8K Sep 29 12:13 TRANS.SQL -bash-3.00$ 6 P a g e

7 Below Virtual Box shows the shared folder between Windows and Solaris. Copy the datafiles to required directories in Solaris ====================================================== cp /mnt/sf_winshare/orabkp/migtest/* /oradata1/test/ -bash-3.00$ cd /oradata1/test/ -bash-3.00$ ls -ltrh total rwxr-xr-x 1 oracle dba 942 Sep 27 22:48 pfile.ora -rwxr-xr-x 1 oracle dba 2.3K Sep 27 22:48 TRANS.SQL drwxr-xr-x 2 oracle dba 512 Sep 29 22:38 arch -rwxr-xr-x 1 oracle dba 5.0M Sep 29 22:59 USERS01.DBF -rwxr-xr-x 1 oracle dba 120M Sep 29 22:59 SYSAUX01.DBF -rwxr-xr-x 1 oracle dba 300M Sep 29 22:59 SYSTEM01.DBF -rwxr-xr-x 1 oracle dba 200M Sep 29 22:59 UNDOTBS01.DBF -rw-r oracle dba 7.0M Sep 29 22:59 control01.ctl Create required directories for test DB =========================================== cd /u01/app/oracle/admin mkdir test cd test mkdir adump bdump cdump udump Create Archive folder ========================== cd /oradata1/test mkdir arch cd arch pwd /oradata1/test/arch 7 P a g e

8 Verify and Copy the pfile to ORACLE_HOME/dbs in Solaris. =========================================================== -bash-3.00$ cat /oradata1/test/pfile.ora test. db_cache_size= test. java_pool_size= test. large_pool_size= test. shared_pool_size= test. streams_pool_size=0 *.db_block_size=8192 *.db_domain='' *.db_file_multiblock_read_count=16 *.java_pool_size=0 *.job_queue_processes=10 *.log_archive_format='test_arch_t%ts%sr%r.arc' *.open_cursors=300 *.pga_aggregate_target= *.processes=150 *.remote_login_passwordfile='exclusive' *.sga_max_size= *.sga_target= *.standby_file_management='auto' *.undo_management='auto' *.undo_tablespace='undotbs1' *.db_name='test' *.log_archive_dest_1='location=/oradata1/test/arch' *.audit_file_dest='/u01/app/oracle/admin/test/adump' *.background_dump_dest='/u01/app/oracle/admin/test/bdump' *.compatible=' ' *.control_files='/oradata1/test/control01.ctl' *.core_dump_dest='/u01/app/oracle/admin/test/cdump' *.user_dump_dest='/u01/app/oracle/admin/test/udump' Copy the pfile to init<sid>.ora ===================================== cp /oradata1/test/pfile.ora $ORACLME/dbs/inittest.ora Modify and run file TRANS.SQL which got generated as part of convert Before Modification ==================== STARTUP NOMOUNT PFILE='C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\INIT_00OL2HTU_1_0.ORA' CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS FORCE LOGGING ARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP 1 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\ARCH_D-TEST_ID _S-23_T- 1_A _00OL2HTU' SIZE 50M, GROUP 2 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\ARCH_D-TEST_ID _S-24_T- 1_A _00OL2HTU' SIZE 50M, GROUP 3 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\ARCH_D-TEST_ID _S-22_T- 1_A _00OL2HTU' SIZE 50M 8 P a g e

9 DATAFILE 'C:\VMDISKS\WINSHARE\ORABKP\MIGTEST\SYSTEM01.DBF', 'C:\VMDISKS\WINSHARE\ORABKP\MIGTEST\UNDOTBS01.DBF', 'C:\VMDISKS\WINSHARE\ORABKP\MIGTEST\SYSAUX01.DBF', 'C:\VMDISKS\WINSHARE\ORABKP\MIGTEST\USERS01.DBF' CHARACTER SET WE8MSWIN1252 ; -- Database can now be opened zeroing the online logs. ALTER DATABASE OPEN RESETLOGS; ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DATA_D- TEST_I _TS-TEMP_FNO-1_00OL2HTU' SIZE AUTOEXTEND ON NEXT MAXSIZE 32767M; SHUTDOWN IMMEDIATE STARTUP UPGRADE SHUTDOWN IMMEDIATE STARTUP set feedback 6; After modification =================== -bash-3.00$ cat TRANS.SQL REM STARTUP NOMOUNT PFILE='/oradata1/test/pfile.ora' STARTUP NOMOUNT CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS FORCE LOGGING ARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP 1 '/oradata1/test/redo01.rdo' SIZE 50M, GROUP 2 '/oradata1/test/redo02.rdo' SIZE 50M, GROUP 3 '/oradata1/test/redo03.rdo' SIZE 50M DATAFILE '/oradata1/test/system01.dbf', '/oradata1/test/undotbs01.dbf', '/oradata1/test/sysaux01.dbf', '/oradata1/test/users01.dbf' CHARACTER SET WE8MSWIN1252 ; -- Database can now be opened zeroing the online logs. ALTER DATABASE OPEN RESETLOGS; ALTER TABLESPACE TEMP ADD TEMPFILE '/oradata1/test/temp01.dbf' SIZE AUTOEXTEND ON NEXT MAXSIZE 32767M; set echo off prompt ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ prompt * Your database has been created successfully! 9 P a g e

10 prompt * There are many things to think about for the new database. Here prompt * is a checklist to help you stay on track: prompt * 1. You may want to redefine the location of the directory objects. prompt * 2. You may want to change the internal database identifier (DBID) prompt * or the global database name for this database. Use the prompt * NEWDBID Utility (nid). prompt ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SHUTDOWN IMMEDIATE REM STARTUP UPGRADE PFILE='/oradata1/test/pfile.ora' STARTUP SHUTDOWN IMMEDIATE REM STARTUP PFILE='/oradata1/test/pfile.ora' STARTUP -- The following step will recompile all PL/SQL modules. -- It may take serveral hours to *****************End of TRANS.SQL ************** export ORACLE_SID=test sqlplus / as sysdba sh-3.00$ sqlplus / as sysdba SQL*Plus: Release Production on Mon Sep 30 20:50: Copyright (c) 1982, 2005, Oracle. All Rights Reserved. Connected to an idle instance set echo -- The following commands will create a new control file and use it -- to open the database. -- Data used by Recovery Manager will be lost. -- The contents of online logs will be lost and all backups will -- be invalidated. Use this only if online logs are damaged. -- After mounting the created controlfile, the following SQL -- statement will place the database in the appropriate -- protection mode: -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE REM> STARTUP NOMOUNT PFILE='/oradata1/test/pfile.ora' STARTUP NOMOUNT ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes 10 P a g e

11 CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS FORCE LOGGING ARCHIVELOG 2 MAXLOGFILES 16 3 MAXLOGMEMBERS 3 4 MAXDATAFILES MAXINSTANCES 8 6 MAXLOGHISTORY LOGFILE 8 GROUP 1 '/oradata1/test/redo01.rdo' SIZE 50M, 9 GROUP 2 '/oradata1/test/redo02.rdo' SIZE 50M, 10 GROUP 3 '/oradata1/test/redo03.rdo' SIZE 50M 11 DATAFILE 12 '/oradata1/test/system01.dbf', 13 '/oradata1/test/undotbs01.dbf', 14 '/oradata1/test/sysaux01.dbf', 15 '/oradata1/test/users01.dbf' 16 CHARACTER SET WE8MSWIN ; Control file created. -- Database can now be opened zeroing the online logs. ALTER DATABASE OPEN RESETLOGS; ALTER DATABASE OPEN RESETLOGS * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced ALTER TABLESPACE TEMP ADD TEMPFILE '/oradata1/test/temp01.dbf' 2 SIZE AUTOEXTEND ON NEXT MAXSIZE 32767M; ERROR: ORA-03114: not connected to ORACLE -- End of tempfile additions. -- set echo off ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Your database has been created successfully! * There are many things to think about for the new database. Here * is a checklist to help you stay on track: * 1. You may want to redefine the location of the directory objects. * 2. You may want to change the internal database identifier (DBID) * or the global database name for this database. Use the * NEWDBID Utility (nid). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ORA-24324: service handle not initialized ORA-01041: internal error. hostdef extension doesn't exist ORA-24324: service handle not initialized ORA-01041: internal error. hostdef extension doesn't exist WHENEVER SQLERROR EXIT; DOC 11 P a g e

12 DOC> The following statement will cause an "ORA-01722: invalid number" DOC> error if there the database was not opened in UPGRADE mode DOC> DOC> If you encounter this error, execute "SHUTDOWN", "STARTUP UPGRADE" and DOC> re-execute utlirp.sql DOC># SELECT TO_NUMBER('MUST_BE_OPEN_UPGRADE') FROM v$instance 2 WHERE status!= 'OPEN MIGRATE'; ERROR: ORA-03114: not connected to ORACLE Disconnected from Oracle Database 10g Enterprise Edition Release Production With the Partitioning, OLAP and Data Mining options sh-3.00$ sh-3.00$ exit Note: Script failed to open database in Reset Logs because the Our Source DB version was and on Solaris Oracle software is We need to upgrade before continuing further steps. Alert.log ========== Mon Sep 30 20:52: Errors in file /u01/app/oracle/admin/test/udump/test_ora_1577.trc: ORA-00704: bootstrap process failure ORA-39700: database must be opened with UPGRADE option Mon Sep 30 20:52: Error 704 happened during db open, shutting down database USER: terminating instance due to error 704 Instance terminated by USER, pid = 1577 ORA-1092 signalled during: ALTER DATABASE OPEN RESETLOGS... We need to manually perform further steps to upgrade to as below: =========================================================================== startup upgrade ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. ORA-01113: file 1 needs media recovery ORA-01110: data file 1: '/oradata1/test/system01.dbf'!ls -ltrh /oradata1/test/*.rdo -rw-r oracle dba 50M Sep 30 20:52 /oradata1/test/redo01.rdo -rw-r oracle dba 50M Sep 30 20:52 /oradata1/test/redo02.rdo -rw-r oracle dba 50M Sep 30 20:52 /oradata1/test/redo03.rdo 12 P a g e

13 select GROUP#,SEQUENCE#,FIRST_CHANGE# from v$log; GROUP# SEQUENCE# FIRST_CHANGE# recover database until cancel using backup controlfile; ORA-00279: change generated at 09/30/ :52:39 needed for thread 1 ORA-00289: suggestion : /oradata1/test/arch/test_arch_t1s1r arc ORA-00280: change for thread 1 is in sequence #1 Specify log: {<RET>=suggested filename AUTO CANCEL} /oradata1/test/redo03.rdo => Here we applied the last redo generated from Log applied. resetlogs. Media recovery complete. Now database recovered successfully, so open database with resetlogs for upgrade as below. ======================================================== ALTER DATABASE OPEN RESETLOGS upgrade; Database altered. Alert.log ============ Mon Sep 30 21:06: ALTER DATABASE RECOVER LOGFILE '/oradata1/test/redo03.rdo' Mon Sep 30 21:06: Media Recovery Log /oradata1/test/redo03.rdo Mon Sep 30 21:06: Incomplete recovery applied all redo ever generated. Recovery completed through change Mon Sep 30 21:06: Media Recovery Complete (test) Completed: ALTER DATABASE RECOVER LOGFILE '/oradata1/test/redo03.rdo' Mon Sep 30 21:08: ALTER DATABASE OPEN RESETLOGS upgrade Mon Sep 30 21:08: RESETLOGS after complete recovery through change Resetting resetlogs activation ID (0x7eb39e79) Online log /oradata1/test/redo01.rdo: Thread 1 Group 1 was previously cleared Online log /oradata1/test/redo02.rdo: Thread 1 Group 2 was previously cleared Mon Sep 30 21:08: Setting recovery target incarnation to 3 Mon Sep 30 21:08: Assigning activation ID (0x7eb35533) LGWR: STARTING ARCH PROCESSES ARC0 started with pid=13, OS id=1620 Mon Sep 30 21:08: ARC0: Archival started ARC1: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE Thread 1 opened at log sequence 1 Current log# 3 seq# 1 mem# 0: /oradata1/test/redo03.rdo 13 P a g e

14 .. Dictionary check beginning Tablespace 'TEMP' #3 found in data dictionary, but not in the controlfile. Adding to controlfile. Dictionary check complete Mon Sep 30 21:08: SMON: enabling tx recovery Mon Sep 30 21:08: ********************************************************************* WARNING: The following temporary tablespaces contain no files. This condition can occur when a backup controlfile has been restored. It may be necessary to add files to these tablespaces. That can be done using the SQL statement: ALTER TABLESPACE <tablespace_name> ADD TEMPFILE Alternatively, if these temporary tablespaces are no longer needed, then they can be dropped. Empty temporary tablespace: TEMP ********************************************************************* Database Characterset is WE8MSWIN1252 Updating NLS parameters in sys.props$ -- adding NLS parameters.. MMON started with pid=11, OS id=1626 MMNL started with pid=12, OS id=1628 Mon Sep 30 21:08: ALTER SYSTEM enable restricted session; Mon Sep 30 21:08: ALTER SYSTEM SET _system_trig_enabled=false SCOPE=MEMORY; Mon Sep 30 21:08: ALTER SYSTEM SET aq_tm_processes=0 SCOPE=MEMORY; Mon Sep 30 21:08: ALTER SYSTEM SET resource_manager_plan='' SCOPE=MEMORY; Threshold validation cannot be done before catproc is loaded. replication_dependency_tracking turned off (no async multimaster replication found) Mon Sep 30 21:08: LOGSTDBY: Validating controlfile with logical metadata Mon Sep 30 21:08: LOGSTDBY: Validation complete Global Name changed to TEST Completed: ALTER DATABASE OPEN RESETLOGS upgrade Mon Sep 30 21:09: Add Temp tablespace: ======================= SQ> ALTER TABLESPACE TEMP ADD TEMPFILE '/oradata1/test/temp01.dbf' SIZE AUTOEXTEND ON NEXT MAXSIZE 32767M; Tablespace altered. 14 P a g e

15 col HOST_NAME for a20 col DB_UNIQUE_NAME for a10 set line 200 select NAME,DB_UNIQUE_NAME,STATUS,OPEN_MODE,CONTROLFILE_TYPE,DATABASE_ROLE,LOG_MODE,PROTEC TION_MODE,VERSION from v$instance,v$database; NAME DB_UNIQUE_ STATUS OPEN_MODE CONTROL DATABASE_ROLE LOG_MODE PROTECTION_MODE VERSION TEST test OPEN MIGRATE READ WRITE CURRENT PRIMARY ARCHIVELOG MAXIMUM PERFORMANCE Upgrade DB, as the database is open in Upgrade mode: ====================================================== Run the Catupgrd.sql to upgrade DB to TIMESTAMP COMP_TIMESTAMP UPGRD_END :49:50. Oracle Database 10.2 Upgrade Status Utility :49:50. Component Status Version HH:MM:SS Oracle Database Server VALID :09:08 Oracle Enterprise Manager VALID :00:43. Total Upgrade Time: 00:09:51 DOC> DOC> Next shutdown immediate, restart for normal operation, and then DOC> run utlrp.sql to recompile any invalid application objects. DOC> Alert.log =============== Mon Sep 30 21:40: SERVER COMPONENT id=patch_bgn: timestamp= :40:01. Thread 1 advanced to log sequence 9 Current log# 2 seq# 9 mem# 0: /oradata1/test/redo02.rdo Mon Sep 30 21:49: SERVER COMPONENT id=catproc: timestamp= :49:06 15 P a g e

16 SERVER COMPONENT id=rdbms: status=valid, version= , timestamp= :49:06 Mon Sep 30 21:49: Thread 1 advanced to log sequence 10 Current log# 3 seq# 10 mem# 0: /oradata1/test/redo03.rdo Mon Sep 30 21:49: SERVER COMPONENT id=em: status=valid, version= , timestamp= :49:50 SERVER ACTION=UPGRADE id=: Upgraded from SERVER COMPONENT id=upgrd_end: timestamp= :49:50 Mon Sep 30 21:52: set line 200 col COMP_NAME for a55 SELECT COMP_ID,comp_name, status, substr(version,1,10)as version,modified from dba_registry; COMP_ID COMP_NAME STATUS VERSION MODIFIED OWM Oracle Workspace Manager VALID SEP :53:13 EM Oracle Enterprise Manager VALID SEP :49:50 CATALOG Oracle Database Catalog Views VALID SEP :49:06 CATPROC Oracle Database Packages and Types VALID SEP :49:06 Now follow further steps from TRANS.SQL for migrating: =========================================================== SHUTDOWN IMMEDIATE REM STARTUP UPGRADE PFILE='/oradata1/test/pfile.ora' STARTUP Out Put of above =================.. Rem =========================================================================== Rem END utlip.sql Rem =========================================================================== DOC DOC> utlirp.sql completed successfully. All PL/SQL objects in the DOC> database have been invalidated. DOC> DOC> Shut down and restart the database in normal mode and run utlrp.sql to DOC> recompile invalid objects. 16 P a g e

17 Execute Below further from TRANS.sql ==================================== SHUTDOWN IMMEDIATE REM STARTUP PFILE='/oradata1/test/pfile.ora' STARTUP -- The following step will recompile all PL/SQL modules. -- It may take serveral hours to complete. archive log list Database log mode Archive Mode Automatic archival Enabled Archive destination /oradata1/test/arch Oldest online log sequence 14 Next log sequence to archive 16 Current log sequence 16 select * from mtest; NAM Cross Plat Mig set line 200 col COMP_NAME for a55 SELECT COMP_ID,comp_name, status, substr(version,1,10)as version,modified from dba_registry; COMP_ID COMP_NAME STATUS VERSION MODIFIED OWM Oracle Workspace Manager VALID SEP :07:40 EM Oracle Enterprise Manager VALID SEP :49:50 CATALOG Oracle Database Catalog Views VALID SEP :07:40 CATPROC Oracle Database Packages and Types VALID SEP :07:40 * There are many things to think about for the new database. Here * is a checklist to help you stay on track: * 1. You may want to redefine the location of the directory objects. * 2. You may want to change the internal database identifier (DBID) * or the global database name for this database. Use the * NEWDBID Utility (nid). Reference: Migration of Oracle Instances Across OS Platforms Doc ID: Note: P a g e