RE: Resource Manager bug in 9.2.0.4?

  • From: "Thomas Jeff" <jeff.thomas@xxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 25 Mar 2004 09:43:54 -0500

Tim,
 
No, the error does not occur when we complete the transaction -- but
obviously,
we cannot control all transaction processing occurring at the time we
want to
perform the switch.   It's not just the session that performs the switch
that
will error, all user sessions with uncommitted transactions will error.

 
One of the things we are trying to do is use Res Mgr for chargeback
purposes
and we'd like to 'reset' the numbers for some interval measurements.
We'd
also like to perform switches for changes between diff types of
processing
loads (nightly/batch, day, etc).    Res Mgr should be able to handle
switches
gracefully.
 
Thanks,
Jeff
 
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Gorman
Sent: Thursday, March 25, 2004 9:27 AM
To: oracle-l@xxxxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx 
                
                Indy DBA Master Documentation available at: 
                http://gkmqp.tce.com/tis_dba
<http://gkmqp.tce.com/tis_dba> <http://gkmqp.tce.com/tis_dba>  
                -------------------------------------------- 
                
                
                

        
        

Other related posts: