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: Lag function problem was: Never ending activity in temp file

Edgar Chupit


I think it's because when you don't directly specify offset for lag
function Oracle has no information regarding to how many rows to store
in the windows. When you specify lag(x,3) it then knows than it have
to store only the three last rows, but when you specify lag(x,N) it
has to store in memory (or on disk) all the data.
For your particular query you can tune it, by specifying partition
clause, and thus limiting the size of the analytic window. If I've
understood your query correctly than you can add "partition by id" to
"fix" performance problem. Your query should look like this:

    CASE WHEN first_code =3D 'LVA' THEN 0
       ELSE 1
    END x
  FROM (
      lag(code, rn-1, 'AAA') over (partition by id order by id,
rn) first_code
    FROM source
WHERE x =3D 1
ORDER BY COUNT(*) desc, code

But I guess what you are really want to ask is: if for particular ID
there is more than one row, give me the code of the first row, else
give me value of current row.
Like Tom Kyte says "Tune the question, not the query". So what you
really need is first_value(code) over (partition by id order by id,
rn) first_code.

On 4/13/05, Gints Plivna <gints.plivna@(protected):
> The problem seems to be in lag function with varying second argument,
> i.e. how many rows to look back. I'v created a small test case that
> worked similarly on my home 1.8GHz Celeron with 500Mb RAM and 10g, as
> well as on work box with parameters I'v described in the first mail.
> I'v switched from automatic sort/hash sizing to manual and gave almost
> 400 M to session that performed select below. As you can see select
> with lag(1) worked fine, but select with varying lag(x) I had to kill
> after almost 2 hours. And the most frustrating thing is that lag had
> to look back 1 or 0 row as you can see from table create script as
> well as later. And then you can see that with constant lag(0) and
> lag(1) also everything works fine.