Oracle Thin Client For Mac
Go Up to Database Connectivity (FireDAC)
This topic describes how to connect to Oracle Server.
- 2Windows Client Software
Oracle Thin Client Macos
Oracle Virtual Desktop Client for Android 1.2. Following the end of life of Sun Ray Software, Oracle Virtual Desktop Client for Android is no longer available on the Google Play Store. Sun Ray Connector for Citrix XenDesktop 1.1. Download Sun Ray Connector for Citrix XenDesktop 1.1 from the Sun Ray Software 5.2 or later Media Pack on the Oracle. Setup and sign in. Download and install the IDrive Thin Client application on your Windows or Mac machine. Manage backups by signing in to your account from the IDrive web interface. All computers connected to your IDrive account appear in the Computers tab in the web interface. Backup and restore. The Oracle JDBC thin driver uses a java based implementation of the SQLNET protocol (JavaNet layer). Unlike the JDBC OCI driver, the SQLNET trace is not available with the JDBC thin driver at the client side for Oracle JDBC Driver versions.
Is there a way to setup a thin client for Apple OSX server? I have Ncomputing but there device does not support apple any ideas? This is going to be setup in a library that can have up to 8 people access The Apple OSX Server at once. Oracle Java Client. Oracle JDBC/THIN Interfaces. Oracle Internet Directory Client. Oracle Call Interface (OCI) Oracle Programmer. Oracle XML Development Kit. Oracle Advanced Security. OLAP Analytic Workspace Manager and Worksheet. Oracle Connection Manager. Oracle Net Listener. Oracle Multimedia Client Option.
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 Object Pascal application, read the 'Using Oracle with FireDAC' chapter.
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.
Linux Client Software
FireDAC requires:
- the libclntsh.so x86 or x64 client library.
To install on Linux, read the article.
Mac OS X Client Software
FireDAC requires:
- the libclntsh.dylib x86 client library.
Oracle Thin Client For Mac Os
You can download it as Instant Client for Mac OS X (here) (more). Then extract and copy the content to the /usr/local/lib folder, using the commands:
You can put tnsnames.ora and sqlnet.ora to /etc folder, using the command:
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
Bully scholarship edition ps2 download torrent. /virtualbox-os-x-el-capitan-iso-download.html. To connect to an Oracle DBMS, most applications will require you to specify DriverID, Database, User_Name, and Password.
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 |
CharacterSet | The character set for the connection. If not specified, the NLS_LANG variable value is used. |
|
BooleanFormat | Defines how to represent Boolean values:
| String |
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 - <option>=<value>[;..]. | |
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 |
Usage 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: