ASM cache....

Hi,
I want to understand what does ASM cache contains and for what purpose its used in ASM instance?I tried finding in docs but some how couldnt find it?ASM has all the other memory parameters than what does ASM cache does and how(if we can) change or configure its size?
Thanks in advance and regards,
Aman....

db_cache_size parameter controls your ASM cache. ASM cache area is used to
cache metadata blocks. The default value will suit most all implementations.
I have worked on single ASM instance with 4 disk groups and 12 databases deployed on it. Best practices only talks about increasing processes parameter if your number of databases increases. Default value (10202) of ASM cache is 24mb and seems to be enough to handle most of the load. Even if you try increase SGA for ASM using SGA_MAX_SIZE it seems most of the memory goes to variable size and ASM cache continues to be 24MB. so I modified db_cache_size value to 64mb and got it increased as I theotically feel that it has to be relative with number of disk groups, database instances supported.
Oracle does say that ASM memeory needs are static and dont change much dynamically during its run.

Similar Messages

Database creation with ASM using dbca

hi all,
i found the steps to create the database using ASM diskgroup.
but i received errors when configuring the FRA(flash recovery area), DBF(normal), +ARCH(archival dest),
i tried atleast 2 to 3 times from scratch but found the same error....................
ORA: 19624
ORA: 19870
here are the steps can somebody correct these steps..................
Create Virtual Disks from VM Ware software when server is down.
Choose Edit Virtual Machine Settings.
Click on Add button
Press Next and Highlight Hard Disk, then click Next
Check ‘Create a New Virtual Disk’
Choose SCSI as type
Select Size as 2 GB
Name the virtual disk as ‘ASMDBF1.vmdk’
Create additional disks as:
ASMDBF1.vmdk for DBF files
ASMDBF2.vmdk Failover group
ASMFRA.vmdk Flash Back Recovery Area
ASMREDO.vmdk Redo Log Area
ASMARCH.vmdk Archived Logs
•     Start up the server OraWorld1
•     Go to Disk Management and you will be prompted with a screen which should display all five disks with a check mark. Accept defaults and Click next.
•     On second script all five will be unchecked, click Next
•     Press Finish to complete and you should see all 5 disks as Type Basic Unallocated. For each of the disk perform:
1.     Right click, New Partition, Extended Partition and Finish
2.     Right click, New Logical drive, Do not assign drive letter nor partition it.
3.     From command prompt type Diskpart and enter Automount enable.
4.     From command prompt, configure basic CRS services as
5.     C:\oracle\product\10.2.0\db_1>localconfig add
6.     C:\oracle\product\10.2.0\db_1>localconfig add
7.     Step 1: creating new OCR repository
8.     Successfully accumulated necessary OCR keys.
9.     Creating OCR keys for user 'administrator', privgrp ''..
10.     Operation successful.
11.     Step 2: creating new CSS service
12.     successfully created local CSS service
13.     successfully added CSS to home
•     Launch DBCA and choose Configure Storage Management.
•     Select Create New group, choose stamp disks which will show you all of your five disks. Configure ASM links to all these disks as:
1.     ORCLDISKASMDBF1 \Device\Harddisk1\Partition1
2.     ORCLDISKASMDBF2 \Device\Harddisk2\Partition1
3.     ORCLDISKASMFRA \Device\Harddisk3\Partition1
4.     ORCLDISKASMREDO \Device\Harddisk4\Partition1
5.     ORCLDISKASMARCH \Device\Harddisk5\Partition1
Now make Change Disk Discovery Path as Null and you should see all disks.
Now create Disk groups as :
ARCH \\.\ORCLDISKASMARCH External 1GB
REDO \\.\ORCLDISKASMREDO External 1GB
FRA \\.\ORCLDISKASMFRA External 2GB
DBF (MAIN GROUP WITH 2 SUB-GROUPS) Must create as Normal Redundancy
DBFP \\.\ORCLDISKASMDBF1 External 2GB
DBFS \\.\ORCLDISKASMDBF2 External 2GB
You now have a running ASM instance on the server.
•     Checking ASM instance
You can always use DBCA to check settings of ASM.
Alternatively, go to command prompt:
Set ORACLE_SID=+ASM
Sqlplus /nolog
Connect sys/password as sysdba
Show sga (80MB)
Total System Global Area 83886080 bytes
Fixed Size 1247420 bytes
Variable Size 57472836 bytes
ASM Cache 25165824 bytes
SQL>desc You can then check C:\oracle\product\10.2.0\db_1\database for these files. You can also view v$parameter for all possible values for ASM instance.
+asm.asm_diskgroups='DATA1','ARCH','REDO','FRA','DBF'#Manual Mount
*.asm_diskgroups='DATA1','ARCH','REDO','FRA','DBF'
*.asm_diskstring=''
*.background_dump_dest='C:\oracle\product\10.2.0\admin\+ASM\bdump'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\+ASM\cdump'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='SHARED'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\+ASM\udump'
You can change some of the values like large pool and even db cache size. You can also manually create the disk group as:
Create diskgroup DBF NORMAL redundancy
Failgroup flgrp1 disk ‘\\.\ORCLDISKDATA0’, ‘\\.\ORCLDISKDATA1’
Failgroup flgrp2 disk ‘\\.\ORCLDISKDATA2’, ‘\\.\ORCLDISKDATA3’;
Check Candidate disks:
select group_number, disk_number, mount_status, header_status, state, path from v$asm_disk;
Other useful queries:
Select group_number, name, total_mb, free_mb, state, type
From v$asm_diskgroup;
Select group_number, disk_number, mount_status, header_status, state, path, failgroup
From v$asm_disk;
You can use sql commands to perform most of the ASM tasks, however EM console can also be used here
Oracle Database Installation
•     Launch DBCA
•     Choose Create Database and select OLTP type
•     Name it as ORCL2, choose ASM as file system, select all disk groups to be used.
•     Use oracle managed files as:+DBF press Next
*•     Specify Flash Recovery Area as +FRA*
*•     Enable archiving at +ARCH*
*•     Choose Auto SGA as 55% of memory*
*•     Leave else default and complete DB creation.*
*•     Launch NetConfig and define Listener with default settings.* here i received the errors,.................
Database ORCL2 is created with the following attributes:
NAME: ORCL2
SPFILE: +ARCH/ORCL2/spfileORCL2.ora
URL: http://oraworld1:1158/em

