Links
Home
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
Parallel query on when it 's not supposed to be (?)

Parallel query on when it 's not supposed to be (?)

2004-09-15       - By Mladen Gogala

Reply:     1     2     3     4     5     6     7     8     9     10     >>  


On 09/14/2004 10:03:10 PM, Mark Richard wrote:
>
>
>
>
> I just wanted to pose a question to anyone on the list (particular the wait
> event guru 's like Cary)...

Event guru? That 's what Cary is? Hmmm, not exactly the expression
that I 'd use.

>
> Eliminating parallel query because you are seeing waits for it sounds to me
> a little like tuning the BCHR. I can 't help but wonder if waiting for a
> parallel query is still the quickest way to get things done? Would killing
> the parallel query effectively move the waits to another category without
> achieving any real gain?

If the instance is OLTP with several hundreds of concurrent users, you definitely
don 't want PQ utilized by users, on regular basis, because it would quickly
drain your machine resources. If a full table scan somehow makes it into production,
and it happens even to the best of us, then you want to minimize the damage and
not resolve it by devoting enormous resources to it, thus starving everybody
else of CPU power. PQ is not a magic potion thad druid Getafix used to cook
(I apologize to my American friends who have never heard of Asterix and Obelix)
to increase power of the tiny Gaul warrior, PQ is a tool that has its place,
primarily in the batch and DW systems. Enabling PQ on a busy OLTP instance is
something that can be compared to another French comic, namely Gaston. There are
many French speaking people on this list, they may explain to you everything
about Gaston Lagaffe.
--
Mladen Gogala
Oracle DBA
--
http://www.freelists.org/webpage/oracle-l