Database Management Systems

This option starts up the database using the static non default attribute file to start up database.

When any changes are made to the database such as updates to data or creating or dropping database objects, the changes are recorded to the redo log files first.

The contents of the database buffer cache are written to datafiles on disk by the database writer background process.

Using this option, the oracle server waits for all currently connected users to disconnect their sessions.

Here, the database is responsible for validating user credentials.

Here, the sizes of the library cache and the data dictionary cache are not set individually and are automatically determined by the oracle server.

In the event when a user process is terminated abnormally, the process monitor background process cleans up the resources that were held by the user process.

The data files in a database contain all of the database data that the users of the database save and retrieve.

This option of STARTUP command can be used to abort the running instance and perform a normal startup.

Using this option, the oracle server automatically rolls back all currently active transactions.

Usually complete recovery up to the point of failure is possible if all archive files are possible.

This is managed in a manner that free blocks are always made available for new blocks being read into memory.

This is in turn made up the persistent area that contains bind information and a runtime area that is created as soon as an execute request is initiated.

These facilitate the oracle mechanism to recover from an instance failure or a media failure.

The database application issuing the distributed transaction is directly connected to the node acting as the global coordinator.