Experiencing the intermittent ibm_db error, as detailed below.

An unexpected error occurred during data retrieval: An unexpected error occurred during data retrieval: uncaught throw :"Fetch Failure: <error message could not be retrieved>"

What's interesting is it will fail at different spots on the page when rapid refreshing (to reproduce the error). For example, in the below code it will sometimes fail on users.each and other times on u.name.

  <% users.each do |u| %> 
        <%= u.name %>

The LUW (Linux/Unix/Windows) version of ibm_db also has this issue.

Working to reproduce issue with PASE CLI tool (thanks Tony Cairns).

Example of running

paseclitrace.ini:

; device_type=[tty,file]
;   0  - console
;   1  - file (/tmp/libdb400_trace)
; device_pid (device_type=1-file)
;   0 - /tmp/libdb400_trace
;   1 - /tmp/libdb400_trace[_pid]
; trace_type
;   0 - trace all
;   1 - trace errors only
; trace_stack
;   0 - no PASE stack dump
;   1 - PASE stack dump errors only
;   2 - PASE stack dump all
; trace_break (use with trace_stack)
;   0 - PASE dspjob stack (faster, less accurate)
;   1 - PASE dbx attach stack (much slower, more accurate)
; cli api=[0,1]
;   0    - API ignore
;   1    - API trace
device_type=1
device_pid=1
trace_type=1
trace_stack=1
trace_break=1
sqloverrideccsid400=1
sqlallocenv=1
sqlallocconnect=1
sqlallochandle=1
sqlallocstmt=1
sqlbindcol=1
sqlbindfiletocol=1
sqlbindfiletoparam=1
sqlbindparam=1
sqlbindparameter=1
sqlcancel=1
sqlclosecursor=1
sqlcolattributes=1
sqlcolumnprivileges=1
sqlcolumns=1
sqlconnect=1
sqlcopydesc=1
sqldatasources=1
sqldescribecol=1
sqldescribeparam=1
sqldisconnect=1
sqldriverconnect=1
sqlendtran=1
sqlerror=1
sqlexecdirect=1
sqlexecute=1
sqlextendedfetch=1
sqlfetch=1
sqlfetchscroll=1
sqlforeignkeys=1
sqlfreeconnect=0
sqlfreeenv=0
sqlfreehandle=0
sqlfreestmt=0
sqlgetcol=1
sqlgetconnectattr=1
sqlgetconnectoption=1
sqlgetcursorname=1
sqlgetdata=1
sqlgetdescfield=1
sqlgetdescrec=1
sqlgetdiagfield=1
sqlgetdiagrec=1
sqlgetenvattr=1
sqlgetfunctions=1
sqlgetinfo=1
sqlgetlength=1
sqlgetposition=1
sqlgetstmtattr=1
sqlgetstmtoption=1
sqlgetsubstring=1
sqlgettypeinfo=1
sqllanguages=1
sqlmoreresults=1
sqlnativesql=1
sqlnextresult=1
sqlnumparams=1
sqlnumresultcols=1
sqlparamdata=1
sqlparamoptions=1
sqlprepare=1
sqlprimarykeys=1
sqlprocedurecolumns=1
sqlprocedures=1
sqlputdata=1
sqlreleaseenv=1
sqlrowcount=1
sqlsetconnectattr=1
sqlsetconnectoption=1
sqlsetcursorname=1
sqlsetdescfield=1
sqlsetdescrec=1
sqlsetenvattr=1
sqlsetparam=1
sqlsetstmtattr=1
sqlsetstmtoption=1
sqlspecialcolumns=1
sqlstarttran=1
sqlstatistics=1
sqltableprivileges=1
sqltables=1
sqltransact=1

##Recreate error##

$ cd git/ibmdb_fetchbug
$ export LIBPATH=/QOpenSys/download/trace-1.0.2-xlc
$ export PASETRACE=/QOpenSys/download/trace-1.0.2-xlc/paseclitrace.ini
$ export IBM_DB_GIL="00000000000000000000000000000000000000000000"
$ rails s -p50000
/PowerRuby/prV2R1/lib/ruby/gems/2.1.0/gems/railties-4.1.8/lib/rails/app_rails_loader.rb:37: warning: Insecure world writable dir /QOpenSys in PATH, mode 042777
/PowerRuby/prV2R1/lib/ruby/gems/2.1.0/gems/bundler-1.7.6/lib/bundler/runtime.rb:222: warning: Insecure world writable dir /QOpenSys in PATH, mode 042777
=> Booting Puma
=> Rails 4.1.8 application starting in development on http://0.0.0.0:50000
=> Run `rails server -h` for more startup options
=> Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (--binding option)
=> Ctrl-C to shutdown server
Puma 2.11.1 starting...
* Min threads: 0, max threads: 16
* Environment: development
* Listening on tcp://0.0.0.0:50000

