IBM Support

PK31976: GOC DROP VIEW CREATES TWO DROP STATEMENTS IN WSL SECOND DROP IS INCORRECT AND CAUSES ERROR WHEN RUN SQLCODEN204 SQLCODE204N 204

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Object Compare with source ddl for a Drop View and automatically
    taking objects from the catalog completes but the WSL give an
    extra DROP statement and this gets errors since the first Drop
    is all that was needed.
    Running WSL with the unneeded drop gives
       DROP VIEW ##T.VDMAR;
    ADBT278E 10-02-2006 16.27.30
     RESULT OF SQL STATEMENT:
     DSNT400I SQLCODE = 000,  SUCCESSFUL EXECUTION
    ...
       DROP VIEW ##T.VVDMAR;
    SQLERROR ON DROP       COMMAND, PREPARE    FUNCTION
     DSNT408I SQLCODE = -204, ERROR:  ##T.VVDMAR IS AN UNDEFINED
                         NAME
     DSNT418I SQLSTATE   = 42704 SQLSTATE RETURN CODE
     DSNT415I SQLERRP    = DSNXOFE SQL PROCEDURE DETECTING ERROR
     DSNT416I SQLERRD    = -200  0  0  -1  0  0 SQL
                            DIAGNOSTIC INFORMATION
     DSNT416I SQLERRD    = X'FFFFFF38'  X'00000000'
       X'00000000'  X'FFFFFFFF   X'00000000'  X'00000000'
       SQL DIAGNOSTIC INFORMATION
    ...
      last drop is not correct because the VW is implicitly
      dropped due to the first drop of VDMAR.
    sqlcoden204 sqlcode204n sqlcode -204 204
    

Local fix

  • Please apply PTF when available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Object Comparison Tool, who     *
    *                 attempt to DROP a View, may be affected.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Two  DROP  statements in WSL were given *
    *                      for  a  DROP  of  a View from automatic *
    *                      Catalog objects. The Second Drop failed *
    *                      because the first Drop was all that was *
    *                      needed.                                 *
    *                      .*                                      *
    *                      Drop  statement  was  generated  for an *
    *                      implicitly dropped view.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    See Problem Description.
    

Problem conclusion

  • Apply the fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK31976

  • Reported component name

    DB2 OBJECT COMP

  • Reported component ID

    5697G6400

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-09-25

  • Closed date

    2006-11-26

  • Last modified date

    2006-12-01

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

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

Modules/Macros

  •    GOC2CMR
    

Fix information

  • Fixed component name

    DB2 OBJECT COMP

  • Fixed component ID

    5697G6400

Applicable component levels

  • R710 PSY UK20017

       UP06/11/30 P F611

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUVH","label":"IBM Db2 Object Comparison Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021