AIX under RAC build oracle10g (vi) DBCA build Library

Source: Internet
Author: User

AIX under RAC Construction series


AIX under RAC build oracle10g (vi) DBCA build Library

Environment

Node

Node 1

Node 2

Small machine Model

IBM p-series 630

IBM p-series 630

Host Name

AIX203

AIX204

Switch

SAN Fibre switch

Store

SAN T3 Storage

The outline flow is as follows:

First part: Host configuration

First, the detection system environment

Second, network configuration

Iii. Users and Groups

Four, network parameter adjustment

Five, time synchronization

Six, Volume group


Part II: Installing HACMP and configuring

Vii. hacmp Installation and configuration


Part III: Installation of CRS

VIII. Installation of CRS


Part IV: Installing Oracle Software

Nine, install Oracle


Part V: With monitoring, creating Oracle Database

X. Setting up Monitoring

Xi. DBCA Construction of the library

12. Verification


Continuation of the previous article *********************************************

Address of the previous article

************************************************************************************************
The following start text:

Xi. Building a library 1, creating a bare device symbolic link file

Create a symbolic link file for a bare device (create a directory on all nodes)

[[Email protected] ~] su-oracle

[18:03:41 [email protected] ~]$mkdir-p/u01/app/oracle/oradata/prod/

[18:01:34 [email protected] ~]$mkdir-p/u01/app/oracle/oradata/prod/

Build links (two nodes are built)

Node 1 establishing Links

[18:08:17 [email protected] ~]$cat mkln.sh

Add to:

Ln-s/dev/rsystem/u01/app/oracle/oradata/prod/system01.dbf

Ln-s/dev/rsysaux/u01/app/oracle/oradata/prod/sysaux01.dbf

Ln-s/dev/rusers/u01/app/oracle/oradata/prod/users01.dbf

Ln-s/dev/rundotbs1/u01/app/oracle/oradata/prod/undotbs01.dbf

Ln-s/dev/rundotbs2/u01/app/oracle/oradata/prod/undotbs02.dbf

Ln-s/dev/rtemp/u01/app/oracle/oradata/prod/temp01.dbf

Ln-s/dev/rcontrol1_1/u01/app/oracle/oradata/prod/control01.ctl

Ln-s/dev/rcontrol2_2/u01/app/oracle/oradata/prod/control02.ctl

Ln-s/dev/rcontrol3_3/u01/app/oracle/oradata/prod/control03.ctl

Ln-s/dev/rredo1_1/u01/app/oracle/oradata/prod/log11.log

Ln-s/dev/rredo1_2/u01/app/oracle/oradata/prod/log12.log

Ln-s/dev/rredo2_1/u01/app/oracle/oradata/prod/log21.log

Ln-s/dev/rredo2_2/u01/app/oracle/oradata/prod/log22.log

Ln-s/dev/rindex/u01/app/oracle/oradata/prod/index01.dbf

Ln-s/dev/rspfile/u01/app/oracle/oradata/prod/spfileprod.ora

Ln-s/dev/rexample/u01/app/oracle/oradata/prod/example01.dbf

[18:08:24 [email protected] ~]$sh mkln.sh //Execute script

[18:09:26 [email protected] ~]$ls-l/u01/app/oracle/oradata/prod/


Establish links on Node 2

[18:09:43 [email protected] ~]$rcp mkln.sh aix204:~/

[18:11:00 [email protected] ~]$cat mkln.sh

Ln-s/dev/rsystem/u01/app/oracle/oradata/prod/system01.dbf

Ln-s/dev/rsysaux/u01/app/oracle/oradata/prod/sysaux01.dbf

Ln-s/dev/rusers/u01/app/oracle/oradata/prod/users01.dbf

Ln-s/dev/rundotbs1/u01/app/oracle/oradata/prod/undotbs01.dbf

Ln-s/dev/rundotbs2/u01/app/oracle/oradata/prod/undotbs02.dbf

Ln-s/dev/rtemp/u01/app/oracle/oradata/prod/temp01.dbf

