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

10g R1, temp tablespace group, level 7 statspack snap - cons stats$seg_stat_pk violated

Paul Drake

2006-04-12

Replies:
10.1.0.4, 10.1.0.4 patch 10 standard edition
w2k adv svr sp4

I'm wondering if anyone has seen this type of error before?

Had contention on a single tempfile in a temp tablespace.
Only one tempfile out of 4 was being used (one temp tablespace with 1 tempfile on each of 4 mount points) which was resulting in contention.
I attempted to leverage a tablespace group for the load to be balanced across multiple temp tablespaces' tempfiles on different mount points.
As no potentially good deed goes unpunished, this arrangement threw an error when attempting a level 7 statspack snapshot:

ERROR at line 1:
ORA-00001: unique constraint (PERFSTAT.STATS$SEG_STAT_PK) violated
ORA-06512: at "PERFSTAT"."STATSPACK". line 2654
ORA-06512: at "PERFSTAT"."STATSPACK". line 4516
ORA-06512: at "PERFSTAT"."STATSPACK". line 91
ORA-06512: at line 1

The cons columns are
(snap_id, dbid, instance_number, dataobj#, obj#)

The offending statement is an insert statement.

Funny thing is that at line 2712 of the package, there is a comment regarding avoiding ORA-1. :)

I'm not going to file an SR on this now, but if its still around with the 10.1.0.5 patchset in place I may do so later.

Paul