DB2 - Problem description
Problem IC91689 | Status: Closed |
FEDERATED OBJECT REFERENCES SHOULD BE DISALLOWED WITHIN COMPILED SQL FUNCTIONS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Prior to DB2 Version 9.7 Fix Pack 6, if your application attempted to access a federated object from within a compiled SQL function, or within a stored procedure that is directly or indirectly called from a compiled SQL function, DB2 would report error SQL20136N. As of Fix Pack 6, the error is no longer reported when the federated object reference occurs within the scope of a compiled SQL function--including any PL/SQL function. This is an error: DB2 does not support federated object references that take place in the scope of a compiled SQL function. The failure of DB2 to report the restriction does not imply support for federated object references in this context. This restriction is documented for external functions in the DB2 InfoCenter, but also applies to SQL functions: * CREATE FUNCTION (external scalar) statement http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2. luw.sql.ref.doc/doc/r0004461.html Notes - If the function allows SQL, the external program must not attempt to access any federated objects (SQLSTATE 55047). | |
Problem Summary: | |
Local Fix: | |
Avoid the use of federated objects from within compiled SQL functions, or within routines called by compiled SQL functions. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Comment | |
This APAR is a duplicate of IC86715 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.04.2013 03.10.2013 03.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 |