<--- here is where I go to the browser and invoke a URL in the app --->

Started GET "/users/2" for 216.114.244.204 at 2015-07-07 17:38:17 +0000
   (7.6ms)  SET SCHEMA ab1_d
   (8.1ms)  SET SCHEMA ab1_d
  ActiveRecord::SchemaMigration Load (5.3ms)  SELECT schema_migrations.* FROM schema_migrations
Processing by UsersController#show as HTML
  Parameters: {"id"=>"2"}  <--- it hangs here.  

WRKACTJOB STS is THDW with the following as the last entry in the call stack:

libpthread.a(shr_xpg5 >          00000584  _event_sleep

Call stack with panic. This revealed we needed to get dbx working with 64-bit PASE.

                              Display Call Stack                             
                                                            System:   xxxxx
Job:   QP0ZSPWP       User:   QSECOFR        Number:   297055                
Thread:   00000009                                                           


Type  Program                  Statement         Procedure                   
      QP0ZPCP2   QSYS                            _CXX_PEP__Fv                
      QP0ZPCPN   QSYS          264               Qp0zNewProcess              
      QP2FORK    QSYS                            _CXX_PEP__Fv                
      QP2FORK    QSYS          16                main                        
      QP2USER2   QSYS          10                __Qp2Fork                   
      QP2USER2   QSYS          6                 runpase_main__FPi           
      QP2USER2   QSYS          5                 runpase_common__FiPvT2      
 P    dbx                              00000074  __start                     
 P    dbx                              000001C8  main                        
 P    libdbx.a(shr_64.o)               0000058C  dpi_main                    
 P    libdbx.a(shr_64.o)               000001CC  dpi_command                 
 P    libdbx.a(shr_64.o)               000000F4  process_input               
 P    libdbx.a(shr_64.o)               00000844  yyparse                     
 P    libdbx.a(shr_64.o)               00000C20  topeval    
 P    libdbx.a(shr_64.o)               0000472C  eval       
 P    libdbx.a(shr_64.o)               00000034  wherecmd   
 P    libdbx.a(shr_64.o)               00000294  walkstack  
 P    libdbx.a(shr_64.o)               000000C0  touch_sym  
 P    libdbx.a(shr_64.o)               000002CC  touch_file 
 P    libdbx.a(shr_64.o)               000009E0  readsyms   
 P    libdbx.a(shr_64.o)               00000F20  enter_nl   
 P    libdbx.a(shr_64.o)               0000081C  entersym   
 P    libdbx.a(shr_64.o)               00000488  typeName   
 P    libdbx.a(shr_64.o)               00000394  constype   
 P    libdbx.a(shr_64.o)               00000E08  constype   
 P    libdbx.a(shr_64.o)               0000019C  consRecord 
 P    libdbx.a(shr_64.o)               00000394  constype           
 P    libdbx.a(shr_64.o)               00000E50  constype           
 P    libdbx.a(shr_64.o)               00000394  constype           
 P    libdbx.a(shr_64.o)               00001470  constype           
 P    libdbx.a(shr_64.o)               000000C8  panic  <---- YIKES
 P    libdbx.a(shr_64.o)               00000068  errmsg             
 P    libc.a(shr_64.o)                 00000080  fflush             
 P    libc.a(shr_64.o)                 00000794  fflush_unlocked    
 P    libc.a(shr_64.o)                 000000BC  _xflsbuf           
 P    libc.a(shr_64.o)                 00000080  _xwrite            
 P    libc.a(shr_64.o)                 00000260  write              
 P    unix                             00000008  <syscall64>:kwrite

Current status: Working with IBM to produce PTF for dbx

fetch column metadata error

Example of running

Comments (157)

An Explanation

ibm_db_adapter.rb insertion