[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::sql_services

Title:SQL/Services Forum
Notice:kits(3) ft info(7) QAR access (8) SPR access (10)
Moderator:SQLSRV::MAVRIS
Created:Thu Oct 13 1988
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2214
Total number of notes:8586

2172.0. "SQLSRV_PREPARE bugchecking." by svrav1.au.oracle.com::MCHAN () Wed Mar 19 1997 22:08

SQL-Services V6.1 eco2
Rdb V6.0-15
ODBC V2.10.11
Visual Basic V4.0A

Hi,

One of our customer keep getting SQLSRV$BUGCHECK when their Visual Basic
users calling the SQLSRV_PREPARE. The first bugcheck with error message 
RDB-F-REQ_NO_TRANS and then user keep getting second bugcheck 
%SQL-F-BUGCHK...SQL$CTX - 0 and SQL$INTERP - 0. 

To workaround the problem user have to commit the transaction then 
try again.

Did anyone came across with the same problem? 
Appreciated for any suggestion.


Thanks,
Michael.




------------------------------------------------------------------------------
SQLSRV$BUGCHECK.DMP;8
=====================

Saved PC = 00006991

ARG# Argument [data...]  -----------------------------------------------------
   1 7FE4F844: 00000000 03C00000 001A09CC 001A08EC 00000001 02228CB4 00000005
   2 7FE4F82C: 00000005 05000002 0028F448 01388062 00000006 7FE50200 00000004

%SQL-F-BUGCHK, There has been a fatal error. 
Please submit an SPR. SQL$INTERP - 0

 Handler = 00000000, PSW = 0000, CALLS = 0, STACKOFFS = 0
        Saved AP = 7FE4F87C, Saved FP = 7FE4F85C, PC Opcode = 05
SR2 = 0138815C: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
SR3 = 7FE4F8CC: 7FE4FB10 2FFC0000 00000000 03C00000 00146259 0138815C 00000003
SR4 = 7FE4F8B4: 00000003 03000002 0028F448 0138815A 00000008 7FE4FFE4 00000004
SR5 = 004BF714: 00000000 00000000 00000000 00000000 00000000 002AC5B8 002AC560
SR6 = 000EB050: 014C95E0 00000001 000EB060 000E2CA8 0000F9AE 00000000 002AAF40
:
:
:
Saved PC = 00186473

ARG# Argument [data...]  -----------------------------------------------------
   1 7FE4F8CC: 7FE4FB10 2FFC0000 00000000 03C00000 00146259 0138815C 00000003
   2 7FE4F8B4: 00000003 03000002 0028F448 0138815A 00000008 7FE4FFE4 00000004

%RDB-F-REQ_NO_TRANS, attempt to execute request with no transaction active


        Handler = 00000000, PSW = 0000, CALLS = 0, STACKOFFS = 0
        Saved AP = 7FE4F918, Saved FP = 7FE4F8DC, PC Opcode = 05
        56 bytes of stack data from 7FE4F8A4 to 7FE4F8DC:


IMAGNAME = "DSA22:[SYS0.SYSCOMMON.][SYSEXE]SQLSRV$EXE.EXE;8"
PRCNAM = "SS_DISCLAS_002F"       
USERNAME = "DISSYS      "   

-----------------------------------------------------------------------------

SQLSRV$BUGCHECK.DMP;9
=====================

R0  = 00002F68: 00000000 00010000 00000000 000003A0 00010001 00000000 00025003
R1  = 00000000
:
:
:
ARG# Argument [data...]  -----------------------------------------------------
   1 7FE4FF20: 00000000 03C00000 001A09CC 001A08EC 00000001 02228CB4 00000005
   2 7FE4FF08: 00000005 05000002 0028F448 01388062 00000006 7FE50200 00000004
   3 FFFFF82C
        Handler = 00000000, PSW = 0000, CALLS = 1, STACKOFFS = 0
        Saved AP = 7FE4FEFC, Saved FP = 7FE4FED0, PC Opcode = D0
SR2 = 000846F0: 00000000 00000000 00000000 FFFFF82C 00000000 00000000 00000000
SR3 = FFFFF82C
SR4 = 7FE4FF08: 00000005 05000002 0028F448 01388062 00000006 7FE50200 00000004
        20 bytes of stack data from 7FE4FEBC to 7FE4FED0:
FFFFF82C7FE4FF087FE4FF2000000003  0000   '.... .a...a.,o..'
                        7FE4FF58  0010   'X.a.'

Saved PC = 00006991

ARG# Argument [data...]  -----------------------------------------------------
   1 7FE4FF20: 00000000 03C00000 001A09CC 001A08EC 00000001 02228CB4 00000005
   2 7FE4FF08: 00000005 05000002 0028F448 01388062 00000006 7FE50200 00000004

%SQL-F-BUGCHK, There has been a fatal error. 
 Please submit an SPR. SQL$INTERP - 0

Handler = 00000000, PSW = 0000, CALLS = 0, STACKOFFS = 0
        Saved AP = 7FE4FF58, Saved FP = 7FE4FF38, PC Opcode = 05
SR2 = 02228CB4: 021D8F50 00000000 00000000 00000000 021D8F50 021D8F50 021C0FF8
SR3 = 7FE4FFA8: 001A28D8 03C00000 001A27F5 001A27C0 00000001 02228CB4 00000005
SR4 = 7FE4FF90: 00000005 05000002 0130DBD4 00084748 00000000 7FE4FFC0 00000004
SR5 = 000EB050: 02196D70 00000001 000EB060 000E2CA8 0000F9AE 00000000 002ABE40
SR6 = 000024CC: 00000000 00000000 00000000 00000000 0000214F 00002148 000882B0
        64 bytes of stack data from 7FE4FEF8 to 7FE4FF38:
7FE4FF087FE4FF20000000029729AA4D  0000   'M?)..... .a...a.'
01388062000000067FE5020000000004  0010   '......a.....b.8.'
02228CB400000005050000020028F448  0020   'Ho(.........'.".'
03C00000001A09CC001A08EC00000001  0030   '....i...I.....A.'
                                                            
:
:
:

ARG# Argument [data...]  -----------------------------------------------------
   1 7FE4FFA8: 001A28D8 03C00000 001A27F5 001A27C0 00000001 02228CB4 00000005
   2 7FE4FF90: 00000005 05000002 0130DBD4 00084748 00000000 7FE4FFC0 00000004
   3 7FE4FF68: 9729AA4D 80000014 7FE4FFC0 7FE4FFF4 00000000 00000000 00000000
        Handler = 00000000, PSW = 0000, CALLS = 1, STACKOFFS = 0
        Saved AP = 7FE4FF84, Saved FP = 7FE4FF6C, PC Opcode = 04
SR2 = 7FE50004: 23FC0000 00000000 090E0024 000E0024 0130A810 7FE50101 000E0503
SR3 = 7FE500C4: 000846F0 00081BC0 0000F9AE 7FE5011C 7FE50144 2FFC0000 000E784D
SR4 = 00000000
        20 bytes of stack data from 7FE4FF58 to 7FE4FF6C:
7FE4FF687FE4FF907FE4FFA800000003  0000   '....?.a...a.h.a.'
                        00000000  0010   '....'

Saved PC = 001A28E9

ARG# Argument [data...]  -----------------------------------------------------
   1 7FE4FFA8: 001A28D8 03C00000 001A27F5 001A27C0 00000001 02228CB4 00000005
   2 7FE4FF90: 00000005 05000002 0130DBD4 00084748 00000000 7FE4FFC0 00000004

%SQL-F-BUGCHK, There has been a fatal error. Please submit an SPR. SQL$CTX - 0

IMAGNAME = "DSA22:[SYS0.SYSCOMMON.][SYSEXE]SQLSRV$EXE.EXE;8"
LOGINTIM = 11-MAR-1997 11:17:23.32
PRCNAM = "SS_DISCLAS_0027"  
USERNAME = "DISSYS      "        

------------------------------------------------------------------------------
Client log:
===========

------------STATEMENT ID
----------------SQLSRV_GENERALIZED_NUMBER, len: 7
--------------------len: 7, value: 1000034
--------END OF MESSAGE

ROUTINE LEVEL LOG at 22:36:25 on 13-Mar-1997
----SQLSRV_PREPARE
--------SQL STATEMENT
------------len: 36, value: Call Supercede_Document(?,?,?,?,?,?)

PROTOCOL LEVEL LOG CLIENT: write (logonly) at 22:36:25 on 13-Mar-1997
----PACKET LENGTH: 50

PROTOCOL LEVEL LOG CLIENT: write (logonly) at 22:36:25 on 13-Mar-1997
----PACKET ID: 74, PACKET SEQUENCE: 0
--------SQLSRV_PREPARE
------------SQL STATEMENT
----------------SQLSRV_ASCII_STRING, len: 36
--------------------len: 36, value: Call Supercede_Document(?,?,?,?,?,?)
--------END OF MESSAGE

PROTOCOL LEVEL LOG CLIENT: read at 22:36:26 on 13-Mar-1997
----PACKET LENGTH: 116

PROTOCOL LEVEL LOG CLIENT: read at 22:36:26 on 13-Mar-1997
----PACKET ID: 74, PACKET SEQUENCE: 0
--------ERROR ACK
------------ERROR_VALUE_TAG
----------------SQLSRV_GENERALIZED_NUMBER, len: 5
--------------------len: 5, value: -2004
------------SPECIFIC_ERROR_TAG
----------------SQLSRV_GENERALIZED_NUMBER, len: 8
--------------------len: 8, value: 35818676
------------SPECIFIC_ERROR_TEXT_TAG
----------------SQLSRV_ASCII_STRING, len: 81
--------------------len: 81, value: %SQL-F-BUGCHK, There has been a
fatal error.
-------------------- Please submit an SPR. SQL$INTERP - 0
--------END OF MESSAGE

ROUTINE LEVEL LOG at 22:36:37 on 13-Mar-1997
----SQLSRV_PREPARE
--------SQL STATEMENT
------------len: 133, value: Update DRAWING_DOCUMENT Set DOCUMENT_SOURCE
= ?, DR
------------AWING_STATUS = 'A' Where SITE_CODE = ? and DRAWING_ID = ?
and DRAWIN
------------G_REVISION = ?

PROTOCOL LEVEL LOG CLIENT: write (logonly) at 22:36:37 on 13-Mar-1997
----PACKET LENGTH: 147

PROTOCOL LEVEL LOG CLIENT: write (logonly) at 22:36:37 on 13-Mar-1997
----PACKET ID: 75, PACKET SEQUENCE: 0
--------SQLSRV_PREPARE
------------SQL STATEMENT
----------------SQLSRV_ASCII_STRING, len: 133
--------------------len: 133, value: Update DRAWING_DOCUMENT Set
DOCUMENT_SOURCE
-------------------- = ?, DRAWING_STATUS = 'A' Where SITE_CODE = ? and
DRAWING_I
--------------------D = ? and DRAWING_REVISION = ?
--------END OF MESSAGE

PROTOCOL LEVEL LOG CLIENT: read at 22:36:38 on 13-Mar-1997
----PACKET LENGTH: 116

PROTOCOL LEVEL LOG CLIENT: read at 22:36:38 on 13-Mar-1997
----PACKET ID: 75, PACKET SEQUENCE: 0
--------ERROR ACK
------------ERROR_VALUE_TAG
----------------SQLSRV_GENERALIZED_NUMBER, len: 5
--------------------len: 5, value: -2004
------------SPECIFIC_ERROR_TAG
----------------SQLSRV_GENERALIZED_NUMBER, len: 8
--------------------len: 8, value: 35818676
------------SPECIFIC_ERROR_TEXT_TAG
----------------SQLSRV_ASCII_STRING, len: 81
--------------------len: 81, value: %SQL-F-BUGCHK, There has been a
fatal error.
-------------------- Please submit an SPR. SQL$INTERP - 0
--------END OF MESSAGE
------------------------------------------------------------------------------

T.RTitleUserPersonal
Name
DateLines
2172.1Maybe a known problem, or at least related...ORASQS::OXBURYOracle Corporation, Rdb Desktop Group|DTN 381-2704Thu Mar 20 1997 09:0614
    Hi Michael,
    
    There was a problem in one of the versions of Rdb 6.0 and/or 6.1, where
    it didn't implicitly start a transaction when it should have done. This
    resulted in a RDB-F-REQ_NO_TRANS error. While you may or may not be
    experiencing exactly the same problem, it does sound like they are
    related, because RDB-F-REQ_NO_TRANS is really an internal Rdb error
    which applications should never see. In order to track this down, we're
    going to need a client log showing the sequence of requests issued by
    the application before it failed. With that information, the SQL or Rdb
    exec folks can get a handle on it. You might also like to post a note
    in the Rdb notes file to see if anyone else has already run into this. 
    
    Si
2172.2"Commit_transaction on db" cause REQ_NO_TRANS error.svrav1.au.oracle.com::MCHANThu Apr 03 1997 01:3139
    
    Hi,
    
    Here are the rdms$debug_flags "T" output:
    
    
    Compile transaction on db: X00000001
    ~T Transaction Parameter Block: (len=3)
    0000 (00000) TPB$K_VERSION = 1
    0001 (00001) TPB$K_WAIT
    0002 (00002) TPB$K_WRITE (read write)
     Start_transaction on db: X00000001, db count=1
     Commit_transaction on db: X00000001
     Prepare_transaction on db: X00000001
    
    Call Supercede_Document(?,?,?,?,?,?,?,?) <-- This is usually where
                                                 customer get a bugcheck.
    
    %SQLSRV-F-BUGCHK, Fatal error encountered, a dump file is being
    generated :
    
    (error in dumpfile: %RDB-F-REQ_NO_TRANS, attempt to execute request with 
                         no transaction active)
      
    
    Update DRAWING_DOCUMENT Set DOCUMENT_SOURCE = ?, DRAWING_STATUS = 'A'
    Where SITE_CODE = ? and DRAWING_ID = ? and DRAWING_REVISION = ?
    
    %SQLSRV-F-BUGCHK, Fatal error encountered, a dump file is being
    generated
               
    (error in dumpfile: %SQL-F-BUGCHK, There has been a fatal error.
     Please submit an SPR. SQL$INTERP - 0)
      
    
    Would it be "Commit_transaction on db" shown on log cause NO_TRANS error?  
    
    
    Michael.