Window Oracle 10g rman heterogeneous directory Recovery

1. Introduction to the experimental environment                                   1.1   soa Original Database                                                                                                                                                                    database name         comsoa instance name            COMSOADBID             4133565260 database version windows 64bit 10.2.0 data file directory H:\ORACLE\ORADATA\ Comsoapfilecomsoa.__db_cache_size=1291845632comsoa.__java_pool_size=16777216comsoa.__large_pool_size= 16777216comsoa.__shared_pool_size=805306368comsoa.__streams_pool_size=0*.audit_file_dest= ' H:\oracle\admin\ Comsoa\adump ' *.background_dump_dest= ' H:\oracle\admin\COMSOA\bdump ' *.compatible= ' 10.2.0.1.0 ' *.control_files= ' H : \oracle\oradata\comsoa\control01.ctl ', ' H:\oracle\oradata\COMSOA\control02.ctl ', ' H:\oracle\oradata\COMSOA\ Control03.ctl ' *.core_dump_dest= ' H:\oracle\admin\COMSOA\cdump ' *.db_block_size=8192*.db_file_multiblock_read_ Count=16*.db_name= ' Comsoa ' *.db_recovery_file_dest= ' H:\oracle\flash_recovery_area ' *.db_recovery_file_dest_size=2147483648*.log_archive_dest_1= ' location=h:\ Oracle\archive\comsoa ' *.nls_language= ' Simplified chinese ' *.nls_territory= ' China ' *.open_cursors=300*.pga_ Aggregate_target=536870912*.processes=300*.remote_login_passwordfile= ' EXCLUSIVE ' *.sessions=335*.sga_target= 2147483648*.undo_management= ' AUTO ' *.undo_tablespace= ' UNDOTBS1 ' *.user_dump_dest= ' H:\oracle\admin\COMSOA\udump ' 1.2   Restore SOA System database name        comsoa instance name           COMSOADBID            4133565260 database version windows 32bit 10.2 data file directory e:\orasoa\oradata\comsoapfilecomsoa.__db_cache_size= 891845632comsoa.__java_pool_size=16777216comsoa.__large_pool_size=16777216comsoa.__shared_pool_size= 505306368comsoa.__streams_pool_size=0*.audit_file_dest= ' e:\orasoa\admin\COMSOA\adump ' *.background_dump_dest= ' E : \orasoa\admin\comsoa\bdump ' *.compatible= ' 10.2.0.1.0 ' *.control_files= ' e:\orasoa\oradata\COMSOA\control01.ctl ', ' e:\orasoa\oradata\COMSOA\control02.ctl ', ' e:\ Orasoa\oradata\comsoa\control03.ctl ' *.core_dump_dest= ' e:\orasoa\admin\COMSOA\cdump ' *.db_block_size=8192*.db_ File_multiblock_read_count=16*.db_name= ' Comsoa ' *.db_recovery_file_dest= ' E:\orasoa\flash_recovery_area ' *.db_ Recovery_file_dest_size=2147483648*.dispatchers= ' (protocol=tcp)   (service=comsoaxdb) ' *.job_queue_processes =10*.log_archive_dest_1= ' Location=e:\orasoa\archive\comsoa ' *.nls_language= ' Simplified chinese ' *.nls_ territory= ' China ' *.open_cursors=300*.pga_aggregate_target=336870912*.processes=300*.remote_login_passwordfile= ' EXCLUSIVE ' *.sessions=335*.sga_target=1147483648*.undo_management= ' AUTO ' *.undo_tablespace= ' UNDOTBS1 ' *.user_ dump_dest= ' e:\orasoa\admin\COMSOA\udump ' *._system_trig_enabled=false2   backup  2.1   Backup Production System c:\administrator>set oracle_sid=comsoac:\administrator>rman target  sys/**** Delete an expired archive log Rman>crosscheck archivelog allrman>delete expired archivelog rman>backup full database  format  ' H:\full_%t_%p_%s.bak ' rman>backup archivelog  all  format  ' h:\ Arch_%p_t_%p.bak '; rman> backup current controlfile format  ' H:\contol_%p_%p_%s.bak ';2.2   The 2.2.1   folder creates the folders required to create an SOA instance, including data files, dumps, archive directories e:\orasoa\admin\COMSOA\adump ' e:\orasoa\admin\COMSOA\ Bdump ' e:\orasoa\admin\COMSOA\cdump ' e:\orasoa\admin\COMSOA\updump ' db_recovery_file_dest= ' E:\orasoa\flash_ Recovery_area ' e:\orasoa\oradata\comsoa2.2.2   Create an instance of the SOA instance creation required Comsoac:\administrator>oradim.exe  -new -sid comsoa -startmode mc:\administrator>oradim.exe -edit -sid  comsoa -startmode a start the database with pfile  to mount the state sql>startup nomount pfile= ' E:\ Initcomsoa. ORA ' 2.2.3   Recovery control file copies the produced backup files to the new SOA system host and connects to the RMANC:\ADMINISTRATOR >SET ORACLE_SID=COMSOAC : \administrator >rman target /Recovery Manager:  release 10.2.0.1.0 - production on   Saturday  12 Month  3 14:24:44 201 connect to the target database: comsoa  (not mounted) rman> set dbid= 4133565260 executing command: set dbidrman> catalog start with  ' backup set ' recovery control file rman>  restore controlfile   from  ' E:\CONTROL. bak_1_20111203718 '; start  restore   03-12 month-11 use channel  ora_disk_1 channel  ORA_DISK_1:  Recovering control File Channel  ORA_DISK_1:  restore complete,  time:  00:00:01 finish  restore   03-12 Month -11 control file will automatically revert to E :\orasoa\oradata\comsoa\  2.2.4   Update control file redolog  information sql>alter  database  rename file  ' H:\oracle\oradata\COMSOA\redo01.log '  to ' E:\oracle\oradata\COMSOA\redo01.log '   sql>alter  database rename file  ' H:\oracle\oradata\COMSOA\redo01.log '  to ' e:\ Oracle\oradata\comsoa\redo01.log '  sql>alter  database rename file  ' H:\oracle\oradata\COMSOA\redo01.log '  to ' E:\oracle\oradata\COMSOA\redo01.log '   2.2.5   compiling Invalid object sql>@\orasoa\oradata\comsoa\utlrp.sqlsql>alter database open  resetlogssql>shutdown immediatesql>startup migrate2.2.6   Rebuilding temporary tablespace sql> select  name from v$tempfile; NAME--------------------------------------------------------------------------------H:\ORACLE\ORADATA\COMSOA\ TEMP01. Dbfh:\oracle\oradata\comsoa\tbs_tmp_dxpt. Orah:\oracle\oradata\comsoa\tbs_tmp_workflow. ora  Delete temporary tablespace sql> drop tablespace temp01  including  contents  and  datafiles; table space has been deleted. sql> drop tablespace tbs_tmp_dxpt including  contents and   Datafiles; The tablespace has been deleted. sql> drop tablespace tbs_tmp_workflow including  contents and  The  datafiles; table space has been deleted. Recreate temporary tablespace SQL> CREATE TEMPORARY&NBsp;tablespace tbs_tmp_dxpt  2  tempfile  ' E:\orasoa\oradata\comsoa\tbs_tmp_ Dxpt.ora '  size 500M; table space has been created. sql> create temporary tablespace  temp01  2  tempfile  ' E : \orasoa\oradata\comsoa\temp01.dbf '  size 500M; table space created. Sql> create temporary tablespace tbs_tmp_workflow  2  tempfile   ' e:\orasoa\oradata\comsoa\tbs_tmp_workflow '  size 500M; table space created. change user default temporary tablespace sql> alter database default temporary tablespace temp01sql> Alter user lgwt temporary tablespace tbs_tmp_comsoasql>alter user dxpt  temporary tablespace tbs_tmp_dxpt3  Recovery Experience issues  3.1 ORA-19751:could not  create the change trackingfile   the,  error when opening the database is as follows: Sql> startuporacle  instance started. total system global area  167772160 bytesfixed size                   1247876 bytesVariable Size               79693180 bytesDatabase Buffers            79691776 bytesRedo Buffers                 7139328 bytesDatabase  Mounted. Ora-19751: could not create the change tracking fileora-19750: change  tracking file:  ' E:\ORACLE\TRACE. LOG ' ora-27040: file create error, unable to create fileosd-04002:  unable to open fileo/s-error:  (os 5)   denied access. Ora-27041: unable to open fileosd-04002: unable to open fileo/s-error:   (Os&nbsP;2)   The system cannot find the file specified. tracking file:  ' E:\ORACLE\TRACE. LOG '   cannot be found within the system. Tracking file is a parameter that optimizes incremental backups, which can be used temporarily without this feature.   Prohibit block change tracking function Sql> alter database disable block change  tracking;database altered. Sql> shutdown immediate;oracle instance shut down. Sql> startuporacle instance started. total system global area  167772160 bytesfixed size                   1247876 bytesvariable  Size              79693180  bytesdatabase buffers           79691776  bytesredo buffers                 7139328 bytesdatabase mounted. database opened. sql>3.1.1  about  tracking  file1.   Track data blocks changed between two backups through a bitmap, 2.   Bitmap switching before each backup; 3.   When developing an incremental backup strategy, consider the limitations of 8 bitmaps; 4.   In a RAC environment, Change tracking file needs to be placed on shared storage; 5. The size of the   parameter change tracking file is proportional to the size of the database and the number of Redo thread enabled; 6. The size of the  change tracking file is independent of the frequency of data updates; 7.   Enable change tracking;8 in the Mount or open state. enable change trackingalter database enable block change tracking  using file  '/mydir/rman_change_track.f '  reuse;9. Disable change trackingalter database disable block change tracking;10. Check the change tracking status select status, filename from v$block_change_tracking;11.       Change the location of Change tracking file 1)   How to not shut down the database sql> alter  database disable block change tracking; Sql> alter database enable block change tracking using file  ' new_location '; Note: This method will lose Change tracking file content 2)   How to close the database SQL > SELECT FILENAME FROM V$BLOCK_CHANGE_TRACKING; (determines the current file name) sql> shutdown  Immediate move the file to the new path Sql> alter database rename file '/disk1/changetracking/o1_mf_ with the operating system command 2f71np5j_.chg '  to '/disk2/changetracking/o1_mf_2f71np5j_.chg '; sql> alter database open;  Test encountered problems                                                                                                                                                                         ora-06544: pl/sql:  internal error, arguments: [56319], ORA-06553: PLS-801: internal  ERROR [56319] " errors while running catupgrd.sql encounter oracle bug solution during migration unpublished  bug 5079213 - ora-06544 [56319] during upgrade from 10.1.0.5  32BIT TO 10.2.0.2 64BIT  workaround 1. Change catupgrd.sql script to always execute utlip.sql into oracle_home directory% CD   $ORACLE _home/rdbms/admin     back up the original Catupgrd.sql script% CP&NBsp;catupgrd.sql catupgrd_orig.sql     Edit Catupgrd.sql Script% vi catupgrd.sql   (Vi is for unix-based systems, for windows - edit as a  text document) Find the ==> @@&utlip_file and modify it to the following ==> @@ Utlip.sql2. Run the modified Catupgrd.sql script sql> spool /tmp/upgrade_aft_wa.outsql> set echo  Onsql> @?/rdbms/admin/catupgrd.sql

This article is from the "O Record" blog, so be sure to keep this source http://evils798.blog.51cto.com/8983296/1420910