RAC +ASM instance [message #612281] |
Tue, 15 April 2014 09:47 |
|
asp_
Messages: 7 Registered: April 2014 Location: msk
|
Junior Member |
|
|
Hello.
I installed Grid Infrastructure and Oracle database on two nodes. Then using dbca I am created a cluster instance (sid: docu11) and it works fine. Now I can connect to sid docu111 or docu112 using sqlplus/toad/.. and create new tablespaces, import db and etc. When i am entering "export ORACLE_SID=+ASM2" and try to connect to sql (sqlplus / as sysdba), I get error when trying to startup this instance:
oracle[10.2.0:SID:+ASM2]@rac2-n1:/u01/dbhome_1/product/db/10.2.0/dbs$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue Apr 15 18:40:09 2014
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/dbhome_1/product/db/10.2.0/dbs/init+ASM2.ora'
SQL>
This files are not exists in this folder. I couldn't find information how is correct to create this files with parametres.
oracle[10.2.0:SID:+ASM2]@rac2-n1:/u01/dbhome_1/product/db/10.2.0/dbs$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 15-APR-2014 18:44:38
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date 14-APR-2014 21:47:46
Uptime 0 days 20 hr. 56 min. 52 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/grid_home/network/admin/listener.ora
Listener Log File /u01/11.2.0/diag/tnslsnr/rac2-n1/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=*.97)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=*.101)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM2", status READY, has 1 handler(s) for this service...
Service "docu11" has 1 instance(s).
Instance "docu112", status READY, has 1 handler(s) for this service...
Service "docu11XDB" has 1 instance(s).
Instance "docu112", status READY, has 1 handler(s) for this service...
The command completed successfully
[Updated on: Tue, 15 April 2014 09:59] Report message to a moderator
|
|
|
|
Re: RAC +ASM instance [message #612286 is a reply to message #612284] |
Tue, 15 April 2014 10:30 |
|
asp_
Messages: 7 Registered: April 2014 Location: msk
|
Junior Member |
|
|
BlackSwan wrote on Tue, 15 April 2014 19:00Welcome to this forum.
Please read and follow the forum guidelines, to enable us to help you:
http://www.orafaq.com/forum/t/88153/0/ and please read http://www.orafaq.com/forum/t/174502/102589/
>ORACLE_SID=+ASM2
what is +ASM2 instance?
As I understand from manuals, tutorials and forums, for example if I want to resize my diskgroup, i need connect to db using sid +ASM (in my case it's +ASM2).
oracle[10.2.0:SID:docu112]@rac2-n1:/u01/dbhome_1/product/db/10.2.0/dbs$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue Apr 15 19:23:48 2014
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
SQL> alter diskgroup DATA resize all;
alter diskgroup DATA resize all
*
ERROR at line 1:
ORA-15000: command disallowed by current instance type
oracle[10.2.0:SID:+ASM2]@rac2-n1:/u01/dbhome_1/product/db/10.2.0/dbs$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue Apr 15 19:23:27 2014
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> alter diskgroup DATA resize all;
alter diskgroup DATA resize all
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0
[Updated on: Tue, 15 April 2014 10:32] Report message to a moderator
|
|
|
|
|
|
|
|
Re: RAC +ASM instance [message #612439 is a reply to message #612366] |
Fri, 18 April 2014 09:13 |
|
asp_
Messages: 7 Registered: April 2014 Location: msk
|
Junior Member |
|
|
Michel Cadot wrote on Wed, 16 April 2014 20:42
Once again, it depends on your current Oracle and the one for ASM.
Thank to everybody who wrote here, I couldn't enter to sql as sysasm because I just had to change my $ORACLE_HOME to /u01/grid_home.
Now I need to change diskgroup size. Is it possible not to create new partiton from new space at harddrive (LUN), not to create new ASM disk and after that not to include new ASM disk to existing diskgroup? Is it possible only to resize diskgroup (like in LVM)?
SQL> alter diskgroup data resize all;
Diskgroup altered.
SQL> select name, total_mb, usable_file_mb from v$asm_diskgroup;
NAME TOTAL_MB USABLE_FILE_MB
------------------------------------------------------------------------------------------ ---------- --------------
DATA 389113 48017
SQL> alter diskgroup data resize all size 437130M;
alter diskgroup data resize all size 437130M
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15057: specified size of 437130 MB is larger than actual size of 389113 MB
[Updated on: Fri, 18 April 2014 09:27] Report message to a moderator
|
|
|
Re: RAC +ASM instance [message #612453 is a reply to message #612439] |
Fri, 18 April 2014 16:47 |
John Watson
Messages: 8962 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
You cannot "resize" a disk group directly. You can add or remove disks to or from the diskgroup, or you can resize disks in a disk group. THis command,alter diskgroup data resize all size 437130M; is attempting to increase the size of every disk to 437G, which is pretty big. What size are the devices?
|
|
|
Re: RAC +ASM instance [message #612572 is a reply to message #612453] |
Tue, 22 April 2014 03:03 |
|
asp_
Messages: 7 Registered: April 2014 Location: msk
|
Junior Member |
|
|
John Watson wrote on Sat, 19 April 2014 01:47You cannot "resize" a disk group directly. You can add or remove disks to or from the diskgroup, or you can resize disks in a disk group. THis command,alter diskgroup data resize all size 437130M; is attempting to increase the size of every disk to 437G, which is pretty big. What size are the devices?
Disk /dev/xvdc: 450.9 GB, 450971566080 bytes
255 heads, 63 sectors/track, 54827 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/xvdc1 1 49605 398452131 83 Linux
/etc/init.d/oracleasm querydisk /dev/oracleasm/disks/DATA1
Device "/dev/oracleasm/disks/DATA1" is marked an ASM disk with the label "DATA1"
select name, total_mb, usable_file_mb from v$asm_diskgroup;
NAME TOTAL_MB USABLE_FILE_MB
------------------------------------------------------------------------------------------ ---------- --------------
DATA 389113 48017
ll /dev/oracleasm/disks/
total 0
brw-rw---- 1 grid asmadmin 202, 33 Apr 16 13:58 DATA1
OK, If i don't want to add or remove ASMdisks to diskgroup, can i remove ASMdisk(DATA1) from my diskgroup(DATA) and then resize this ASMdisk (If it is possbile, how I can do this)? Or I need to delete ASM disk with all data and create new asmdisk?
[Updated on: Tue, 22 April 2014 03:08] Report message to a moderator
|
|
|