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

The main content of this article is "WindowsServer 2012 database migration analysis", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next, let the editor take you to learn "WindowsServer 2012 Database Migration Analysis"!

Scenario Windows Server migrates to WIndows Server data volume of 3T, archiving about 30G per hour. Network 100Mbps storage, source database IP-SAN storage, target side SSD. Migration method: RMAN migration

1. Full backup because there is a bigfile tablespace 2.8T, the backup time is very slow. You can use the following command to speed up the backup of bigfile tablespace: / * pay attention to the channel, resources are sufficient to open sufficient parallelism, the following is an example, RMAN > backup as compressed backupset section size 100m tablespace users format'/ rman/user_%d_%T_%s_%p.bak' / * if you can, try not to use bigfile tablespaces, which will be very difficult during backup and recovery. two。 Transfer basic backup to destination network map disk to destination side, however, network speed and disk write speed are tortoise speed, 500G compressed backup set, transferred for 10 hours. 3. The best version of the database software installed on the target side is the same as that on the source side, and if an upgrade is involved, then upgrade. 3. Create instance service oradim-NEW-SID-STARTMODE manual-PFILE "D:\ ORADATA\ PFILE.ORA" use sqlplus to start the instance to nomount, restore the control files, then mount, and restore the data files in different directories using SET NEWNAME FOR and switch datafile all. 4. Back up the incremental archive, transfer, and restore backup as compressed backupset archivelog from sequence format'/ rman/arch_%d_%T_%s_%p';5 again on the source side. The last backup on the source side is incremental and the current redo log transfer is restored. The final redo log uses sqlplus recovery SQL > recover database using backup controlfile until cancel;d:\ oradata\ redo08.log6.redo log rename to renameALTER DATABASE RENAME FILE''TO''all redo log; 7. Open the database and process the temporary tablespace SQL > alter database open resetlogs;SQL > CREATE TEMPORARY TABLESPACE TEST_TEMP TEMPFILE'E:\ ORADATA\ TEMP01.DBF' SIZE 30G AUTOEXTEND OFF;SQL > ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEST_TEMP;SQL > SELECT * FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME='DEFAULT_TEMP_TABLESPACE';/* delete the original temp tablespace SQL > DROP TABLESPACE TEMP INCLUDING CONTENTS AND DATAFILES;8. Set up eavesdropping to ensure that the database is registered with the snooping netcalsnrctl status9. If there is a windows firewall, pay attention to setting outbound rules, inbound rules, release the listening port. 10. Check the alert log to see if there are any errors in the previously established index using nologging, resulting in index block corruption, the need to rebuild the index. ALTER INDEX REBUILD ONLINE PARALLEL 8 NOLOGGING LOCAL;ALTER INDEX noparallel; so far, I believe you have a deeper understanding of "WindowsServer 2012 Database Migration Analysis". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.