DB2 - Problem description
Problem IC72159 | Status: Closed |
FEDERATED DDL MAY FAIL WITH SQL0901N AFTER ROLLBACK TRANSACTION CONTAINING OTHER DDLS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
SQL0901N Reason "Null Server" is reported when autocommit is turned off and you perform the following operations: 1) issue federated DDL statements 2) issue some other federated DDL or DML statements 3) rollback 4) issue some federated DDL or DML statements The following error message is received: DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "Null Server".) SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * see ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.5 Fix Pack 8. * **************************************************************** | |
Local Fix: | |
Use AUTOCOMMIT feature or commit/rollback every federated DDL statement | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.5 Fix Pack 8. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.10.2010 01.07.2011 01.07.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.8 |