IBm DB2 licensing Error


Sequencing Toad for Oracle Application, but db2 related shortcut are not launching on verification machine.

As ODBC data source administrator shows TACM251 driver is not marked
to provide licensing info i have used following command

C:\Program Files\Quest Software\Toad for Data Analysts 2.5.1\SQLLIB\BIN>db2licm.
exe -a "c:\Program Files\Quest Software\Toad for Data Analysts 2.5.1\SQLLIB\lic

db2licm: Problem retrieving message number 1416 in db2lic.mo

it gives me above error please suggest me

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 11 years ago
Red Belt
Have you tested whether or not your install works outside of an AppV bubble? I ask because I packaged a DB2-dependent product a while ago and the DB2 end of things was a chuffin' nightmare. Documentation on IBM's web site was at best opaque and the vendor was used to installing either to pre-existing instances or to installing and using their product with users as members of the local Administrators group!

In short, you have to tell DB2 that a local user is allowed to futz with the database, which includes licensing. See the notes on the hoops I had to jump through with this wonderous product here. There's a link in those notes to the DB2 Express note, too. Lastly, if you're using a "proper" DB2 instance rather than a local one, you'll probably have to liaise with the DB2 DBAs about which groups have access to the database(s) and how to set up for that scenario. Knowing what I do about DBAs, I wish you good luck with that!
Posted by: shreedhar.ghare 11 years ago
Senior Yellow Belt
Hi VBScab
Answer to your first question is IBM DB2 works fine outside of an AppV bubble
i have captured licensing info but it shows driver are not marked.

Even if below command (Help) gives me same error
C:\Program Files\Quest Software\Toad for Data Analysts 2.5.1\SQLLIB\BIN>db2licm.exe -h

db2licm: Problem retrieving message number 1416 in db2lic.mo

Is this error related with virtual environment?
Posted by: amar.secunia 11 years ago
Yellow Belt
In some db2 releases like v9.7 nodelock file is a soft link back to ../../install/license, because of this reason you get the 'LIC1416N' error.

so because of soft link, its not allow to write nodelock file.

solution :

go into ../sqllib/license and type 'presto nodelock'

now you can try to add the License
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