Ln-s/dev/rcontrol1_1/u01/app/oracle/oradata/prod/control01.ctl

Ln-s/dev/rcontrol2_2/u01/app/oracle/oradata/prod/control02.ctl

Ln-s/dev/rcontrol3_3/u01/app/oracle/oradata/prod/control03.ctl

Ln-s/dev/rredo1_1/u01/app/oracle/oradata/prod/log11.log

Ln-s/dev/rredo1_2/u01/app/oracle/oradata/prod/log12.log

Ln-s/dev/rredo2_1/u01/app/oracle/oradata/prod/log21.log

Ln-s/dev/rredo2_2/u01/app/oracle/oradata/prod/log22.log

Ln-s/dev/rindex/u01/app/oracle/oradata/prod/index01.dbf

Ln-s/dev/rspfile/u01/app/oracle/oradata/prod/spfileprod.ora

Ln-s/dev/rexample/u01/app/oracle/oradata/prod/example01.dbf

[18:11:23 [email protected] ~]$sh mkln.sh //Execute script

[18:11:37 [email protected] ~]$ls-l/u01/app/oracle/oradata/prod/


"Supplemental": Force rebuild DBF File

$ln-sf/dev/rexample/u01/app/oracle/oradata/prod/example01.dbf

Plus F means forced reconstruction.

2. Build a mapping file for bare devices

The mapping file is established on Node 1, which is then used to correlate execution of the file when the DBCA is built

[[Email protected] ~] su-oracle

[18:14:08 [email protected] ~]$cat Raw_map.txt

System=/dev/rsystem

Sysaux=/dev/rsysaux

Users=/dev/rusers

Undotbs1=/dev/rundotbs1

Undotbs2=/dev/rundotbs2

Temp=/dev/rtemp

Control1=/dev/rcontrol1_1

Control2=/dev/rcontrol2_2

Control3=/dev/rcontrol3_3

Redo1_1=/dev/rredo1_1

Redo1_2=/dev/rredo1_2

Redo2_1=/dev/rredo2_1

Redo2_2=/dev/rredo2_2

Index=/dev/rindex

Spfile=/dev/rspfile

Example=/dev/rexample

3, graphical DBCA building Library

Execute DBCA command under X-manager:

$Export display=192.168.8.73:0 //Control host IP Address

$source/etc/profile

$DBCA


During the DBCA build process, be careful to select the raw device and then choose to use the raw map file, which selects the mapping file that was previously established on Node 1.















The following locations are automatically read by the mapping file (control file location, data file location, log file location) without modification, as follows:





Preview " Database information " as follows:









Error, then you can manually start node 1.


12. Verification

[08:34:29 [email protected]/]#crs_stat-t //Node 1 view process status


[08:34:53 [email protected]/]#crs_stat-t //Node 2 view process status


[08:35:49 [email protected]/]#crsctl Check CRS //Node 1 detection service status


[08:34:57 [email protected]/]#crsctl Check CRS //Node 2 detection service status


[08:34:36 [email protected]/]#su-oracle

[t [email protected] w]$bash

[08:35:12 [email protected] ~]$source/etc/profile

[08:35:20 [email protected] ~]$sqlplus '/as sysdba ' //node 1 login sqlplus


[08:36:20 [email protected]/]#su-oracle

[You have NEW MAIL]

[08:36:27 [email protected] ~]$sqlplus '/as sysdba ' //Node 2 login Sqlplus


Sql> SELECT * from Scott.dept; Node 1 Viewing table information


Sql> SELECT * from Scott.dept; Node 2 Viewing table information


Sql>selectstatus,instance_name from Gv$instance; View cluster instance status on Node 1


Sql> Select Status,instance_name from Gv$instance; View cluster instance status on Node 2



*********************************************** declaration ***************************************** *******

Original works, from the "Blue Blog" blog, Welcome to reprint, please be sure to indicate the source (Http://blog.csdn.net/huangyanlong).

There is an error in the statement, please leave a message, greatly appreciated.

Reminder: Click on the table of contents, more helpful to your view.

*************************************************************************************************** **





























Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.