Is Rebind required for dynamic SQL Cobol prog after RUNSTATS

Furor · New User Joined: 04 Jun 2009 Posts: 30 Location: Bangalore

Hi,

Normally we REBIND after RUNSTATS for DB2 to pick up the latest statistics from the DB2 catalog.

Will the same rule apply to the application having only Dynamic SQL.

Thanks for your help.

rohanthengal · Posted: Thu Sep 19, 2013 12:37 pm

After the completion of every RUNSTATS statement, you should execute an explicit COMMIT WORK. The COMMIT releases locks and avoids filling up the log when gathering statistics on multiple tables.

Rebind packages containing static SQL using the BIND command, or the REBIND command (and optionally re-explain their statements) after collecting statistics with RUNSTATS. The db2rbind command can be used to rebind all packages in the database. Use the FLUSH PACKAGE command to remove all cached dynamic SQL statements currently in the package cache and force the next request to be implicitly compiled.