Re: Aw: RE: Re: Can Bind variables be an issue with respect to network transfer?

  • From: Tim Gorman <tim.evdbt@xxxxxxxxx>
  • To: rogel@xxxxxx
  • Date: Wed, 14 Oct 2020 10:10:41 -0700

Even though you declared the variable as CLOB, I'm guessing that there might be a VARCHAR2(32767) limitation for EXECUTE IMMEDIATE?

Can you measure the length of "stmt" before EXECUTE IMMEDIATE and add an exception handler that shares that length as well as the error, perhaps something like...

           len := length(stmt);
           execute immediate stmt;
    exception
          when others then
                  dbms_output.put_line('len = '||len);
                  raise;
    end;
    /

Just an idea...



On 10/14/2020 9:07 AM, rogel@xxxxxx wrote:

ok, "line 4" != "line 7"
*Gesendet:* Mittwoch, 14. Oktober 2020 um 18:04 Uhr
*Von:* rogel@xxxxxx
*An:* nenad.noveljic@xxxxxxxxxxxx
*Cc:* "jlewisoracle@xxxxxxxxx" <jlewisoracle@xxxxxxxxx>, "Oracle L" <oracle-l@xxxxxxxxxxxxx>
*Betreff:* Aw: RE: Re: Can Bind variables be an issue with respect to network transfer?
I am not able to reproduce this 1e5, for me it seems to be 3760 instead, see (note: execute immediate select-stmt just parses the select-stmt)
*declare stmt clob default 'select null from dual where (0,0) in (';
begin
for i in 1..3760 loop
stmt:=stmt||'(0,'||i||'),';
end loop;
stmt:=stmt||'(0,-1))';
execute immediate stmt;
end;
/*
*PL/SQL procedure successfully completed.*
*3
  3* for i in 1..3760 loop
c/0/1/
  3* for i in 1..3761 loop
l
  1  declare stmt clob default 'select null from dual where (0,0) in (';
  2  begin
  3  for i in 1..3761 loop
  4  stmt:=stmt||'(0,'||i||'),';
  5  end loop;
  6  stmt:=stmt||'(0,-1))';
  7  execute immediate stmt;
  8* end;
/
declare stmt clob default 'select null from dual where (0,0) in (';
*
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 4*
*Gesendet:* Mittwoch, 14. Oktober 2020 um 16:04 Uhr
*Von:* "Noveljic Nenad" <nenad.noveljic@xxxxxxxxxxxx>
*An:* "jlewisoracle@xxxxxxxxx" <jlewisoracle@xxxxxxxxx>, "Oracle L" <oracle-l@xxxxxxxxxxxxx>
*Betreff:* RE: Re: Can Bind variables be an issue with respect to network transfer?

“An IN list is limited to 1,000”

Unless it’s a multi-value IN list, which is limited to 1e5 elements.

Best regards,

Nenad

*From:*oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> *On Behalf Of *Jonathan Lewis
*Sent:* Mittwoch, 14. Oktober 2020 16:00
*To:* Oracle L <oracle-l@xxxxxxxxxxxxx>
*Subject:* Re: Re: Can Bind variables be an issue with respect to network transfer?

Lothar,

Comparing the ela for the "PGA allocate memory" with the matching "tim=" I think what you're seeing is the time it takes Oracle to build an array and copy data from the SQL*Net packet to the array. Obviously some of the difference is about the time to write to the trace file, even so there's a lot of other CPU to account for.and it's happening between the memory allocations.  I doubt if "traffic" (i.e. movement across the network) is relevant - the ns calls are probably a layer above that moving the data between the sql*net layer and the session layer.

I am curious about the internal_function() and 4,700 variables.  An IN list is limited to 1,000 and I wouldn't have expected an OR of IN lists to turn into a single internal_function(), Perhaps there's something about data types and character set conversion (or some other conversion) that's adding to the CPU time.

Regards

Jonathan Lewis

____________________________________________________

Please consider the environment before printing this e-mail.

Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.


Important Notice

This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall prevail in any case, we take it as your authorization to correspond with you by e-mail if you send us messages by e-mail. However, we reserve the right not to execute orders and instructions transmitted by e-mail at any time and without further explanation.
E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively referred to as "Vontobel Group") for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version.
Please note that all e-mail communications to and from the Vontobel Group are subject to electronic storage and review by Vontobel Group. Unless stated to the contrary and without prejudice to any contractual agreements between you and Vontobel Group which shall prevail in any case, e-mail-communication is for informational purposes only and is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.
The legal basis for the processing of your personal data is the legitimate interest to develop a commercial relationship with you, as well as your consent to forward you commercial communications. You can exercise, at any time and under the terms established under current regulation, your rights. If you prefer not to receive any further communications, please contact your client relationship manager if you are a client of Vontobel Group or notify the sender. Please note for an exact reference to the affected group entity the corporate e-mail signature. For further information about data privacy at Vontobel Group please consult www.vontobel.com <https://www.vontobel.com>.

-- //www.freelists.org/webpage/oracle-l
-- //www.freelists.org/webpage/oracle-l

Other related posts: