| Extension of datafile in ASM [message #612341] |
Wed, 16 April 2014 04:51  |
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
|
Senior Member |
|
|
Dear All,
Datafiles are stored in ASM. So datafiles are having its own nomenclatures. Bi-mistake, one of the datafile is created on the same path as mentioned below -
create bigfile tablespace bi datafile 'E:\APP\ADMINISTRATOR\ORADATA\TREGTST1\bi01.dbf' size 100m autoextend on next 12M extent management local segment space management auto;
Now, my concerned is, whether there will be any impact on this datafiles? Will it use the benefit of ASM (like - mirroring,etc)
Waiting for your kind response...
Regards,
Ashish
|
|
|
|
|
|
|
|
| Re: Extension of datafile in ASM [message #612375 is a reply to message #612374] |
Thu, 17 April 2014 03:33  |
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
|
Senior Member |
|
|
Dear @all,
Apologize !!!
Tablespace is created on the below path but name is "bi01.dbf".
create bigfile tablespace bi datafile '+DATADG1/lvgiprod/datafile/hlthchk01.dbf/bi01.dbf' size 100m autoextend on next 12M extent management local segment space management auto;
On ASM, script should be like this
create bigfile tablespace bi;
Now, whether created tablespace will be benefited by ASM? Though, File name is by OMF
Regards,
Ashish Kumar Mahanta
[Updated on: Thu, 17 April 2014 03:44] Report message to a moderator |
|
|
|
|
|
|
|
| Re: Extension of datafile in ASM [message #612389 is a reply to message #612374] |
Thu, 17 April 2014 07:46 |
 |
EdStevens
Messages: 1376
Registered: September 2013
|
Senior Member |
|
|
vslabs wrote on Thu, 17 April 2014 03:03Not a good idea to mix datafiles of a database across local cooked filesystems and ASM.
It negates a lot of the advantages of ASM by having a local file on a cooked filesystem as a datafile - like striping, like redundancy, like ability to perform storage management without database downtime, etc.
That local file must be removed from the database asap.
And the DBA(s) need to realise that managing tablespaces means NOT specifying a filename - and instead using db_create_file_dest as target for Oracle to create an OFA compliant directory structure and filename.
True, not having the file under ASM negates the advantages of ASM --- for that particular file.
But it does not follow that "file must be removed from the database asap". Oracle is perfectly happy to use that file. Yes, I'd recommend getting it moved, but the urgency implied by "asap" is misplaced.
In fact, I was recently out for several weeks of medical leave and in my absence my backfill created a data file on the FS instead of ASM. They ran like that for over a month before I was able to take any "corrective" action.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
