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

This article introduces the relevant knowledge of "how to migrate Oracle from Linux x86 stand-alone to Solaries dual-node RAC cluster". In the operation of actual cases, many people will encounter this dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Online redo log adjustment

(note: one for each group, increase the number of groups to 8 and resize to 1G)

SQL > set linesize 300 countries SQL > col member for A50 countries SQL > select * from v$logfile GROUP# STATUS TYPE MEMBER IS_--2 ONLINE + DATADG/cams/onlinelog/group_2.292.989624633 NO 1 ONLINE + DATADG/cams/onlinelog/group_1.256.989624629 NO 3 ONLINE + DATADG/cams/onlinelog/group_3.296.989624869 NO 4 ONLINE + DATADG/cams/onlinelog/group_4.295.989624875 NO 5 ONLINE + DATADG/cams/onlinelog/group_5 NO 6 ONLINE + DATADG/cams/onlinelog/group_6 NO 7 ONLINE + DATADG/cams/onlinelog/group_7 NO8 ONLINE + DATADG/cams/onlinelog/group_8 NO8 rows selected.SQL > select GROUP# BYTES,MEMBERS,STATUS from v$log GROUP# BYTES MEMBERS STATUS- 1 1073741824 1 INACTIVE 2 1073741824 1 INACTIVE 3 1073741824 1 CURRENT 4 1073741824 1 INACTIVE 5 1073741824 1 CURRENT 6 1073741824 1 INACTIVE 7 1073741824 1 INACTIVE8 1073741824 1 INACTIVE8 rows selected.2. Control file adjustment

(note: adjust the control files to 3, which exist in different paths)

SQL > set linesize 300 countries SQL > col name for A55 countries SQL > select * from v$controlfile STATUS NAME IS_ BLOCK_SIZE FILE_SIZE_BLKS-- + DATADG/cams/controlfile/controlfile1/controlfile1 NO 16384 1128 + DATADG/cams/controlfile/controlfile2/controlfile2 NO 16384 1128 + DATADG/cams/controlfile/current.303.989624627 NO 16384 11283. Memory parameter adjustment

(note: each node has 64 gigabytes of memory, enable AMM)

SQL > show parameter memory NAME TYPE VALUE-- hi_shared_memory_address integer 0memory_max _ target big integer 32256Mmemory_target big integer 32256Mshared_memory_address integer 0SQL > show parameter sga NAME TYPE VALUE-- lock_sga Boolean FALSEpre_page_sga boolean FALSEsga_max_size big integer 32256Msga_target big integer 0SQL > show parameter pga NAME TYPE VALUE---pga_aggregate_target big integer 04. Adjust other parameters

adjustment

Job_queue_processes

Log_buffer

Db_block_checking

Processes

Session_cached_cursors

Open_cursors

Undo_retention

And other parameters, in line with the production specifications.

5. Open database archiving SQL > archive log list;Database log mode Archive ModeAutomatic archival EnabledArchive destination + DATADGOldest online log sequence 8Next log sequence to archive 11Current log sequence 116. Define RMAN backup policy

(1) set up database automatic backup control files

(2) make RMAN level 0 full database backup every Sunday

(3) do RMAN level 1 incremental backup every day (except Sunday)

(4) keep only 2-week full database backup and incremental backup on the main server

(5) copy the full database backup and incremental backup from two weeks ago to other environments

7. Deploy backup scripts and crontab

(note: according to customer requirements, RMAN will be backed up to ASM disk here)

First create the RMAN backup directory "+ DATADG/CAMS/RMAN"

Script storage directory: / u01/app/oracle/backup/rman

Log storage directory: / u01/app/oracle/backup/rman/logs

Under the oracle user: crontab-e, perform a backup at 3: 00 a. M. every day

0 3 * 0-6 / u01/app/oracle/backup/rman/start_rman.sh > > / u01/app/oracle/backup/rman/start_rman.log8. Perform full RMAN backup manually

Manually execute the RMAN level 0 backup script to do full RMAN backup of the database.

9. Control file corruption test

(1) close the database

(2) modify the name of one of the control files

(3) start the database (error message)

(4) use RMAN to recover control files

(5) start the database

(6) check the control file information

10.spfile file corruption test

(1) close the database

(2) modify the name of spfile file

(3) start the database (error message)

(4) use RMAN to recover spfile files

(5) restart the database

(6) check the database status

11. Redo log corruption test

(1) close the database

(2) modify the name of redo file

(3) start the database (error message)

(4) full recovery using RMAN

(5) recover database in sqlplus

(6) Open the database

(7) check the database status

twelve。 Data corruption test

(1) full recovery

RMAN > startup mount;RMAN > restore database;RMAN > recover database;RMAN > alter database open

(2) incomplete recovery

Oracle@cwgsdb1:~$ srvctl stop database-d camsoracle@cwgsdb1:~$ srvctl start database-d cams-o mountoracle@cwgsdb1:~$ export NLS_DATE_FORMAT= "yyyy-mm-dd hh34:mi:ss" $rman target / RMAN > restore database until time "to_date ('2018-10-25 01V 07L hh34:mi:ss')"; RMAN > recover database until time "to_date"; RMAN > alter database open resetlogs;RMAN > exit13. Deal with other problems

The Solaries system time is not consistent with the Internet time. Because it is a test environment, it will clean up and re-import production data when switching, so directly modify the system time to solve the problem.

If the production environment finds this problem, it is recommended to turn off the hardware synchronously with the system time, shut down the library for one day, wait for the time to exceed the current time, then turn on the system, time synchronization, and then start the database.

That's all for "how Oracle migrates from Linux x86 standalone to Solaries dual-node RAC cluster". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.