Prophet Database Administration

Presentation Transcript

Prophet Database Administration CSCI E256 Session 7 Oracle Networking

Oracle Networks The capacity of Oracle Net is to build up and keep up associations between a customer application and an Oracle database server. Prophet Net has numerous correspondence layers that empower customers and database servers to share and change information.

TCP/IP The Transmission Control Protocol/Internet Protocol (TCP/IP) is the accepted standard Ethernet convention utilized for customer/server discussions over a system. TCP/IP empowers an Oracle application on a customer to speak with remote Oracle databases (if the Oracle database is running on a host framework that backings arrange correspondence utilizing TCP/IP).

Oracle Networks The correspondence engineering depends on the Open Systems Interconnection (OSI) demonstrate The OSI show utilizes a correspondence stack where data moves from one hub to the next, through a few layers of code

Communications Stack The idea of disseminated handling depends on the capacity of PCs isolated by both plan and physical area to impart and cooperate with each other. This is proficient through a procedure known as stack interchanges. Stack correspondences can be clarified by referencing the Open Systems Interconnection (OSI) display.

OSI URL More Information http://www.ietf.org/for data about the OSI stack

OSI Communications Stack

Oracle Client/Server Connections

Communications Stack Client Application The OSI layer nearest to the client, and is reliant on the usefulness asked for by the client. Presentation Ensures that information is spoken to in an organization that the application and session layers can suit. This incorporates monitoring language structure and semantics of the information exchanged between the customer and server.

Communications Stack Session Establishes, oversees, and ends organize sessions between the customer and server. This is a virtual pipe that conveys information solicitations and reactions. The session layer oversees whether the information activity can go in both headings in the meantime (offbeat), or in one and only bearing at once (synchronous). Transport Implements the information transport guaranteeing that the information is transported dependably.

Communications Stack Network Ensures that the information transported is directed through ideal ways, through a progression of interconnected sub-systems. Interface Provides solid travel of information over a physical connection. Physical Defines the electrical, mechanical, and procedural details for enacting, keeping up and deactivating the physical connection amongst customer and server.

OSI Stack

OSI Layers

Oracle Stack

Client Application Oracle customer applications give information presentation and application stream. The application recognizes database operations to send to the server and goes them through to the Oracle Call Interface (OCI).

Oracle Call Interface (OCI) Oracle Call Interface (OCI) code contains all the data required to start a SQL discourse between the customer and the server. It characterizes the calls made to the server Parse SQL explanations for linguistic structure approval Open a cursor for the SQL proclamation Close the cursor

Two-Task Common (TTC) This is Oracle " s execution of the presentation layer. TTC gives character set and information sort change between various character sets or arrangements on the customer and server. It performs change just when required At the season of introductory association, it figures out whether transformations are required for the two PCs to convey.

Oracle Net Oracle Net gives all the session and transport layer usefulness in an Oracle correspondence stack. It is in charge of building up and keeping up the association between the customer application and server, and trading messages between them. Prophet Net is additionally in charge of mapping session usefulness into industry-standard conventions.

Network Interface (NI) This layer gives a bland interface to Oracle customers, servers, or outside procedures to get to Oracle Net capacities. The NI layer handles the "break" and "reset" demands for an association. NI utilizes Network Naming (NN) to determine names to associate descriptors.

Network Session (NS) This layer gets demands from NI, and settles all bland machine-level availability issues, for example, the area of the server NS utilizes Network Route (NR) to course the system session to the goal and Network Authentication (NA) to arrange any verification prerequisites with the goal.

Oracle Protocols Oracle conventions are Oracle " s usage of the vehicle layer. Prophet conventions are in charge of mapping NS usefulness to industry-standard conventions utilized as a part of the customer server association. convention. Prophet conventions include: TCP/IP TCP/IP with SSL SPX

