But it translates your application's clumsy SQL into elegant network packets. It encrypts your data mid-flight. It finds the database across subnets and firewalls and virtualized chaos. It retries dead connections. It pools, it arrays, it negotiates, it whispers.
Similarly, the Client runs (Database Resident Connection Pooling) or its own local pools. Creating a database connection is like forging a sword—expensive and slow. The Client keeps a quiver of pre-forged connections, handing them out to threads in milliseconds. The War on Eavesdropping (Native Encryption) In the old days, SQL*Net sent passwords in the clear. A network tap meant total compromise. The 19c Client fights back with Native Network Encryption and SSL/TLS via TCPS. It wraps every SQL statement, every fetched credit card number, in a shroud of AES256. To a packet sniffer, the traffic looks like a waterfall of noise. The War on Incompatibility (Version Skew) Here lies the Client’s greatest trick: Backward compatibility . An Oracle 19c Client can talk to an Oracle 8i database from 1998. It knows the old authentication protocols. It emulates the ancient cursor behaviors. It is a time traveler, fluent in every dialect of Oracle SQL*Net ever spoken. oracle database client 19c
Inside the OCI layer, the Client maintains a state machine for every connection. It knows if a transaction is active. It knows if a LOB locator is open. It knows if the session is in ALTER SESSION mode. When an application crashes without calling OCITransCommit or OCILogoff , the Client does not just drop the socket. It sends a to the database, a polite "I am dying; please roll back my work." But it translates your application's clumsy SQL into
It has no UI. It writes no logs unless asked. It accepts no glory. It retries dead connections
FINDB = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = db-server.finance.gov)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = finprod)) ) This is the Client’s map. It resolves human concepts ("FINDB") into a network pilgrimage: a TCP handshake to port 1521, a negotiation of the SQL*Net protocol, and a connection to a specific service. If the database is a fortress, the Client is the messenger who knows the secret knock. The Client does not merely connect. It protects . The War on Latency (Array Fetching & Connection Pooling) A naive application asks the database for one row at a time. The Client laughs at this. It hoards rows in its internal buffers, returning them in batches. The arraysize parameter is not a setting; it is a battle plan. With one round trip, the Client brings back 100, 500, or 5000 rows. The network sighs in relief.