Strange, those messages are RMAN backup errors -- are you trying to backup the database?
Or...if you selected "create starter database" it may be that dbca is not finding the backup files from the "demo" database.
:p

Error while starting ASM instance

when i was trying to startup my ASM database , i was getting the following error.
SQL> startup
ASM instance started
Total System Global Area 125829120 bytes
Fixed Size 2019000 bytes
Variable Size 98644296 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15003: diskgroup "DBDATA" already mounted in another lock name space"
thnx in advance

Hi,
i was not aware of ASM anymore, i can give some more details of this.
There was already an instance named +ASM in the host, which has the diskgroup 'DBDATA' created.
But now i have created a new instance and i was trying to connect to the same diskgroup.
I dont have permission of the root, but i have the oracle login.
could u pleaze help me in this regard...
i need to connect to the diskgroup, if i try to stop the other instance, i was not getting the error, but the diskgroup is getting dis-mounted.
thnx alot for the replies

Not able to start the oracle database with ASM

HI all,
WE are using oracle10.2.0.1 on OEL5.
I have mounted ASM but when i try to start the oracle database, it is asking "db is already started shut it down first"
[root@localhost ~]# /etc/init.d/oracleasm listdisks
VOL1
VOL2
[root@localhost ~]#
[root@localhost ~]# su - oracle
-bash-3.2$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Mon May 31 02:12:06 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> shutdown
ORA-01012: not logged on
SQL> startp mount
SP2-0734: unknown command beginning "startp mou..." - rest of line ignored.
SQL> conn / as sysdba
Connected.
SQL> shutdown
ASM diskgroups dismounted
ASM instance shutdown
SQL> startup mount
ASM instance started
Total System Global Area 130023424 bytes
Fixed Size                  2019032 bytes
Variable Size             102838568 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
-bash-3.2$ export ORACLE_SID=dbtest
-bash-3.2$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Mon May 31 02:13:30 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> exit
-bash-3.2$ cd /u01/app/oracle/admin/dbtest/pfile/
-bash-3.2$ ls -l
total 8
-rw-r----- 1 oracle oinstall 2442 May 27 23:07 init.ora.427201023913
-rw-r--r-- 1 oracle oinstall 1406 May 31 01:44 sqlnet.log
-bash-3.2$ pwd
/u01/app/oracle/admin/dbtest/pfile
-bash-3.2$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Mon May 31 02:14:00 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> exit
-bash-3.2$ sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Mon May 31 02:14:09 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> startup pfile="/u01/app/oracle/admin/dbtest/pfile/init.ora.427201023913';
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL>
-bash-3.2$ ps -ef|grep ora
root      5501 5483 0 00:32 ?        00:00:00 hald-addon-storage: polling /dev/hdc
root      6333     1 0 00:32 ?        00:00:00 /bin/su -l oracle -c sh -c 'cd /u01/app/oracle/product/10.1.0/db_1/log/localhost/cssd; ulimit -c unlimited; exec /u01/app/oracle/product/10.1.0/db_1/bin/ocssd '
oracle    6527 6333 0 00:33 ?        00:00:00 /u01/app/oracle/product/10.1.0/db_1/bin/ocssd.bin
oracle    6849     1 0 00:49 ?        00:00:00 /u01/app/oracle/product/10.1.0/db_1/bin/tnslsnr LISTENER -inherit
root      7637 7617 0 01:53 pts/2    00:00:00 su - oracle
oracle    7638 7637 0 01:53 pts/2    00:00:00 -bash
root      7751 6763 0 02:11 pts/1    00:00:00 su - oracle
oracle    7752 7751 0 02:11 pts/1    00:00:00 -bash
oracle    7773     1 0 02:12 ?        00:00:00 oracledbtest (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
oracle    7777     1 0 02:13 ?        00:00:00 asm_pmon_dbtest
oracle    7779     1 0 02:13 ?        00:00:00 asm_psp0_dbtest
oracle    7781     1 0 02:13 ?        00:00:00 asm_mman_dbtest
oracle    7783     1 0 02:13 ?        00:00:00 asm_dbw0_dbtest
oracle    7785     1 0 02:13 ?        00:00:00 asm_lgwr_dbtest
oracle    7787     1 0 02:13 ?        00:00:00 asm_ckpt_dbtest
oracle    7789     1 0 02:13 ?        00:00:00 asm_smon_dbtest
oracle    7791     1 0 02:13 ?        00:00:00 asm_rbal_dbtest
oracle    7793     1 0 02:13 ?        00:00:00 asm_gmon_dbtest
oracle    7805 7752 0 02:15 pts/1    00:00:00 ps -ef
oracle    7806 7752 0 02:15 pts/1    00:00:00 grep ora
-bash-3.2$
{code}
so anybody can help me how to start the oracle database....

-bash-3.2$ sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Mon May 31 02:26:11 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> show parameter instance
NAME                                 TYPE        VALUE
active_instance_count                integer
cluster_database_instances           integer     1
instance_groups                      string
instance_name                        string      dbtest
instance_number                      integer     0
instance_type                        string      asm
open_links_per_instance              integer     4
parallel_instance_group              string
parallel_server_instances            integer     1
SQL>
-bash-3.2$ sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Mon May 31 02:26:11 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> show paramete instance_name
SP2-0158: unknown SHOW option "paramete"
instance "local"
SP2-0158: unknown SHOW option "_name"
SQL> show parameter instance
NAME                                 TYPE        VALUE
active_instance_count                integer
cluster_database_instances           integer     1
instance_groups                      string
instance_name                        string      dbtest
instance_number                      integer     0
instance_type                        string      asm
open_links_per_instance              integer     4
parallel_instance_group              string
parallel_server_instances            integer     1
SQL>
-bash-3.2$ ps -ef|grep pmon
oracle    7777     1 0 02:13 ?        00:00:00 asm_pmon_dbtest
oracle    7851 7752 0 02:32 pts/1    00:00:00 grep pmon
-bash-3.2$
-bash-3.2$

ASM instance wont mount diskgroup..

HI, I have 10g release 2 installed on CENTOS 4.4, I use ASM striping with with 4 raw disks.
I had a system crash due to a power failure and now the the ASM wont mount the diskgroup.
export $ORACLE_HOME=+ASM
SQL> startup mount;
ASM instance started
Total System Global Area 130023424 bytes
Fixed Size 2071000 bytes
Variable Size 102786600 bytes
ASM Cache 25165824 bytes
ORA-15110: no diskgroups mounted
SQL> alter diskgroup RESEARCH1 mount;
alter diskgroup RESEARCH1 mount
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup
"RESEARCH1"
now when I use /etc/init.d/oracleasm listdisks I can see all my disks:
DISK1
DISK2
DISK3
DISK4
then i tried to change asm_diskstring to point the mounting point, here is my ora file:
*.asm_diskgroups='RESEARCH1'
+ASM.asm_diskgroups='RESEARCH1' #Manual Dismount
*.asm_diskstring='/dev/oracleasm/disks'
*.background_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/bdump'
*.core_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/cdump'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'
*.user_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/udump'
any ideas?
Thanks
Assaf

Hi,
by oracleasm lib utility you can configure as below
# /etc/init.d/oracleasm configure
Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Scanning system for ASM disks: [ OK ]
# /etc/init.d/oracleasm enable
Thanks

Oracle restart and ASM

Hi,
I have noticed following 'strange' behaviour of Oracle Restart and ASM.
starting position:
-bash-3.2 $ crsctl status resource -t
NAME           TARGET STATE        SERVER                   STATE_DETAILS
Local Resources
ora.DATA.dg
               ONLINE ONLINE       oracle-restart
ora.LISTENERASM.lsnr
               ONLINE ONLINE       oracle-restart
ora.asm
               ONLINE ONLINE       oracle-restart           Started
Cluster Resources
ora.cssd
      1        ONLINE ONLINE       oracle-restart
ora.diskmon
      1        ONLINE ONLINE       oracle-restartstep 1:
-bash-3.2 $ srvctl stop asm
-bash-3.2 $ srvctl stop diskgroup -g data
-bash-3.2 $ srvctl disable diskgroup -g datastep 2:
via sqlplus start ASM instance
SQL> startup
ASM instance started
Total System Global Area 283930624 bytes
Fixed Size                  2212656 bytes
Variable Size             256552144 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted
ASM diskgroups volume enabled
SQL> select * from v$asm_diskgroup;
GROUP_NUMBER NAME                           SECTOR_SIZE BLOCK_SIZE
ALLOCATION_UNIT_SIZE STATE       TYPE     TOTAL_MB    FREE_MB HOT_USED_MB
COLD_USED_MB REQUIRED_MIRROR_FREE_MB USABLE_FILE_MB OFFLINE_DISKS
COMPATIBILITY
DATABASE_COMPATIBILITY                                       V
           1 DATA                                   512       4096
             1048576 MOUNTED     EXTERN      10236      10177           0
          59                       0          10177             0
GROUP_NUMBER NAME                           SECTOR_SIZE BLOCK_SIZE
ALLOCATION_UNIT_SIZE STATE       TYPE     TOTAL_MB    FREE_MB HOT_USED_MB
COLD_USED_MB REQUIRED_MIRROR_FREE_MB USABLE_FILE_MB OFFLINE_DISKS
COMPATIBILITY
DATABASE_COMPATIBILITY                                       V
11.2.0.0.0
10.1.0.0.0                                                   N
-bash-3.2 $ crsctl status resource -t
NAME           TARGET STATE        SERVER                   STATE_DETAILS
Local Resources
ora.DATA.dg
               OFFLINE OFFLINE      oracle-restart          <== funny !!!
ora.LISTENERASM.lsnr
               ONLINE ONLINE       oracle-restart
ora.asm
               ONLINE ONLINE       oracle-restart           Started
Cluster Resources
ora.cssd
      1        ONLINE ONLINE       oracle-restart
ora.diskmon
      1        ONLINE ONLINE       oracle-restartIs this behaviour a 'feature' or bug?
Anyone had similar experience?
thanks,
goran

Hi,
asm resource is depending on diskgroup resource ... if diskgroup res. is not available, crsctl status shows offline, I would expect asm should be also shown as 'offline' (and brought offline) as they are dependent.
What is the point of managing resources via srvctl when it doesn't take care of dependencies? For me it's wrong.ora.asm : is ASM Instance
ora.*.dg : is Diskgroup
ora.*.dg is dependent of ora.asm, not to the contrary.
I can have more than one diskgroup and want only one diskgroup disabled, so I need the ASM Instance (ora.asm) online.
Important:
If you shut down the database with SQL*Plus, Oracle Restart does not interpret this as a database failure and does not attempt to restart the database.
Similarly, if you shut down the Oracle ASM instance with SQL*Plus or ASMCMD, Oracle Restart does not attempt to restart it.
An important difference between starting a component with SRVCTL and starting it with SQL*Plus (or another utility) is the following:
When you start a component with SRVCTL, any components on which this component depends are automatically started first, and in the proper order.
When you start a component with SQL*Plus (or another utility), other components in the dependency chain are not automatically started; you must ensure that any components on which this component depends are started.
Oracle Restart also manages the weak dependency between database instances and the Oracle Net listener (the listener): When a database instance is started, Oracle Restart attempts to start the listener. If the listener startup fails, then the database is still started. If the listener later fails, Oracle Restart does not shut down and restart any database instances.
It makes no sense Oracle Restart to shut down all environment (databases) because the listener down.
Regards,
Levi Pereira

Shrinking ASM disk

I just tried to resize an ASM disk and although the feedback was 'successful', there doesn't appear to have been any change.
I was attempting to shrink disk DATA_0001 from 200G to 100G. Am I missing something obvious?
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          0                      /dev/iscsi/rman11                   20489          0          0
          0                      /dev/iscsi/rmanB11                 102398          0          0
          0                      /dev/iscsi/rman1                    20490          0          0
          0                      /dev/iscsi/vote3                      300          0          0
          0                      /dev/iscsi/vote1                      300          0          0
          0                      /dev/iscsi/rmanP11                 204805          0          0
          0                      /dev/iscsi/vote2                      300          0          0
          0                      /dev/iscsi/rmanP1                  204810          0          0
          0                      /dev/iscsi/rmanB1                  102405          0          0
          1 DATA_0000            /dev/iscsi/db1                      10245      10245      10109
          2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
          1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202297
13 rows selected.
SQL> alter diskgroup data resize disk 'data_0001' size 100g;
Diskgroup altered.
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          0                      /dev/iscsi/rman11                   20489          0          0
          0                      /dev/iscsi/rmanB11                 102398          0          0
          0                      /dev/iscsi/rman1                    20490          0          0
          0                      /dev/iscsi/vote3                      300          0          0
          0                      /dev/iscsi/vote1                      300          0          0
          0                      /dev/iscsi/rmanP11                 204805          0          0
          0                      /dev/iscsi/vote2                      300          0          0
          0                      /dev/iscsi/rmanP1                  204810          0          0
          0                      /dev/iscsi/rmanB1                  102405          0          0
          1 DATA_0000            /dev/iscsi/db1                      10245      10245      10004
          2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
          1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202402
13 rows selected.The free_mb seems to have increased, but otherwise I can't see the effect of my change. Maybe I'm looking in the wrong place??
I tried restarting the ASM instance but it made no difference.
After resizing the disk in ASM I shrunk the disk volume in our storage array. ASM was of course down at the time.
When I attempted to restart ASM I saw this ...
SQL> startup
ASM instance started
Total System Global Area 283930624 bytes
Fixed Size                  2158992 bytes
Variable Size             256605808 bytes
ASM Cache                  25165824 bytes
ORA-15032: not all alterations performed
ORA-15036: disk '/dev/iscsi/dbR1' is truncatedNone of my diskgroups are mounted ...
SQL> select group_number, name, state from v$asm_diskgroup;
GROUP_NUMBER NAME            STATE
          0 DATA            DISMOUNTED
          0 FRA             DISMOUNTEDHere's the messages from the ASM instance alert log ...
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: cache registered group DATA number=1 incarn=0x5f5e3343
NOTE: cache began mount (not first) of group DATA number=1 incarn=0x5f5e3343
NOTE: cache registered group FRA number=2 incarn=0x5f5e3344
NOTE: cache began mount (not first) of group FRA number=2 incarn=0x5f5e3344
WARNING::ASMLIB library not found. See trace file for details.
NOTE: Assigning number (1,0) to disk (/dev/iscsi/db1)
NOTE: cache dismounting group 1/0x5F5E3343 (DATA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 1/0x5F5E3343 (DATA)
NOTE: cache ending mount (fail) of group DATA number=1 incarn=0x5f5e3343
kfdp_dismount(): 1
kfdp_dismountBg(): 1
NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
ERROR: diskgroup DATA was not mounted
NOTE: Assigning number (2,1) to disk (/dev/iscsi/flshbkR1)
NOTE: Assigning number (2,0) to disk (/dev/iscsi/flshbk1)
NOTE: cache dismounting group 2/0x5F5E3344 (FRA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 2/0x5F5E3344 (FRA)
NOTE: cache ending mount (fail) of group FRA number=2
incarn=0x5f5e3344
kfdp_dismount(): 2
kfdp_dismountBg(): 2
NOTE: De-assigning number (2,0) from disk (/dev/iscsi/flshbk1)
NOTE: De-assigning number (2,1) from disk (/dev/iscsi/flshbkR1)
ERROR: diskgroup FRA was not mounted
ORA-15032: not all alterations performed
ORA-15036: disk '/dev/iscsi/dbR1' is truncated
ERROR: ALTER DISKGROUP ALL MOUNTAny clues?
Thanks,
Steve

Thanks Markus. I changed the size of the volume back to the original and was able to restart the ASM instances on both nodes. I confirmed it saw the size as the original 200G.
I then shut down ASM on the second node and issued the alter on the first node. Here's what happened ...
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk order by name;
GROUP_NUMBER NAME       PATH                                OS_MB   TOTAL_MB    FREE_MB
           1 DATA_0000 /dev/iscsi/db1                      10245      10245      10004
           1 DATA_0001 /dev/iscsi/dbR1                    204810     204810     202402
           2 FRA_0000   /dev/iscsi/flshbk1                  20490      20490      20465
           2 FRA_0001   /dev/iscsi/flshbkR1                409605     409605     409262
           0            /dev/iscsi/rman1                    20490          0          0
           0            /dev/iscsi/rmanP1                  204810          0          0
           0            /dev/iscsi/rmanB1                  102405          0          0
           0            /dev/iscsi/rmanP11                 204805          0          0
           0            /dev/iscsi/rmanB11                 102398          0          0
           0            /dev/iscsi/rman11                   20489          0          0
10 rows selected.
SQL> alter diskgroup data resize disk 'data_0001' size 100g;
alter diskgroup data resize disk 'data_0001' size 100g
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15066: offlining disk "DATA_0001" may result in a data lossHere's the details from the alert log ...
SQL> alter diskgroup data resize disk 'data_0001' size 100g
NOTE: requesting all-instance membership refresh for group=1
WARNING: cache read a corrupted block gn=1 dsk=1 blk=257 from disk 1
NOTE: a corrupted block was dumped to /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
ERROR: cache failed to read gn=1 dsk=1 blk=257 from disk(s): 1
ORA-15196: invalid ASM block header [kfc.c:9133] [endian_kfbh] [2147483649] [257] [0 != 1]
System State dumped to trace file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
NOTE: cache initiating offline of disk 1 group 1
WARNING: initiating offline of disk 1.3688884620 (DATA_0001) with mask 0x7e
NOTE: initiating PST update: grp = 1, dsk = 1, mode = 0x15
kfdp_updateDsk(): 14
Thu May 07 15:45:38 2009
kfdp_updateDskBg(): 14
ERROR: too many offline disks in PST (grp 1)
Thu May 07 15:45:38 2009
NOTE: halting all I/Os to diskgroup DATA
Thu May 07 15:45:38 2009
SQL> alter diskgroup DATA dismount force
NOTE: active pin found: 0x0x6ddf6060
NOTE: active pin found: 0x0x6ddf6168
ERROR: ORA-15130 signalled during resize of diskgroup DATA
Thu May 07 15:45:38 2009
NOTE: membership refresh pending for group 1/0xdc0f1999 (DATA)
kfdp_query(): 15
kfdp_queryBg(): 15
SUCCESS: refreshed membership for 1/0xdc0f1999 (DATA)
ERROR: ORA-15130 thrown in RBAL for group number 1
Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
ORA-15130: diskgroup "DATA" is being dismounted
Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15066: offlining disk "DATA_0001" may result in a data loss
ERROR: alter diskgroup data resize disk 'data_0001' size 100g
NOTE: cache dismounting group 1/0xDC0F1999 (DATA)
NOTE: dbwr not being msg'd to dismount
Thu May 07 15:45:41 2009
Dirty detach reconfiguration started (old inc 6, new inc 6)
List of nodes:
0
Global Resource Directory partially frozen for dirty detach
* dirty detach - domain 1 invalid = TRUE
10 GCS resources traversed, 0 cancelled
Dirty Detach Reconfiguration complete
Thu May 07 15:45:41 2009
freeing rdom 1
Thu May 07 15:45:41 2009
WARNING: dirty detached from domain 1
NOTE: cache dismounted group 1/0xDC0F1999 (DATA)
kfdp_dismount(): 16
kfdp_dismountBg(): 16
NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
NOTE: De-assigning number (1,1) from disk (/dev/iscsi/dbR1)
SUCCESS: diskgroup DATA was dismounted
SUCCESS: alter diskgroup DATA dismount force
ERROR: PST-initiated MANDATORY DISMOUNT of group DATA
Thu May 07 15:46:06 2009
SQL> alter diskgroup data resize disk 'data_0001' size 100g
ORA-15032: not all alterations performed
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ERROR: alter diskgroup data resize disk 'data_0001' size 100gLooks like my earlier attempt has indeed screwed up something so even though the instances start OK and mount the diskgroup, I think there's a fair chance something would go splat sooner rather than later.
As this is a test database, I think I'll cut my losses and rebuild the diskgroup then restore it from backup. I'm assuming the effort involved in correcting the corruption will be greater than rebuilding and restoring.
Do you agree with this?
Then I'll try again and hopefully get it right.
Thanks for your help!!!
Steve

Drop ASM instance.

Hi,
My OCR got corrupted and I am not able to recover as I don't have backup of that. Because of this, CRS daemon is not coming up and this leads me to clean up this cluster and build it again. I am not much worried as this is my second development env.
I want to drop the disk groups but I am not able to do because those are not being mounted.
SQL> select name from v$asm_diskgroup;
NAME
DG1
RECOVERYDEST
SQL> drop diskgroup DG1 including contents;
drop diskgroup DG1 including contents
ERROR at line 1:
ORA-15039: diskgroup not dropped
ORA-15001: diskgroup "DG1" does not exist or is not mounted
If I do remove ASM using DBCA, will all diskgroups be removed or do I need to perform any cleanup?
Thanks,

Thanks Vishwa,
Here is the output,
$ ps -aef|grep d.bin
oracle 5234 5215 0 18:37 ? 00:00:00 /u01/app/oracle/product/10.2.0/crs_1/bin/evmd.bin
oracle 5330 5329 0 18:37 ? 00:00:00 /u01/app/oracle/product/10.2.0/crs_1/bin/ocssd.bin
oracle 7646 7191 0 18:39 pts/1 00:00:00 grep d.bin
$ crs_stat -t
CRS-0184: Cannot communicate with the CRS daemon.
When I do mount the DG1 diskgroup I am getting below error on all nodes,
SQL> startup
ASM instance started
Total System Global Area 92274688 bytes
Fixed Size 1217884 bytes
Variable Size 65890980 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DG1" is being dismounted
ORA-15066: offlining disk "DG1_0000" may result in a data loss
SQL> alter diskgroup DG1 mount;
alter diskgroup DG1 mount
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DG1" is being dismounted
ORA-15066: offlining disk "DG1_0000" may result in a data loss
Ashok: As far as I know, OCR stores the information about Oracle clusterware controls and if it is not up then clusterware controls won't come up. My crsd daemon is not comming up (even though If I try manually to bring it up) and this daemon is directly liked up with OCR. Does it mean that if this daemon is not up then it won't allow O/S to access OCR? Even If I try to take backup using ocrconfig -export ..it throws an error.
As I don't have backup of OCR, I need to drop the database and uninstall just Oracle clusterware and re-install and create the database. I want to clean up the disk headers as I want to use those to build diskgroup again, do you guys have any idea, how to do that?
Do let me know if you have different view on this.
Thanks.

Oracle RAC 10g: ASM can't start in one node.

Hi all,
I succesfully installed RAC in Enterprise Linux. Node1 starts correctly (ASM and DB) but Node2 doesn´t. This is the error in Node2 when I try to startup de ASM instance:
SQL> startup
ASM instance started
Total System Global Area 92274688 bytes
Fixed Size 1217884 bytes
Variable Size 65890980 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DG1" is being dismounted
ORA-15066: offlining disk "VOL1" may result in a data loss
Any ideas?
Thanks!

Hi, you will must check the configuration of your shared storage, maybe the problem is there, you can verify the some log information in the clusterware layer, and you can find more information in the bdump directory of ASM Instance.
Please paste here the alert logfile of ASM Instance.
Luck.
Have a good day.

ORA-15063: ASM discovered an insufficient number of disks for diskgroup

Hello DBAs,
I have encountered this problem. I am using storage vendor snapshot capability. On my first node, I have 2 disks for ASM diskgroups. ORCL:DATA belongs to DATA diskgroup and ORCL:FLASH belongs to FLASH diskgroup. After making the snapshots of these two disks, I mapped them to my second host which already has ASM instance. I ran /etc/init.d/oracleasm scandisk and listdisks I see two disks. But when I start up ASM instance I get this error:
SQL> startup
ASM instance started
Total System Global Area 130023424 bytes
Fixed Size 2019032 bytes
Variable Size 102838568 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "FLASH"
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"
Of course, I have the asm_diskstring and asm_diskgroups parameter set in my init+ASM.ora file. The ASM version is identical across both hosts. I guess my question would be, is it possible to do this? Do I need to re-create the ASM disks using /etc/init.d/oracleasm? Any help is much appreciated.
Thanks,
TD

What is your configuration?
If you have AIX and EMC san, then refer to this metalink note: 467702.1
In my case, it was HP-UX and HP san EVA8200. But our problem was two different disks were presented to the two nodes, with same names by the unix admin/san admin guys.
Before they could figure out the problem, I had done a lot of research for few days to figure this out. Another problem I noticed in some cases was improper permissions. Either the db software owner didn't have permissions to the asm disks, or if the owner of both software was same, then the actual permissions/ownership of the shared raw devices was different on the two nodes.
Hope this helps. And I will appreciate once you fix the problem if you can also update this forum with your solution. That will help the community in future.
Thanks

ASM instance startup problem..

Hi,
SQL> startup
ASM instance started
Total System Global Area 79691776 bytes
Fixed Size 1289004 bytes
Variable Size 53236948 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"
DB Version=10.2.0.2.0
Os = windows xp
Thanks,

ORA-15063:     ASM discovered an insufficient number of disks for diskgroup "string"
Cause:     ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation.
Action:     Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.

Oracle ASM Member disks online & offline options are disable

Hi Guru's
OS:- RHEL5
DB :- 11GR2
I am trying to offline the members of a disk group using EM but what i found that the members are listed there but online and offline options are inactive there. Can you please tell me why it is so . Even after selecting the member the options are still inactive
Thanks in advance

vk82 wrote:
Actually now what happens is as the options are disabled i thought i added another physical disk by powering off the machine with properly shutdown the db and ASM instance. But when i try to restart the db i am getting the error as :-
ERROR at line 1:
ORA-01565: error in identifying file '+DATA/orcl/spfileorcl.ora'
ORA-17503: ksfdopn:2 Failed to open file +DATA/orcl/spfileorcl.ora
ORA-15056: additional error message
ORA-17503: ksfdopn:DGOpenFile05 Failed to open file +DATA/orcl/spfileorcl.ora
ORA-17503: ksfdopn:2 Failed to open file +DATA/orcl/spfileorcl.ora
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-06512: at line 4
ASM Instance is started fine
SQL> startup
ASM instance started
Total System Global Area 284565504 bytes
Fixed Size                  1336036 bytes
Variable Size             258063644 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted
SQL>
Please help me over the same
Sorry, I read error again:
ORA-15001: diskgroup "DATA" does not exist or is not mounted
select name from v$asm_diskgroup:
Regards
Mahir

ASM AMM questions

Hi,
I now have the strangest behaviour here. That is, it puzzles me.
I have an Oracle 11.1.0.7 ASM single instance on an IBM AIX 5.3 TL 06 server
There is no database configured yet to use this ASM instance as storage.
What I see here is that any setting of SGA_MAX_SIZE less than 90M results in an error. SGA_MAX_SIZE of 90M is the absolute minimum on this server.
Now the "problem":
On normal - i.e. non-ASM - instances as far as I know sga_max_size is the absolute maximum whereas sga_target can be tuned up to this size
On my ASM instance whenever I only set sga_max_size=90M the instance starts up as expected:
SQL> startup nomount
ASM instance started
Total System Global Area *96026624* bytes
Fixed Size 2151248 bytes
Variable Size 68709552 bytes
ASM Cache 25165824 bytes
SQL>
Now when I set SGA_TARGET also to the same value something strange happens.
First only in memory:
SQL> alter system set sga_target=90M scope=memory;
System altered.
SQL> show sga
Total System Global Area *96026624* bytes
Fixed Size 2151248 bytes
Variable Size 68709552 bytes
ASM Cache 25165824 bytes
SQL>
Seems OK, doesn't it ?
Now in the SPFILE:
SQL> alter system set sga_target=90M scope=spfile;
System altered.
SQL> shutdown immediate
ORA-15100: invalid or missing diskgroup name
ASM instance shutdown
SQL> startup nomount;
ASM instance started
Total System Global Area 162856960 bytes
Fixed Size 2151848 bytes
Variable Size 135539288 bytes
ASM Cache 25165824 bytes
Now why has the total SGA size increased to 156M.
It's even more strange when I remove the SGA_MAX_SIZE from the spfile and only set SGA_TARGET=90M. Then
SQL> startup nomount;
ASM instance started
Total System Global Area 283930624 bytes
Fixed Size 2153056 bytes
Variable Size 256611744 bytes
ASM Cache 25165824 bytes
SQL>
Please note: Removing sga_max_size from the spfile is done by recreating it from an pfile
Anyone a suggestion in how to set the AMM parameters for an ASM instance so it behaves like expected, or at least like a "normal" database?
Thanks

The answer is quite simple - ASM currently does not employ the Oracle Database 10g Automatic Memory Management feature. There was significant optimizations done in 11gR1 with respect to memory management, thus there is no
need to set the SGA parameters in 11gR1. ASM now leverages the MEMORY_TARGET parameter and
the default of 256MB is more than enough for the ASM instance. The management of (ASM) processes
was also optimized, therefore the processes parameter also does not need to be set in 11gR1.
You can reffer to metalink note 265633.1 - there is a pdf document and that describes what should be set and what is not supported.
ASM is not a "normal" database.
Edited by: Laura Gaigala on May 6, 2009 4:27 PM

ASM discovered an insufficient number of disks for diskgroup

Running RH4U3 and Oracle 10gr2
Every time I reboot my system, the minor number changed and i can't startup the ASM instance. Does any one know why this is happening? Any advise would be appreciated.
the minor number was 4 and 5, now after reboot i got::
# ls -l /dev/oracleasm/disks
total 0
brw-rw---- 1 ora dba 253, 4 Feb 21 10:10 VOL1
brw-rw---- 1 ora dba 8, 65 Feb 21 10:10 VOL2
I can't startup my ASM instance:
$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Feb 21 10:13:03 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ASM instance started
Total System Global Area 83886080 bytes
Fixed Size 1217836 bytes
Variable Size 57502420 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "OARCH"
y ASM instance:

I have no problem reading the disks.
$ dd if=/dev/oracleasm/disks/VOL1 of=/dev/null
485336+0 records in
485336+0 records out
$ dd if=/dev/oracleasm/disks/VOL2 of=/dev/null
741760+0 records in
741760+0 records out

Unable to Drop ASM Disk Group

Hi,
working on Oracle 11gR2, (Solaris).
unable to drop diskgroup, need to deinstall asm setup manually insted of running with deinstall tool.
sqlplus / as sysasm
SQL> startup pfile='/u01/grid/oracle/product/11.2.0/asm_1/dbs/init+ASM.ora';
ASM instance started
Total System Global Area 283930624 bytes
Fixed Size                  2210328 bytes
Variable Size             256554472 bytes
ASM Cache                  25165824 bytes
ORA-15110: no diskgroups mounted
SQL> alter diskgroup fra mount;
Diskgroup altered.
SQL> alter diskgroup data mount;
Diskgroup altered.
SQL> drop diskgroup FRA INCLUDING CONTENTS;
drop diskgroup FRA INCLUDING CONTENTS
ERROR at line 1:
ORA-15039: diskgroup not dropped
ORA-29786: SIHA attribute GET failed with error [Attribute 'SPFILE' sts[200]
lsts[0]]
SQL> DROP DISKGROUP DATA INCLUDING CONTENTS;
DROP DISKGROUP DATA INCLUDING CONTENTS
ERROR at line 1:
ORA-15039: diskgroup not dropped
ORA-29786: SIHA attribute GET failed with error [Attribute 'SPFILE' sts[200]
lsts[0]]

Sachin B wrote:
Hi,
working on Oracle 11gR2, (Solaris).
unable to drop diskgroup, need to deinstall asm setup manually insted of running with deinstall tool.
sqlplus / as sysasm
SQL> startup pfile='/u01/grid/oracle/product/11.2.0/asm_1/dbs/init+ASM.ora';
ASM instance started
Total System Global Area 283930624 bytes
Fixed Size                  2210328 bytes
Variable Size             256554472 bytes
ASM Cache                  25165824 bytes
ORA-15110: no diskgroups mounted
SQL> alter diskgroup fra mount;
Diskgroup altered.
SQL> alter diskgroup data mount;
Diskgroup altered.
SQL> drop diskgroup FRA INCLUDING CONTENTS;
drop diskgroup FRA INCLUDING CONTENTS
ERROR at line 1:
ORA-15039: diskgroup not dropped
ORA-29786: SIHA attribute GET failed with error [Attribute 'SPFILE' sts[200]
lsts[0]]
SQL> DROP DISKGROUP DATA INCLUDING CONTENTS;
DROP DISKGROUP DATA INCLUDING CONTENTS
ERROR at line 1:
ORA-15039: diskgroup not dropped
ORA-29786: SIHA attribute GET failed with error [Attribute 'SPFILE' sts[200]
lsts[0]]
Did you create ASM instance manually? If yes, then follow MOS DOC ID: 976075.1

ASM cache....

Similar Messages

Maybe you are looking for