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

DB2 Admin client failing

P: n/a
I'm trying this again, after no response the first time. Any help will
be greatly; appreciated.

The db2 windows administrative client v8.1 fails after installation
(without error, on XP Pro)) whenever I try to start it in either Set-up
Tools/Configuration Assistant or Set-up Tools/First Steps with the
following message:

'The procedure entry point
?create@OSSHIPCQueue@@QAEIBPVOSSIPCQueResID@@I@Z could not be located in
the dynamic link library db2osse.dll.'

What did I miss?

Google has only three references to db2osse, none of which appear applicable

Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"Robert Stearns" <rs**********@charter.net> wrote in message
news:10*************@corp.supernews.com...
I'm trying this again, after no response the first time. Any help will
be greatly; appreciated.

The db2 windows administrative client v8.1 fails after installation
(without error, on XP Pro)) whenever I try to start it in either Set-up
Tools/Configuration Assistant or Set-up Tools/First Steps with the
following message:

'The procedure entry point
?create@OSSHIPCQueue@@QAEIBPVOSSIPCQueResID@@I@Z could not be located in
the dynamic link library db2osse.dll.'

What did I miss?

Google has only three references to db2osse, none of which appear applicable

Why don't you uninstall it and then install the latest version, which is
Fixpack 6.
Nov 12 '05 #2

P: n/a
Mark A wrote:
"Robert Stearns" <rs**********@charter.net> wrote in message
news:10*************@corp.supernews.com...
I'm trying this again, after no response the first time. Any help will
be greatly; appreciated.

The db2 windows administrative client v8.1 fails after installation
(without error, on XP Pro)) whenever I try to start it in either Set-up
Tools/Configuration Assistant or Set-up Tools/First Steps with the
following message:

'The procedure entry point
?create@OSSHIPCQueue@@QAEIBPVOSSIPCQueResID@@I @Z could not be located in
the dynamic link library db2osse.dll.'

What did I miss?

Google has only three references to db2osse, none of which appear


applicable

Why don't you uninstall it and then install the latest version, which is
Fixpack 6.

Thank you. That did the trick, but it dropped all the connections I'd
made with quest, which had to be restored.

What is the trick to setting username/password in the select database
dialogue in Command center interactive rather than having to type them
in on a connect statement? Control Center does prompt for them. Is there
a better source of documentation/help than "help" which is installed
with the product?

Another question: Is there a simple way to create a table like or
similar to an existing table? The predefined columns are all good and
well if you are doing traditional applications, but (and I'm sure you've
never heard this before :-) my application is non-traditional. Of course
there are some traditional components, but they're secondary.

Nov 12 '05 #3

P: n/a
> Thank you. That did the trick, but it dropped all the connections I'd
made with quest, which had to be restored.

What is the trick to setting username/password in the select database
dialogue in Command center interactive rather than having to type them
in on a connect statement? Control Center does prompt for them. Is there
a better source of documentation/help than "help" which is installed
with the product?

Another question: Is there a simple way to create a table like or
similar to an existing table? The predefined columns are all good and
well if you are doing traditional applications, but (and I'm sure you've
never heard this before :-) my application is non-traditional. Of course
there are some traditional components, but they're secondary.

Not sure about your password problem. But I think that if you grant the
authority needed in DB2 to your current Windows userid, then you may be able
to avoid keying it in when you connect.

There is a CLI command to create a table like another table, but you cannot
change any of the columns definitions:
CREATE TABLE table_name_2 LIKE table_name_1
See the SQL Reference manual.

Many years ago in the DB2 GUI, you could do a create table "like" another
(without actually creating the table) and then modify the columns you want
different in the GUI, and then finish the table create. Unfortunately that
feature (and many other GUI features) were dropped (I believe starting in
release 5), because they were written with native calls to DB2, and the DB2
call interfaces changed, so they dropped the old GUI completely.

You might want to try the db2look command that will produce the DDL for an
existing table or other object, make the changes you want and recreate
another table using the modified DDL. Unfortunately, this is not using the
GUI, just a DB2 command. See the Command Reference manual for details.
Nov 12 '05 #4

P: n/a
Mark A wrote:
Thank you. That did the trick, but it dropped all the connections I'd
made with quest, which had to be restored.

