How do i break this code.

Question

All,
I am getting the "PLS-00123: program too large error"
when i execute the following code. Is there a way i can break the huge
update statement.
Please suggest me.
PROCEDURE PR_UPD_FACT ( v_Part in varchar2 )
IS
fupd_stmnt VARCHAR2(19190);
upd_cid      NUMBER;
upd_recnum     NUMBER;
BEGIN
fupd_stmnt :=
'UPDATE ' ||v_Part|| ' SET ' ||
     'WRKG01_ASM_BODY_DONE_Y = ' || 'TO_DATE(' || '''' || to_char
(ods_record.WRKG01_ASM_BODY_DONE_Y,'DD/MON/YY HH:MI:SS') || ''''
|| ',' || '''' || 'DD/MON/YY HH:MI:SS' || '''' || ')' || ',' ||
'WRKG01_ASM_BUCK_Y = ' || 'TO_DATE(' || '''' || to_char(
ods_record.WRKG01_ASM_BUCK_Y,'DD/MON/YY HH:MI:SS') || '''' || ','
|| '''' || 'DD/MON/YY HH:MI:SS' || '''' || ')' || ',' ||
-- *** UPDATTING 366 COLUMNS OF A HUGE TABLE ***
' WHERE ' ||
' WRKG01_CNT_MDL_YEAR_C = ' || '''' || ods_record.WRKG01_CNT_MDL_YEAR_C || '''' ||
' AND WRKG01_ORD_PROD_SRC_C = ' || '''' || ods_record.WRKG01_ORD_PROD_SRC_C || '''' ||
' AND WRKG01_ORD_PROD_ORD_ID_C = ' || '''' || ods_record.WRKG01_ORD_PROD_ORD_ID_C || '''';     
upd_cid := DBMS_SQL.OPEN_CURSOR;
     DBMS_SQL.PARSE(upd_cid, fupd_stmnt, DBMS_SQL.NATIVE);
     upd_recnum := DBMS_SQL.EXECUTE(upd_cid);
     DBMS_SQL.CLOSE_CURSOR(upd_cid);
END PR_UPD_FACT;
Thank You

Answer 1

I can't tell which Oracle version you are on, but the limit for v7.x is 64K, v8.0 (up to 8.1.3) is 128K, and 8i and up have a limit of 256M.
One thing you should definitely incorporate - regardless of whether you split up this statement - is bind variables. Instead of hardcoding the literal values within the string, just assign placeholders and then, on a call(s) to dbms_sql.bind_variable, supply the value(s).
So instead of:
'WRKG01_ASM_BODY_DONE_Y = ' || 'TO_DATE(' || '''' || to_char (ods_record.WRKG01_ASM_BODY_DONE_Y,'DD/MON/YY HH:MI:SS')
use:
'wrkg01_asm_body_done_y = :w01abd'
and then, after the call to dbms_sql.parse but before dbms_sql.execute:
dbms_sql.bind_variable(upd_cid, 'w01abd', to_char(ods_record.wrkg01_asm_body_done_y, 'DD/MON/YY HH:MI:SS'));
Also use bind variable for the parameters in your WHERE clause. You will still need to hardcode the table and column names (as you do for the tablename parameter v_part).
Now, using bind variables is extremely important, but it doesn't help your size issue. Is this procedure in a package? It might be, but I couldn't tell. If not, it probably should be.
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:571023051648
Another thing you might try is to break the update into two steps, each handled in a separate procedure (or separate packages). Now, if you are updating a column included in the WHERE clause, then this will not be a viable option.
Just some initial thoughts...