Hello!
I need to execute a dynamic RUNSTATS in a stored procedure, but it´s not working...
the error message is:
SQL0104N An unexpected token "TABLE" was found following "RUNSTATS ON ".
Expected tokens may include: "JOIN". SQLSTATE=42601

My stored procedure is:
PREPARE V_SQL_C1 FROM V_COMANDO;
SET V_COMANDO2 = "RUNSTATS ON TABLE EPI03.DBM_ATIVIDADE_ETL";
SET V_COMANDO3 = " WITH DISTRIBUTION AND INDEXES ALL";
SET V_COMANDO = V_COMANDO2 || V_COMANDO3;
EXECUTE V_COMANDO;

What´s the problem??
Thanks,
Tessy

ADMIN_CMD Stored Procedure

Cheers

Sathyaram

But, how this ADMIN_CMD Stored Procedure works?
where can I see the stored procedure code???
Can you give me an example please?
Thanks,
Tessy

Here's the documentation link

http://publib.boulder.ibm.com/infoce...n/r0012547.htm

Sathyaram

Hi Sathyaram!
Now there is another error message:
SQL0440N No authorized routine named "SYSPROC.ADMIN_CMD" of type "PROCEDURE"
having compatible arguments was found. SQLSTATE=42884
SQL0440N No authorized routine named "SYSPROC.ADMIN_CMD" of type "PROCEDURE

My stored procedure is:
SET V_COMANDO = 'CALL SYSPROC.ADMIN_CMD(';
SET V_COMANDO = V_COMANDO || '''RUNSTATS ON TABLE EPI03.DBM_ATIVIDADE_ETL';
SET V_COMANDO = V_COMANDO || ' WITH DISTRIBUTION AND INDEXES ALL''' || ')';
EXECUTE IMMEDIATE V_COMANDO;

How can I fix it?
Thanks,
Tessy

You haven't mentioned about your DB2 version and fixpak!!

This SP wasn't available until FP9 of Version 8.

If you are on earlier fixpaks/versions, an option is to use a C Stored Proc which calls the db2Runstats API ... A sample program (not a SP) is available in the sqllib/samples/c directory.

HTH

Sathyaram

Hi Sathyaram! Sorry...
DB2 version and fixpack:
DB2 v8.1.1.80
FixPak "8"
DB2ESE

Where is this directory "sqllib/samples/c" ?
Is it at "/" directory?
It cant´t be a C program...
Do you have an example of a C Stored Procedure which calls the db2Runstats API?
Is the C Stored Procedure compile form the same as SQL Stored Procedure?
Thanks,
Tessy

It is under the instance owner home directory ..

Read the readme file in the directory and you'll have all information you need

Sathyaram