Hi Experts,
I have made a new SQL server database connection by editing the .odbc.ini and uvodbc.config files.
Entry:
[RockfaceET_PROD]
Driver=/opt/IBM/InformationServer/Server/branded_odbc/lib/VMmsss23.so
Description=DataDirect SQL Server Wire Protocol driver
Database=EE2SQL
LogonID=******
Password=******
Address=sodium,1433
QuotedId=No
QEWSD=2455182
AnsiNPW=No
But I am getting an error while ODBC metadata import.
Error:
DSR.MetaGeta(GET.DSNINFO)(SQLConnect('RockfaceET_PROD','wiproee')) : BCI Error :
SQLSTATE=28000,CODE=18456,[DataStage][SQL Client][ODBC][IBM(DataDirect OEM)][ODBC SQL Server Driver][SQL Server]Login failed for user 'wiproee'.
Search is not helping... Please help.
SQL Server database connection not working
Moderators: chulett, rschirm, roy
Googled for your SQLSTATE & CODE. Perhaps these help:
http://dba.stackexchange.com/questions/ ... d-for-user
or
http://www.sqlserverblogforum.com/2012/ ... ep-failed/
http://dba.stackexchange.com/questions/ ... d-for-user
or
http://www.sqlserverblogforum.com/2012/ ... ep-failed/
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Some corrections for your connection.
1) The login id and password are not used by DataStage and can be removed. This is the first place hackers go to find id's and passwords and is a huge security breach. DataStage supplies its id / password information at connection time from the stage or connector (usually derived from parameters and/or environment variables) and ignores what is in the file.
2) The QEWSD entry is a marker inserted by the drivers to show illegal use of the drivers by products other than DataStage. The DataDirect drivers are licensed for use only with DataStage, and insert that marker anytime they detect that the driver is not being used by a job or agent. If enough connections are marked with QEWSD the ODBC drivers will stop working. Unfortunately the debug / test programs that come with the drivers will cause this marker to be inserted when you are debugging a connection. Assuming your debugging attempts caused this to be inserted, I'd suggest removing the entire line from the definition.
3) Either the password being supplied for the import is incorrect or the id has been locked due to too many failed attempts. Per #1, don't assume the id and password listed in the .odbc.ini file is correct since it isn't used.
All documentation for the DataDirect drivers is located in $DSHOME/../branded_odbc/docs in pdf format that can be loaded down to your PC.
1) The login id and password are not used by DataStage and can be removed. This is the first place hackers go to find id's and passwords and is a huge security breach. DataStage supplies its id / password information at connection time from the stage or connector (usually derived from parameters and/or environment variables) and ignores what is in the file.
2) The QEWSD entry is a marker inserted by the drivers to show illegal use of the drivers by products other than DataStage. The DataDirect drivers are licensed for use only with DataStage, and insert that marker anytime they detect that the driver is not being used by a job or agent. If enough connections are marked with QEWSD the ODBC drivers will stop working. Unfortunately the debug / test programs that come with the drivers will cause this marker to be inserted when you are debugging a connection. Assuming your debugging attempts caused this to be inserted, I'd suggest removing the entire line from the definition.
3) Either the password being supplied for the import is incorrect or the id has been locked due to too many failed attempts. Per #1, don't assume the id and password listed in the .odbc.ini file is correct since it isn't used.
All documentation for the DataDirect drivers is located in $DSHOME/../branded_odbc/docs in pdf format that can be loaded down to your PC.
Last edited by asorrell on Mon Dec 09, 2013 11:00 am, edited 3 times in total.
