All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

Re: (no subject)

Jared Still



On Wed, 2004-06-02 at 01:26, Computer Centre - NIIPL wrote:
> Dear All,
> We are getting the following error during database export.
> ORA-1555 :- snapshot too old.
> How to assign a big RBS to the export session.

There are methods to deal with this.

If you are using a third party app, and downtime is not
available, fixing the app, as has been suggested already,
may not be possible.

One method is to create new rollback segments with a very
large tablespace, larger than you expect to need during
the duration of the export.

Assign a transaction to each rollback segment, and do not
commit it. This will force the rollback segs to extend
rather than wrap.

When done, drop the temp RBS, bring the old ones back online,
drop the temp RBS tablespace and data files.

This has worked very well for me in the past with very long
running SAP jobs ( couldn't fix the source code ).

Details may be found at ixora.com.au ( of course )


Please see the official ORACLE-L FAQ: http://www.orafaq.com
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html