I will appreciate for the following information.
I just created a DSN (Data Source Name) for ODBC connection to SQL Server daatabase. Now I want to see the tables that exist in the database and import the metadata for some of the tables.
However, in the import Metadata (ODBC) screen I dont see the DSN just created in the dropdown box.
How do I see the tables?
Appreciate your help.
Thanks in advance.
ODBC DSN setup
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Have you made an entry in the uvodbc.config file (in the project directory) of the following form?
The space either side of "=" is mandatory.
Code: Select all
<MyDatabaseServer>
DBMSTYPE = ODBC
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.
Thanks Ray. I have not made any changes to uvodbc.config yet. Do I also have to modify odbc.ini file?ray.wurlod wrote:Have you made an entry in the uvodbc.config file (in the project directory) of the following form?The space either side of "=" is mandatory.Code: Select all
<MyDatabaseServer> DBMSTYPE = ODBC
Bhusan
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Yes, you also need to define the DSN in .odbc.ini; I assumed that you had done that when you claimed to have "created a data source name".
How DID you "create a data source name" on a UNIX machine if you didn't edit .odbc.ini?
How DID you "create a data source name" on a UNIX machine if you didn't edit .odbc.ini?
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: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You are trying to configure ODBC access from DataStage to SQL Server.
DataStage is running on UNIX (according to your original post).
There is NO Control Panel for UNIX !
So it all has to be done with ini files and the like (just like ancient versions of Windows!).
The DataStage engine is the client. The DSN must be set up on the client's machine.
Setting up a DSN on the Windows machine where SQL Server is running only allows Windows clients from that machine to access SQL Server; it is no help at all for remote clients (whether on Windows or UNIX).
I hope this is now clearer.
The automatic behaviour you describe relates to uvodbc.config, not to .odbc.ini. You must always manually edit the .odbc.ini file on UNIX.
DataStage is running on UNIX (according to your original post).
There is NO Control Panel for UNIX !
So it all has to be done with ini files and the like (just like ancient versions of Windows!).
The DataStage engine is the client. The DSN must be set up on the client's machine.
Setting up a DSN on the Windows machine where SQL Server is running only allows Windows clients from that machine to access SQL Server; it is no help at all for remote clients (whether on Windows or UNIX).
I hope this is now clearer.
The automatic behaviour you describe relates to uvodbc.config, not to .odbc.ini. You must always manually edit the .odbc.ini file on UNIX.
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.
Thank you.
I had created in Windows. After I read your reply I went through the DS manuals and got my answer fully. I thank you very much and appreciate your help.ray.wurlod wrote:You are trying to configure ODBC access from DataStage to SQL Server.
DataStage is running on UNIX (according to your original post).
There is NO Control Panel for UNIX !
So it all has to be done with ini files and the like (just like ancient versions of Windows!).
The DataStage engine is the client. The DSN must be set up on the client's machine.
Setting up a DSN on the Windows machine where SQL Server is running only allows Windows clients from that machine to access SQL Server; it is no help at all for remote clients (whether on Windows or UNIX).
I hope this is now clearer.
The automatic behaviour you describe relates to uvodbc.config, not to .odbc.ini. You must always manually edit the .odbc.ini file on UNIX.