Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2003
    Posts
    7

    Question Unanswered: Can't Update Java Stored Proc?

    DBA is gone for the week and we're having issues updating a previously created java stored procedure. Using DB2 7.2.

    The SP was created through the SPB Friday. While working on the SP that day making changes worked as expected. Our database is dropped and recreated each evening while doing a download from the mainframe. So the SP was exported from the SPB before close of business Friday. Successfully used the batch file the SPB generated to recreate the stored procedure this morning. Only problem is, we can't modify it now! Friday's version of the code runs no matter how many changes we make to the code in the SPB.

    Looking on the server in the /functions/jars dir there appears to be old version of the procedures jar files. However, trying to run a CALL SQLJ.REMOVE_JAR('myProc_jar') doesn't work as it's telling us the jar name is invalid, even though we can see it on the server. I'm thinking this has something to do with the DB being dropped each evening???

    Only thing we have gotten to work is to recreate the SP with a DIFFERENT name through the SPB by using the wizard to create an SP from our existing java code. We can then modify it to our hearts content. But we need to use the name we were using before because some external programs already rely on that name.

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: Can't Update Java Stored Proc?

    Can you stop and start the instance ?

    If you are in development, setting the dbm config parameter KEEPDARI to NO makes better sense ..

    db2 get dbm cfg

    and look for the KEEPDARI parameter ...

    If it is YES, then
    db2 update dbm cfg using KEEPDARI NO

    With V7.2, you will have to stop and start your instance before the change comes into effect

    Cheers
    Sathyaram

    Originally posted by GTI337
    DBA is gone for the week and we're having issues updating a previously created java stored procedure. Using DB2 7.2.

    The SP was created through the SPB Friday. While working on the SP that day making changes worked as expected. Our database is dropped and recreated each evening while doing a download from the mainframe. So the SP was exported from the SPB before close of business Friday. Successfully used the batch file the SPB generated to recreate the stored procedure this morning. Only problem is, we can't modify it now! Friday's version of the code runs no matter how many changes we make to the code in the SPB.

    Looking on the server in the /functions/jars dir there appears to be old version of the procedures jar files. However, trying to run a CALL SQLJ.REMOVE_JAR('myProc_jar') doesn't work as it's telling us the jar name is invalid, even though we can see it on the server. I'm thinking this has something to do with the DB being dropped each evening???

    Only thing we have gotten to work is to recreate the SP with a DIFFERENT name through the SPB by using the wizard to create an SP from our existing java code. We can then modify it to our hearts content. But we need to use the name we were using before because some external programs already rely on that name.
    Visit the new-look IDUG Website , register to gain access to the excellent content.

Posting Permissions

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