Can we connect to Oracle database from Unix system without OCCI? Is it necessary for a Instant Client to be installed to use the Database connection?
Kindly give suggestions.
Thanks
Related
My program uses ADO to connect to SQL Server in Visual C++ 2008. Now it seems that ADO is out-dated and MS recommends to use ODBC again.
Therefore, I now study how to use ODBC to connect to SQL Server. I see there is a class CDatabase that can do that. However, there are no good article in introducing how to use CDatabase to connect to SQL Server via ODBC.
Basd on my research, it seems one can connect to SQL Server via ODBC in the following way:
Via a direct connection string like this one:
Driver={SQL Server Native Client 11.0};Server=myServerAddress;
Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Using ODBC administrator to create a DSN(Data Source Name), and then connect with DSN.
THen if 1 works, why do we need to create DSN?
You don't need a ODBC DSN. A DSN simply allows one to externalize the ODBC configuration such that server name, driver. etc. can be configured in a common way for all ODBC applications.
It is not a requirement to use a DSN when you store connection string in an external file so that environment-specific values can be configured without code changes. Regardless of the technique used, be sure to protect secrets rather than storing as clear text.
In Informatica, What are the different ways to connect Unix server from Informatica Windows client?
If informatica server is sitting on Unix, you can create a command task with the following:
set >/tmp/informatica.task.out
And then check the output in your Unix file.
Also, you can run an ssh command from that machine to reach additional servers.
This is just a couple of thoughts from the top of the head.
I am newbie to VMware. When I am longing into the VCenter I am getting "Connection time out" in first 3 attempts, after 3 attempts I am able to Login to VCenter.
I did some troubleshoot and in vcenter changed the Client to server time extended to 300sec. But still I am facing same issue. Can anyone please help me how to resolve this issue.
Thanks in advance
Are you connecting by IP or hostname? Make sure DNS is OK. Are you using a standalone MSSQL server? Windows server built-in MSSQL? Is this VCSA (linux appliance)?
If Windows, did you reboot everything? Slowness within vCenter can indicate a sql issue of sorts. Check all applicable items for available resources, including disk space on all partitions.
PostgreSql Bulkloader step is applicable in local system and if so is it possible to implement this step for JNDI connection
If you are considering your LocalSystem as a Window's Machine, it didnt work for me where the db was in a linux machine and the pentaho was in windows. It has got some issues with dual OS. Check this issue. But ideally on a windows to windows db , bulk loader step should work.
But for a Linux System, it works fine. I am not sure about MacOS.
For JNDI Connection: You cannot use a JNDI database connection since its not supported.
Please check this link.
Hope this is what you are looking for :)
I'm pretty perplexed... I've got 5 different test computers, all relatively blank Windows XP machines running similar hardware specs. I run a silent install of the FireBird (Classic) database and my application. Some computers require "localhost:" (or 127.0.0.1) before the database location to make a connection, and some simply don't work at all! This is running the exact same software across the board. Does anybody have any suggestions as to what needs to happen to make the connection string universal, or what I could be doing wrong??
It's firebird version 2.1.1.17910 Classic
By the way, i tried connecting to the same database using FlameRobin (a small db management tool) and it worked just fine on the computers that don't connect.
Any more information necessary just let me know! Thanks a lot in advance
For anybody's future reference, the answer is in the services. Apparently it's not being registered as a service for some reason, and on the working computers, was at some point registered, probably through some sort of far earlier tests of Interbase is my best guess.
C:\Windows\System32\drivers\etc and opening up the file 'services' and adding the following line allows the server to run properly.
gds_db 3050/tcp
I'm not sure whether you are aware of that, but a connection string without "localhost:" or "127.0.0.1:" in front of the database name or alias will use the local protocol, which can't be used when connecting to Firebird Classic Server (see this link for more information). If a host name or IP address is given, then TCP port 3050 will be used for the connection.
If you have registered a server in FlameRobin, and did not leave the hostname field in the registration dialog blank, then the host name will be part of the connection string. That would explain why you can connect using FlameRobin.
As for the differences between the machines: You should first go to the Firebird Server Manager applet and make sure that the server is indeed running on all machines, and that the version is the same.
Does it have something to do with the hosts file on some of the computers? Or is that what you're referring to with your
Some computers require "localhost:" (or 127.0.0.1) before the database location...
comment?