SQL0443N even after binding db2schema.bnd

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Troels Arvin

    #1

    SQL0443N even after binding db2schema.bnd

    Hello,

    DB2 installation: V. 8.1 LUW, fixpak 10.

    In certain situations, I get strange error messages. Example: I want to
    add a NOT NULL constraint to a column. Through db2cc, I try to do what
    corresponds to
    CONNECT TO SOMEDB;
    CALL SYSPROC.ALTOBJ ( 'APPLY_CONTINUE _ON_ERROR', 'CREATE TABLE
    TRA_TEST.FOOBAR ( K INTEGER NOT NULL , C VARCHAR (50) ) IN WHATEVER ',
    -1, ? ); ;
    CONNECT RESET;

    However, DB2 responds with:
    [IBM][CLI Driver][DB2/6000] SQL0443N Routine "ALTOBJ" (specific
    name "") has returned an error SQLSTATE with diagnostic text
    "SQL0551 Reason code or token: TRA|BIND|NULLID .ALTOBJ_S
    ". SQLSTATE=38553

    I've tried following the steps from

    I.e.:
    db2 terminate
    db2 connect to <database-name>
    db2 bind <path>/db2schema.bnd blocking all grant public sqlerror continue
    db2 terminate

    However, that doesn't help.

    I'm running out of ideas. Suggestions?

    --
    Regards,
    Troels Arvin <troels@arvin.d k>

  • Knut Stolze

    #2
    Re: SQL0443N even after binding db2schema.bnd

    Troels Arvin wrote:
    Hello,
    >
    DB2 installation: V. 8.1 LUW, fixpak 10.
    >
    In certain situations, I get strange error messages. Example: I want to
    add a NOT NULL constraint to a column. Through db2cc, I try to do what
    corresponds to
    CONNECT TO SOMEDB;
    CALL SYSPROC.ALTOBJ ( 'APPLY_CONTINUE _ON_ERROR', 'CREATE TABLE
    TRA_TEST.FOOBAR ( K INTEGER NOT NULL , C VARCHAR (50) ) IN WHATEVER ',
    -1, ? ); ;
    CONNECT RESET;
    >
    However, DB2 responds with:
    [IBM][CLI Driver][DB2/6000] SQL0443N Routine "ALTOBJ" (specific
    name "") has returned an error SQLSTATE with diagnostic text
    "SQL0551 Reason code or token: TRA|BIND|NULLID .ALTOBJ_S
    ". SQLSTATE=38553
    $ db2 "? SQL0551"

    SQL0551N "<authoriza tion-ID>" does not have the privilege to
    perform operation "<operation >" on object
    "<name>".

    <authorizatio n-ID= TRA
    <operation= BIND
    <name= NULLID.ALTOBJ_S


    Are you working as DBA?

    --
    Knut Stolze
    DB2 z/OS Utilities Development
    IBM Germany

    Comment

    • Troels Arvin

      #3
      Re: SQL0443N even after binding db2schema.bnd

      On Wed, 24 Jan 2007 19:18:50 +0100, Knut Stolze wrote:
      <authorizatio n-ID= TRA
      <operation= BIND
      <name= NULLID.ALTOBJ_S
      >
      >
      Are you working as DBA?
      No, but I have all permissions on the table, e.g. I could even drop the
      table.

      When I perform the same action with as a SYSADM user, db2cc pops up
      a window called "Alter Table" with an arrow on a step called "Find
      dependent objects and generate SQL statements"; this step seems to take a
      very long time, even for a dummy table with two simple columns and two
      rows.



      --
      Regards,
      Troels Arvin <troels@arvin.d k>

      Comment

      • Knut Stolze

        #4
        Re: SQL0443N even after binding db2schema.bnd

        Troels Arvin wrote:
        On Wed, 24 Jan 2007 19:18:50 +0100, Knut Stolze wrote:
        ><authorizati on-ID= TRA
        ><operation= BIND
        ><name= NULLID.ALTOBJ_S
        >>
        >>
        >Are you working as DBA?
        >
        No, but I have all permissions on the table, e.g. I could even drop the
        table.
        Do you have the BIND privilege as the error message indicates?

        --
        Knut Stolze
        DB2 z/OS Utilities Development
        IBM Germany

        Comment

        • Troels Arvin

          #5
          Re: SQL0443N even after binding db2schema.bnd

          On Thu, 25 Jan 2007 09:20:05 +0000, Troels Arvin wrote:

          On Thu, 25 Jan 2007 09:20:05 +0000, I wrote:
          When I perform the same action with as a SYSADM user, db2cc pops up
          a window called "Alter Table" with an arrow on a step called "Find
          dependent objects and generate SQL statements"; this step seems to take a
          very long time, even for a dummy table with two simple columns and two
          rows.
          Tried again this morning, and now it worked. There was probably a locking
          situation.



          --
          Regards,
          Troels Arvin <troels@arvin.d k>

          Comment

          Working...