Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: DBMS_SQL will not work with SQL statement > 32K

Re: DBMS_SQL will not work with SQL statement > 32K

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Sat, 4 Dec 1999 14:27:35 -0000
Message-ID: <944318806.22247.0.nnrp-04.9e984b29@news.demon.co.uk>

As others have pointed out, the newer version of dbms_sql allows for a dbms_sql.varchar2s input - array of varchar(255).

There is a little article on my website that packages this up to allow for an easy call with the option to output where a parse error occured or simply fail and return the sql error code.

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

kjhealey_at_my-deja.com wrote in message <8297ou$lc2$1_at_nnrp1.deja.com>...
>Is there any way to execute dynamic DDL from PL/SQL when the DDL
>statement is larger than 32K?
>
>We are writing a PL/SQL function that will create Audit Trail like
>Triggers for all of the tables in our database.
>
>The PL/SQL function creates "CREATE TRIGGER..." statements based on
>information in the system_tables and then executes the statements using
>the DBMS_SQL package.
>
>The problem is that in some cases, the "CREATE TRIGGER..." statement
>becomes larger than 32K and cannot fit in a VARCHAR2 or be passed to the
>DBMS_SQL.PARSE function.
>
>Any ideas?
>
>Thanks,
>Kevin
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
Received on Sat Dec 04 1999 - 08:27:35 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US