Database Management Systems

It ensures that the if the transaction fails due to the power failure or system crash, then its effect will remain in the system.

This component of the RMAN environment is a copy of the primary database that is updated using archived logs created by the primary database.

During the execution phase, if more than one channel is allocated, then RMAN can execute certains commands in parallel so that all of the channel's target database sessions are concurrently executing an RPC call.

This classification of the degree of durability avoids the problem of lost transactions.

Here, a transaction commits as soon as it commit log record is written to stable storage at the primary site.

This RAID level is known as memory-style error correcting-code organization.

It is a block of RMAN job commands that is stored in the recovery catalog.

It includes archived redo logs and flashback logs.

This component of the RMAN environment contains the metadata that RMAN uses to perform its backup and recovery operations.

A transaction can lock a data item in exclusive mode only if it is not locked at all.

The node that originates the distributed transaction.

Here, the net server middleware is able to connect its pure java clients to many different databases.

This allows a direct call from the client machine to the DBMS server and is a practical solution for intranet access.

ODBC binary code and in many cases database client code must be loaded on each client machine that uses JDBC-ODBC Bridge plus ODBC driver.

JDBC works on top of ODBC and then we have something called as a JDBC-ODBC bridge to access the database.