Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to understand Oracle ASM startup and shutdown

2025-03-31 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

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

This article shows you how to understand Oracle ASM startup and shutdown, the content is concise and easy to understand, can definitely brighten your eyes, through the detailed introduction of this article, I hope you can get something.

Oracle+ASM startup and shutdown

Startup and shutdown considerations

1 there is a strict relationship between the startup of the ASM instance and the startup of the database instance. ASM must start earlier than the database instance, and the shutdown must be later than the ASM instance, because it is the storage location of the database data file.

2 priority needs to be given to starting the CSS,HAS service.

Start:

As soon as you start, you should start ASM first, and then start the database

An error will be reported if the order is reversed.

For example:

1 close ASM

[grid@ogg1 ~] $sqlplus

Enter user-name: / as sysasm

SQL > shutdown immediate

ASM diskgroups dismounted

ASM instance shutdown

2 error reporting when starting the database

[oracle@ogg1 ~] $sqlplus / as sysdba

SQL > startup

ORA-01078: failure in processing system parameters

ORA-01565: error in identifying file'+ SYSTEDG/prod1/spfileprod1.ora'

ORA-17503: ksfdopn:2 Failed to open file + SYSTEDG/prod1/spfileprod1.ora

ORA-15077: could not locate ASM instance serving a required diskgroup

The correct order is

You should make sure that the css,has service is started before starting ASM

one

Check that the CSS service is started:

[grid@ogg1 ~] $crsctl check css

[grid@ogg1 ~] $ps-ef | grep cssd

two

Check that the HAS service is started:

[grid@ogg1 ~] $crsctl check has

[grid@ogg1 ~] $ps-ef | grep d.bin

It is found that the HAS service is started, while the ora.cssd and ora.diskmon services are dependent on HAS maintenance.

three

Further check the status of each resource

[grid@ogg1] $crs_stat-t

[grid@ogg1] $crsctl status resource-t

four

Check the default properties of ora.cssd and ora.diskmon

[grid@ogg1] $crs_stat-p ora.cssd

.

AUTO_START=never

.

[grid@ogg1] $crs_stat-p ora.diskmon

.

AUTO_START=never

.

You can see that the AUTO_START property of both resources is set to never by default

In other words, they do not start automatically when the HAS service starts, although the HAS service starts automatically by default.

five

Manual start

[grid@ogg1 ~] $crsctl start resource ora.cssd

Note: ora.cssd and ora.diskmon are dependent on each other. Starting either service will bring both up.

6 other operations

1) HAS (High Availability Service) starts automatically by default.

You can cancel and enable automatic startup with the following command

Cancel self-startup: crsctl disable has

Enable self-boot: crsctl enable has

2) HAS starts and stops manually

Crsctl start has

Crsctl stop has

3) check the status of HAS

Crsctl check has

4) if you want ora.css and ora.diskmon services to start automatically with the start of HAS, you can use the AUTO_START property of these two services

Crsctl modify resource "ora.cssd"-attr "AUTO_START=1"

Or

Crsctl modify resource "ora.diskmon"-attr "AUTO_START=1"

5) if you want to cancel the Auto start of ora.css and ora.diskmon

Crsctl modify resource "ora.cssd"-attr "AUTO_START=never"

Crsctl modify resource "ora.diskmon"-attr "AUTO_START=never"

Start the ASM instance

[grid@ogg1 ~] $sqlplus / as sysasm

SQL > startup

SQL > col instance_name for A15

SQL > col status for A15

SQL > select instance_name,status from v$instance

INSTANCE_NAME STATUS

--

+ ASM STARTED

Three start the database

[oracle@ogg1 ~] $sqlplus / as sysdba

SQL > startup

SQL > col instance_name for A15

SQL > col status for A15

SQL > select instance_name,status from v$instance

INSTANCE_NAME STATUS

--

Prod1 OPEN

Close ASM

As soon as it is closed, the database should be closed first, before shutting down ASM.

An error will be reported if the order is reversed.

For example:

1 close ASM

[root@ogg1 ~] # su-grid

[grid@ogg1 ~] $sqlplus / as sysasm

SQL > shutdown immediate

ORA-15097: cannot SHUTDOWN ASM instance with connected client (process 7322)

The correct order is:

As soon as the database is closed

[oracle@ogg1 ~] $sqlplus / as sysdba

SQL > shutdown immediate

Two, close ASM.

[root@ogg1 ~] # su-grid

[grid@ogg1 ~] $sqlplus / as sysasm

SQL > shutdown immediate

ASM diskgroups dismounted

ASM instance shutdown

The above is how to understand Oracle ASM startup and shutdown. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report