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: tempspace usage

jametong@gmail.com

2005-04-20

Replies:
comment in line.

On 4/20/05, Yongping Yao <yaoyongping@(protected):
> Well, some statements cannot be tuned more. In our design, these kind
> of operations are rare (delete the duplicate rows and due to the load
> speed we do not use unique index). But I did use them these days since
> the application did something wrong :(
if your table is very big , then use partition table will be a must.
then you can use exchange  partition to minimize the undo with it.
delete from a big table is a bad idea.

> And by the way, SMON clean the undo tablespace? It also has some
> delay. Some transanctions are commited and they still occupy the undo
> space. Can it be solved? Or just add more space to the undo
> tablespace?

if you have a undo tablespace that extended beyond your control. then
create a new undo tablespace . and change the undo tablespace online
may be a better solution than to wait the SMON to clean then undo
tablespace.

within my technical scope. if there were no other transaction request
the undo from the undo tablespace , oracle will not release this undo
segment.

> On 4/20/05, jame tong <jametong@(protected):
> > I think you tune the sql statement to minimize the temp space usage.
> >
> >
> > On 4/20/05, Yongping Yao <yaoyongping@(protected):
> > > I have a related question. After I run a statement consuming the
> > > temporary tablespace a lot and commit the transaction, the tablespace
> > > is not cleaned soon. Then other sessions got an error something like
> > > "can't extend ...in ..." which means the temporary tablespace is not
> > > enough. Is there something wrong with the background process?
> > > Do I have to use a separate temporary tablespace or set the temporary
> > > tablespace autoextend (which I think is not safe and hard to control
> > > the datafile size)?
> > >
> > > --
> > > Yao Yongping
> > > Learning Oracle, UNIX/Linux...
> > > Love Reading, Classical Music, Philosophy, Economics etc.
> > > Blog: http://blog.csdn.net/
> > >
> >
>=20
> --
> Yao Yongping
> Learning Oracle, UNIX/Linux...
> Love Reading, Classical Music, Philosophy, Economics etc.
> Blog: http://blog.csdn.net/
>
--
http://www.freelists.org/webpage/oracle-l