5/11/2021 0 Comments Oracle 12C Odbc Driver
The downloads that support Entity Framework deployment below do not contain design-time tools, only run-time support.To be able to use these existing data source attributes, copy the tnsnames.ora file in the ORACLEHOMEnetworkadmin directory from your previous Oracle Home installation to the same directory in your new installation.However, ODP.NET is supported with Visual Studio Express Edition.If you use distributed transactions with ODP.NET, Managed Driver, then only the OraMTS recovery service needs to be configured.
The recovery service can be configured by installing OraMTS or running the OraMTS recovery service utility, oramtsctl.exe. Consult the OraMTS documentation for instructions on creating the recovery service with the utility. Xcopy installation instructions are included with the download itself. ![]() OUI provides location information for these files from up to three other existing Oracle Homes if they exist. The.ora files can be customized if the new Oracle Home uses a different configuration from the previous Oracle Home from which the files were copied over. OUI will then automatically create the tnsnames.ora file. If no alias information is provided, no tnsnames.ora file will be created. Even if the user doesnt have all the database connection information readily available, Oracle recommends inserting placeholder values during the install process, then modifying the tnsnames.ora file later with actual values to replace the placeholders later. A typical directory for an OUI Oracle client Home is: C:app product12.1.0client1. To specify a data source, you can use the EZCONNECT format. In the ODP.NET data source attribute, use the following format to define how the client connects to the database server: host:portservicename. The alias definition contains all the information needed to create a connection to the database server. Alias information is stored in the tnsnames.ora file typically located in the ORACLEHOMENetworkAdmin directory. This alias is used as the data source value in your connection string. ODAC installations do not create a tnsnames.ora file so you need to create one. The following instructions assume you will have to create a new tnsnames.ora file. If the TNS entries in the ORACLEHOMEnetworkadmintnsnames.ora file are not recognized by the Oracle client, create a ORACLEHOMEoracle.key file using any text editor and type in the following line. For example, if the default Oracle Home location was used during the install, the proper entry for the oracle.key file would be the following: SOFTWAREORACLEKEYOraClient12chome1. For more information on using Multiple Oracle Homes with ODP.NET, Unamanged Driver, consult the ODP.NET documentation. Installing ODAC on top of an existing Oracle home may break existing Oracle applications. If you do install on top of an existing Oracle Home, make sure to stop all the Windows services using that Oracle Home (e.g. OracleMTSRecoveryService). Uninstall all the products in the existing Oracle Home before installing the new ODAC version. You must manually select the ODAC components to be installed during the install process (i.e. ODAC components to be installed). This is recommended for all ODAC components you wish to use, especially ODP.NET. However, if this is not desired, be sure to remove the policy DLLs from the GAC.
0 Comments
Leave a Reply. |