JR27049: A SQL QUERY INVOLVING VIEWS AND SUBQUERIES CAN RETURN A SQL0901NERROR.

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• A SQL query involving views and subqueries can return a SQL0901N
  error.
   Example:
  
  select c1, c2, c3 from view1 where c2 in (select c2  from
  table1);
  SQL0901N  The SQL statement failed because of a non-severe
  system error.
  Subsequent SQL statements can be processed.  (Reason
  "sqlnt_translate_ship  [725]:rc(     0)                ".)
  SQLSTATE=58004
  
  Here are the conditions where a query may hit this problem:
  
  1) There must be a view created against one or more nickname
  objects.
  2) There must be a subquery in the select statement.
  

Local fix

• Reducing optimization level to 3 might solve the problem.
  

Problem summary

• Users affected:
     Users of the DB2 for LUW Homogeneous Federation Feature or
  InfoSphere Federation Server
  Problem description and summary:
     See error description.
  

Problem conclusion

• Problem was first fixed in Version 8.2, FixPak 16 (s080111).
  This fix should be applied on the federation server.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WS INFO INTEGRA

• Fixed component ID

  5724C7400

Applicable component levels