can we install informatica server and client in one machine?
I am facing issues with configuring the odbc for informatica. Can anyone please let me know how to configure it.
Yes, you could install the PowerCenter client on the same machine as the server.
To enable Oracle connectivity via ODBC you will need to install and configure the Oracle Instant Client (or equivalent). Once you have a connect string from your tnsnames.ora file you can configure an ODBC connection using the Data Sources (ODBC) configuration page (assuming you are using Windows).
Related
I have installed Oracle Client when I try to connect Oracle DB receiving a TNS no listener error message, I did not found oracleoraClient11g_home1tnslistener service on my machine. could you please advise on this.
is oracleoraClient11g_home1tnslistener part of Oracle11g Client installation?
is oracleoraClient11g_home1tnslistener need to be configured manually?
You installed the Client software.
But, is there a database on your computer? If not, you should first install the database and - once you do it - you don't need the Client software because the Server already contains all that stuff (and more).
That's what
I did not found oracleoraClient11g_home1tnslistener service on my machine
suggests - listener is installed along with the database.
If you're in doubt which database to install, I'd suggest the Oracle 11g Express Edition (XE) as it is easy to install (in a few Next clicks), contains a pre-installed HR (Human Resources) schema so you can test your skills immediately, comes with Application Express (Apex) - a really nice piece of software to start with.
I've installed win64_11gR2 client from here http://www.oracle.com/technetwork/topics/winx64soft-089540.html. I want to install sql developer. I understand that I'll have to use sql developer 2.1 or later. I do not see network/admin folder after 11gR2 installation to put my tnsnames.ora file. Any document/guidance to install/config sqldeveloper with this client will be appreciated. Thanks.
You don't need win64_11gR2 client to run SQDeveloper.
Also you don't need to configure tnsnames,ora file to connect to the database from SQL Developer
Just download SQL Developer, run it, add Database Connection and connect.
See this tutorial: http://st-curriculum.oracle.com/tutorial/SQLDeveloper/index.htm
I am buiding an internet web application using c# ASP.NET. I am using my own computer to develop the application. I've installed the oracle database on my computer. In order to deploy this application on the server, does the server have to install oracle client? I already included Oracle.DataAccess.dll in the bin folder.
Yes it does, assuming you're connecting to the database on the same server!
For example, you can connect to remote databases, but the point is where ever the database lives (server or PC), it will need Oracle installed.
The web server you will deploy your application to does not need to have Oracle server but it must have the Oracle client installed (Instant client for instance) + you will have to deploy your database to the Oracle server
My course requires me to connect to an Oracle database server at the university for my project. I am provided with a url (like oracle.xyz.edu) and username and password. How can I connect to the database from Visual Studio. I have only dealt with SQL Server 2008. I don't know how to go ahead with setting up the database. I tried to install Oracle Instant Client, but could not find a setup exe to install. The instant client download zip consists of a set of files. Where can I find the steps to connect to Oracle database from VS.
Do you need to use the Oracle Instant Client? Or would it be acceptable to you to download and install the full version of the Oracle client?
The full version of the Oracle client is generally what ought to be installed on a developer machine. The Instant Client is a very slimmed down version of the client that is designed for developers to distribute along with their Windows applications on machines that do not have or need any way to access the database other than via the application. As a developer, I'd strongly recommend the full version of the Oracle client if only because it includes various additional utilities like SQL*Plus and SQL*Loader.
The full Oracle client is available for download from OTN on the same page that the database is available. For example, the Oracle 11.2 client for 64-bit Windows is a 615 MB download on the OTN site.
Don't use ODBC. Use ODP.NET (Oracle's Instant Client) Oracle Data Provider for .NET. (Read technical notes in provided link.)
I have a freshly built 64-bit Windows Server 2008 R2 box that I have installed 64-bit Coldfusion 9 Standard on. I've upgraded and hotfixed it up to the most current version of CF. I also had 64-bit Oracle 11g (11.1.0.7.0) Client installed on the box. I've created a System DSN using the 64-bit ODBC Data Source Administrator in Windows and can successfully test the connection of the data source.
All of these installations went smoothly, however, when I went to add a datasource in the Coldfusion Administrator I receive the error:
Connection verification failed for data source: myDatabaseName
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
I am having a hard time understanding exactly where this architecture mismatch is coming from since the box is entirely 64-bit. I see while looking at all the processes that are running, some related CF processes are running in 32-bit (Verity related processes, SOLR and CFDotNetSVC). I am not sure if those could cause this issue but I am at a loss to explain were this mismatch would come from otherwise.
Anyone have any ideas?
Using Dan's advice I grabbed a JDBC Driver from Oracle here:
http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-111060-084321.html
I then moved the JAR (ojdbc6.jar in my case) and added it to my Coldfusion Class Path.
Determining the correct settings for using the datasource to Coldfusion was slightly harder but here are the settings I ended up going with:
JDBC URL: jdbc:oracle:thin:#//dbsrv.mydomain.com:1521/myDB.world
Driver Class: oracle.jdbc.driver.OracleDriver
Driver Name: Oracle Thin Driver
Then the username and password for the DB.
Sure enough it worked like a charm.
Dan, I want to give you a check mark because you definitely put me in the right direction, but I can only mark one correct.
I believe you need to either step down to the 32-bit drivers, or use native JDBC drivers to connect to Oracle successfully. My suggestion would be to go the JDBC route, and connect directly through a native Oracle JDBC driver by using the "other" selection on the Datasource screen. You'll get better performance that way, and have more control over your connection via ColdFusion.
Connecting to Oracle information in ColdFusion Livedocs.
i found an alternate way to do this
install the ODBC drivers for 64bit and 32bit (in that order) on your win2008 64bit OS
thereafter create the DSNs on both the System32 folder and SysWow64 folder by running the odbc32ad32.exe
ensure your tnsnames are setup fine in the respective network/admin folder (if you use tnsnames to maintain your sids)
now on the CF admin you creaet a new ODBC source with aODBC Socket and name. the next page should show you a drop down of all DSNs that exists in the 64bit DSN setup. When you go and test it in CF, it will strangely use the config of the 32bit DSN setup for validationb
voila....your connections should work. No worries of those architectural failures etc
We needed to setup 64 bit ODBC connections for a ColdFusion 11 server to query against 2012 SQL Server instance on Windows 2008 R2 Server. The ODBC connections would show up but would never work. We received so many various messages when verifying such as "needing SSL connections to work" and also timeout messages as it was having problems logging into SQL Server.
I stumbled across this post and we decided to follow setting up 64bit ODBC connections and then effectively overwriting them--preserving the name using the 32bit ODBC. Thank you again fellow developers, especially Souzam! My instructions are below:
For Windows 2008R2 Server you must disguise 64bit ODBC socket configurations for 32 bit in order for them to appear in CF Admin as datasources (obvious bug in CF 11):
Creating 64bit ODBC connections via 2008 R2 ODBC application, follow a naming convention that will allow you to recall in 32 bit configuration.
Configure ODBC 32bit connection in SYSWOW64 (C:\Windows\SysWOW64) using the odbcad32.exe using the previous 64bit names in Step #1.
Create data sources in CF Admin as these should appear in a dropdown when creating ODBC Socket Type connections.