Conference orarep::nomahs::dbintegrator_public_public

1087.0. "DBI-I-INV_DESC_TYPE?" by ORAREP::GIDDAY::REINHOLD (Skippy) Tue Aug 13 1996 03:17

                                          
    
    Gidday,
    
            I have a customer doing some development on the following
    versions,
           
    			VMS V6.2
                        RDB V6.1-ECO-3
                        DBI V3.1-02A
    
    	    At the moment they have the following error message,
    
    
    ------------------- SQL ERROR and EXIT ------------
    sqlcode =
         -1006
    ------------------- ERROR and EXIT ----------------
    %WHO-F-ERRPRC, Error in procedure who_dc_trnsfr_desp_rjctns_prog
    -WHO-F-ERRPRC, Error in procedure who_dc_trnsfr_desp_itm_ur01
    -RDB-E-INVALID_BLR, request BLR is incorrect at offset 329
    -DBI-I-INV_DESC_TYPE, Invalid datatype or subtype used with BLR_K_CURRENT_
    TIMEST
    ---------------------------------------------------
    
    The sqlmod which causes the error is:-
    
    procedure WHO_DC_TRNSFR_DESP_ITM_UR01
      sqlca
      datarec     record from 'who_records.dc_trnsfr_desp_itm' end record
      ;
      UPDATE dc_trnsfr_desp_itm SET
        dc_trnsfr_desp_itm_iss_ctn_qty = datarec.dc_trnsfr_desp_itm_iss_ctn_qty,
        dc_trnsfr_desp_itm_amt          =  datarec.dc_trnsfr_desp_itm_amt,
        db_row_no                       =  datarec.db_row_no,
        dc_trnsfr_desp_itm_stat_cd      =  datarec.dc_trnsfr_desp_itm_stat_cd,
        rec_tmstamp                     =  current_timestamp
      WHERE
        dc_trnsfr_rcpt_dc_no            =  datarec.dc_trnsfr_rcpt_dc_no
      and dc_trnsfr_ord_no              =   datarec.dc_trnsfr_ord_no
      and ord_itm_id                    =   datarec.ord_itm_id
      and itm_per_iss_ctn_qty           =   datarec.itm_per_iss_ctn_qty
      ;
    
    
    Note: The error does not occur if you run the same query in interactive
              SQL
    
    
    
    
    	Any ideas?
    
    			Cheers,
    				Dave Reinhold,
    				DIGITAL CSC,
    				Sydney,
    				Australia.
    

    
    Hi Dave,
    
    I think this problem is fixed in the version of DBI now in field test.
    I'd like to confirm this though - could the customer
    
    $define dbi_trace_flags "BLR"
    $define dbi_trace_output "trace.out"
    
    and send us the trace?
    
    Thanks,
    
    Dan

    Hi Dan,
    
    	  Thanks, I have placed the TRACE file on ORAREP:: called
    1087.txt.
    
    	  Meanwhile the customer claimes that this may be an RDB issue, as
    if they compile it under RDB V6.1 it fails with the problem. If they
    compile it under RDB V4.2 and link it under RDB V6.1 it works fine.
    
    	  Anyway, let me know what you think.
    
    						Cheers,
    							Dave
    

    
    Hi Dave,
    
    This is a DBI issue, and its fixed in the latest release.  Rdb is
    constantly adding features and changing the definition of what BLR is
    legal (it is a good thing - the product is being updated and changes
    are required to support new features).  In this case rules changed
    regarding what BLR can legally be generated, and DBI didn't understand 
    it until we added support for it (next release, currently in FT)
    
    Hope this clarifies things.
    
    Dan

    Hi Dan,
    
    	   Just so I can update the customer, any idea when the next
    release of DBI will be expected to be available?
    
    Dave
    

    
    Hi Dave,
    
    Our ship date is relative to Rdb's ship date (between 1 and 2 months
    afterward).
    
    I am unsure of the Rdb7 ship date, but I believe it is next month.
    
    Dan