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 > DB2 migration from 7.2 to 8.1 stored procedure problem

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-22-04, 11:19
casaben casaben is offline
Registered User
 
Join Date: Apr 2004
Posts: 2
DB2 migration from 7.2 to 8.1 stored procedure problem

We have been able to restore a database backup made on DB 7.2 in DB2
8.1. But now, while trying to rebuild the stored procedures which
reside
in our database, we receive the following error :

Error: -rootpkgname value must be between 1 and 7 characters

And the build fails.

If we look at the packagename we see this is 8 characters long (e.g.
S1234567).
This was no problem in the previous DB2 7.2 version. Just changing the
package name (by deleting the last
character) doesn't resolve the issue, we just get a different error :

[IBM][CLI Driver][DB2/NT] SQL20204N The user defined function or
procedure "UBENCH.UBS_SALE_GETDATA" was unable to map to a single Java
method. LINE NUMBER=6. SQLSTATE=46008

and the build fails, no matter how many methods there are in the Java code...

We use DB2 8.1.5 Enterprise Edition for Windows, running on Windows
2000
Server SP4.
Reply With Quote
  #2 (permalink)  
Old 04-27-04, 04:02
mitait mitait is offline
Registered User
 
Join Date: Mar 2004
Location: Finland
Posts: 22
I'm not sure the packagename really is the problem. At least if I take a look at the db2 package names we have they are all 8 characters and build is working fine in 8.1.5 after restore/migrate from 7.2.8. (on nt 4.0 sp6). Yet I'm not sure the rootpgkname really refers to db2 stored procedure package names... does it?

However we also had big problems with build at first. Errors however where different and compiler related. We ended up upgrading the c++ compiler. (visual c++ 5.0 does not work anymore, 6.0 seems to be required)
Reply With Quote
  #3 (permalink)  
Old 04-27-04, 04:06
casaben casaben is offline
Registered User
 
Join Date: Apr 2004
Posts: 2
Migration problems

Mhh, same problems here...we'll try upgrading the compiler, Thanks for the tip !
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