If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > SQL0443N with SQLSTATE=38553 after executing ALTOBJ with VALIDATE OPTION

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-27-06, 08:32
grofaty grofaty is offline
Registered User
 
Join Date: Jan 2003
Posts: 1,570
SQL0443N with SQLSTATE=38553 after executing ALTOBJ with VALIDATE OPTION

Hi,
my system: db2 ese v8.2 fp11 on Linux390.

I would like to change column definition from null to not null by executing ALTOBJ system procedure.

Sample:
Create table:
Code:
CREATE TABLE DB2ADMIN.TAB1 (COL1 INT)
Calling Validate option:
Code:
CALL SYSPROC.ALTOBJ ('VALIDATE', 'CREATE TABLE DB2ADMIN.TAB1 (COL1 INT NOT NULL)', -1, ? )
The above command returns error:
Code:
SQL0443N  Routine "ALTOBJ" (specific name "") has returned an error SQLSTATE
with diagnostic text "SQL0443  Reason code or token:
SYSPROC.DB2LK_TBLNDEP|DB2LK_TBL".  SQLSTATE=38553
What does this error means?

I have tried the same commands on my notebook WindowsXP sp2 db2v8.2 fp9 and works fine.

Is there something I have missed out or is there a bug in fixpack 11?

Thanks,
Grofaty
Reply With Quote
  #2 (permalink)  
Old 12-27-06, 09:55
guyprzytula guyprzytula is offline
Registered User
 
Join Date: Jun 2006
Posts: 471
altobj

this is known error :see apar IY87539
resolved in fp11
have a look at apar list for this fixpack if this fix was included
__________________
Best Regards, Guy Przytula
DB2 UDB LUW certified V6/7/8
Reply With Quote
  #3 (permalink)  
Old 12-28-06, 01:46
grofaty grofaty is offline
Registered User
 
Join Date: Jan 2003
Posts: 1,570
Hi,
I have looked at appar list for db2 version 8 but there is no such apar (IY87539) listed.

It seems this apar was not included in any db2 v8 fixpack. By the way I am using fp11 on db2 v8.2 on Linux390 and the bug is still present.

On WindowsXP sp2 db2 v8.2 fp9 it is working well, so this bug is probably appearing between fp9 and fp11.

Do you have any idea how to solve the problem of apar you have provided?

Thanks,
Grofaty
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On