Skip to content
TheChatArchiveThe Chat Archive
gpt-3.5-turbo-0301· OpenAIAi2 WildChat-4.8M (AI2)

numeric or value error: Bulk Bind: Truncated Bind declare oanumchange_…

  1. User

    numeric or value error: Bulk Bind: Truncated Bind declare oa_num_change_ {INTM:s/[^\d\w]//g}_SBMS_AQF_TEMPL.NUM10_ARRAY; oa_name_template_ {INTM:s/[^\d\w]//g}SBMS_AQF_TEMPL.NAME255_ARRAY; oa_start_date {INTM:s/[^\d\w]//g}_SBMS_AQF_TEMPL.DATE_ARRAY; oa_end_date_ {INTM:s/[^\d\w]//g}SBMS_AQF_TEMPL.DATE_ARRAY; oa_user_method {INTM:s/[^\d\w]//g}_SBMS_AQF_TEMPL.NAME50_ARRAY; oa_date_operation_ {INTM:s/[^\d\w]//g}SBMS_AQF_TEMPL.DATE_ARRAY; oa_sum_AP ${INTM:s/[^\d\w]//g}_SBMS_AQF_TEMPL.NUM10_ARRAY;

    begin SBMS_AQF_TEMPL.getRatePlanConstructorHistory( ip_subs_id => :SUBS_ID<int, in>, ip_row_first => :P_ROW_FIRST<int, in>, ip_row_last => :P_ROW_LAST<int, in>, -- Раздел выходных параметров oa_num_change => oa_num_change_, oa_name_template => oa_name_template_, oa_start_date => oa_start_date_, oa_end_date => oa_end_date_, oa_user_method => oa_user_method_, oa_date_operation => oa_date_operation_, oa_sum_AP => oa_sum_AP_, op_total => :P_TOTAL<int, out> );

    :NUM_CHANGE<BIG_UINT, out[500]> := oa_num_change_; :NAME_TEMPLATE<CHAR[255], out[500]> := oa_name_template_; :START_DATE<DATE, out[500]> := oa_start_date_; :END_DATE<DATE, out[500]> := oa_end_date_; :USER_METHOD<CHAR[50], out[500]> := oa_user_method_; :DATE_OPERATION<DATE, out[500]> := oa_date_operation_; :SUM_AP<BIG_UINT, out[500]> := oa_sum_AP_;

    end;

  2. Assistant

    This error can occur when the size of the input values exceeds the size of the target variables in the bulk bind operation. In this case, the bulk bind operation is being used to transfer multiple values between the PL/SQL block and the database procedure, and one or more of the target arrays may not be large enough to hold all the data being returned by the procedure.

    To resolve the error, you may need to increase the size of the target arrays or adjust the range of data being returned by the database procedure. You may also need to check the data types and lengths of the input and output variables to ensure compatibility between the PL/SQL block and the procedure.