Hmmm. Doesn't look so simple to me. I dislike the ORA-27059 error. I
suspect you have set your datafile in AUTOEXTEND mode (bad idea ! bad
idea !) and that you have hit the 2 Gb limit or any limit on file size
you have (log on as Oracle and try ulimit -a; file size limit is likely
to be close to what you have). Adding a new datafile to the tablespace
would have solved the problem in this case.
--
Regards,
Stephane Faroult
email: sfaroult_at_oriolecorp.com
Oriole Corporation
Voice: +44 (0) 7050-696-269
Fax: +44 (0) 7050-696-449
Performance Tools & Free Scripts
------------------------------------------------------------------
http://www.oriolecorp.com, designed by Oracle DBAs for Oracle DBAs
------------------------------------------------------------------
>
> Don't take this the wrong way, but you really need to do some reading on
> space management. There are numerous books that you could go buy to cover
> this topic, but since you should have the Oracle documentation, I would
> recommend starting there.
>
> Steve Boyd
>
> >From: Russell Fray <russf_at_u-net.net>
> >To: oracledba_at_lazydba.com
> >CC: oracle-l_at_fatcity.com
> >Subject: Req Failed - Error
> >Date: Fri, 12 May 2000 10:48:25 +0100 (BST)
> >
> >
> >Hi,
> >
> >We use Oracle 8 with OWAS 3 running our front end via a web browser. One
> >of our tables, "staff_log" (which is used to log all activity on the
> >database), was up to about 1.6million rows - suddenly all users received
> >the following error whilst trying to use the system:
> >
> >Request Failed
> >We were unable to process your request at this time.
> >Error occured while accessing
> > "/unetagent/plsql/websalesview.view_account"
> >at Fri May 12 10:30:44 2000
> >
> >OWS-05101: Execution failed due to Oracle error 1654
> >ORA-01654: unable to extend index OWS_LISTENER.STAFF_LOG_LOG_DATE by 12137
> >in tablespace UNETDB
> >ORA-27059: skgfrsz: could not reduce file size
> >SVR4 Error: 22: Invalid argument
> >Additional information: 1
> >ORA-27059: skgfrsz: could not reduce file size
> >SVR4 Error: 22: Invalid argument
> >Additional information: 1
> >
> >As it's a 24x7 database I truncated the staff_log table and recreated the
> >indexes and it was fine (it's only a log file so it wasn't major). Does
> >anybody have any ideas why it fell over? We have plenty of hard drive
> >space. There are some other tables which are just hitting over a million
> >rows (these are important ones which we can't truncate!) and I don't want
> >the same thing to happen...
> >
> >Any suggestions will be greatly appreciated.
> >
> >Regards,
> >Russ.
> >
> >--
> >U-NET Ltd (a VIA NET.WORKS company)
> >"Local Touch Global Reach"
> >Russell Fray | Mail : russ_at_u-net.net
> >Database Manager | Tel : 01925 484490
> >U-NET Ltd | Fax : 0845 330 8106
Received on Mon May 15 2000 - 08:45:23 CDT
