- Oracle Thin Client For Mac Os
- Oracle Thin Client Macos
- Oracle Thin Client For Mac High Sierra
- Oracle Thin Client For Macbook
- Oracle Thin Client For Mac Catalina
Go Up to Database Connectivity (FireDAC)
This topic describes how to connect to Oracle Server.
The Oracle Virtual Desktop Client application runs on an ordinary PC or tablet and provides a Sun Ray session in a desktop window. It is supported and can be installed on Windows, Linux, Mac OS X, iPad, and Android. An Oracle Virtual Desktop Client supports most of the standard Sun Ray Client functionality. Instead of relying only on a Sun Ray Client for session access, a user can install and run the Oracle Virtual Desktop Client.
- 2Windows 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 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
Oracle Thin Client For Mac Os
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:
Oracle Thin Client Macos
- the libclntsh.dylib x86 client library.
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
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 - =[;...]. | |
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:
See Also
Oracle Thin Client For Mac High Sierra
Explains how to run Oracle Universal Installer to perform most database client installations.
- Guidelines for Installing Oracle Database Client
In most cases, Oracle Universal Installer provides a graphical user interface (GUI) to install Oracle Universal Installer to install Oracle Database Client. However, you can also use Oracle Universal Installer to complete silent or response file installations, without using the GUI. - Procedure for Installing Oracle Database Client
Review the procedure in this topic for installing Oracle Database Client.
Guidelines for Installing Oracle Database Client
In most cases, Oracle Universal Installer provides a graphical user interface (GUI) to install Oracle Universal Installer to install Oracle Database Client. However, you can also use Oracle Universal Installer to complete silent or response file installations, without using the GUI.
This method is particularly useful if you need to perform multiple installations of Oracle Database Client.
Oracle Thin Client For Macbook
As you install Oracle Database Client, follow these guidelines:
Do not use Oracle Universal Installer from an earlier Oracle product release to install components from this release.
Use the same installation media to install Oracle Database Client on all supported Windows platforms.
If you reinstall Oracle software into an Oracle home directory where Oracle Database Client is already installed, then you must reinstall any components that were installed before you began the reinstallation.
Do not modify the Java Runtime Environment (JRE) except by using a patch provided by Oracle Support Services. Oracle Universal Installer automatically installs the Oracle-supplied version of the JRE. This version is required to run Oracle Universal Installer and several Oracle assistants.
If you encounter errors during installation, click Help.
Products not installed by default, in case of Custom installation:
Oracle SQLJ
Oracle Database Utilities
Oracle Java Client
SQL *Plus
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 Net
Oracle Connection Manager
Oracle Net Listener
Oracle Multimedia Client Option
Oracle ODBC Driver
Oracle Clusterware High Availability API
Oracle SQL Developer
Oracle Scheduler Agent
Oracle Services for Microsoft Transaction Server
Oracle Administration Assistant for Windows
Oracle Provider for OLE DB
Oracle Data Provider for .NET
Oracle Providers for ASP .NET
Procedure for Installing Oracle Database Client
Review the procedure in this topic for installing Oracle Database Client.
Oracle Thin Client For Mac Catalina
- Log in to Windows as an Administrator user. If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.
- Navigate to the location of the installation media for Oracle Database Client, open a command prompt with administrator privileges, and run the
setup.exe
command. Use the same installation media to install Oracle Database on all supported Windows platforms. - In the Select Installation Type screen, select the type of installation that you want: Instant Client, Administrator, Runtime, or Custom and click Next.
- Starting with Oracle Database 12c Release 1 (12.1), during installation, you can specify an Oracle Home User associated with the Oracle Database home on the Specify Oracle Home User screen. The Oracle home user owns all the Windows services run by the Oracle Database software. You can either specify an existing Windows user, or have the installer create the user for you. The Oracle Home User and several database services with the proper Access Control Lists (ACLs) are configured during installation. Select Use Windows Built-in Account if you do not specify an Oracle Home User during installation. Then the services for the Oracle home run as the LocalService or LocalSystem user. The Oracle Home User is not available if you select Instant Client as the type of installation.
- In the Specify Installation Location screen, enter the following details:
Oracle Base: This path appears by default. You can change the path based on your requirement.
The Oracle Base section is not displayed if you select Instant Client as the type of installation.
In the Software Location section, accept the default value or enter the Oracle home directory path in which you want to install Oracle components. The directory path must not contain spaces. Click Next.
- If you selected Custom as the type of installation, then the Available Product Components screen is displayed. Select the products that you want to install and click Next.
Note:
Starting with Oracle Database 11g Release 2 (11.2), you can install Oracle Connection Manager, Oracle Net Listener, Oracle Scheduler Agent, and Oracle Services for Microsoft Transaction Server using the Custom install option. - If you selected Oracle Scheduler Agent as one of the components to install, then the Oracle Database Scheduler Agent screen is displayed with the default host name and default port number. Enter the Scheduler Agent Hostname and the Scheduler Agent Port Number. Click Next.
- The Perform Prerequisite Checks screen verifies if your computer meets the minimum system requirements to install the desired product. Click Next.
Note:
Oracle recommends that you use caution in checking the Ignore All option. If you check this option, then Oracle Universal Installer may not confirm that your system is able to install Oracle Database successfully. - Review the information displayed in the Summary screen, and click Install.
Note:
Starting with Oracle Database 11g Release 2 (11.2), you can save all the installation steps into a response file by clicking Save Response File. Later, this file can be used for a silent installation. - The Install Product screen shows the progress of a client installation. After Oracle Database Client is installed, click OK.
- If you perform a Custom installation, then select Oracle Net Listener from the list of components.
- In the Finish screen, click Close to exit Oracle Universal Installer.
Related Topics