Network-Specific Protocols All Oracle programming in the customer server association handle requires a current system convention stack to make the machine-level association between the two machines for the vehicle layer. The system convention is capable just to get the information from the customer machine to the server machine, and soon thereafter the information is passed to the server-side Oracle convention.

Oracle Program Interface (OPI) Oracle Program Interface (OPI) plays out a correlative capacity to that of the OCI. It is in charge of reacting to each of the conceivable messages sent by the OCI. For instance, an OCI ask for to get 25 lines would have an OPI reaction to give back the 25 pushes once they have been brought.

Bequeath The Bequeath convention empowers customers that exist on an indistinguishable machine from the server to recover data from the database without utilizing the audience. The Bequeath convention inside produces a committed server prepare for every customer application. Hand down is utilized for neighborhood associations where an Oracle customer application, for example, SQL*Plus, speaks with an Oracle server running on a similar machine

Oracle Network Oracle Net, Net8(Oracle8) and SQL*Net V2 (Oracle7) are utilized to interface a customer to a server The customer is the application, in either a two-level or 3-level engineering The server is the framework where the database is found Oracle Net and SQL*Net V2 are Oracle instruments

Oracle Network The Oracle Net programming should be introduced on both customer and the server, for 2-level applications. It is a piece of the RDBMS establishment 3-Tier or online applications needn't bother with Oracle Net programming introduced on the customer

Java Application Connections

Web Connections

Listener Connection

Client/Server

Oracle Network The Oracle Net programming must be introduced on the Application Server and the Database Server, for 3-level applications Oracle Net is likewise used to interface appropriated databases

Application Server

Server to Server

Oracle Networks The Oracle Net for forms Oracle10g and Oracle11g, bolsters associations with databases running renditions 7.3.4 or higher Each protest in a database is exceptionally recognized by it's proprietor and it's name With equivalent words we discovered that the completely qualified question name, incorporated the server name and the case name, the proprietor and the question's name

Oracle Networks Oracle Net depends on a progression of arrangement records The principle document is the tnsnames.ora document It is as a matter of course situated in the/$ORACLE_HOME/organize/administrator registry From Oracle8i onwards, we have to utilize the TNS_ADMIN shell variable

Oracle Networks This variable indicates the area of the tnsnames.ora record. It can likewise be put away in a general index, as/var/pick/prophet or/and so on

Architecture The 3 primary documents for Oracle Net and SQL*Net V2 are Tnsnames.ora Listener.ora Sqlnet.ora They are situated in the catalog recognized by the TNS_ADMIN variable resound $TNS_ADMIN /u01/application/prophet/item/11.1.0/organize/administrator

Architecture The sqlnet.ora holds a portion of the parameter settings for sql*net The listener.ora record indicates the arrangement of the audience The tnsnames.ora record characterizes the sid-mappings used to interface with a database. It is utilized by both the customer and server, to interface with the database

Application Server

Tnsnames This record can hold associate descriptors to numerous databases The interface descriptor indicates the interchanges convention, server name and the occasion name

Connect Descriptors Every database requires an interface descriptor. An associate descriptor depicts the area of the system audience and the framework identifier (SID) of the database to which to interface. Database interface descriptors usually comprise of two segments: the audience ADDRESS the database SID

Connect Descriptors CLASS.HARVARD.EDU = - This is a false name ( DESCRIPTION = (ADDRESS = (COMMUNITY = TCP.edu) (PROTOCOL = TCP) (Host = kermit.dce.harvard.edu) (Port = 1521)) (CONNECT_DATA = (SID = E256)))

Tnsnames The convention is TCP The HOST kermit.dce.harvard.edu, is completely qualified The default port is 1521, another decision is 1526. These are the default ports that Oracle Net employments. You can pick you possess, for security

Tnsnames CLASS.HARVARD.EDU is an administration name or assumed name All the administration names with their related interface descriptors are put away in the tnsnames.ora record. All administration names must be exceptional inside the tnsnames document

Tnsnames To associate with a database utilizing the client scott and the secret word tiger, utilize the accompanying