Re: ora 19502 with adding datafile

yls177_at_hotmail.com (yls177) wrote in message news:<c06e4d68.0406142036.5c3f3473_at_posting.google.com>...
> joel-garry_at_home.com (Joel Garry) wrote in message news:<91884734.0406141443.62fdcdc0_at_posting.google.com>...
> > yls177_at_hotmail.com (yls177) wrote in message news:<c06e4d68.0406132103.5571da1a_at_posting.google.com>...
> > > i wanted to add a new datafile. my current free space value is
> > > 3790940K. i started with 3650000K but i got the below messages
> > >
> > >
> > > ORA-19502: write error on file
> > > "/oracle/SID/mydata/btabd_56/btabd.data56",
> > > blockno 450561 (blocksize=8192)
> > > ORA-27063: skgfospo: number of bytes read/written is
> > > incorrect
> > > IBM AIX RISC System/6000 Error: 28: No space left on device
> > > Additional information: -1
> > > Additional information: 1048576
> > > ORA-19502: write error on file
> > > "/oracle/SID/mydata/btabd_56/btabd.data56", blockno 450433
> > > (blocksize=8192)
> > > ORA-27063: skgfospo: number of bytes read/written is
> > > incorrect
> > > IBM AIX RISC System/6000 Error: 28: No space lef
> > >
> > > afterwhich i changed to 3500000Kand everything is fine.
> > >
> > > i suspect that some space is needed for the block headers.. please
> > > confirm.
> > >
> > > thanks
> >
> > Free space may not be accurate, for several reasons including
> > underlying fragmentation, files deleted but not closed, timing issues,
> > soft v. hard limits, some unix only let superuser use last 10%, wasted
> > space at end of files, broken inodes, etc. YMMV.
> > K is not 1000.
> > Conversion of K or M may not be as you expect - if you are using OEM,
> > show SQL.
> > Multiply 450433 * 8192.
> > http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76965/c02block.htm#2599
> > http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=109630.1
> >
> > If you are trying to use every last bit on a unix filesystem, you may
> > be over-administrating.
> >
> > jg
>
>
>
> so the understanding is not to squeeze out of the filesystem free
> space due to the space required by the operating system, database
> inherent attributes..?

Not really, the point is just to either leave a bit of slop space or make sure you understand the tools, which tools may be misleading at times. You could simply keep manually expanding until you can't anymore, but only do that if there is nothing else on the device than data files that you control. On some older unix, system administrators would start worrying when devices get to 90 or 95% full, but I don't think that applies to a modern AIX data-only volume that isn't normally creating or deleting files.

jg

--
@home.com is bogus.
http://www.dennis-carpenter.com/news/EplylAulyFmjZrkItp.php