Oracle Single Instance +asm startup and shutdown

Transferred from: chenoracle:http://blog.itpub.net/29785807/viewspace-1744718/

Startup shutdown considerations

1 The start of ASM instance and the start of DB instance have strict relations, ASM boot must be earlier than the database instance, shutdown must be later than ASM instance, because it is the database data file storage location;

2 priority is required to start the Css,has service.

Start:

a You should start ASM first , when you start the database

If the order is reversed, the error will be

For example:

1 Turn off ASM

[Email protected] ~]$ Sqlplus

Enter user-name:/as sysasm

sql> shutdown Immediate

ASM diskgroups dismounted

ASM instance shutdown

2 Start Database error

[Email protected] ~]$ 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

a Start ASM before you should make sure that Css,has Service has been started

1

Check CSS whether the service starts:

[[email protected] ~]$ crsctl Check CSS

[Email protected] ~]$ Ps-ef|grep CSSD

2

Check has whether the service starts:

[Email protected] ~]$ CRSCTL Check has

[Email protected] ~]$ Ps-ef|grep D.bin

Discovery has service started, while ORA.CSSD and Ora.diskmon these 2 services are dependent on has maintained.

3

View the status of each resource further

[Email protected] ~]$ crs_stat-t

[Email protected] ~]$ crsctl status resource-t

4

Check ORA.CSSD and Ora.diskmon the default properties

[Email protected] ~]$ crs_stat-p ORA.CSSD

。。。。。

Auto_start=never

。。。。。

[Email protected] ~]$ 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.

This means that they will not start automatically with the start of the has service, although the has service is started automatically by default.

5

Manual start

[Email protected] ~]$ crsctl start resource ORA.CSSD

Note: ORA.CSSD and Ora.diskmon The two services are dependent, starting which will be two all up.

6 Other Operations

1) The Have (high availability Service) is automatically started by default.

Use the following command to cancel and enable auto-start

Cancel self-boot: crsctl Disable has

enable self-booting: Crsctl Enable has

2) has manual start and stop

Crsctl start has

Crsctl Stop has

3) View the status of has

CRSCTL Check has

4) If you want the ORA.CSS and Ora.diskmon services to start automatically as has, the Auto_start property of both services can be

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 auto start for Ora.css and Ora.diskmon

Crsctl Modify Resource "ORA.CSSD"-attr "Auto_start=never"

Crsctl Modify Resource "Ora.diskmon"-attr "Auto_start=never"

two Start ASM Example

[Email protected] ~]$ 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

[Email protected] ~]$ 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

Turn off ASM

a shutdown should first shut down the database before turning off ASM

If the order is reversed, the error will be

For example:

1 Turn off ASM

[Email protected] ~]# Su-grid

[Email protected] ~]$ Sqlplus/as sysasm

sql> shutdown Immediate

Ora-15097:cannot SHUTDOWN ASM Instance with connected client (process 7322)

The correct order is:

a Close the database

[Email protected] ~]$ Sqlplus/as SYSDBA

sql> shutdown Immediate

two Turn off ASM

[Email protected] ~]# Su-grid

[Email protected] ~]$ Sqlplus/as sysasm

sql> shutdown Immediate

ASM diskgroups dismounted

ASM instance shutdown

Oracle Single Instance +asm startup and shutdown