1. 실습
환경
OS : Oracle
Linux Server 7.9 (Linux rdb01d 5.4.17-2102.201.3.el7uek.x86_64)
DB : Oracle
Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
RAC1 :
rdb01d(192.168.0.31) : DRDB1
RAC2 : rdb01d(192.168.0.32) :
DRDB2
클러스터명을 기존 drdb에서 drdb2로 바꿀 것임
기존 grid 엔진을 deconfig하고 재구성 할 것임 (결국 grid 엔진만 재설치 하는 것임)
2. 작업 전 확인
--클러스터명 확인
[DRDB1:oracle@rdb01d][/home/oracle]$ olsnodes
-c
drdb
[DRDB1:oracle@rdb01d][/home/oracle]$
csrt
--------------------------------------------------------------------------------
Name
Target State
Server
State
details
--------------------------------------------------------------------------------
Local
Resources
--------------------------------------------------------------------------------
ora.ASMNET1LSNR_ASM.lsnr
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
ora.CRS.dg
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
ora.DATA1.dg
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
ora.FRA1.dg
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
ora.LISTENER.lsnr
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
ora.MGMT.dg
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
ora.net1.network
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
ora.ons
ONLINE ONLINE
rdb01d
STABLE
ONLINE ONLINE
rdb02d
STABLE
--------------------------------------------------------------------------------
Cluster
Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1 ONLINE
ONLINE
rdb02d
STABLE
ora.LISTENER_SCAN2.lsnr
1 ONLINE
ONLINE
rdb01d
STABLE
ora.LISTENER_SCAN3.lsnr
1 ONLINE
ONLINE
rdb01d
STABLE
ora.MGMTLSNR
1 ONLINE
ONLINE
rdb01d
169.254.110.230
10.0
.0.31,STABLE
ora.asm
1 ONLINE
ONLINE
rdb01d
Started,STABLE
2 ONLINE
ONLINE
rdb02d
Started,STABLE
3 OFFLINE
OFFLINE
STABLE
ora.cvu
1 ONLINE
ONLINE
rdb01d
STABLE
ora.drdb.db
1 ONLINE
ONLINE
rdb01d
Open,HOME=/u01/app/o
racle/product/12c/db
_1,STABLE
2 ONLINE
ONLINE
rdb02d
Open,HOME=/u01/app/o
racle/product/12c/db
_1,STABLE
ora.mgmtdb
1 ONLINE
ONLINE
rdb01d
Open,STABLE
ora.qosmserver
1 ONLINE
ONLINE
rdb01d
STABLE
ora.rdb01d.vip
1 ONLINE
ONLINE
rdb01d
STABLE
ora.rdb02d.vip
1 ONLINE
ONLINE
rdb02d
STABLE
ora.scan1.vip
1 ONLINE
ONLINE
rdb02d
STABLE
ora.scan2.vip
1 ONLINE
ONLINE
rdb01d
STABLE
ora.scan3.vip
1 ONLINE
ONLINE
rdb01d
STABLE
--------------------------------------------------------------------------------
[DRDB1:oracle@rdb01d][/home/oracle]$ srvctl config database -db
drdb
Database unique name: DRDB
Database name: DRDB
Oracle home:
/u01/app/oracle/product/12c/db_1
Oracle user: oracle
Spfile:
+DATA1/DRDB/PARAMETERFILE/spfile.268.1198106043
Password file:
+DATA1/DRDB/PASSWORD/pwddrdb.256.1196204543
Domain:
Start options:
open
Stop options: immediate
Database role: PRIMARY
Management policy:
AUTOMATIC
Server pools:
Disk Groups: FRA1,DATA1
Mount point
paths:
Services:
Type: RAC
Start concurrency:
Stop
concurrency:
OSDBA group: dba
OSOPER group: oper
Database instances:
DRDB1,DRDB2
Configured nodes: rdb01d,rdb02d
CSS critical: no
CPU count:
0
Memory target: 0
Maximum memory: 0
Default network number for
database services:
Database is administrator managed
3. CRS Deconfig 작업
-- RAC1번 노드 deconfig
[root@rdb01d][/root]$ cd
$GRID_HOME/crs/install
[root@rdb01d][/u01/app/12c/grid/crs/install]$
./rootcrs.sh -deconfig -force -verbose
Using configuration parameter file:
/u01/app/12c/grid/crs/install/crsconfig_params
The log of current session can
be found at:
/u01/app/oracle/crsdata/rdb01d/crsconfig/crsdeconfig_rdb01d_2025-05-31_03-41-00PM.log
CRS-2791:
Starting shutdown of Oracle High Availability Services-managed resources on
'rdb01d'
CRS-2673: Attempting to stop 'ora.crsd' on 'rdb01d'
CRS-2790:
Starting shutdown of Cluster Ready Services-managed resources on server
'rdb01d'
CRS-2673: Attempting to stop 'ora.drdb.db' on 'rdb01d'
CRS-2677:
Stop of 'ora.drdb.db' on 'rdb01d' succeeded
CRS-2673: Attempting to stop
'ora.CRS.dg' on 'rdb01d'
CRS-2673: Attempting to stop 'ora.DATA1.dg' on
'rdb01d'
CRS-2673: Attempting to stop 'ora.FRA1.dg' on 'rdb01d'
CRS-2673:
Attempting to stop 'ora.MGMT.dg' on 'rdb01d'
CRS-2677: Stop of 'ora.CRS.dg'
on 'rdb01d' succeeded
CRS-2677: Stop of 'ora.DATA1.dg' on 'rdb01d'
succeeded
CRS-2677: Stop of 'ora.FRA1.dg' on 'rdb01d' succeeded
CRS-2677:
Stop of 'ora.MGMT.dg' on 'rdb01d' succeeded
CRS-2673: Attempting to stop
'ora.asm' on 'rdb01d'
CRS-2677: Stop of 'ora.asm' on 'rdb01d'
succeeded
CRS-2673: Attempting to stop 'ora.ASMNET1LSNR_ASM.lsnr' on
'rdb01d'
CRS-2677: Stop of 'ora.ASMNET1LSNR_ASM.lsnr' on 'rdb01d'
succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on
'rdb01d' has completed
CRS-2677: Stop of 'ora.crsd' on 'rdb01d'
succeeded
CRS-2673: Attempting to stop 'ora.storage' on 'rdb01d'
CRS-2673:
Attempting to stop 'ora.crf' on 'rdb01d'
CRS-2673: Attempting to stop
'ora.gpnpd' on 'rdb01d'
CRS-2673: Attempting to stop 'ora.mdnsd' on
'rdb01d'
CRS-2677: Stop of 'ora.gpnpd' on 'rdb01d' succeeded
CRS-2677:
Stop of 'ora.crf' on 'rdb01d' succeeded
CRS-2677: Stop of 'ora.storage' on
'rdb01d' succeeded
CRS-2673: Attempting to stop 'ora.asm' on
'rdb01d'
CRS-2677: Stop of 'ora.mdnsd' on 'rdb01d' succeeded
CRS-2677:
Stop of 'ora.asm' on 'rdb01d' succeeded
CRS-2673: Attempting to stop
'ora.cluster_interconnect.haip' on 'rdb01d'
CRS-2677: Stop of
'ora.cluster_interconnect.haip' on 'rdb01d' succeeded
CRS-2673: Attempting to
stop 'ora.ctssd' on 'rdb01d'
CRS-2673: Attempting to stop 'ora.evmd' on
'rdb01d'
CRS-2677: Stop of 'ora.ctssd' on 'rdb01d' succeeded
CRS-2677:
Stop of 'ora.evmd' on 'rdb01d' succeeded
CRS-2673: Attempting to stop
'ora.cssd' on 'rdb01d'
CRS-2677: Stop of 'ora.cssd' on 'rdb01d'
succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'rdb01d'
CRS-2677:
Stop of 'ora.gipcd' on 'rdb01d' succeeded
CRS-2793: Shutdown of Oracle High
Availability Services-managed resources on 'rdb01d' has completed
CRS-4133:
Oracle High Availability Services has been stopped.
2025/05/31 15:43:27
CLSRSC-336: Successfully deconfigured Oracle Clusterware stack on this
node
-- RAC2번 노드
deconfig
[root@rdb02d][/root]$ cd
$GRID_HOME/crs/install
[root@rdb02d][/u01/app/12c/grid/crs/install]$
./rootcrs.sh -deconfig -force -verbose -lastnode
--> 해당 작업을 진행하면 lastnode 옵션으로 인해 CRS 공유
디스크의 내용이 모두 날라가게됨
--> CRS 공유 디스크내에 중요한 파일이 있는지 반드시 확인해야함
Using
configuration parameter file:
/u01/app/12c/grid/crs/install/crsconfig_params
The log of current session can
be found at:
/u01/app/oracle/crsdata/rdb02d/crsconfig/crsdeconfig_rdb02d_2025-05-31_03-56-14PM.log
2025/05/31
15:56:17 CLSRSC-332: CRS resources for listeners are still
configured
CRS-2791: Starting shutdown of Oracle High Availability
Services-managed resources on 'rdb02d'
CRS-2673: Attempting to stop
'ora.crsd' on 'rdb02d'
CRS-2790: Starting shutdown of Cluster Ready
Services-managed resources on server 'rdb02d'
CRS-2673: Attempting to stop
'ora.drdb.db' on 'rdb02d'
CRS-2677: Stop of 'ora.drdb.db' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.CRS.dg' on 'rdb02d'
CRS-2673:
Attempting to stop 'ora.MGMT.dg' on 'rdb02d'
CRS-2673: Attempting to stop
'ora.DATA1.dg' on 'rdb02d'
CRS-2673: Attempting to stop 'ora.FRA1.dg' on
'rdb02d'
CRS-2677: Stop of 'ora.MGMT.dg' on 'rdb02d' succeeded
CRS-2677:
Stop of 'ora.DATA1.dg' on 'rdb02d' succeeded
CRS-2677: Stop of 'ora.FRA1.dg'
on 'rdb02d' succeeded
CRS-2677: Stop of 'ora.CRS.dg' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'rdb02d'
CRS-2677:
Stop of 'ora.asm' on 'rdb02d' succeeded
CRS-2673: Attempting to stop
'ora.ASMNET1LSNR_ASM.lsnr' on 'rdb02d'
CRS-2677: Stop of
'ora.ASMNET1LSNR_ASM.lsnr' on 'rdb02d' succeeded
CRS-2792: Shutdown of
Cluster Ready Services-managed resources on 'rdb02d' has completed
CRS-2677:
Stop of 'ora.crsd' on 'rdb02d' succeeded
CRS-2673: Attempting to stop
'ora.storage' on 'rdb02d'
CRS-2673: Attempting to stop 'ora.crf' on
'rdb02d'
CRS-2673: Attempting to stop 'ora.gpnpd' on 'rdb02d'
CRS-2673:
Attempting to stop 'ora.mdnsd' on 'rdb02d'
CRS-2677: Stop of 'ora.crf' on
'rdb02d' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'rdb02d'
succeeded
CRS-2677: Stop of 'ora.storage' on 'rdb02d' succeeded
CRS-2673:
Attempting to stop 'ora.asm' on 'rdb02d'
CRS-2677: Stop of 'ora.mdnsd' on
'rdb02d' succeeded
CRS-2677: Stop of 'ora.asm' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on
'rdb02d'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.ctssd' on 'rdb02d'
CRS-2673:
Attempting to stop 'ora.evmd' on 'rdb02d'
CRS-2677: Stop of 'ora.ctssd' on
'rdb02d' succeeded
CRS-2677: Stop of 'ora.evmd' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'rdb02d'
CRS-2677:
Stop of 'ora.cssd' on 'rdb02d' succeeded
CRS-2673: Attempting to stop
'ora.gipcd' on 'rdb02d'
CRS-2677: Stop of 'ora.gipcd' on 'rdb02d'
succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed
resources on 'rdb02d' has completed
CRS-4133: Oracle High Availability
Services has been stopped.
CRS-4123: Oracle High Availability Services has
been started.
CRS-2672: Attempting to start 'ora.evmd' on
'rdb02d'
CRS-2672: Attempting to start 'ora.mdnsd' on 'rdb02d'
CRS-2676:
Start of 'ora.mdnsd' on 'rdb02d' succeeded
CRS-2676: Start of 'ora.evmd' on
'rdb02d' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on
'rdb02d'
CRS-2676: Start of 'ora.gpnpd' on 'rdb02d' succeeded
CRS-2672:
Attempting to start 'ora.cssdmonitor' on 'rdb02d'
CRS-2672: Attempting to
start 'ora.gipcd' on 'rdb02d'
CRS-2676: Start of 'ora.cssdmonitor' on
'rdb02d' succeeded
CRS-2676: Start of 'ora.gipcd' on 'rdb02d'
succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'rdb02d'
CRS-2672:
Attempting to start 'ora.diskmon' on 'rdb02d'
CRS-2676: Start of
'ora.diskmon' on 'rdb02d' succeeded
CRS-2676: Start of 'ora.cssd' on 'rdb02d'
succeeded
CRS-2672: Attempting to start 'ora.crf' on 'rdb02d'
CRS-2672:
Attempting to start 'ora.ctssd' on 'rdb02d'
CRS-2672: Attempting to start
'ora.cluster_interconnect.haip' on 'rdb02d'
CRS-2676: Start of 'ora.crf' on
'rdb02d' succeeded
CRS-2676: Start of 'ora.ctssd' on 'rdb02d'
succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'rdb02d'
succeeded
CRS-2672: Attempting to start 'ora.asm' on 'rdb02d'
CRS-2676:
Start of 'ora.asm' on 'rdb02d' succeeded
CRS-2672: Attempting to start
'ora.storage' on 'rdb02d'
CRS-2676: Start of 'ora.storage' on 'rdb02d'
succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'rdb02d'
CRS-2676:
Start of 'ora.crsd' on 'rdb02d' succeeded
CRS-2673: Attempting to stop
'ora.crsd' on 'rdb02d'
CRS-2677: Stop of 'ora.crsd' on 'rdb02d'
succeeded
CRS-2791: Starting shutdown of Oracle High Availability
Services-managed resources on 'rdb02d'
CRS-2673: Attempting to stop
'ora.ctssd' on 'rdb02d'
CRS-2673: Attempting to stop 'ora.evmd' on
'rdb02d'
CRS-2673: Attempting to stop 'ora.storage' on 'rdb02d'
CRS-2673:
Attempting to stop 'ora.mdnsd' on 'rdb02d'
CRS-2673: Attempting to stop
'ora.gpnpd' on 'rdb02d'
CRS-2677: Stop of 'ora.evmd' on 'rdb02d'
succeeded
CRS-2677: Stop of 'ora.ctssd' on 'rdb02d' succeeded
CRS-2677:
Stop of 'ora.storage' on 'rdb02d' succeeded
CRS-2673: Attempting to stop
'ora.asm' on 'rdb02d'
CRS-2677: Stop of 'ora.mdnsd' on 'rdb02d'
succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'rdb02d' succeeded
CRS-2677:
Stop of 'ora.asm' on 'rdb02d' succeeded
CRS-2673: Attempting to stop
'ora.cluster_interconnect.haip' on 'rdb02d'
CRS-2677: Stop of
'ora.cluster_interconnect.haip' on 'rdb02d' succeeded
CRS-2673: Attempting to
stop 'ora.cssd' on 'rdb02d'
CRS-2677: Stop of 'ora.cssd' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.crf' on 'rdb02d'
CRS-2677:
Stop of 'ora.crf' on 'rdb02d' succeeded
CRS-2673: Attempting to stop
'ora.gipcd' on 'rdb02d'
CRS-2677: Stop of 'ora.gipcd' on 'rdb02d'
succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed
resources on 'rdb02d' has completed
CRS-4133: Oracle High Availability
Services has been stopped.
CRS-4123: Oracle High Availability Services has
been started.
CRS-2672: Attempting to start 'ora.evmd' on
'rdb02d'
CRS-2672: Attempting to start 'ora.mdnsd' on 'rdb02d'
CRS-2676:
Start of 'ora.mdnsd' on 'rdb02d' succeeded
CRS-2676: Start of 'ora.evmd' on
'rdb02d' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on
'rdb02d'
CRS-2676: Start of 'ora.gpnpd' on 'rdb02d' succeeded
CRS-2672:
Attempting to start 'ora.cssdmonitor' on 'rdb02d'
CRS-2672: Attempting to
start 'ora.gipcd' on 'rdb02d'
CRS-2676: Start of 'ora.cssdmonitor' on
'rdb02d' succeeded
CRS-2676: Start of 'ora.gipcd' on 'rdb02d'
succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'rdb02d'
CRS-2672:
Attempting to start 'ora.diskmon' on 'rdb02d'
CRS-2676: Start of
'ora.diskmon' on 'rdb02d' succeeded
CRS-2676: Start of 'ora.cssd' on 'rdb02d'
succeeded
ASM de-configuration trace file location:
/u01/app/oracle/cfgtoollogs/asmca/asmcadc_clean2025-05-31_04-00-11-PM.log
ASM
Clean Configuration START
ASM Clean Configuration END
ASM instance deleted successfully. Check /u01/app/oracle/cfgtoollogs/asmca/asmcadc_clean2025-05-31_04-00-11-PM.log for details.
CRS-2791:
Starting shutdown of Oracle High Availability Services-managed resources on
'rdb02d'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'rdb02d'
CRS-2673:
Attempting to stop 'ora.evmd' on 'rdb02d'
CRS-2673: Attempting to stop
'ora.gpnpd' on 'rdb02d'
CRS-2677: Stop of 'ora.evmd' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'rdb02d'
CRS-2677:
Stop of 'ora.mdnsd' on 'rdb02d' succeeded
CRS-2677: Stop of 'ora.gpnpd' on
'rdb02d' succeeded
CRS-2677: Stop of 'ora.cssd' on 'rdb02d'
succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'rdb02d'
CRS-2677:
Stop of 'ora.gipcd' on 'rdb02d' succeeded
CRS-2793: Shutdown of Oracle High
Availability Services-managed resources on 'rdb02d' has completed
CRS-4133:
Oracle High Availability Services has been stopped.
2025/05/31 16:01:43
CLSRSC-336: Successfully deconfigured Oracle Clusterware stack on this
node
2025/05/31 16:01:43 CLSRSC-559: Ensure that the GPnP profile data under
the 'gpnp' directory in /u01/app/12c/grid is deleted on each node before using
the software in the current Grid Infrastructure home for
reconfiguration.
--RAC1번 노드 grid 엔진 mv
[root@rdb01d][/u01/app/12c]$ mv /u01/app/12c/grid
/u01/app/12c/grid.bak
--RAC2번 노드 grid 엔진 mv
[root@rdb02d][/u01/app/12c]$ mv /u01/app/12c/grid /u01/app/12c/grid.bak
--RAC1번 노드 grid 엔진 디렉토리 권한 변경 (root os user)
[root@rdb01d][/]$ chown grid:oinstall u01
[root@rdb01d][/]$ chown
grid:oinstall /u01/app
[root@rdb01d][/]$ chown grid:oinstall
/u01/app/12c
--RAC2번 노드 grid 엔진 디렉토리 권한 변경 (root os user)
[root@rdb02d][/]$ chown grid:oinstall u01
[root@rdb02d][/]$ chown
grid:oinstall /u01/app
[root@rdb02d][/]$ chown grid:oinstall
/u01/app/12c
[root@rdb01d][/u01/app/oraInventory/ContentsXML]$
vi /etc/oratab
[root@rdb01d][/u01/app/oraInventory/ContentsXML]$ cat
/etc/oratab
#
# This file
is used by ORACLE utilities. It is created by root.sh
# and updated by
either Database Configuration Assistant while creating
# a database or ASM
Configuration Assistant while creating ASM instance.
# A colon,
':', is used as the field terminator. A new line terminates
# the
entry. Lines beginning with a pound sign, '#', are comments.
#
#
Entries are of the form:
#
$ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are
the system identifier and home
# directory of the database
respectively. The third field indicates
# to the dbstart utility that
the database should , "Y", or should not,
# "N", be brought up at system boot
time.
#
# Multiple entries with the same $ORACLE_SID are not
allowed.
#
#
#-MGMTDB:/u01/app/12c/grid:N
--> 바로 윗줄 주석 처리
[root@rdb02d][/]$ vi
/etc/oratab
[root@rdb02d][/]$ cat /etc/oratab
#
# This file
is used by ORACLE utilities. It is created by root.sh
# and updated by
either Database Configuration Assistant while creating
# a database or ASM
Configuration Assistant while creating ASM instance.
# A colon,
':', is used as the field terminator. A new line terminates
# the
entry. Lines beginning with a pound sign, '#', are comments.
#
#
Entries are of the form:
#
$ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are
the system identifier and home
# directory of the database
respectively. The third field indicates
# to the dbstart utility that
the database should , "Y", or should not,
# "N", be brought up at system boot
time.
#
# Multiple entries with the same $ORACLE_SID are not
allowed.
#
#
4. grid 엔진 새로 설치
--12cR2 grid 엔진 Base Release 압축 해제 (RAC1번 노드만)
[+ASM1:grid@rdb01d][/home/grid]$ unzip linuxx64_12201_grid_home.zip -d $GRID_HOME
--cvuqdisk 패키지 설치 (RAC1번
노드)
[root@rdb01d][/u01/app/oraInventory/ContentsXML]$ cd
/u01/app/12c/grid/cv/rpm
[root@rdb01d][/u01/app/12c/grid/cv/rpm]$ rpm -ivh
cvuqdisk-1.0.10-1.rpm
Preparing...
################################# [100%]
Updating /
installing...
1:cvuqdisk-1.0.10-1
################################# [100%]
--cvuqdisk 패키지 rpm파일을 RAC2번 노드로
전송
[root@rdb01d][/u01/app/12c/grid/cv/rpm]$ scp cvuqdisk-1.0.10-1.rpm
rdb02d:/tmp
root@rdb02d''s
password:
cvuqdisk-1.0.10-1.rpm
100% 8860 1.2MB/s 00:00
--cvuqdisk 패키지 설치 (RAC2번 노드)
[root@rdb02d][/root]$ cd /tmp
[root@rdb02d][/tmp]$ rpm -ivh
cvuqdisk-1.0.10-1.rpm
Preparing...
################################# [100%]
Updating /
installing...
1:cvuqdisk-1.0.10-1
################################# [100%]
--/tmp/patch 위치에 패치 파일 업로드
시킴
[root@rdb01d][/tmp/patch]$ chmod 777 -R
/tmp/patch
[root@rdb01d][/tmp/patch]$ ls -l
total 2467460
-rwxrwxrwx. 1 root
root 2393137641 May 31 16:23 p33583921_122010_Linux-x86-64.zip
-rwxrwxrwx. 1
root root 133535622 May 31 16:23
p6880880_122010_Linux-x86-64.zip
[root@rdb01d][/tmp/patch]$ unzip
p33583921_122010_Linux-x86-64.zip
[root@rdb01d][/tmp/patch]$ chmod 777 -R
/tmp/patch
[+ASM1:grid@rdb01d][/]$ cd
$GRID_HOME
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ mv OPatch
OPatch.bak.20241020
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ unzip
/tmp/patch/p6880880_122010_Linux-x86-64.zip
Archive:
/tmp/patch/p6880880_122010_Linux-x86-64.zip
...생략
inflating:
OPatch/modules/features/oracle.glcm.opatch.common.api.classpath.jar
inflating: OPatch/modules/features/orapki.lib.jar
inflating:
OPatch/modules/features/com.oracle.orapki.jar
inflating:
OPatch/modules/features/com.oracle.glcm.patch.opatch-common-api-classpath.jar
inflating: OPatch/modules/com.sun.org.apache.xml.internal.resolver.jar
inflating:
OPatch/modules/com.oracle.glcm.patch.opatchauto-wallet_12.2.1.42.0.jar
inflating: OPatch/modules/com.sun.xml.bind.jaxb-jxc.jar
inflating:
OPatch/modules/javax.activation.javax.activation.jar
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ opatch version -oh
$GRID_HOME
OPatch Version: 12.2.0.1.42
OPatch succeeded.
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ cd
$GRID_HOME/oui/prov/resources/scripts
[+ASM1:grid@rdb01d][/u01/app/12c/grid/oui/prov/resources/scripts]$
./sshUserSetup.sh -user oracle -hosts "rdb01d rdb02d" -noPromptPassphrase
-advanced
The output of this script is also logged into
/tmp/sshUserSetup_2025-05-31-16-29-48.log
Hosts are rdb01d rdb02d
user is
oracle
Platform:- Linux
Checking if the remote hosts are reachable
PING
rdb01d (192.168.0.31) 56(84) bytes of data.
64 bytes from rdb01d
(192.168.0.31): icmp_seq=1 ttl=64 time=0.011 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=2 ttl=64 time=0.040 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=3 ttl=64 time=0.082 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=4 ttl=64 time=0.052 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=5 ttl=64 time=0.021 ms
--- rdb01d
ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time
4088ms
rtt min/avg/max/mdev = 0.011/0.041/0.082/0.025 ms
PING rdb02d
(192.168.0.32) 56(84) bytes of data.
64 bytes from rdb02d (192.168.0.32):
icmp_seq=1 ttl=64 time=3.89 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=2 ttl=64 time=0.413 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=3 ttl=64 time=0.816 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=4 ttl=64 time=1.10 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=5 ttl=64 time=1.09 ms
--- rdb02d
ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time
4057ms
rtt min/avg/max/mdev = 0.413/1.464/3.895/1.241 ms
Remote host
reachability check succeeded.
The following hosts are reachable: rdb01d
rdb02d.
The following hosts are not reachable: .
All hosts are reachable.
Proceeding further...
firsthost rdb01d
numhosts 2
The script will setup
SSH connectivity from the host rdb01d to all
the remote hosts. After the
script is executed, the user can use SSH to run
commands on the remote hosts
or copy files between this host rdb01d
and the remote hosts without being
prompted for passwords or confirmations.
NOTE
1:
As part of the setup procedure, this script will use ssh and scp to
copy
files between the local host and the remote hosts. Since the script does
not
store passwords, you may be prompted for the passwords during the
execution of
the script whenever ssh or scp is invoked.
NOTE
2:
AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME
DIRECTORY
AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEGES
TO THESE
directories.
Do you want
to continue and let the script make the above mentioned changes
(yes/no)?
yes
The user
chose yes
User chose to skip passphrase related questions.
Creating .ssh
directory on local host, if not present already
Creating authorized_keys file
on local host
Changing permissions on authorized_keys to 644 on local
host
Creating known_hosts file on local host
Changing permissions on
known_hosts to 644 on local host
Creating config file on local host
If a
config file exists already at /home/grid/.ssh/config, it would be backed up to
/home/grid/.ssh/config.backup.
Creating .ssh directory and setting
permissions on remote host rdb01d
THE SCRIPT WOULD ALSO BE REVOKING WRITE
PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR oracle. THIS IS AN
SSH REQUIREMENT.
The script would create ~oracle/.ssh/config file on remote
host rdb01d. If a config file exists already at ~oracle/.ssh/config, it would be
backed up to ~oracle/.ssh/config.backup.
The user may be prompted for a
password here since the script would be running SSH on host rdb01d.
Warning:
Permanently added 'rdb01d,192.168.0.31' (ECDSA) to the list of known
hosts.
Done with creating .ssh directory and setting permissions on remote
host rdb01d.
Creating .ssh directory and setting permissions on remote host
rdb02d
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND
others ON THE HOME DIRECTORY FOR oracle. THIS IS AN SSH REQUIREMENT.
The
script would create ~oracle/.ssh/config file on remote host rdb02d. If a config
file exists already at ~oracle/.ssh/config, it would be backed up to
~oracle/.ssh/config.backup.
The user may be prompted for a password here
since the script would be running SSH on host rdb02d.
Warning: Permanently
added 'rdb02d,192.168.0.32' (ECDSA) to the list of known hosts.
Done with
creating .ssh directory and setting permissions on remote host
rdb02d.
Copying local host public key to the remote host rdb01d
The user
may be prompted for a password or passphrase here since the script would be
using SCP for host rdb01d.
Done copying local host public key to the remote
host rdb01d
Copying local host public key to the remote host rdb02d
The
user may be prompted for a password or passphrase here since the script would be
using SCP for host rdb02d.
Done copying local host public key to the remote
host rdb02d
Creating keys on remote host rdb01d if they do not exist already.
This is required to setup SSH on host rdb01d.
Creating keys on remote host rdb02d if they do not exist already. This is required to setup SSH on host rdb02d.
Updating
authorized_keys file on remote host rdb01d
Updating known_hosts file on
remote host rdb01d
Updating authorized_keys file on remote host
rdb02d
Updating known_hosts file on remote host rdb02d
SSH setup is
complete.
------------------------------------------------------------------------
Verifying
SSH setup
===================
The script will now run the date command on
the remote nodes using ssh
to verify if ssh is setup correctly. IF THE SETUP
IS CORRECTLY SETUP,
THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH
SHOULD NOT ASK FOR
PASSWORDS. If you see any output other than date or are
prompted for the
password, ssh is not setup correctly and you will need to
resolve the
issue and set up ssh again.
The possible causes for failure
could be:
1. The server settings in /etc/ssh/sshd_config file do not allow
ssh
for user oracle.
2. The server may have disabled public key based
authentication.
3. The client public key on the server may be outdated.
4.
~oracle or ~oracle/.ssh on the remote host may not be owned by oracle.
5.
User may not have passed -shared option for shared remote users or
may be
passing the -shared option for non-shared remote users.
6. If there is output
in addition to the date, but no password is asked,
it may be a security alert
shown as part of company policy. Append the
additional text to the <OMS
HOME>/sysman/prov/resources/ignoreMessages.txt
file.
------------------------------------------------------------------------
--rdb01d:--
Running
/usr/bin/ssh -x -l oracle rdb01d date to verify SSH connectivity has been setup
from local host to rdb01d.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF
THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP
HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be
OK but being prompted for a password is ERROR.
Sat May 31 16:30:02 KST
2025
------------------------------------------------------------------------
--rdb02d:--
Running
/usr/bin/ssh -x -l oracle rdb02d date to verify SSH connectivity has been setup
from local host to rdb02d.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF
THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP
HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be
OK but being prompted for a password is ERROR.
Sat May 31 16:30:03 KST
2025
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying
SSH connectivity has been setup from rdb01d to rdb01d
IF YOU SEE ANY OTHER
OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A
PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Sat May 31
16:30:03 KST
2025
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying
SSH connectivity has been setup from rdb01d to rdb02d
IF YOU SEE ANY OTHER
OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A
PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Sat May 31
16:30:04 KST
2025
------------------------------------------------------------------------
-Verification
from complete-
SSH verification complete.
[+ASM1:grid@rdb01d][/u01/app/12c/grid/oui/prov/resources/scripts]$
./sshUserSetup.sh -user grid -hosts "rdb01d rdb02d" -noPromptPassphrase
-advanced
The output of this script is also logged into
/tmp/sshUserSetup_2025-05-31-16-30-40.log
Hosts are rdb01d rdb02d
user is
grid
Platform:- Linux
Checking if the remote hosts are reachable
PING
rdb01d (192.168.0.31) 56(84) bytes of data.
64 bytes from rdb01d
(192.168.0.31): icmp_seq=1 ttl=64 time=0.020 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=2 ttl=64 time=0.081 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=3 ttl=64 time=0.423 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=4 ttl=64 time=0.030 ms
64 bytes from rdb01d
(192.168.0.31): icmp_seq=5 ttl=64 time=0.025 ms
--- rdb01d
ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time
4120ms
rtt min/avg/max/mdev = 0.020/0.115/0.423/0.155 ms
PING rdb02d
(192.168.0.32) 56(84) bytes of data.
64 bytes from rdb02d (192.168.0.32):
icmp_seq=1 ttl=64 time=1.72 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=2 ttl=64 time=0.283 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=3 ttl=64 time=0.440 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=4 ttl=64 time=0.365 ms
64 bytes from rdb02d (192.168.0.32):
icmp_seq=5 ttl=64 time=0.682 ms
--- rdb02d
ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time
4104ms
rtt min/avg/max/mdev = 0.283/0.699/1.727/0.531 ms
Remote host
reachability check succeeded.
The following hosts are reachable: rdb01d
rdb02d.
The following hosts are not reachable: .
All hosts are reachable.
Proceeding further...
firsthost rdb01d
numhosts 2
The script will setup
SSH connectivity from the host rdb01d to all
the remote hosts. After the
script is executed, the user can use SSH to run
commands on the remote hosts
or copy files between this host rdb01d
and the remote hosts without being
prompted for passwords or confirmations.
NOTE
1:
As part of the setup procedure, this script will use ssh and scp to
copy
files between the local host and the remote hosts. Since the script does
not
store passwords, you may be prompted for the passwords during the
execution of
the script whenever ssh or scp is invoked.
NOTE
2:
AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME
DIRECTORY
AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEGES
TO THESE
directories.
Do you want
to continue and let the script make the above mentioned changes
(yes/no)?
yes
The user
chose yes
User chose to skip passphrase related questions.
Creating .ssh
directory on local host, if not present already
Creating authorized_keys file
on local host
Changing permissions on authorized_keys to 644 on local
host
Creating known_hosts file on local host
Changing permissions on
known_hosts to 644 on local host
Creating config file on local host
If a
config file exists already at /home/grid/.ssh/config, it would be backed up to
/home/grid/.ssh/config.backup.
Creating .ssh directory and setting
permissions on remote host rdb01d
THE SCRIPT WOULD ALSO BE REVOKING WRITE
PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR grid. THIS IS AN SSH
REQUIREMENT.
The script would create ~grid/.ssh/config file on remote host
rdb01d. If a config file exists already at ~grid/.ssh/config, it would be backed
up to ~grid/.ssh/config.backup.
The user may be prompted for a password here
since the script would be running SSH on host rdb01d.
Warning: Permanently
added 'rdb01d,192.168.0.31' (ECDSA) to the list of known
hosts.
grid@rdb01d's password:
Done with creating .ssh directory and setting permissions
on remote host rdb01d.
Creating .ssh directory and setting permissions on
remote host rdb02d
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR
group AND others ON THE HOME DIRECTORY FOR grid. THIS IS AN SSH
REQUIREMENT.
The script would create ~grid/.ssh/config file on remote host
rdb02d. If a config file exists already at ~grid/.ssh/config, it would be backed
up to ~grid/.ssh/config.backup.
The user may be prompted for a password here
since the script would be running SSH on host rdb02d.
Warning: Permanently
added 'rdb02d,192.168.0.32' (ECDSA) to the list of known hosts.
Done with
creating .ssh directory and setting permissions on remote host
rdb02d.
Copying local host public key to the remote host rdb01d
The user
may be prompted for a password or passphrase here since the script would be
using SCP for host rdb01d.
grid@rdb01d's password:
Done copying local host
public key to the remote host rdb01d
Copying local host public key to the
remote host rdb02d
The user may be prompted for a password or passphrase here
since the script would be using SCP for host rdb02d.
Done copying local host
public key to the remote host rdb02d
Creating keys on remote host rdb01d if
they do not exist already. This is required to setup SSH on host
rdb01d.
Creating keys on remote host rdb02d if they do not exist already. This is required to setup SSH on host rdb02d.
Updating
authorized_keys file on remote host rdb01d
Updating known_hosts file on
remote host rdb01d
Updating authorized_keys file on remote host
rdb02d
Updating known_hosts file on remote host rdb02d
cat:
/home/grid/.ssh/known_hosts.tmp: No such file or directory
cat:
/home/grid/.ssh/authorized_keys.tmp: No such file or directory
SSH setup is
complete.
------------------------------------------------------------------------
Verifying
SSH setup
===================
The script will now run the date command on
the remote nodes using ssh
to verify if ssh is setup correctly. IF THE SETUP
IS CORRECTLY SETUP,
THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH
SHOULD NOT ASK FOR
PASSWORDS. If you see any output other than date or are
prompted for the
password, ssh is not setup correctly and you will need to
resolve the
issue and set up ssh again.
The possible causes for failure
could be:
1. The server settings in /etc/ssh/sshd_config file do not allow
ssh
for user grid.
2. The server may have disabled public key based
authentication.
3. The client public key on the server may be outdated.
4.
~grid or ~grid/.ssh on the remote host may not be owned by grid.
5. User may
not have passed -shared option for shared remote users or
may be passing the
-shared option for non-shared remote users.
6. If there is output in addition
to the date, but no password is asked,
it may be a security alert shown as
part of company policy. Append the
additional text to the <OMS
HOME>/sysman/prov/resources/ignoreMessages.txt
file.
------------------------------------------------------------------------
--rdb01d:--
Running
/usr/bin/ssh -x -l grid rdb01d date to verify SSH connectivity has been setup
from local host to rdb01d.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF
THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP
HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be
OK but being prompted for a password is ERROR.
Sat May 31 16:30:58 KST
2025
------------------------------------------------------------------------
--rdb02d:--
Running
/usr/bin/ssh -x -l grid rdb02d date to verify SSH connectivity has been setup
from local host to rdb02d.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF
THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP
HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be
OK but being prompted for a password is ERROR.
Sat May 31 16:30:58 KST
2025
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying
SSH connectivity has been setup from rdb01d to rdb01d
IF YOU SEE ANY OTHER
OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A
PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Sat May 31
16:30:59 KST
2025
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying
SSH connectivity has been setup from rdb01d to rdb02d
IF YOU SEE ANY OTHER
OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A
PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Sat May 31
16:30:59 KST
2025
------------------------------------------------------------------------
-Verification
from complete-
SSH verification complete.
-- 설치 전
검증
[+ASM1:grid@rdb01d][/u01/app/12c/grid/oui/prov/resources/scripts]$ cd
$GRID_HOME
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ ./runcluvfy.sh stage -pre
crsinst -n rdb01d,rdb02d -fixup
-verbose
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ ./runcluvfy.sh stage -pre
crsinst -n rdb01d,rdb02d -osdba dba -orainv oinstall -fixup -method root
-networks enp0s3/enp0s9 -verbose
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ export
ORACLE_HOME=/u01/app/12c/grid
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ cd
/u01/app/12c/grid
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ /usr/bin/make -f
/u01/app/12c/grid/rdbms/lib/ins_rdbms.mk client_sharedlib libasmclntsh12.ohso
libasmperl12.ohso ORACLE_HOME=/u01/app/12c/grid
--인벤토리 위치
확인
[+ASM1:grid@rdb01d][/u01/app/12c]$ cat
/etc/oraInst.loc
inventory_loc=/u01/app/oraInventory
inst_group=oinstall
[+ASM1:grid@rdb01d][/u01/app/12c]$ cd
/u01/app/oraInventory
[+ASM1:grid@rdb01d][/u01/app/oraInventory]$
ls
backup
ContentsXML logs oraInst.loc orainstRoot.sh
oui
--인벤토리 파일 백업한 후 새로 작성
[+ASM1:grid@rdb01d][/u01/app/oraInventory]$ cd
ContentsXML
[+ASM1:grid@rdb01d][/u01/app/oraInventory/ContentsXML]$
ls
comps.xml
inventory.xml libs.xml
[+ASM1:grid@rdb01d][/u01/app/oraInventory/ContentsXML]$ cp
inventory.xml
inventory.xml.bak
[+ASM1:grid@rdb01d][/u01/app/oraInventory/ContentsXML]$
vi inventory.xml
[+ASM1:grid@rdb01d][/u01/app/oraInventory/ContentsXML]$ cat
inventory.xml
<?xml version="1.0" standalone="yes"
?>
<!-- Copyright (c) 1999, 2025, Oracle and/or its affiliates.
All
rights reserved. -->
<!-- Do not modify the contents of this file by
hand. -->
<INVENTORY>
<VERSION_INFO>
<SAVED_WITH>12.2.0.1.4</SAVED_WITH>
<MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME="OraDB12Home1"
LOC="/u01/app/oracle/product/12c/db_1" TYPE="O"
IDX="2"/>
</HOME_LIST>
<COMPOSITEHOME_LIST>
</COMPOSITEHOME_LIST>
</INVENTORY>
--> 위에서 grid home(HOME NAME으로 시작하는데 grid home 기재되어 있는거 제거) 관련된 라인 제거 (오라클 홈은
남겨둠)
--각각의 노드의 /etc/hosts/ 정보 맞춰줘야함
[root@rdb01d][/tmp/patch]$ vi
/etc/hosts
[root@rdb01d][/tmp/patch]$ cat
/etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
::1
localhost localhost.localdomain localhost6
localhost6.localdomain6
### Public
IP
192.168.0.31
rdb01d
192.168.0.32
rdb02d
### Private
IP
10.0.0.31 rdb01d-priv
10.0.0.32
rdb02d-priv
### Virtual
IP
192.168.0.34
rdb01d-vip
192.168.0.35
rdb02d-vip
###
DNS
192.168.0.37
drdb2-scan
192.168.0.38
drdb2-scan
192.168.0.39
drdb2-scan
##
Standby
192.168.0.41 tdb01p
[root@rdb02d][/tmp]$ vi /etc/hosts
[root@rdb02d][/tmp]$ cat
/etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
::1
localhost localhost.localdomain localhost6
localhost6.localdomain6
### Public
IP
192.168.0.31
rdb01d
192.168.0.32
rdb02d
### Private
IP
10.0.0.31 rdb01d-priv
10.0.0.32
rdb02d-priv
### Virtual
IP
192.168.0.34
rdb01d-vip
192.168.0.35
rdb02d-vip
###
DNS
192.168.0.37
drdb2-scan
192.168.0.38
drdb2-scan
192.168.0.39
drdb2-scan
##
Standby
192.168.0.41 tdb01p
--CRS 디스크
포맷
[+ASM1:grid@rdb01d][/dev/oracleasm/disks]$ dd if=/dev/zero of=/dev/sdb
bs=1M count=1 conv=notrunc
status=progress
[+ASM1:grid@rdb01d][/dev/oracleasm/disks]$ dd if=/dev/zero
of=/dev/sdc bs=1M count=1 conv=notrunc
status=progress
[+ASM1:grid@rdb01d][/dev/oracleasm/disks]$ dd if=/dev/zero
of=/dev/sdd bs=1M count=1 conv=notrunc status=progress
[+ASM1:grid@rdb01d][/u01/app/12c/grid]$ ./gridSetup.sh -applyPSU
/tmp/patch/33583921
Preparing the home to
patch...
Applying the patch /tmp/patch/33583921...
Successfully applied
the patch.
The log can be found at:
/u01/app/oraInventory/logs/GridSetupActions2025-05-31_04-43-56PM/installerPatchActions_2025-05-31_04-43-56PM.log
Launching
Oracle Grid Infrastructure Setup Wizard...
cluster name : drdb2
scan name :
drdb2-scan
2번노드 추가 : rdb02d, HUB, rdb02d-vip
--CLSRSC-175: Failed to write
the checkpoint 'ROOTCRS_FIRSTNODE' with status 'SUCCESS' (error code 1) 에러가 발생
시
--RAC1 및 RAC2 모두 수행해줌
chown
grid:oinstall /u01/app/
chown grid:oinstall /u01/app/12c
chown
grid:oinstall /u01/app/12c/grid
chown grid:oinstall
/u01/app/12c/grid/crs
--> 설치가 완료되면 클러스터명을 확인함
[+ASM1:grid@rdb01d][/home/grid]$ olsnodes
-c
drdb2
[root@rdb01d][/root]$ oracleasm
listdisks
CRS1
CRS2
CRS3
DATA1_1
FRA1_1
GIMR1_1
[root@rdb01d][/root]$
[+ASM1:grid@rdb01d][/home/grid]$ sa
SQL*Plus: Release 12.2.0.1.0 Production on Sat May 31 18:46:28 2025
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release
12.2.0.1.0 - 64bit Production
SQL>
col
name for a20
col state for a30
SELECT name, state FROM
v$asm_diskgroup;
SQL>
alter diskgroup DATA1 mount;
SQL> alter diskgroup FRA1
mount;
--> asm disk 마운트
--> crs에 DB를
등록함
[DRDB1:oracle@rdb01d][/home/oracle]$ srvctl add database -db DRDB
-oraclehome /u01/app/oracle/product/12c/db_1 -spfile
+DATA1/DRDB/PARAMETERFILE/spfile.268.1198106043 -pwfile
+DATA1/DRDB/PASSWORD/pwddrdb.256.1196204543 -startoption open -stopoption
immediate -role PRIMARY -diskgroup "FRA1,DATA1"
[DRDB1:oracle@rdb01d][/home/oracle]$ srvctl add instance -db DRDB
-instance DRDB1 -node rdb01d
[DRDB1:oracle@rdb01d][/home/oracle]$ srvctl add
instance -db DRDB -instance DRDB2 -node rdb02d
--> 인스턴스도 추가해줌
[DRDB1:oracle@rdb01d][/home/oracle]$
srvctl config database -db DRDB
Database unique name: DRDB
Database
name:
Oracle home: /u01/app/oracle/product/12c/db_1
Oracle user:
oracle
Spfile: +DATA1/DRDB/PARAMETERFILE/spfile.268.1198106043
Password
file: +DATA1/DRDB/PASSWORD/pwddrdb.256.1196204543
Domain:
Start options:
open
Stop options: immediate
Database role: PRIMARY
Management policy:
AUTOMATIC
Server pools:
Disk Groups: FRA1,DATA1
Mount point
paths:
Services:
Type: RAC
Start concurrency:
Stop
concurrency:
OSDBA group: dba
OSOPER group: oper
Database instances:
DRDB1,DRDB2
Configured nodes: rdb01d,rdb02d
CSS critical: no
CPU count:
0
Memory target: 0
Maximum memory: 0
Default network number for
database services:
Database is administrator managed
--> DB 시작
[2025-05-31
18:52:18][rdb01d]<SYS@DRDB1> startup
[2025-05-31 18:52:37][rdb02d]<SYS@DRDB2> startup
'Oracle > RAC' 카테고리의 다른 글
| [2025-05-29] Interconnect Private IP 정보 변경(네트워크 인터페이스명 변경) (12cR2) (0) | 2025.09.28 |
|---|---|
| [2025-06-06] RAC환경에서 로컬 파일 시스템에 데이터 파일을 잘못 만든 후 ASM 영역으로 move하는 방법 (19c) (2) | 2025.08.15 |
| [2025-05-31] RAC환경에서 Scan Name 변경 (12cR2) (0) | 2025.07.18 |
| [2025-05-29] Interconnect Private IP 정보 변경(네트워크 인터페이스명 변경) (12cR2) (0) | 2025.07.13 |
| [2025-05-29] RAC환경에서 ORACLE LOCAL REGISTRY(OLR) 실습 (12cR2) (0) | 2025.07.13 |