By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,004 Members | 1,222 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,004 IT Pros & Developers. It's quick & easy.

Problems with performing db2updv8 on database in db2

P: n/a
Hi

I am trying to create a federated database using information
integrator. When I tried creating wrapper on by right clicking on
"Federated database objects" which appears under every database, I get
the following error:

[IBM][CLI Driver][DB2/NT] SQL0444N Routine
"SYSPROC.GET_WRAP_CFG_C"
(specific name "GET_WRAP_CFG_C") is implemented with code in
library or path
"\db2dsproc", function "getWrapperXMLFiles" which cannot be
accessed. Reason
code: "4". SQLSTATE=42724

The federated database has not been updated to the current
version.
Use the db2updv8 utility to update this database.

I performed db2updv8 command on the database, restarted the db2admin
and also did db2start but I still keep getting the same error.

Any suggestions as to what I may be doing wrong?

I am using the following on Windows XP machine.
================================================== ==========
About DB2 Administration Tools Environment
================================================== ==========
DB2 administration tools level:
Product identifier SQL08020
Level identifier 03010106
Level DB2 v8.1.7.445
Build level s040812
PTF WR21342
================================================== ==========
Java development kit (JDK):
Level IBM Corporation 1.4.1
================================================== ==========

Thanks
Mahesh

Apr 19 '06 #1
Share this Question
Share on Google+
10 Replies


P: n/a
Mahesh S wrote:
Hi

I am trying to create a federated database using information
integrator. When I tried creating wrapper on by right clicking on
"Federated database objects" which appears under every database, I get
the following error:

[IBM][CLI Driver][DB2/NT] SQL0444N Routine
"SYSPROC.GET_WRAP_CFG_C"
(specific name "GET_WRAP_CFG_C") is implemented with code in
library or path
"\db2dsproc", function "getWrapperXMLFiles" which cannot be
accessed. Reason
code: "4". SQLSTATE=42724


I've seen this error message before and it occurred when someone tried to
use federated features on a DB2 Personal Edition - where it is not
supported. Which DB2 edition are you running? (db2licm -l will tell you
that)

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Apr 19 '06 #2

P: n/a
Hi Knut

Thanks for the information. Yes, I am using DB2 PE. Guess I will have
to get some other version. Any suggestions? Could you please suggest
the version that I need to use to get the federated features definitely
working?

Thanks a lot

Mahesh

Apr 20 '06 #3

P: n/a
In article <11**********************@v46g2000cwv.googlegroups .com>,
ma********@gmail.com says...
Hi Knut

Thanks for the information. Yes, I am using DB2 PE. Guess I will have
to get some other version. Any suggestions? Could you please suggest
the version that I need to use to get the federated features definitely
working?


Db2 Express-C is the free DB2 version with federated db support.
You can download it from
http://www-306.ibm.com/software/data.../download.html
Apr 20 '06 #4

P: n/a
hey

thanks..

i assume that i will still need to download and install information
integrator seperately.. or is it included in this version of db2?

thanks
mahes

Apr 20 '06 #5

P: n/a
In article <11**********************@e56g2000cwe.googlegroups .com>,
ma********@gmail.com says...
hey

thanks..

i assume that i will still need to download and install information
integrator seperately.. or is it included in this version of db2?

thanks
mahes


For defining wrappers to DB2 UDB LUW (Linux, Unix, Windows) you don't
need DB2 II. I'm not sure about DB2 z/OS.
Apr 20 '06 #6

P: n/a
Mahesh S wrote:
hey

thanks..

i assume that i will still need to download and install information
integrator seperately.. or is it included in this version of db2?


If you want to access DB2 or Informix databases only, then you don't need
II.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Apr 20 '06 #7

P: n/a
OK.. At this point, I am looking at accessing only DB2 databases. So,
thats good news.

Any tutorials available for bringing together multiple DB2 databases
with the same structure (but present in multiple locations) under one
roof?

I apologise for troubling you.

Cheers
Mahesh

Apr 20 '06 #8

P: n/a
Hi Gert

I do have one more query. Hope I am not troubling you too much.

I have successfully created wrappers for two db2 databases located in
different locations. The thing is, they have the exact same structure
but storing different data. I have a table named Patient which stores
patient details pertaining to that location. What I would like to do
is have a single table that would combine records present in the two
db2 tables located in different locations. I am not talking of a join
here but more of sticking records from one table at the end of records
from another table. How do I go about doing that?

Thank you for your time.

Regards
Mahesh

Apr 20 '06 #9

P: n/a
Mahesh S wrote:
Hi Gert

I do have one more query. Hope I am not troubling you too much.

I have successfully created wrappers for two db2 databases located in
different locations. The thing is, they have the exact same structure
but storing different data. I have a table named Patient which stores
patient details pertaining to that location. What I would like to do
is have a single table that would combine records present in the two
db2 tables located in different locations. I am not talking of a join
here but more of sticking records from one table at the end of records
from another table. How do I go about doing that?


You have to create two nicknames. One points to the table in database A and
the other to the table in database B. Then you create a view over both
nicknames and UNION the results:

CREATE NICKNAME n1 FOR server1.schema.table
CREATE NICKNAME n2 FOR server2.schema.table
CREATE VIEW v AS
SELECT * FROM n1
UNION ALL
SELECT * FROM n2

If you still want to distinguish where the data came from, just put this
into the view definition (this is just plain and simple SQL):

CREATE VIEW v AS
SELECT 'n1' AS source, n1.* FROM n1
UNION ALL
SELECT 'n2' AS source, n2.* FROM n2

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Apr 20 '06 #10

P: n/a
thats great man.. it worked.. thanks a lot..

Apr 20 '06 #11

This discussion thread is closed

Replies have been disabled for this discussion.