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: [Q] way to shrink temporary tablespace ??

stephen booth


On 19/01/06, David Sharples <davidsharples@(protected):
> you have data beyond the 2Gb limit of the file, there is nothing to fix and
> it will stay like that as temporary tablespace segments just get reused.

I had the same problem, the temproary tablespace datafile had grown to
32Gb. This was worrying as the database contained less than 3Gb of
actual data. We eventually concluded (after looking at the sorts of
queries that were popping up in v$sql) that a lot of users were
running very unselective queries with sorts in them that meant that
virtually the entire database was being sorted repeatedly in many

In the long term the solution was to get the users trained to use the
app properly (i.e. use highly selective searches to get the relevant
results rather than highly unselective and manually seaching through
many pages of results to find the record they want). Very
frustrating, i even blogged about it

> Create a new temporary ts then drop old one

What I did was create more datafiles, to the appropriate size, in the
same tablespace and then when the database was quiet offline the
problematic file and drop it.

> As for cold backup, no you dont need to back it up

That's my understanding. Took a long time to convince the managers of
it though.


It's better to ask a silly question than to make a silly assumption.