|
Problem IC64518
|
Status: Closed |
A QUERY EXECUTED AGAINST 2 OR MORE OLEDB TABLE FUNCTIONS THAT REFERENCES THE SAME DATA SOURCE RETURNS SQL1182 ERROR. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If a select query is executed against 2 or more OLEDB table
functions that references the same data source, SQL1182 error is
returned.
Eg)
1) View V1 was created with a reference to a table function F1.
CREATE VIEW V1 AS SELECT * FROM TABLE(F1( )) OLEDBTB;
Where the table function F1( ) uses Provider=SQLOLED and gets
data from SQL server.
2) View V2 was created with a reference to a table function
CREATE VIEW V2 AS SELECT * FROM TABLE(F2( )) OLEDBTB;
Where the table function F2 also gets the data from the same SQl
Server data source.
3) View VW is a join of the V1 and V2 views noted above.
Queries ran directly against views V1 & V2 are successful.
A query ran against view VW fails with the error
Select from V1 works
Select from V2 works
Select from VW throws this error;
0 rows selected because of ERROR.
[DB2/NT] SQL1182N User defined function "F2" could not
initialize data source object of specified OLE DB provider.
HRESULT="0x80040e52". Diagnostic text: "Data source object is
already initial". SQLSTATE=38506 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 V9.7 users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* If a select query is executed against 2 or more OLEDB table *
* functions that references the same data source, error *
* returned. *
* *
* [DB2/NT] SQL1182N User defined function "F2" could not *
* initialize data source object of specified OLE DB provider. *
* *
* HRESULT="0x80040e52". Diagnostic text: "Data source object *
* is already initial". SQLSTATE=38506 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V9.7 FP2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.11.2009
30.06.2010
30.06.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
|
 |
