Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Infosys
September, 2013
INFOSYS LIMITED
Bangalore
COPYRIGHT NOTICE
© 2013 Infosys Limited, Chandigarh, India. All rights reserved. Infosys believes the
information in this document is accurate as of its publication date; such information is subject
to change without notice. Infosys acknowledges the proprietary rights of other companies to
the trademarks, product names and such other intellectual property rights mentioned in this
document. Except as expressly permitted, neither this document nor any part of it may be
reproduced, stored in a retrieval system, or transmitted in any form or by any means,
electronic, mechanical, printing, photocopying, recording or otherwise, without the prior
permission of Infosys Limited and/or any named intellectual property rights holders under
this document.
Infosys Limited
Hosur Road
Electronic City, 3rd Cross
Bangalore 560 100
India.
Telephone: (91) (80)28520 261-270
Fax: (91) (80) 8520 362
Website: http://www.infosys.com
Project Details
Project(s) involved: CGEUITLZ
H/W Platform: Dell Machine
S/W Environment: Informatica Powercenter Worklfow Manager 9.0.1
Application Type: ETL Tool
Project Type: DW (FSI)
Target readers
Informatica tool developers and testers
Keywords
Informatica Powercenter Workflow Manager, Connection String, ODBC, SQL Server,
Odbc.ini
Introduction:
The document provides a brief overview of the “creating a relational ODBC connection for
the Microsoft SQL server type of connection and the corresponding entry of the connection
string in informatica server file odbc.ini”. Also it shows how we can edit the permissions for
the created connection and give the permissions to a particular connection.
To explain the purpose and need of creating a relational ODBC connection for MS SQL
Server type of connection, let’s discuss a scenario.
Scenario:
We can create an ODBC type of connection for MS SQL server type of connection in the cane
when we are facing some issue with the SQL server type of connection. This ODBC
connection would be compatible to SQL server type of connection in the same manner.
In Informatica when the Microsoft SQL Server Connection is not supported by the OS on
which informatica is running, and the Relational connection created in the powercenter is of
type ‘Microsoft SQL server’, at that time on running the session which is using the MS SQL
server type of connection, the error encountered is:
“The server does not support the database type specified on this OS platform.”
At such time create an ‘ODBC’ type of connection in your workflow manager instead of ‘MS
SQL Server’ type of connection.
But this doesn’t mean that you need to change your DSN too. Create the same Data source
driver of type ‘SQL Server’ for importing tables from MS SQL server database.
Just create the ODBC type of connection in the workflow manager for running the session.
For creating the ODBC Relational Connection you would also need to make an entry of your
connection string in the informatica server file ‘odbc.ini’ in order to make the entry of your
MS SQL server database and the schema. Then using this connection string we can connect
to the SQL server database from our informatica client.
This ‘connection string name’ that we gave in odbc.ini server file will be used for creating
the connection in Powercenter workflow manager.
Below example shows the details of an entry of the connection string in odbc.ini server file.
[connection_string_dev]
Driver=/users/pmserver9/ODBC6.0/lib/DWsqls24.so
Description=DataDirect 6.0 SQL Server Native Wire Protocol
Address= Microsoft SQL server Name
AnsiNPW=Yes
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=Database Name
WorkArounds2=2
In the above details, you should be aware of some of the basic things that are required for
creating the connection string entry in an informatica server file odbc.ini
Microsoft SQL Server Name – The name of the server on which the Database is
*Note – I have removed/made hidden the existing created relational connections and other
details for project security purpose.
In the next window select a Connection type as ‘ODBC’ from the dropdown and click
on ‘New’
Fill in all the required details for creating the new connection in the following screen.
Here in the below screenshot the ‘Connect String’ is the same name as that we have
given in the odbc.ini file. Use the same name as entered in the odbc.ini server file.
Click on Select other user and then choose the user from all the listed users as the
owner of the connection.
In this way we can create an ODBC connection which would be compatible to a Microsoft
SQL server connection, when we face an issue with the MS SQL server connection or when it
is not been supported by the OS.
*Note – I have removed/made hidden the existing created relational connections and other
details for project security purpose.
Reference(s):-
1. Project Experience
2. www.informatica.com