JR33602: SYBASE ENTERPRISE STAGE INCORRECTLY PULLING TABLE SCHEMA BASED ON USERS DEFAULT DATABASE, NOT THE DATABASE BEING ACCESSED.

APAR status

• Closed as program error.

Error description

• Sybase Enterprise stage incorrectly pulling table schema
  information based on users default database, not the database
  being accessed when the table in the query exists in both the
  users default database and another database.
  

Local fix

• Use the Database Connection property to override the users
  default database.
  
  This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All platforms , jobs using Sybase ASE EE Stage
  ****************************************************************
  PROBLEM DESCRIPTION:
  Sybase Enterprise Stage incorrectly pulling table schema based
  on users default database , not the database being accessed.
  
  ****************************************************************
  RECOMMENDATION:
  Install Patch for JR33602
  ****************************************************************
  

Problem conclusion

• The Sybase ASE operator was trying to get table definition from
  system tables, but gets confused when same table name exists in
  two different databases.
  
  Removed the function that got table definition from system
  tables as new procedure to get the table definition is
  sufficient.
  

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:

Modules/Macros

• SYBASE
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSN

     UP