Could you please advise me, how to configure a DSN entry for SQL Azure on UNix AIX box with DataDirect 6.1 to connect from PowerCenter 9.1.0.
Aix Server: 10.10.10.10 : 2222
On this Port, ABCXYZ9PQR(Database Server name) Database is configured.
Database name: TestDatabase
Telent is working from application server. Telnet 10.10.10.10 2222 --> Connected
Able to connect to the SQL server from Windows.
Please advise me what are the tests do I need to perform, and configure the DSN entry in ODBC.ini.
Thanks,
Sarat
Below steps are necessary for configuring odbc:
Ensure that the env variables ODBCHOME & ODBCINI are set. These has to be set before Informatica Services are started. Else they wont get picked up.
configure DNS in obdc.ini file for the DB server.
Use ssgbodbc utility (download from mysupport site) to test if the odbc connection goes through
Copy the DNS name from the entry in odbc.ini variable and paste it in the Connection String section of the ODBC connection in Workflow Manager.
I'm not clear from your description though:
Can you clarify if the Informatica Services is installed on AIX box (10.10.10.10)? how did you configure the connection to azure on windows box?
-Sadagopan
Related
We have oracle oledb connections in SSIS packages that are working well on windows server 2008.
We moved them to windows server 2012 and installed the needed softwares. We installed oracle client (oraoledb driver), moved tnsnames.ora, ldap.ora and sqlnet.ora to %Oracle_Home%\Network\admin path, add %Oracle_Home% and %Oracle_Home%\bin to path variable.
But on server 2012 oracle connections are giving this error ORA-12541: TNS: no listener. Where as on server 2008 same oracle connections are working fine.
Looked so much across internet but found these solutions:
Check tnsnames.ora
Check listener is running
Check path variable contain oracle home, oracle_home\bin
I don't see a problem with tnsnames.ora because same file is present on both window servers. Correct path variables are also set. Listener is also running (since SSIS on server 2008 is connecting). And I am able to ping oracle db server from both machines.
Can anyone suggest anything that we may try.
To put a formal answer in here.
Basic troubleshooting steps with SSIS:
Use the database native tools to check connectivity
In this case for Oracle that is SQLPLUS.EXE
If you have an issue with native tools then it isn't an SSIS issue
Check that you can resolve the host by using PING <hostname>.
If that doesn't work try PING <ip address>
If ping works, check the port with TELNET <host> <port>
If that doesn't work, either the service is not listening or you need to get your network guys to open the port
This goes for any network service
i.e.
SQL Server (default port 1433)
a web server (default port 80 for unencrypted comms)
I can't tune ODBC connection in ODBC Data Source Administrator using IP or host name of server. Only with localhost using.
Although I can successfully ping the server via IP or host name.
Firewall is tuned-of.
OpenEdge 10.2B is installed at Win Server 2003
The error I got:
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver]Connection refused. Verify host name and port number ErrNum=10038
I am sssuming you clicked "Test Connect"? Is your database really named TEMP? That seems unlikely.
"Administrator" is also an unusual name for a user of the db. "sysprogress" is more typical (although you should certainly setup a non-default userid.)
So far you have shown roughly half of the configuration required to make this work. Your DSN setup isn't obviously wrong but if it does not match a running database that is listening on port 3333 at that IP address then you will get this error.
The next useful thing that you could do to clarify the problem is to show the database configuration and demonstrate that you have a properly configured broker running and listening for connections on port 3333.
check list：
1、you must start your openEdge database
$DLC/bin/_mprosrv {database-full-path} -L 8000 -c 350 -B 1000 -N TCP -S {Port} -n 100
2、check Firewalls rule
3、use userID : SYSPROGRESS password ：SYSPROGRESS to test odbc connect
I have spent 3 days now trying to figure out why I can't connect to my Oracle 12 database from a client machine. I have read lots of articles and Googling around but haven't been able to find a solution yet. I have tried everything possible and know of already. So I am hoping someone maybe able to point me in the right direction.
Here are some details:
Win7 x64 with Oracle 12c installed.
Windows Server 2012 R2 (client, yes this setup isn't ideal. will explain why later).
Windows Server 2012 R2 (domain controller)
All machines are VM's and part of a domain.
All VM's are running under ESXI 6.0
I can do the following without any issues:
Logon to oracle server.
ORCL is my oracle isntance (global database identifier).
6.1 run tnsping orcl
6.2 lsnrctl status (up and running)
6.3 stop and restart the listner service from the Windows Services snap-in.
6.4 sqlplus system/xyz#orcl
Connects w/o any problems.
6.5 Oracle SQL Developer can connect to ORCL
6.6 can ping client machine.
However I CAN NOT do the following:
Logon to client machine
7.1 copied tnsnames.ora from oracle server to this client machine and placed under [ORACLE_HOME]\network\admin where it should be. replaced "localhost" with the oracle sserver IP.
7.2 Using sqlplus system/xyz#orcl or Oracle SQL Developer to connect
I get TNS: no listener found.
7.3 can ping oracle server.
7.4 tnsping orcl (failed)
7.4 already disabled all firewalls (domain, private and public) on oracle server.
There shouldn't be any issues with firewalls or ports.
No matter what I do, I just can't connect from the client machine. Can someone tell me what I'm doing wrong? As a side note, I was not able to install Oracle 12c on Win2012R2. So I installed on a Win7x64. But eventually
all the VM's will run on Windows Server 2012R2. This setup is my home lab.
Thank you!
replaced "localhost" with the oracle sserver IP
It looks like the listener is only listening on localhost (127.0.0.1); you can confirm that with lsnrctl status, or with netstat -an | find "1521" (or your actual port number if you aren't using the default).
It isn't listening on the server's external IP address, so when you try to connect to post 1521 (or whatever you have configured) on that IP there is nothing there listening - which is why you get "no listener found".
You need to modify your listener.ora to either listen to both localhost and the server IP address, or to only listen to the external address. But the latter has side-effects - your existing connections and tnsnames.ora entries would need to change to refer to that address (or, even if it is static, a DNS name that resolves to that address), and your database may need to be modified so it knows the listener address to register against, via the LOCAL_LISTENER initialisation parameter. After changing the listener.ora you will need to bounce the listener, and you can then check netstat again.
I'm trying to setup a ODBC connection from a Windows XP/Pro (32bit) client to a MySQL database running on a CentOS 6.3 64bit server.
Both systems are on the same subnet.
I have Samba installed and working on the CentOS server.
I can map the server directory that contains the database tables on the XP system.
The DB server is fully updated on all packages.
I can login to the server with myid:mypw via ssh, a standard user. Same user can make SELECTS from the database.
Can not ssh to root on CentOS server, root is excluded in the ssh config.
When I try to run the ODBC Data Source Administrator on the XP client, on the Create a New
Data Source to SQL Server screen, I select using a login ID entered by the user. I'm
entering the same ID:pw I use to ssh into the server. At that point I get an error,
SQLState = '08001';
SQL Server error: 17;
SQL Server does not exist or access denied"
The Server name I'm entering for "Which SQL Server do you want to connect to?", I've entered the host name of the CentOS that is defined in the XP's /etc/host file. It does appear in the drop down list for that question.
I have installed unixODBC*, mysql-connector-odbc & libtool* packages via yum.
On the server, odbc -q -d returns: [MySQL]
odbcinst.ini includes lines for Driver | Setup | Driver64 | Setup64. The 64 versions do point to /usr/lib64.....
odbc.ini includes: [MyDSN} & Driver = MySQL ODBC 5.1 Driver
Any idea what I've missed so far? Am I running into 32/64 bit system issues? And if so how do I solve this, I will have both 32 & 64 bit users most of them on Windows 7/Pro 64 bit, a few stuck on XP/Pro 32 bit.
I'm a bit lost in this task, so some detailed instructions would be great.
Thanks in advance..
Assuming you have not made a mistake and you really want to access a MySQL database on a remote Centos based system from Windows using ODBC you'll need to install the MySQL ODBC Driver on your Windows machine. You cannot use the MS SQL Server driver to access MySQL. Once you've done that you create a MySQL ODBC data source (although you can use DSNless connections) and not a SQL Server DSN.
2 and 3 are irrelevant as the MySQL ODBC driver is capable of talking directly to your MySQL Database server over the network assuming your server is set up to listen for external connections.
5 is also irrelevant as you'll need a MySQL database username and password and you database needs to allow connections from your windows machine.
(9-12) You also do not need to install unixODBC of the MySQL connector on your Centos box unless you want to access that same MySQL database with an application running on Centos that uses ODBC. 10 just tells you you've got an entry in your odbcinst.ini file for the MySQL ODBC driver which you don't need. 11 is the same info. 12 is a MySQL ODBC DSN which you also don't need.
I am able to ping a database server from my machine but am having a hard time connecting. Should I be able to connect or could there be other network features that are getting in the way?
I am trying to connect with Oracle SQL developer to an Oracle 11g R2 database.
Here are the instructions to connect to database using sql developer
Know the port number on which database is listening (by default 1521)
Make sure you can telnet to the host and the port number
There are several ways, you can connect (BASIC, TNS, Advanced etc)
For Basic, you need to give host ip or resolvable name, port and sid or service name as part of the connect string. Similarly for JDBC you need to give valid JDBC url and also you are supposed to ojdbc jar file in the appropriate location of sql developer.