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: SQL Tuning -- large, long-running outer join query

Wolfgang Breitling

2006-01-19

Replies:
That query has no predicates whatsoever, apart from the join predicates
and those are outer joins. What that means is that Oracle has to read
every row of each of the five tables - at least once.
Like Mladen, I wonder what the original business question is which this
query is supposed to answer. I have the funny feeling that the
developer(s) threw in the outer join "just in case" for good measure,
especially on the last two outer joins.
For the aql ASIS, I would try to replace the two "nested loop outer"
with hash joins as well with full scans of IA_SALES_ORDLNS and
OD_SALES_ORDLNS. And make sure you have the highest
db_file_multi_block_read_count your OS can handle and potentially use
parallel slaves.

Thomas Jeff wrote:
> We have this purchased app that is generating the following query.  It
> runs
> for 8 hours then crashes due to ORA-1555. I'm reluctant to tinker with
> the undo settings or increase the undo tablespace size, as it appears
> from
> longops that this thing would likely run for another 7-8 hours before
> completing.  I'm at a loss on how to tune this -- I can't touch the
> physical structure, and I don't know enough to see any hints that could
> possibly help.  
>
> Any ideas?
>
>
> SELET (boatload of columns)
> FROM
> TS_SALES_ORDLNS,   /*   465,175 rows, 20,930 blocks   */
> OD_SALES_ORDLNS,   /* 18,733,125 rows, 1,247,303 blocks */
> IA_SALES_ORDLNS,   /* 18,631,135 rows, 603,410 blocks  */
> TS_SALES_ORDLNS_HD, /*   474,465 rows, 25,819 blocks   */
> TS_SALES_ORDLNS_LN /*   472,645 rows, 14,043 blocks   */
> WHERE
>  TS_SALES_ORDLNS.SALES_ORDER_NUM = TS_SALES_ORDLNS_HD.SALES_ORD_NUM(+)
> AND TS_SALES_ORDLNS.SALES_ORDER_ITEM =
> TS_SALES_ORDLNS_HD.SALES_ORD_ITEM(+)
> AND TS_SALES_ORDLNS.SALES_ORDER_NUM =
> TS_SALES_ORDLNS_LN.SALES_ORD_NUM(+)
> AND TS_SALES_ORDLNS.SALES_ORDER_ITEM =
> TS_SALES_ORDLNS_LN.SALES_ORD_ITEM(+)
> AND TS_SALES_ORDLNS.KEY_ID = OD_SALES_ORDLNS.KEY_ID(+)
> AND TS_SALES_ORDLNS.KEY_ID =IA_SALES_ORDLNS.KEY_ID(+);
>

--
Regards

Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
http://www.freelists.org/webpage/oracle-l