Ora-01119

[bang_dba]

Hi,

I am having problem creating tablespace on the 1 logical RAW partion.
Whereas on 2nd partion, it works. I guess the first one is Extended and second is Linux. What is the reason ?

My layout is as follows:

# fdisk -l /dev/sdc

Disk /dev/sdc: 106 MB, 106954752 bytes
64 heads, 32 sectors/track, 102 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 30 30704 5 Extended
/dev/sdc2 31 41 11264 83 Linux



[root@localhost dev]#


SQL> create tablespace Dat01 datafile '/dev/sdc1';
create tablespace Dat01 datafile '/dev/sdc1'
*
ERROR at line 1:
ORA-01119: error in creating database file '/dev/sdc1'
ORA-27044: unable to write the header block of file
Additional information: 7


SQL> create tablespace Dat02 datafile '/dev/sdc2';

Tablespace created.

SQL>

[LKBrwn_DBA]

1) You should not (cannot) mix different disk format(s) for database files.
2) You cannot directly create a tablespace on a raw disk, you need to use ASM or some kind of "DirectIO" option.
3) Again: DO NOT mix filesystem formats (types) for database files.

[bang_dba]

Hi,

What i am doing is, i have added few disks to my enterprise linux 4 box viz., sda,sdb,sdc etc.

After this i am using fdisk to create partition on these disks.

fdisk /dev/sda..... etc.....

Now i am creating tablespaces on these raw devices.

Is this not recommended ? Is this not correct ?

Of course, I know that future release will not support raw, etc.....
I am doing this for some benchmarking. I am using Oracle 10.2

[PAVB]

I know that future release will not support raw

really?... do tell please.

[sunidba]

really?... do tell please.

Note:578455.1

[LKBrwn_DBA]

Note:578455.1
...
Customers who create a new 11.2 database will need to store their database files in either ASM, a file system, or on an NFS file...

That is why you need to either "cook" (format) the partitions or use ASM.
Anyway you do it you still CANNOT mix file formats for database files.