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: Resource Manager bug in 9.2.0.4?

Bobak, Mark

2004-03-25

Replies:
Re: Resource Manager bug in 9.2.0.4?
Not to mention, ORA-00600 is, by definition, a bug.
-----Original Message-----
From: John Hallas [mailto:john.hallas@hcresources.co.uk]
Sent: Thursday, March 25, 2004 10:38 AM
To: oracle-l@freelists.org
Subject: RE: Resource Manager bug in 9.2.0.4?

Fair point Tim, but it should not be the case that you need a quiescent system before changing plans.

On many systems that situation is almost impossible to achieve

John

 

-----Original Message-----
From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Tim Gorman
Sent: 25 March 2004 14:27
To: oracle-l@freelists.org
Subject: Re: Resource Manager bug in 9.2.0.4?

 

Jeff,

Wouldn’t it make more sense to complete the transaction before using ALTER SYSTEM?  Does the error reproduce when you do that?

-Tim

on 3/25/04 6:47 AM, Thomas Jeff at jeff.thomas@thomson.net wrote:

Wondering if anyone has experienced the following bug in Res Mgr (we
are running 9.2.0.4 on AIX 4.3.3).   We have a TAR in for this, but

our experience is that tech support is completely hapless when it
comes to Res Mgr issues.

The error occurs when we switch plans while users have ongoing uncommitted
transactions,  their session will terminate with an ORA-600: internal
error code, arguments: [kgskdecrstat1] when they issue a COMMIT.     
We had planned on implementing Res Mgr in our prod databases for various
reasons, with a need to switch plans, so this is a big show-stopper.


I can recreate the error in every database with something like the
following:


SQL> create table xyz as select * from dba_objects where 1=2;

Table created.

SQL> insert into xyz select * from dba_objects where owner = 'SYS';

12561 rows created.

SQL> alter system set resource_manager_plan = '';

System altered.

SQL> alter system set resource_manager_plan = 'ES_RM_PLAN';

System altered.

SQL> commit;
commit
*
ERROR at line 1:
ORA-00603: ORACLE server session terminated by fatal error
                                                                      

-
-------------------------------------------
Jeffery D Thomas
DBA
Thomson Information Services
Thomson, Inc.

Email: jeff.thomas@thomson.net

Indy DBA Master Documentation available at:
http://gkmqp.tce.com/tis_dba <http://gkmqp.tce.com/tis_dba>
--------------------------------------------

 


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.581 / Virus Database: 368 - Release Date: 09/02/2004


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.581 / Virus Database: 368 - Release Date: 09/02/2004