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: ORA-01652: unable to extend temp segment

Roger Xu



6 from dba_tablespaces
SQL> /

-------------- ----------- ---------- --------- ------
     16384     40960 DICTIONARY USER    MANUAL


-----Original Message-----
From: Michael McMullen [mailto:ganstadba@(protected)]
Sent: Monday, January 23, 2006 1:43 PM
To: Roger Xu; Oracle-L@(protected))
Subject: Re: ORA-01652: unable to extend temp segment

It doesn't look like you are running out of temp tablespace, unless your
temp tablespace is named PSAPREROGI
It's building the index in parallel so each process will take take up n
extents during the build and then be coalesced at the end. What are your
extent sizes on PSAPREROGI. Is it ASM? You can build the index serially if
you can handle the extra time delay.
I had the same problem last week, my final index was 5.3Gb but was taking >
13Gb during the parallel build.
You can see all of this happening by querying dba_segments during the build.


For technical support please email tech_support@(protected)
call (972)721-8257.
This email has been scanned for all viruses by the MessageLabs Email Security System.

This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material.
This email has been scanned for all viruses by the MessageLabs Email Security System. Any questions please call 972-721-8257 or email your request to tech_support@(protected).