Home
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: fetch across commit

Steve Rospo

2004-12-03

Replies:

[Appolgies if this gets double posted, I got an "overquote" bounce. ]

I haven't tried a "where current of" or the "order by" workarounds, but I
usually just push the data into some sort of PL/SQL collection. It's got
the same transactional semantics with no (real) risk of 1555s with only a
minor code tweak. Even if there wasn't a commit in the loop, this might
be a good technique to prevent the RBSs from getting enormous if the inner
part of the loop took an *extremely* long time.

If you do a bulk collect, you get the added benefit of doing a single
round trip, rather than a row by row fetch. (I think 9i or 10g does a
transparent optimization here, turning your row by row fetch into a bulk
under the covers)

S-


>
> On Tue, 30 Nov 2004, Jared Still wrote:
>
> > Hi all,
> >
> > Have any of you considered using a 'where current of' update
> > cursor to work around this?
> >
> > I've used it in the past to avoid both ora-1555 and 'fetch across commit'.
> >

--
http://www.freelists.org/webpage/oracle-l