V$ASM_FILE reporting different size than RDBMS datafile (Doc ID 1560659.1)

Last updated on JUNE 11, 2013

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.

Symptoms

After a successful datafile resize from RDBMS database, the file on ASM side still reports the old size and space was not regained.

alter database datafile '+U01/nlvenwms/datafile/users.292.733852319' resize 5120M
ORA-19567 signalled during: alter database datafile '+U01/nlvenwms/datafile/users.292.733852319' resize 5120M
...

alter database datafile '+U01/nlvenwms/datafile/users.292.733852319' resize 5120M
Completed: alter database datafile '+U01/nlvenwms/datafile/users.292.733852319' resize 5120M

New datafile size at ASM should be 5G, but still shows the older size:

select * from v$asm_file; 

GROUP_NUMBER FILE_NUMBER COMPOUND_INDEX INCARNATION BLOCK_SIZE BLOCKS BYTES SPACE TYPE REDUND STRIPE CREATION_DATE MODIFICATION_DATE R PERMISSIONS USER_NUMBER USER_INCARNATION USERGROUP_NUMBER USERGROUP_INCARNATION PRIM MIRR HOT_READS HOT_WRITES HOT_BYTES_READ HOT_BYTES_WRITTEN COLD_READS COLD_WRITES COLD_BYTES_READ COLD_BYTES_WRITTEN
2 292 33554724 733852319 8192 3356161 27493670912 5.5032E+10 DATAFILE MIRROR COARSE 31-OCT-2010 15:51:59 10-JUN-2013 09:00:00 U rw-rw-rw- 0 0 0 0 COLD COLD 0 0 0 0 3929690 342086 2.1528E+11 5.1717E+10

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms