Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT06188 Status: Closed

901 CAN OCCUR WHEN THE STATEMENT CONTAINS A SIMPLE SCALAR SUBQUE RY
REFERENCE IN THE OUTPUT OF A SUB-SELECT WHICH ALSO CONTAINS A

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
901 Error Message can occur when the statement contains a simple 
scalar subquery reference in the output of a sub-select which 
also contains a predicate using either the ROWNUM pseudo column 
or row_number() over(...) syntax. The scalar subquery must be 
referenced in the containing query, sub-select or full-select. 
 
Example: 
 
select protocol from 
    (SELECT (select value from registryentries where 
description='Access Protocol (http|https)') protocol 
       FROM rt_entity en 
       WHERE ROWNUM = 1) hostquery 
 
SQL0901N  The SQL statement or command failed because of a 
database system error. (Reason "The entity is not part of this 
relationship".) 
SQLSTATE=58004
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 6                       * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 10.5 Fix Pack 6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.12.2014
25.08.2015
25.08.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.6 FixList
10.5.0.7 FixList