What is the trick to setting username/password in the select database
dialogue in Command center interactive rather than having to type them
in on a connect statement? Control Center does prompt for them. Is there
a better source of documentation/help than "help" which is installed
with the product?

Another question: Is there a simple way to create a table like or
similar to an existing table? The predefined columns are all good and
well if you are doing traditional applications, but (and I'm sure you've
never heard this before :-) my application is non-traditional. Of course
there are some traditional components, but they're secondary.


Not sure about your password problem. But I think that if you grant the
authority needed in DB2 to your current Windows userid, then you may be able
to avoid keying it in when you connect.

There is a CLI command to create a table like another table, but you cannot
change any of the columns definitions:
CREATE TABLE table_name_2 LIKE table_name_1
See the SQL Reference manual.

Many years ago in the DB2 GUI, you could do a create table "like" another
(without actually creating the table) and then modify the columns you want
different in the GUI, and then finish the table create. Unfortunately that
feature (and many other GUI features) were dropped (I believe starting in
release 5), because they were written with native calls to DB2, and the DB2
call interfaces changed, so they dropped the old GUI completely.

You might want to try the db2look command that will produce the DDL for an
existing table or other object, make the changes you want and recreate
another table using the modified DDL. Unfortunately, this is not using the
GUI, just a DB2 command. See the Command Reference manual for details.

Thanks for the quick reply. I thought that might be the password
problem. I'll try to create a windows user id like the db2 one on the
server and see if that works. It does seem a little odd that it works
properly in one function but not in the other.

I thought that might be the case with tables; it's not impossible, quest
can do it. How powerful is the GUI alter processor? Could you use it
after generating the base table, to make all your changes, or are you
limited to the SQL alter capability, even on an empty table?

Nov 12 '05 #5

P: n/a

"Robert Stearns" <rs**********@charter.net> wrote in message
news:10*************@corp.supernews.com...
Mark A wrote:
Thank you. That did the trick, but it dropped all the connections I'd
made with quest, which had to be restored.

What is the trick to setting username/password in the select database
dialogue in Command center interactive rather than having to type them
in on a connect statement? Control Center does prompt for them. Is there
a better source of documentation/help than "help" which is installed
with the product?

Another question: Is there a simple way to create a table like or
similar to an existing table? The predefined columns are all good and
well if you are doing traditional applications, but (and I'm sure you've
never heard this before :-) my application is non-traditional. Of course
there are some traditional components, but they're secondary.


Not sure about your password problem. But I think that if you grant the
authority needed in DB2 to your current Windows userid, then you may be able to avoid keying it in when you connect.

There is a CLI command to create a table like another table, but you cannot change any of the columns definitions:
CREATE TABLE table_name_2 LIKE table_name_1
See the SQL Reference manual.

Many years ago in the DB2 GUI, you could do a create table "like" another (without actually creating the table) and then modify the columns you want different in the GUI, and then finish the table create. Unfortunately that feature (and many other GUI features) were dropped (I believe starting in release 5), because they were written with native calls to DB2, and the DB2 call interfaces changed, so they dropped the old GUI completely.

You might want to try the db2look command that will produce the DDL for an existing table or other object, make the changes you want and recreate
another table using the modified DDL. Unfortunately, this is not using the GUI, just a DB2 command. See the Command Reference manual for details.

Thanks for the quick reply. I thought that might be the password
problem. I'll try to create a windows user id like the db2 one on the
server and see if that works. It does seem a little odd that it works
properly in one function but not in the other.

I thought that might be the case with tables; it's not impossible, quest
can do it. How powerful is the GUI alter processor? Could you use it
after generating the base table, to make all your changes, or are you
limited to the SQL alter capability, even on an empty table?

The DB2 Control Center GUI Alter is limited to what SQL can do. In DB2 LUW
the only change to columns you can make via SQL is to alter the length of a
varchar, even if there is no data in the table. This may change in version
8.2 (Stinger), but I don't recall the details.

Be forewarned that Quest very recently lost a major copyright infringement
lawsuit to CA (via their purchase of Platinum) and the Quest product for DB2
can no longer be purchased and licenses will not be renewed.
Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.