Booking An Order Says Not Eligible For Booking, Check Tablespace Status
(Doc ID 330066.1)
Last updated on JUNE 07, 2021
Applies to:Oracle Order Management - Version 11.5.9 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 09-Jan-2011***
***Checked for relevance on 21-Aug-2012***
Run the select statement:
SQL> select tablespace_name,status from dba_tablespaces;
Look for any Tablespace name which has a status of "OFFLINE"
Then run the select statement:
SQL> select file#,name,status,enabled from v$datafile
Look for the data files which also show as "OFFLINE".
You will see the data files are on the tablespace names which are also "OFFLINE" from the first select.
Within these files, there will be one which was the file shown in the debug log which failed.
Per <Document 183327.1> on the error ORA-00376, if a tablespace reaches max extents and cannot extend further, or if there is a rollback in the Standard Report Writer on the database, a tablespace may be disconnected suddenly.
In this case, we really don't know why the Tablespace went OFF-LINE, only that it did.
This was found by running the SQL above for select tablespace_name, status from dba_tablespaces;
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document