An Oracle database is an object-relational database management system produced and marketed by the Oracle Corporation. It supports heterogeneous data. We can stack our data here. It has the following two main parts: Oracle Database Server Oracle Client; Oracle Database Server This is where your data is saved. 1.1 Installation Overview. The Oracle Database Client installation process consists of five steps: Read the release notes: Read the Oracle Database 10g release 2 (10.2) release notes before you begin the installation. The release notes are available with the platform-specific documentation.
Oracle client is needed to access multiple data sources from the different client tool (PL SQL Developer, TOAD). Here we are using ansible tool to deploy oracle client into the multiple servers at a time.
![Oracle client for windows Oracle client for windows](/uploads/1/2/6/3/126342040/934263251.jpg)
Note: Please modify all necessary configuration files based on your own environment.
This article describes the installation of Oracle Database Client 19c 64-bit on Oracle Linux 7 (OL7) 64-bit.
Oracle Installation Prerequisites: Database Installation Guide for Linux(https://docs.oracle.com/en/database/oracle/oracle-database/19/ladbi/index.html)
Setup:OS: OEL 7.5Ansible: ansible 2.7.6
Oracle Software: Download the Oracle software from OTN or MOS depending on your support status. Oracle binaries are staged from the 'edelivery: Oracle Database 19c Software (64-bit)'. They have to be manually downloaded and made available for this article to apply
- Install Oracle Database SoftwareOracle DBA - Automation with Ansible (Install Oracle 19c Database Software)
Steps: 1 :Stage Oracle Client software (Oracle Database 19c Client (19.3) for Linux x86-64 - LINUX.X64_193000_client.zip ) from edelivery.oracle.com.2 :Unpack Oracle Client Software3 :Install Oracle Client Software4 :Validation - Connect to SQLPLUS binary.
Summary commands:
- Clone this repository:git clone https://github.com/asiandevs/OracleDBAwithAnsible
- Stage the following Oracle Software on the control machinehttps://www.oracle.com/technetwork/database/enterprise-edition/downloads/oracle19c-linux-5462157.htmlOracle Database 19c Client (19.3) for Linux x86-64 - LINUX.X64_193000_client.zip
- Configure an Ansible inventory file (example as below)[root@oel75 ansible]# cat ansible.cfg | grep inventoryinventory = ./inventory[root@oel75 ansible]# cat inventory[ora-x1]192.168.56.102
Note: Modify variables according to your requirements. Add TNS entry according to your databases.
-->DBMS-based drivers are used with data sources such as Oracle or SQL Server that provide a stand-alone database engine for the driver to use. These drivers access the physical data through the stand-alone engine; that is, they submit SQL statements to and retrieve results from the engine.
![Installation Installation](http://help.prognoz.com/en/mergedProjects/setup/uiwebsetup/serverconfig.png)
Because DBMS-based drivers use an existing database engine, they are usually easier to write than file-based drivers. Although a DBMS-based driver can be easily implemented by translating ODBC calls to native API calls, this results in a slower driver. A better way to implement a DBMS-based driver is to use the underlying data stream protocol, which is usually what the native API does. For example, a SQL Server driver should use TDS (the data stream protocol for SQL Server) rather than DB Library (the native API for SQL Server). An exception to this rule is when ODBC is the native API. For example, Watcom SQL is a stand-alone engine that resides on the same machine as the application and is loaded directly as the driver.
DBMS-based drivers act as the client in a client/server configuration where the data source acts as the server. In most cases, the client (driver) and server (data source) reside on different machines, although both could reside on the same machine running a multitasking operating system. A third possibility is a gateway, which sits between the driver and data source. A gateway is a piece of software that causes one DBMS to look like another. For example, applications written to use SQL Server can also access DB2 data through the Micro Decisionware DB2 Gateway; this product causes DB2 to look like SQL Server.
The following illustration shows three different configurations of DBMS-based drivers. In the first configuration, the driver and data source reside on the same machine. In the second, the driver and data source reside on different machines. In the third, the driver and data source reside on different machines and a gateway sits between them, residing on yet another machine.