|
Problem IC96288
|
Status: Closed |
ALTER TABLE STATEMENT REFERENCING A TABLE NAME CONTAINING TRAILING SPACES MIGHT PRODUCE SQL0901N |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Under rare scenarios, DB2 might produce a SQL0901N error message
if the following conditions are true
1. The statement is an alter
2. The table is a dependent object for view/trigger/procedure
3. Delimited table name inside the alter statement or the
view/trigger/procedure body has trailing
spaces
Example:
Create table "Table1234" (c1 DECIMAL(16,0) NOT NULL GENERATED
ALWAYS AS IDENTITY (
START WITH +1
INCREMENT BY +1
MINVALUE +1
MAXVALUE +9999999999999999
NO CYCLE
CACHE 20
NO ORDER ),
c2 GRAPHIC(1) NOT NULL WITH DEFAULT 'i');
create trigger "trigger1234"
no cascade before update of c2 on "Table1234" referencing old as
"deleted" new as "inserted"
for each row mode db2sql
begin atomic
if ("deleted".c2 <> 'i'
and "inserted".c2 <> 'i') then
SIGNAL SQLSTATE '75000' SET MESSAGE_TEXT= 'Error';--
end if;--
end;
alter table "Table1234 " alter column c1 drop identity;
SQL0901N The SQL statement failed because of a non-severe system
error.
Subsequent SQL statements can be processed. (Reason "table not
found
in dep list during alt/drop".) SQLSTATE=58004 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 and Fix Pack 3 *
**************************************************************** |
| Local Fix: |
Workaround:
Make sure that the table names referenced across all objects and
the
alter statement are an exact match. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2013
18.10.2013
18.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
