Shulou(Shulou.com)05/31 Report--

This article mainly introduces "what is the process of oracle migrating from linux to windows through rman". In daily operation, I believe many people have doubts about the process of migrating oracle from linux to windows through rman. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubt that "what is the process of oracle migrating from linux to windows through rman?" Next, please follow the editor to study!

1. Back up the entire library

Omit this step by backing up the entire library through rman and copying the backup set to the windows environment in the linux environment.

There are two backup sets:

O1_mf_s_1042364904_hfoxqb24_.bkp-parameter files and control files

441724361_0cv22ehf_1_1-dataset

2.windows environment configuration

(1) configure the windows environment first. Here, you need to install the database software and configure monitoring, and there is no need to build a library.

(2) add the database instance manually. This experiment instance is named dbmon:

C:\ Users\ zace > oradim-NEW-SID dbmon-startmode auto

(3) manually configure a pfile, path: C:\ app\ zace\ product\ 11.2.0\ dbhome_2\ database\ initdbmon.ora, as follows:

Db_name=dbmon

Db_unique_name=dbmon

(4) start the database to nomount status

(5) restore spfile:

RMAN > restore spfile from'C:\ O1mflips 1042364904 / hfoxqb24.bkp'

(6) rebuild pfile according to spfile:

SQL > create pfile from spfile

Edit the pfile, and modify the path to the path in the windows environment, which is roughly as follows:

* .audit_file_dest='C:\ app\ zace\ admin\ dbmon\ adump'

* .compatible='11.2.0.4.0'

* .control_files='C:\ app\ zace\ oradata\ dbmon\ control01.ora','C:\ app\ zace\ flash_recovery_area\ dbmon\ control02.ora'

* .db_block_size=8192

* .db_domain=''

* .db_name='dbmon'

* .db_recovery_file_dest='C:\ app\ zace\ flash_recovery_area'

* .db_recovery_file_dest_size=10737418240

* .diagnostic_dest='C:\ app\ zace'

* .dispatchers=' (PROTOCOL=TCP) (SERVICE=dbmonXDB)'

* .open_cursors=300

* .processes=150

* .remote_login_passwordfile='EXCLUSIVE'

* .sec_case_sensitive_logon=FALSE

* .undo_tablespace='UNDOTBS1'

(7) rebuild spfile according to pfile:

SQL > shutdown immediate

SQL > create spfile from pfile

(8) restore controlfile:

Start the database to the nomount state:

SQL > startup nomount

RMAN target /

RMAN > restore controlfile from'C:\ O1mflips 1042364904 / hfoxqb24.bkp'

(9) start the database to mount state, and then execute:

Run {

Set newname for datafile'/ data/u01/app/oracle/oradata/dbmon/tps_audit01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ tps_audit01.dbf'

Set newname for datafile'/ data/u01/app/oracle/oradata/dbmon/newmon01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ newmon01.dbf'

Set newname for datafile'/ data/u01/app/oracle/oradata/dbmon/dbmon01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ dbmon01.dbf'

Set newname for datafile'/ data/u01/app/oracle/oradata/dbmon/undotbs01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ undotbs01.dbf'

Set newname for datafile'/ data/u01/app/oracle/oradata/dbmon/tools01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ tools01.dbf'

Set newname for datafile'/ data/u01/app/oracle/oradata/dbmon/users01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ users01.dbf'

Set newname for tempfile'/ data/u01/app/oracle/oradata/dbmon/temp01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ temp01.dbf'

Set newname for tempfile'/ data/u01/app/oracle/oradata/dbmon/dbmon_temp01.dbf' to'C:\ app\ zace\ oradata\ dbmon\ dbmon_temp01.dbf'

Set newname for tempfile'/ data/u01/app/oracle/oradata/dbmon/dbmon_temp02.dbf' to'C:\ app\ zace\ oradata\ dbmon\ dbmon_temp02.dbf'

Restore database

}

It should be noted that there is an error in this place, and the information is as follows:

Channel ORA_DISK_1: reading backup fragment C:\ 441724361_0CV22EHF_1_1

Channel ORA_DISK_1: ORA-19870: error restoring backup fragment C:\ 441724361_0CV22EHF_1_1

ORA-19504: unable to create the file "C:\ DATA\ U01\ APP\ ORACLE\ ORADATA\ DBMON\ SYSAUX01.DBF"

ORA-27040: file creation error, unable to create file

OSD-04002: unable to open file

O/S-Error: (OS 3) the system cannot find the specified path.

Fail over to previous backup

RMAN-00571: =

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-03002: the restore command (on 06Accord 06Universe 13:29:56) failed

RMAN-06026: some targets have not been found-abort restore

RMAN-06023: no copy restore of data file 4 was found

RMAN-06023: no copy restore of data file 2 was found

RMAN-06023: no copy restore of data file 1 was found

It is a bit strange to see the error message. Obviously, the path I specified is'C:\ app\ zace\ oradata\ dbmon\', but here it has become'C:\ DATA\ U01\ APP\ ORACLE\ ORADATA\ DBMON\'. After carefully searching the official website and netizens' blogs, I found a problem. It can only be successful in the following ways:

Run {

Set newname for datafile 1 to'C:\ app\ zace\ oradata\ dbmon\ system01.dbf'

Set newname for datafile 2 to'C:\ app\ zace\ oradata\ dbmon\ sysaux01.dbf'

Set newname for datafile 3 to'C:\ app\ zace\ oradata\ dbmon\ undotbs01.dbf'

Set newname for datafile 4 to'C:\ app\ zace\ oradata\ dbmon\ users01.dbf'

Set newname for datafile 5 to'C:\ app\ zace\ oradata\ dbmon\ dbmon01.dbf'

Set newname for datafile 6 to'C:\ app\ zace\ oradata\ dbmon\ tools01.dbf'

Set newname for datafile 7 to'C:\ app\ zace\ oradata\ dbmon\ newmon01.dbf'

Set newname for datafile 8 to'C:\ app\ zace\ oradata\ dbmon\ tps_audit01.dbf'

Set newname for tempfile 1 to'C:\ app\ zace\ oradata\ dbmon\ temp01.dbf'

Set newname for tempfile 2 to'C:\ app\ zace\ oradata\ dbmon\ dbmon_temp01.dbf'

Set newname for tempfile 3 to'C:\ app\ zace\ oradata\ dbmon\ dbmon_temp02.dbf'

Restore database

}

The implementation results are as follows:

Channel ORA_DISK_1: reading backup fragment C:\ 441724361_0CV22EHF_1_1

Channel ORA_DISK_1: segment handle = C:\ 441724361_0CV22EHF_1_1 tag = TAG20200606T094935

Channel ORA_DISK_1: backup fragment 1 restored

Channel ORA_DISK_1: restore completed. Time: 00:00:45

Completion of restore in 06-June-20

Since then, the restore process for the media has been completed.

(10) perform switch operation (modify the record information of the control file)

RMAN > switch database to copy

Replace the recovery directory with the target database control file

Data file 1 has been switched to a copy of the data file "C:\ APP\ ZACE\ ORADATA\ DBMON\ SYSTEM01.DBF"

Data file 2 has been switched to a copy of the data file "C:\ APP\ ZACE\ ORADATA\ DBMON\ SYSAUX01.DBF"

Data file 3 has been switched to a data file copy "C:\ APP\ ZACE\ ORADATA\ DBMON\ UNDOTBS01.DBF"

Data file 4 has been switched to a copy of the data file "C:\ APP\ ZACE\ ORADATA\ DBMON\ USERS01.DBF"

Data file 5 has been switched to a data file copy "C:\ APP\ ZACE\ ORADATA\ DBMON\ DBMON01.DBF"

Data file 6 has been switched to a copy of the data file "C:\ APP\ ZACE\ ORADATA\ DBMON\ TOOLS01.DBF"

Data file 7 has been switched to a data file copy "C:\ APP\ ZACE\ ORADATA\ DBMON\ NEWMON01.DBF"

Data file 8 has been switched to a data file copy "C:\ APP\ ZACE\ ORADATA\ DBMON\ TPS_AUDIT01.DBF"

(11) modify the redo file:

After an attempt, the redo log is finally resolved by rebuilding the control file:

CREATE CONTROLFILE reuse

SET DATABASE dbmon

LOGFILE GROUP 1 ('C:\ app\ zace\ oradata\ dbmon\ redo01.log') size 200m

GROUP 2 ('C:\ app\ zace\ oradata\ dbmon\ redo02.log') size 200m

GROUP 3 ('C:\ app\ zace\ oradata\ dbmon\ redo03.log') size 200m

RESETLOGS

DATAFILE'C:\ app\ zace\ oradata\ dbmon\ system01.dbf'

'C:\ app\ zace\ oradata\ dbmon\ sysaux01.dbf'

'C:\ app\ zace\ oradata\ dbmon\ undotbs01.dbf'

'C:\ app\ zace\ oradata\ dbmon\ users01.dbf'

'C:\ app\ zace\ oradata\ dbmon\ dbmon01.dbf'

'C:\ app\ zace\ oradata\ dbmon\ tools01.dbf'

'C:\ app\ zace\ oradata\ dbmon\ newmon01.dbf'

'C:\ app\ zace\ oradata\ dbmon\ tps_audit01.dbf'

MAXLOGFILES 50

MAXLOGMEMBERS 3

MAXLOGHISTORY 400

MAXDATAFILES 200

MAXINSTANCES 6

NOARCHIVELOG

After the creation is complete, the open database:

SQL > alter database open resetlogs

(12) rebuild the temp file:

Create temporary tablespace TEMP2

TEMPFILE'C:\ app\ zace\ oradata\ dbmon\ temp02.dbf'

SIZE 500M

AUTOEXTEND ON

NEXT 1M MAXSIZE 32000M

EXTENT MANAGEMENT LOCAL

Modify the default temp tablespace:

Alter database default temporary tablespace temp2

Alter user DBMON temporary tablespace temp2

Since then, the database recovery is complete.

At this point, the study on "what is the process of oracle migrating from linux to windows through rman" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.