Hi all,

We are on DB2 V8.1 Connect Unlimited Edition Fixpak 5 on Solaris 8. I am trying to compile a procedure, which gives me the following error. Can some please interpret the error and let me know what needs to be done? Appreciate your help.

Thanks in advace.
Newbie


-- LOG FILE P1381778.log FOR PROCEDURE DPS .IF_EXISTS_DROP_ROUTINE

-- DB2_SQLROUTINE_PREPOPTS=

-- PREP/BIND MESSAGES FOR /export/home/dps/sqllib/function/routine/sqlproc/SAS2N1D2/DPS/tmp/P1381778.sqc

LINE MESSAGES FOR P1381778.sqc
------ --------------------------------------------------------------------
SQL0060W The "C" precompiler is in progress.
SQL0091W Precompilation or binding was ended with "0"
errors and "0" warnings.

-- DB2_SQLROUTINE_COMPILER_PATH=/export/home/dps/sqllib/function/routine/sr_cpath

-- CONTENTS OF /export/home/dps/sqllib/function/routine/sr_cpath

#!/bin/sh
PATH=$PATH:/opt/SUNWspro/bin
export PATH

-- CONTENTS OF /export/home/dps/sqllib/function/routine/sqlproc/SAS2N1D2/DPS/tmp/P1381778.sh

SQLROUTINE_FILENAME=P1381778
export SQLROUTINE_FILENAME

-- COMPILATION COMMAND:

CC -xarch=v9 -mt -KPIC -I/export/home/dps/sqllib/include P1381778.c -G -o P1381778 -L/export/home/dps/sqllib/lib -R/export/home/dps/sqllib/lib -ldb2


-- CONTENTS OF /export/home/dps/sqllib/function/routine/sqlproc/SAS2N1D2/DPS/tmp/P1381778.exp

pgsjmp


-- COMPILATION MESSAGES FOR /export/home/dps/sqllib/function/routine/sqlproc/SAS2N1D2/DPS/tmp/P1381778.c
"P1381778.sqc", line 315: Warning: String literal converted to char* in initialization.
"P1381778.sqc", line 324: Warning: String literal converted to char* in initialization.
"P1381778.sqc", line 541: Error: The type "sqla_setdata_list[2]" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.7
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The function "sqlasetdata" must have a prototype.
"P1381778.sqc", line 541: Error: The type "sqla_setdata_list[1]" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
"P1381778.sqc", line 539: Error: The type "sqla_setdata_list" is incomplete.
Compilation aborted, too many Error messages.

-- END OF LOG FILE (SQLCODE: -7032)

Hi,

sqlcode: -7032

sqlstate: 42904

SQL7035W The executable of the SQL procedure "<procedure-name>" is not saved in the database catalog.


Explanation: The executable of the SQL procedure exceeds the limit of 2 megabytes and therefore cannot be stored in the database catalog. It will not be recovered automatically at database restore time or on ROLLBACK of a DROP PROCEDURE statement.

User Response: If the warning resulted from a CREATE PROCEDURE statement, ensure that you keep a backup of the executable associated with SQL procedure "<procedure-name>". If the warning was issued during a restore operation or a ROLLBACK of a DROP PROCEDURE statement, then the executable associated with "<procedure-name>" must be manually synchronized with the SQL procedure that is defined in the catalog.

With Regards

Bala