ArticleDirectory
- Step 1:
- Step 2:
- Step 3:
- Step 4:
- Step 1:
- Step 2:
- Step 3: In ideal cases, all are OK. If any problem occurs, handle the problem one by one.
Close sequence: [other nodes]-> [first node]
Operation: Step 1:
{
Use a grid user or close the listener: {crs_stop listener Resource Name | srvctl stop listener}-- Global
|
Oracle user disable listener: {LSNRCTL stop}-- Single Node
}
Step 2:
Shut down the database instance: shutdown immediate through sqlplus as an oracle user
Step 3:
Stop the cluster as a grid user or root user: crsctl stop CRS
Step 4:
Check the effect of disabling and view the cluster status:
{
PS-Ef | grep ora _
|
PS-Ef | grep ASM _
|
Crs_stat-T
}
######################################## ########################################
Startup sequence: [first node]-> [other nodes]
Operation: Step 1:
Start the cluster as a grid user or root user: crsctl start CRS
Step 2:
Check the cluster status as a grid or root user:
{
Crsctl check CRS
|
Crs_stat-T
|
PS-Ef | grep ora _
|
PS-Ef | grep ASM _
}
Step 3: In ideal cases, all are OK. If any problem occurs, handle the problem one by one.
(1) If the data disk group is not suspended, run the following command as a grid user:
{
Crs_start ora. Data. DG
|
Use the sqlplus interface in ORACLE_HOME of the ASM instance to mount the disk: Alter diskgroup Mount
}
(2 ). if the tnslistener of the cluster in the grid is faulty, you can bypass the control in the grid and directly use the listener listening under ORACLE of each node. You do not need to configure the listener. ora
######################################## ########################################
Restart = close + start