SQL Server connections
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 50
- Joined: Wed Jul 14, 2004 7:56 am
SQL Server connections
Hi all,
I am currently hitting an error in the DataStage Manager > Import > Table Definitions > ODBC Table Definitions >
DSR.MetaGeta(GET.TABLES)(SQLConnect('MYS_SIEBEL_DB','MIFactBase')): BCI Error:
SQLSTATE=IM003,CODE=0,[DataStage][SQL Client]An unknown DBMS type has been specified
SQLSTATE=IM997,CODE=0,[DataStage][SQL Client]An illegal configuration option was found
Below are the .odbc.ini file that is configured:-
[KOREA_DB]
Driver=/u01/app/Ascential/DataStage/branded_odbc/lib/VMmsss19.so
Description=DataDirect SQL Server Wire Protocol
Database=DB_MI_TEST
LogonID=pcakorea
Password=pcakorea
Address=128.231.160.65,1433
QuotedId=Yes
AnsiNPW=Yes
[MYS_SIEBEL_DB]
Driver=/u01/app/Ascential/DataStage/branded_odbc/lib/VMmsss19.so
Description=DataDirect SQL Server Wire Protocol
Database=ESG_MLY_PS01
LogonID=MIFactBase
Password=abcd1234
Address=18.37.20.20,1433
QuotedId=Yes
AnsiNPW=Yes
The connection to the KOREA_DB works perfectly fine. Why does MYS_SIEBEL_DB encounters an error? Please help!!
I am currently hitting an error in the DataStage Manager > Import > Table Definitions > ODBC Table Definitions >
DSR.MetaGeta(GET.TABLES)(SQLConnect('MYS_SIEBEL_DB','MIFactBase')): BCI Error:
SQLSTATE=IM003,CODE=0,[DataStage][SQL Client]An unknown DBMS type has been specified
SQLSTATE=IM997,CODE=0,[DataStage][SQL Client]An illegal configuration option was found
Below are the .odbc.ini file that is configured:-
[KOREA_DB]
Driver=/u01/app/Ascential/DataStage/branded_odbc/lib/VMmsss19.so
Description=DataDirect SQL Server Wire Protocol
Database=DB_MI_TEST
LogonID=pcakorea
Password=pcakorea
Address=128.231.160.65,1433
QuotedId=Yes
AnsiNPW=Yes
[MYS_SIEBEL_DB]
Driver=/u01/app/Ascential/DataStage/branded_odbc/lib/VMmsss19.so
Description=DataDirect SQL Server Wire Protocol
Database=ESG_MLY_PS01
LogonID=MIFactBase
Password=abcd1234
Address=18.37.20.20,1433
QuotedId=Yes
AnsiNPW=Yes
The connection to the KOREA_DB works perfectly fine. Why does MYS_SIEBEL_DB encounters an error? Please help!!
-
- Participant
- Posts: 50
- Joined: Wed Jul 14, 2004 7:56 am
Hi,
if your actually connecting to a SQLServer DB for your siebel despite the driver saying: hey it's not!
check you configured it correctly.
I'm not sure if a class A IP should be an issue.
Is the KOREA_DB connection working properly?
if your actually connecting to a SQLServer DB for your siebel despite the driver saying: hey it's not!
check you configured it correctly.
I'm not sure if a class A IP should be an issue.
Is the KOREA_DB connection working properly?
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
-
- Participant
- Posts: 50
- Joined: Wed Jul 14, 2004 7:56 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It might be the class A IP address. Can you ping 18.37.20.20 from the DataStage server machine? Given that both databases are SQL Server, and that they are identically configured (same driver, same port) it's got to be something about the connectivity. Also check that MYS_SIEBEL_DB really is using port number 1433.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 50
- Joined: Wed Jul 14, 2004 7:56 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
OK, we've eliminated one possibility (assuming you tested Query Analyzer from the DataStage server machine).
Next is to try to figure out what is meant by "An unknown DBMS type". Can you enable ODBC tracing for this particular DSN, and try once again to connect. You will gather a huge amount of information, so disable tracing as soon as you're done.
Next is to try to figure out what is meant by "An unknown DBMS type". Can you enable ODBC tracing for this particular DSN, and try once again to connect. You will gather a huge amount of information, so disable tracing as soon as you're done.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 50
- Joined: Wed Jul 14, 2004 7:56 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
That, and the absolute requirement to have a space either side of the "=" character, are well-known annoyances. (It's not only in DataStage, however; for example most database's bulk loader control scripts must also have that final line-terminator, as an indicator that a command is ended.) Well done for finding it! Did you - on the point of giving up - re-type the enture uvodbc.config file entry?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 50
- Joined: Wed Jul 14, 2004 7:56 am