How to manage ASM instance [message #561799] |
Wed, 25 July 2012 06:21 |
|
x-oracle
Messages: 380 Registered: April 2011 Location: gujarat
|
Senior Member |
|
|
hello i have create asm instance on my single database name wser
i have successfully create this asm instance
now i want to know how can i start and stop this asm instance and my database
when i using this steps and i want to access database i got this error
C:\Users\Administrator>set oracle_sid=+asm
C:\Users\Administrator>sqlplus
SQL*Plus: Release 10.2.0.3.0 - Production on Wed Jul 25 16:35:55 2012
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Enter user-name: sys as sysdba
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> select name from v$database;
select name from v$database
*
ERROR at line 1:
ORA-01507: database not mounted
SQL> select instance_name from v$instance;
INSTANCE_NAME
----------------
+asm
this is not a rac database i just create this asm instance on my single database only
[EDITED by LF: fixed topic title typo; was "hwo"]
[Updated on: Wed, 25 July 2012 15:06] by Moderator Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
Re: Hwo to manage asm instance [message #562373 is a reply to message #562362] |
Tue, 31 July 2012 21:38 |
trantuananh24hg
Messages: 744 Registered: January 2007 Location: Ha Noi, Viet Nam
|
Senior Member |
|
|
@alan: The ASM instance is independent to Oracle Database Instance.
Before 9i, datafile was created with 2 options: File-system based on OS managed block or raw-device. Both of them without any Oracle manage or control separetly. After 10g, ASM is introduced, I think you should read ASM instance at tahiti.oracle.com.
|
|
|
Re: Hwo to manage asm instance [message #562507 is a reply to message #562373] |
Wed, 01 August 2012 14:12 |
|
alan.kendall@nfl.com
Messages: 163 Registered: June 2012 Location: Culver City, California
|
Senior Member |
|
|
Here are commands that I used to check and stop "ASM" before some maintenance
on our disaster recovery boxes. The asm instances came up on their own
when the Unix boxes were restarted.
csdrdb01(oracle)/u01/home/oracle>srvctl status asm -n csdrdb01
ASM instance +ASM1 is running on node csdrdb01.
csdrdb01(oracle)/u01/home/oracle>srvctl status asm -n csdrdb02
ASM instance +ASM2 is running on node csdrdb02.
csdrdb01(oracle)/u01/home/oracle>srvctl stop asm -n csdrdb01
csdrdb01(oracle)/u01/home/oracle>srvctl stop asm -n csdrdb02
csdrdb01(oracle)/u01/home/oracle>srvctl status asm -n csdrdb01
ASM instance +ASM1 is not running on node csdrdb01.
csdrdb01(oracle)/u01/home/oracle>srvctl status asm -n csdrdb02
ASM instance +ASM2 is not running on node csdrdb02.
To shutdown the production database prior to shutting down ASM
I used the following commands.
>srvctl status database -d CSCDAP
>srvctl stop instance -d CSCDAP -i CSCDAP1
>srvctl stop instance -d CSCDAP -i CSCDAP2
>srvctl stop instance -d CSCDAP -i CSCDAP3
>srvctl status database -d CSCDAP
Whenever I do maintenance on RAC, I stop then start one
instance at a time. This way if there is a startup error,
I can fix it from one of the started instances and "Voila"
I never have an outage related to changing oracle memory parameters.
SQL> alter system set sessions=10000 scope=spfile sid='*';
System altered.
SQL> alter system set processes=10000 scope=spfile sid='*';
System altered.
SQL> alter system set open_cursors=10000 scope=spfile sid='*';
System altered.
>srvctl status database -d CSCDAP
Instance CSCDAP1 is running on node csprdcdadb01-fe
Instance CSCDAP2 is running on node csprdcdadb02-fe
Instance CSCDAP3 is running on node csprdcdadb03-fe
>srvctl stop instance -d CSCDAP -i CSCDAP1
>srvctl status database -d CSCDAP
Instance CSCDAP1 is not running on node csprdcdadb01-fe
Instance CSCDAP2 is running on node csprdcdadb02-fe
Instance CSCDAP3 is running on node csprdcdadb03-fe
>srvctl start instance -d CSCDAP -i CSCDAP1
>srvctl status database -d CSCDAP
Instance CSCDAP1 is running on node csprdcdadb01-fe
Instance CSCDAP2 is running on node csprdcdadb02-fe
Instance CSCDAP3 is running on node csprdcdadb03-fe
>srvctl stop instance -d CSCDAP -i CSCDAP2
>srvctl status database -d CSCDAP
Instance CSCDAP1 is running on node csprdcdadb01-fe
Instance CSCDAP2 is not running on node csprdcdadb02-fe
Instance CSCDAP3 is running on node csprdcdadb03-fe
>srvctl start instance -d CSCDAP -i CSCDAP2
>srvctl status database -d CSCDAP
Instance CSCDAP1 is running on node csprdcdadb01-fe
Instance CSCDAP2 is running on node csprdcdadb02-fe
Instance CSCDAP3 is running on node csprdcdadb03-fe
>srvctl stop instance -d CSCDAP -i CSCDAP3
>srvctl status database -d CSCDAP
Instance CSCDAP1 is running on node csprdcdadb01-fe
Instance CSCDAP2 is running on node csprdcdadb02-fe
Instance CSCDAP3 is not running on node csprdcdadb03-fe
>srvctl start instance -d CSCDAP -i CSCDAP3
>srvctl status database -d CSCDAP
Instance CSCDAP1 is running on node csprdcdadb01-fe
Instance CSCDAP2 is running on node csprdcdadb02-fe
Instance CSCDAP3 is running on node csprdcdadb03-fe
To stop CRS after shutting down ASM, I did the following:
cd /u01/app/oracle/product/10.2.0/crs
crsctl check crs
crsctl stop crs
To restart the stage listener on one node:
csstgcdadb11(oracle)/home/oracle>srvctl status listener -n csstgcdadb11
Listener LISTENER is enabled on node(s): csstgcdadb11
Listener LISTENER is running on node(s): csstgcdadb11
csstgcdadb11(oracle)/home/oracle>srvctl status listener -n csstgcdadb12
Listener LISTENER is enabled on node(s): csstgcdadb12
Listener LISTENER is running on node(s): csstgcdadb12
csstgcdadb11(oracle)/home/oracle>srvctl stop listener -n csstgcdadb11
csstgcdadb11(oracle)/home/oracle>srvctl status listener -n csstgcdadb11
Listener LISTENER is enabled on node(s): csstgcdadb11
Listener LISTENER is not running on node(s): csstgcdadb11
csstgcdadb11(oracle)/home/oracle>srvctl start listener -n csstgcdadb11
csstgcdadb11(oracle)/home/oracle>srvctl status listener -n csstgcdadb11
Listener LISTENER is enabled on node(s): csstgcdadb11
Listener LISTENER is running on node(s): csstgcdadb11
|
|
|