DB2 - Problem description
Problem IC67578 | Status: Closed |
SQLCODE 100 ENCOUNTERED WHILE ATTEMPTING TO DROP SQL PROCEDURE OR FUNCTION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
While executing DROP PROCEDURE or DROP FUNCTION, you may receive an SQL0100W warning: db2 => drop procedure myschema.myproc SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table. SQLSTATE=02000 This error prevents the SQL routine from being dropped. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * This issue may happen when there are no entries intable * * SYSIBM.SYSDEPENDENCIES for the correspondingprocedure.This * * fix makes dropping a procedure more tolerant. * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 V9.7 FP2 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in db2 V9.7 FP2 | |
Workaround | |
n/a | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67730 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.04.2010 27.07.2010 27.07.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |