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 > Error with Mixed Case Passwords in Federation (DB2 9.5.4 on AIX)

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-18-09, 01:57
Ashwin@DB2 Ashwin@DB2 is offline
Registered User
 
Join Date: Sep 2009
Posts: 7
Red face Error with Mixed Case Passwords in Federation (DB2 9.5.4 on AIX)

Hi Everybody,

We are facing a problem while creating a nickname. The Server definition is created successfully using the following command:-

db2 connect to federatedDB user user1 using Password1

db2 "create server XYZDBserver type DB2/UDB VERSION 9.5 WRAPPER DRDA AUTHORIZATION "user" PASSWORD "passwd" OPTIONS (ADD DBNAME 'XYZDB',FOLD_ID 'L', FOLD_PW 'L')"

When we try to create a nickname we get the following error:-

DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
SQL1101N Remote database "XYZDB" on node "<unknown>" could not be accessed with the specified authorization id and password. SQLSTATE=08004

When we changed the password from Password1 to password1 then the nickname was created successfully. Creating a user mapping also solved the problem.

However since both the databases are on the same server our client, is it absolutely neccessary to create a user mapping? Is there any way we can create a nickname without changing the password or creating a user mapping?

Regards
Ashwin
Reply With Quote
  #2 (permalink)  
Old 12-18-09, 03:08
stolze stolze is offline
Registered User
 
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
The problem is that you enclose the whole CREATE SERVER statement in double-quotes and also enclose the nested password in double-quotes without escaping the quotes. Therefore, the shell interprets all double-quotes and does not pass them to DB2. So DB2 sees a non-quoted password and converts it to upper case, of course.

You have a few different choices:
- properly escape the double quotes inside your statement
- use single quotes to escape the whole statement (but then you just shift the problem to the server OPTIONS)
- execute the statement directly in a DB2 shell
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
Reply With Quote
  #3 (permalink)  
Old 12-18-09, 05:15
Ashwin@DB2 Ashwin@DB2 is offline
Registered User
 
Join Date: Sep 2009
Posts: 7
Thanks a ton Stolze, it worked!!!
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