DROP system stored procedure restriction

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Parnamwulan
    New Member
    • Apr 2008
    • 16

    DROP system stored procedure restriction

    Hello everybody,

    I am running DB2 on linux ....

    I need to import a huge table to the database I created and I found out that I have not enough BLOB size (I hope I have 320k - it should be default) ... the table is stored in .ixf format (the source db is on mainframe) and it has 180 columns.

    The error I got and the explanation how to correct it is here: http://publib.boulder.ibm.com/infoce...p/trs20002.htm

    nice one - but I have a problem with this solution - I am not sure if I am not wrong, but since the procedure ICMUPDATEITEMS doesnt exist, IMHO the whole description should be SYSIBM.ICMCREAT EITEMS, no?

    but another problem appeared - seems that this object exists but it cannot be changed ...

    The outputs:

    Code:
    [db2inst1@xxxxx db2inst1]$ db2 DROP PROCEDURE ICMCREATEITEMS
    DB21034E  The command was processed as an SQL statement because it was not a
    valid Command Line Processor command.  During SQL processing it returned:
    SQL0204N  "DB2INST1.ICMCREATEITEMS" is an undefined name.  SQLSTATE=42704
    
    [db2inst1@xxxxx db2inst1]$ db2 DROP PROCEDURE SYSIBM.ICMCREATEITEMS
    DB21034E  The command was processed as an SQL statement because it was not a
    valid Command Line Processor command.  During SQL processing it returned:
    SQL0607N  "DROP PROCEDURE" is not defined for system objects.  SQLSTATE=42832
    Pls is there anybody who can help me with advise how to avoid SQLSTATE=42832 or is there any other way how to change BLOB size?

    Thanks a lot for any help
    Last edited by docdiesel; Apr 16 '08, 08:12 PM. Reason: Added code tags
  • Parnamwulan
    New Member
    • Apr 2008
    • 16

    #2
    It is solved ... I was importing (using import command) with "insert into" statement and I had bad informations about the data format

    The IMPORT command with "create into" statement solved the problem

    Comment

    • docdiesel
      Recognized Expert Contributor
      • Aug 2007
      • 297

      #3
      Hi,

      and thank you for sharing the solution! By the way, I took the liberty to add some code tags to your first post for better readability.

      Regards,

      Bernd

      Comment

      Working...