Oct 12, 2007 From an Oracle 10.x Fat client installation, copy tnsus.msb into c: oracle instantclient network mesg. This is the file that tnsping uses to 'lookup' the message text while running. At this point, you should be able to fire up PL/SQL Dev and still have things work. Okay, now the weird part starts. This happens because PL/SQL Developer is incapable of loading 64-bit version of oci.dll file. To fix this, download the 32-bit version of Oracle Instant Client, extract it to a directory such as instantclient. Next, configure PL/SQL Developer to use this version by clicking on Tool menus - Preferences. Connect to an Oracle database. After you install the matching Oracle client driver, you can connect to an Oracle database. To make the connection, take the following steps: From the Home tab, select Get Data. From the Get Data window that appears, select More (if necessary), select Database Oracle database, and then select Connect. Client Tools:: Unable To See Database List In Dropdown Of PL/SQL Developer Mar 27, 2013. I installed Oracle 11g client and set the ORACLEHOME and tnsadmin env variables.I installed the pl/sql developer, but unfortunately after installing, i am unable to see any database details in the drop-down list of pl/sql developer. View 4 Replies View.
- Pl Sql Developer Oracle Client Not Properly Installed Oracle Home Key Chain
- Pl Sql Developer Oracle Client Not Properly Installed Oracle Home Key Crack
Go Up to Database Connectivity (FireDAC)
Manycam old version for mac. This topic describes how to connect to Oracle Server.
- 2Client Software
- 2.1Windows Client Software
Supported Versions
The FireDAC native driver supports Oracle Enterprise, Standard (ex Workgroup), and Express (ex Personal) server editions version 8.0.3 and later. For detailed discussion on Oracle usage in FireDAC for the Delphi application, read the 'Using Oracle with FireDAC' chapter.
Client Software
Windows Client Software
FireDAC requires one of the following Oracle x86 or x64 client software types to be installed on the workstation:
- 'Fat' Oracle Client (details) -- It requires the standard install procedure. The driver uses the client that is installed in the primary Oracle Home, if not specified explicitly.
- 'Thin' Oracle Instant Client (details) -- The driver uses the client, which is either copied into a folder in the PATH or into the application EXE folder, if not specified explicitly. See 'Using Instant Client' below.
If the Oracle client software has not been installed properly, an exception is raised when trying to connect:
Using Instant Client
To install Instant Client, download the Oracle Instant x86 or x64 client archive, unpack it and copy the files:
- oci.dll
- oraocci11.dll
- oraociei11.dll
- orasql11.dll
in your application EXE folder or in a folder in the PATH.
When you are using TNS names, put the tnsnames.ora file in the same folder or set the TFDPhysOracleDriverLink.TNSAdmin property value to a folder path with tnsnames.ora or use the TNSAdmin driver configuration parameter.
Set TFDPhysOracleDriverLink.NLSLang to the required value or use the NLSLang driver configuration parameter.
macOS Client Software
FireDAC requires:
- the libclntsh.dylib x86 client library.
You can download it as Instant Client for macOS (here)
To install on Linux, read the following articles:
- Instant Client Installation - for basic Oracle Instant Client installation steps;
- SQL*Plus Instant Client - for advanced Oracle Instant Client configuration, including configuring language and TNS parameters.
Linux Client Software
To install the Linux client library:
- Install the libaio library:
- On Ubuntu Server 16.04 LTS, run:
sudo apt-get install libaio1
- On Red Hat Enterprise Linux 7, run:
sudo yum install libaio
- On Ubuntu Server 16.04 LTS, run:
- Install the Instant Client for Linux as described in any of the following articles:
- Instant Client Installation - for basic Oracle Instant Client installation steps.
- SQL*Plus Instant Client - for advanced Oracle Instant Client configuration, including configuring language and TNS parameters.
Driver Linkage
To link the driver:
- Drop a TFDPhysOracleDriverLink component from the 'FireDAC Links' palette page.
- Or include the FireDAC.Phys.Oracle unit in an uses clause.
Connection Definition Parameters
To connect to an Oracle DBMS, most applications require that you specify DriverID, Database, User_Name, and Password (see Defining Connection (FireDAC) for details).
DriverID=Ora
Parameter | Description | Example value |
---|---|---|
Database | The value can be one of the following:
|
|
OSAuthent | Specify Yes to use OS authentification, and No to use the DBMS authentification. | No |
User_Name | The Oracle user name, if OSAuthent=No | Scott |
Password | The Oracle user password, if OSAuthent=No | tiger |
AuthMode | The Oracle authentification mode:
| Normal |
ReadTimeout | Specifies the timeout value in milliseconds for the receive or read operations. Specifying zero means no timeout.
| |
WriteTimeout | Specifies the timeout value in milliseconds for the database server to complete a send operation to clients. Specifying zero means no timeout.
| |
CharacterSet | The character set for the connection. If not specified, the NLS_LANG variable value is used. |
|
BooleanFormat | Defines how to represent Boolean values:
| Choose |
ApplicationName | Name of the application. If specified, this value is stored in the V$SESSION column MODULE. | AllBooks |
OracleAdvanced | Additional Oracle session options. For details, see the ALTER SESSION SET chapter, the 'Initialization Parameters and ALTER SESSION' paragraph. A value format is - =[;..]. | |
NewPassword | Specifies the new Oracle user password. FireDAC connects to the DB using the old password and immediately changes it to the new one. | tiger2 |
MetaDefSchema | Specifies the default schema for the application. The design time code omits the schema name in object names if it is equal to MetaDefSchema. | SCOTT |
Use Cases
- Connect to a database using the predefined TNS name (stored in tnsnames.ora):
- Connect to a database using host, port, and instance name info:
When you are using TNS names, put the tnsnames.ora file in the same folder or set the TFDPhysOracleDriverLink.TNSAdmin property value to a folder path with tnsnames.ora or use the TNSAdmin driver configuration parameter.
Set TFDPhysOracleDriverLink.NLSLang to the required value or use the NLSLang driver configuration parameter.
macOS Client Software
FireDAC requires:
- the libclntsh.dylib x86 client library.
You can download it as Instant Client for macOS (here)
To install on Linux, read the following articles:
- Instant Client Installation - for basic Oracle Instant Client installation steps;
- SQL*Plus Instant Client - for advanced Oracle Instant Client configuration, including configuring language and TNS parameters.
Linux Client Software
To install the Linux client library:
- Install the libaio library:
- On Ubuntu Server 16.04 LTS, run:
sudo apt-get install libaio1
- On Red Hat Enterprise Linux 7, run:
sudo yum install libaio
- On Ubuntu Server 16.04 LTS, run:
- Install the Instant Client for Linux as described in any of the following articles:
- Instant Client Installation - for basic Oracle Instant Client installation steps.
- SQL*Plus Instant Client - for advanced Oracle Instant Client configuration, including configuring language and TNS parameters.
Driver Linkage
To link the driver:
- Drop a TFDPhysOracleDriverLink component from the 'FireDAC Links' palette page.
- Or include the FireDAC.Phys.Oracle unit in an uses clause.
Connection Definition Parameters
To connect to an Oracle DBMS, most applications require that you specify DriverID, Database, User_Name, and Password (see Defining Connection (FireDAC) for details).
DriverID=Ora
Parameter | Description | Example value |
---|---|---|
Database | The value can be one of the following:
|
|
OSAuthent | Specify Yes to use OS authentification, and No to use the DBMS authentification. | No |
User_Name | The Oracle user name, if OSAuthent=No | Scott |
Password | The Oracle user password, if OSAuthent=No | tiger |
AuthMode | The Oracle authentification mode:
| Normal |
ReadTimeout | Specifies the timeout value in milliseconds for the receive or read operations. Specifying zero means no timeout.
| |
WriteTimeout | Specifies the timeout value in milliseconds for the database server to complete a send operation to clients. Specifying zero means no timeout.
| |
CharacterSet | The character set for the connection. If not specified, the NLS_LANG variable value is used. |
|
BooleanFormat | Defines how to represent Boolean values:
| Choose |
ApplicationName | Name of the application. If specified, this value is stored in the V$SESSION column MODULE. | AllBooks |
OracleAdvanced | Additional Oracle session options. For details, see the ALTER SESSION SET chapter, the 'Initialization Parameters and ALTER SESSION' paragraph. A value format is - =[;..]. | |
NewPassword | Specifies the new Oracle user password. FireDAC connects to the DB using the old password and immediately changes it to the new one. | tiger2 |
MetaDefSchema | Specifies the default schema for the application. The design time code omits the schema name in object names if it is equal to MetaDefSchema. | SCOTT |
Use Cases
- Connect to a database using the predefined TNS name (stored in tnsnames.ora):
- Connect to a database using host, port, and instance name info:
- Connect to a local database as sysdba:
- Connect to a database using the TNS name and change the password:
- Connect to a database using the easy connect string:
See Also
Note:
This guide assumes that you plan to download SQL Developer and run it as a freestanding tool.
For information about operating system versions supported for Oracle JDK 8, see http://www.oracle.com/technetwork/java/javase/certconfig-2095354.html
.
Pl Sql Developer Oracle Client Not Properly Installed Oracle Home Key Chain
Katarina witt today. If you plan to use SQL Developer as part of an Oracle Database release installation, see the Oracle Database installation documentation.
Pl Sql Developer Oracle Client Not Properly Installed Oracle Home Key Crack
Please read the information in this chapter before you install Oracle SQL Developer. This chapter contains the following major sections: