Conference rdgeng::cics_technical

192.0. "Abend A148 dealing with oracle" by TRN02::PIOVANO (For money we do anything!!!) Tue Jun 03 1997 17:07

    Hi
    
    Our customer got A148 abend using a cobol transaction with oracle.
    
    The console.msg show :
    
    ERZ080010W/8015 06/03/97 17:54:12 TOE0S105 TOP9: XA Resource Manager
    rollback for indeterminate reason in 'XA_END' by 'Oracle_XA' for XID '
    0000000a010c544f45305331303511000000   01544f45305331303511000000'
    (Transaction='', TermId='', UserId='').  'The Resource Manager has
    marked the transaction rollback-only'.  ''.
    
    ERZ016050W/0234 06/03/97 17:54:13 TOE0S105 TOP9: Logical unit of work
    for transaction 'MB10' has been backed out; Distributed Transaction
    Service (TRAN) reason 'ENC-tra-1025: A client (not the transaction
    service) aborted'
    
    ERZ014016E/0028 06/03/97 17:54:13 TOE0S105 TOP9: Transaction 'MB10',
    Abend 'A148', at 'TOP9'.
    
    ERZ011012I/2014 06/03/97 17:54:26 TOE0S105 TOP9: Terminal 'TOP9' with
    netname 'TOE0TYP9' has been uninstalled.
    
    
    in /tmp I found a xa trace wich show an ora-23 error :
    
    ::::::::::::::
    xa_NULL060297.trc
    ::::::::::::::
    
    
    094257.1596.0:
    ORACLE XA: Version 1.1.1.0.0 - Production. RM name = 'Oracle_XA'.
    
    094257.1596.0:
    xaoend: XA_RBROLLBACK; upisdt rtn ORA-23.
    
    094257.1596.0:
    ORA-00023: session references process's private memory; cannot detach
    session
    
    Current environment :
    
    Digital Unix 3.2c
    MFCobol 3.2b
    Oracle 7.1.6
    
    Oracle itself was unable to determine the reason of the error. They
    told me to upgrade current Oracle version to 7.2.3. We are awaiting for
    the kit, but they are not sure that the upgrade solve he problem.
    
    Any hints, suggestions, opinions ?!?!?!?
    
    
    	Thanx in advance
    			Gianmario PIOVANO
    

  Could you tell us a little more about the circumstances?

  From the log, I assume you are using the Oracle XA interface. Can you
  confirm that you are _not_ doing and SQL CONNECT statement in teh
  transaction?

  Has this transaction ever worked? Eg is this a failure that occurs
  occasionally or do all attempts to access Oracle fail this way?

  If it is a problem with Oracle then an upgrade is likely to be the only way
  to fix it.

  Geoff. 

    
    Yes Geoff,
    we are using the oracle XA interface.
    The programmers confirm me that they are not using SQL CONNECT
    statememnt.
    The transaction never worked and they got always the failure!,
    but other transaction work correctly (almost without Oracle).
    
    Let me know if you need more information. We plan to upgrade
    Oracle next week to 7.2.3 version.
    
    	Many Thanks for your support.
    
    					Gianmario PIOVANO
    					DEC Turin
    					ITALY