Package not found



IBM's flagship relational database management system

Package not found

Postby p19689 » Wed Dec 01, 2010 9:44 pm

Hi , I have an error :
DBRM or Package name 'SUBSYSTENMANE.PACKAGE_1.Consistancey_token_1' was not found in
plan 'PLAN1'.

When I checked the Catalog there are 2 version of operable packages exist for PACKAGE_1.
PACKAGE_1 (version 1) bind under db2 8 - With Consistancy_Token_2
PACKAGE_1 (version 2) Bind under Db2 9 (current version) - With Consistance_Token_3
( Above consistance tokens were extracted from admin tool - under precompiler infor)
When I checked the PLAN1, It has package_1 (Version 1) bound.


My Question is why did I get -805 instead of -818. I thought the package is there but it's a incorrect pakage. Can you advice Please ?
p19689
 
Posts: 65
Joined: Fri Oct 01, 2010 1:13 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Package not found

 

Re: Package not found

Postby GuyC » Wed Dec 01, 2010 10:37 pm

well, according to you there is no package with Consistancey_token_1.

Select name,version,contoken from sysibm.syspackage where name = 'PACKAGE_1'
will show you if it's true.
I can explain it to you, but i can not understand it for you.
GuyC
 
Posts: 315
Joined: Tue Aug 11, 2009 3:23 pm
Has thanked: 1 time
Been thanked: 4 times

Re: Package not found

Postby p19689 » Fri Dec 03, 2010 3:37 pm

Thanks for the reply. If there is No pakage with Consistancy_token_1 , I thought it should come with ( -818) consistancy token mismatch as It has a packages with consistancy_token_2 and 3 for the same package name (PACKAGE_1). Where I am wrong here !

I have issued the query but CONTOKEN field came with unreadable format. Do I need to convert it to some other format ?
p19689
 
Posts: 65
Joined: Fri Oct 01, 2010 1:13 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Package not found

Postby GuyC » Fri Dec 03, 2010 5:13 pm

you can use hex(contoken)

primary key of a package = collid,name,contoken or collid,name,version
thus different contoken = different package. => -805

This is a standard confusion: Most site let DB2 decide the Version and this looks like a timestamp (but really isn't)
so each time you precompile you get a new VERSION.

But you can also specify the VERSION in the precompile options.
so each time you precompile your version (and contoken) remain the same. f.e IBM sometimes uses fixpack numbers or APARnumbers as Version.

Somewhere in the DBRM there is also a real timestamp_precompile.
and if this is different you get -818
I can explain it to you, but i can not understand it for you.
GuyC
 
Posts: 315
Joined: Tue Aug 11, 2009 3:23 pm
Has thanked: 1 time
Been thanked: 4 times

Re: Package not found

Postby p19689 » Mon Dec 06, 2010 7:54 pm

Hi , thanks for the reply and it explains my question.
I thought if we need vesioning we always have to use precomplier options. How can you get version without precompile options ?
Thanks very much for your excellent explanation earlier !
p19689
 
Posts: 65
Joined: Fri Oct 01, 2010 1:13 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Package not found

Postby iamamainframer » Wed Mar 09, 2011 7:32 pm

if you bind your dbrm to package and token doesn't match then -805 and
if you bind your dbrm to plan and token doesn't match then -818
iamamainframer
 
Posts: 7
Joined: Sun Feb 27, 2011 11:54 am
Has thanked: 1 time
Been thanked: 0 time


Return to DB2

 


  • Related topics
    Replies
    Views
    Last post