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
oradebug dump processstate 10

oradebug dump processstate 10

2005-06-10       - By Egor Starostin

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

> > Run1 latches total versus runs -- difference and pct
> > Run1        Run2        Diff       Pct
> > 7,067   2,301,590   2,294,523       .31%
> > ***
>=20
> Are you sure this is a reliable figure?
No. Actually it were systemwide latches. And test was run on suffering
from lack of resources instance. On idle system I have numbers like:
Run1 ran in 1 hsecs
Run2 ran in 17 hsecs
run 1 ran in 5.88% of the time
Run1 latches total versus runs -- difference and pct
Run1        Run2        Diff       Pct
3,410      30,898      27,488     11.04%

> > To me, v$access is only usable on idle instances.
>=20
> Not necessarily.  v$* views were put there for a reason, if
I'm not talking about generic v$* views. I'm talking only about slow
(very slow on real nstances) selects from v$access view.

> Don't forget you are not comparing apples with apples:
> traces themselves have not been instrumented with waits, you simply
> do NOT know if your trace isn't causing a lot more overhead in
> places where waits are not counted!
It might be true for systemstate dump, but not for hanganalyze dump.
'hanganalyze level 2' is very fast even on overloaded (in terms of
CPUs and disks) instances.

--=20
Egor
http://www.oracledba.ru/orasrp/
Free Oracle Session Resource Profiler
--
http://www.freelists.org/webpage/oracle-l