DB2 - Problem description
Problem IC95597 | Status: Closed |
INSERT INTO ODBC/JDBC NICKNAME FAILED WITH SQL0901N REASON "BAD | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
SQL0901N will be reported when insert into ODBC/JDBC nickname if not specify server type when creating server. Reproduce the problem: create wrapper odbc library 'libdb2rcodbc.so' options(db2_fenced 'Y', module '/opt/oemclient/odbc60/64/lib/odbc.so'); create server <your_server> wrapper "ODBC" options (DB2_IUD_ENABLE 'Y', node '<your_node>', dbname '<your_db>'); create user mapping for <user name> server SQL2008 options (REMOTE_AUTHID '<userid>', REMOTE_PASSWORD '<password>'); CREATE NICKNAME NNN FOR <your_server>."<schema>"."<table>"; insert into <nick> values('11') 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 "Bad Compiler return code!".) SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.5 Fix Pack 4. * **************************************************************** | |
Local Fix: | |
Add server type when creating server | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.08.2013 10.09.2014 10.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |