Results 1 to 2 of 2
  1. #1
    Join Date
    Jan 2012
    Posts
    82

    Unanswered: DB2 System created Package Issue.

    Hi,
    I have no idea about about Db2 packages. this is my 1st encounter with them. So bear with me.

    Ok so I have system created packages. we did not create any packages.

    So some packages are giving errors. Maybe because some stored procedures or things got dropped I guess ( New to the project.. Old Dba made a mess and left without any docs)


    so when I try to rebind the packages I get errors like these...

    rebind package Customer.P6174726
    SQL0206N "COUNT" is not valid in the context where it is used.
    SQLSTATE=42703

    OR

    rebind package User.P6174641
    SQL0206N "OPEN_DATE_KEY_ID" is not valid in the context where it is used.
    SQLSTATE=42703

    OR

    rebind package USER.P6154402
    SQL0440N No authorized routine named "USER.GETPSEGBYPNAMESP" of type
    "PROCEDURE" having compatible arguments was found. SQLSTATE=42884



    And when I try to drop the packages so the DB can recreate a new one. I get this

    DB21034E The command was processed as an SQL statement because it was not a
    valid Command Line Processor command. During SQL processing it returned:
    SQL0658N The object "USER.P6154402" cannot be explicitly dropped or altered.
    SQLSTATE=42917


    Also I checked the database and we have no triggers or stored procedures that are invalid. ( Count is not valid in the context suggests that a SP might be invalid because the DDL of the table might have been changed.) But nothing... everything is running fine..


    Any advice ?? what should I do ??


    DB2 9.7.3 on zlinux server.

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Check the dependency for this package in syscat.routinedep. If it's SP, you need to drop SP.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •