Explore topic-wise InterviewSolutions in .

Some of the common RMAN errors are:

RMAN-20242: Specification does not MATCH any archivelog in the recovery catalog.

Add to RMAN SCRIPT: SQL 'alter SYSTEM archive log CURRENT' .

RMAN-06089: archived log xyz not found or out of sync with catalog.

Execute from RMAN: change archivelog all validate;

Some of the common RMAN errors are:

RMAN-20242: Specification does not match any archivelog in the recovery catalog.

Add to RMAN script: sql 'alter system archive log current' .

RMAN-06089: archived log xyz not found or out of sync with catalog.

Execute from RMAN: change archivelog all validate;

Oracle provide the following TOOLS/ UTILITIES to assist with performance monitoring and tuning:

• TKProf
• UTLBSTAT.SQL and UTLESTAT.SQL - BEGIN and end stats monitoring
• Statspack
• Oracle ENTERPRISE Manager: Tuning Pack

Oracle provide the following tools/ utilities to assist with performance monitoring and tuning:

The following high-level TUNING indicators can be used to establish if a database is performing optimally or not:

• Buffer Cache Hit RATIO.

FORMULA: Hit Ratio = (LOGICAL READS - Physical Reads) / Logical Reads.

Action: Increase DB_CACHE_SIZE (DB_BLOCK_BUFFERS prior to 9i) to increase hit ratio.

• Library Cache Hit Ratio.

Action: Increase the SHARED_POOL_SIZE to increase hit ratio.

The following high-level tuning indicators can be used to establish if a database is performing optimally or not:

Formula: Hit Ratio = (Logical Reads - Physical Reads) / Logical Reads.

Action: Increase DB_CACHE_SIZE (DB_BLOCK_BUFFERS prior to 9i) to increase hit ratio.

Action: Increase the SHARED_POOL_SIZE to increase hit ratio.

A break GROUP is used to display one RECORD for one group ONES. While multiple related records in other group can be DISPLAYED.

A break group is used to display one record for one group ones. While multiple related records in other group can be displayed.

False.

False.

A query record group is a record group that has an ASSOCIATED SELECT statement. The columns in a query record group DERIVE their default names, DATA TYPES, had lengths from the database columns referenced in the SELECT statement. The records in query record group are the rows RETRIEVED by the query associated with that record group.

A query record group is a record group that has an associated SELECT statement. The columns in a query record group derive their default names, data types, had lengths from the database columns referenced in the SELECT statement. The records in query record group are the rows retrieved by the query associated with that record group.

A RECORD GROUP can have an unlimited number of COLUMNS of type CHAR, LONG, NUMBER, or DATE provided that the total number of column does not EXCEED 64K.

A record group can have an unlimited number of columns of type CHAR, LONG, NUMBER, or DATE provided that the total number of column does not exceed 64K.

REPORT 2.5 is OBJECT ORIENTED.

Report 2.5 is object oriented.

Run_product is a built-in, USED to INVOKE ONE of the supported oracle tools products and SPECIFIES the name of the document or module to be run. If the CALLED product is unavailable at the time of the call, Oracle Forms returns a message to the operator.

Run_product is a built-in, Used to invoke one of the supported oracle tools products and specifies the name of the document or module to be run. If the called product is unavailable at the time of the call, Oracle Forms returns a message to the operator.

Show_lov, List_values.

Show_lov, List_values.

Oracle exports are "logical" database backups (not physical) as they extract data and logical definitions from the database into a file. Other backup strategies normally back-up the physical data files.

One of the ADVANTAGES of exports is that one can selectively re-import TABLES, however one cannot roll-forward from an RESTORED EXPORT file. To completely restore a database from an export file one practically needs to recreate the entire database. Always do full system level exports (FULL=YES). Full exports include more information about the database in the export file than user level exports.

Oracle exports are "logical" database backups (not physical) as they extract data and logical definitions from the database into a file. Other backup strategies normally back-up the physical data files.

One of the advantages of exports is that one can selectively re-import tables, however one cannot roll-forward from an restored export file. To completely restore a database from an export file one practically needs to recreate the entire database. Always do full system level exports (FULL=YES). Full exports include more information about the database in the export file than user level exports.

Restoring involves copying backup files from secondary storage (backup media) to disk. This can be done to replace damaged files or to copy/move a DATABASE to a new location. Recovery is the process of applying REDO logs to the database to roll it FORWARD. One can roll-forward until a specific point-in-time (before the disaster occurred), or roll-forward until the last transaction recorded in the log files. Sql> connect SYS as SYSDBA Sql> RECOVER DATABASE UNTIL TIME '2001-03-06: 16: 00: 00' USING BACKUP CONTROLFILE;

Restoring involves copying backup files from secondary storage (backup media) to disk. This can be done to replace damaged files or to copy/move a database to a new location. Recovery is the process of applying redo logs to the database to roll it forward. One can roll-forward until a specific point-in-time (before the disaster occurred), or roll-forward until the last transaction recorded in the log files. Sql> connect SYS as SYSDBA Sql> RECOVER DATABASE UNTIL TIME '2001-03-06: 16: 00: 00' USING BACKUP CONTROLFILE;

A HOT backup is a backup PERFORMED while the database is online and AVAILABLE for read / write. Except for ORACLE exports, one can only do on-line backups when running in ARCHIVELOG mode.

A cold backup is a backup performed while the database is off-line and UNAVAILABLE to its users.

A hot backup is a backup performed while the database is online and available for read / write. Except for Oracle exports, one can only do on-line backups when running in ARCHIVELOG mode.

A cold backup is a backup performed while the database is off-line and unavailable to its users.

DBA: role CONTAINS all database SYSTEM privileges.

SYS user ACCOUNT: The DBA role will be assigned to this account. All of the base tables and views for the database's dictionary are store in this schema and are manipulated only by ORACLE.

SYSTEM user account: It has all the system privileges for the database and additional tables and views that display administrative INFORMATION and internal tables and views used by oracle tools are created using this username.

DBA: role Contains all database system privileges.

SYS user account: The DBA role will be assigned to this account. All of the base tables and views for the database's dictionary are store in this schema and are manipulated only by ORACLE.

SYSTEM user account: It has all the system privileges for the database and additional tables and views that display administrative information and internal tables and views used by oracle tools are created using this username.

CHOOSE, ALL_ROWS, FIRST_ROWS and RULE.

CHOOSE, ALL_ROWS, FIRST_ROWS and RULE.

No, this is listed as Enhancement Request 148742.

Workaround:

• Export all of the objects from the TABLESPACE
• DROP the tablespace INCLUDING contents
• RECREATE the tablespace
• Import the objects

No, this is listed as Enhancement Request 148742.

Workaround:

For long transactions that CONTAIN many SQL statements, INTERMEDIATE markers or savepoints can be declared which can be used to divide a transaction into smaller parts. This allows the option of later ROLLING back all WORK performed from the current point in the transaction to a declared savepoint within the transaction.

For long transactions that contain many SQL statements, intermediate markers or savepoints can be declared which can be used to divide a transaction into smaller parts. This allows the option of later rolling back all work performed from the current point in the transaction to a declared savepoint within the transaction.

The GOAL of the OPTIMIZER is to CHOOSE the most efficient way to EXECUTE a SQL STATEMENT.

The goal of the optimizer is to choose the most efficient way to execute a SQL statement.

These two Oracle utilities are USED for loading DATA into the database. The difference is that the import utility relies on the data being produced by ANOTHER Oracle utility EXPORT while the SQL*Loader utility allows data to be loaded that has been produced by other utilities from different data SOURCES just so long as it conforms to ASCII formatted or delimited files.

These two Oracle utilities are used for loading data into the database. The difference is that the import utility relies on the data being produced by another Oracle utility EXPORT while the SQL*Loader utility allows data to be loaded that has been produced by other utilities from different data sources just so long as it conforms to ASCII formatted or delimited files.

USE the DBMS_SESSION.SET_SQL_TRACE;

or

Use ALTER SESSION SET SQL_TRACE = TRUE;

Use the DBMS_SESSION.SET_SQL_TRACE;

or

Use ALTER SESSION SET SQL_TRACE = TRUE;

The ANALYZE COMMAND.

The ANALYZE command.

SHOW ERRORS.

SHOW ERRORS.

ALTER INDEX <index_name> REBUILD;

ALTER INDEX <index_name> REBUILD;

TURN on FINE GRAIN AUDITING for the table.

Turn on fine grain auditing for the table.

DBA_FREE_SPACE.

DBA_FREE_SPACE.

DBA_DATA_FILES.

DBA_DATA_FILES.

ALTER DATABASE DATAFILE &LT;datafile_name&GT; RESIZE <new_size>;

ALTER DATABASE DATAFILE <datafile_name> RESIZE <new_size>;

ALTER TABLESPACE &LT;tablespace_name> ADD DATAFILE <datafile_name> SIZE;

ALTER TABLESPACE <tablespace_name> ADD DATAFILE <datafile_name> SIZE;

GRANT the CONNECT to the USER.

Grant the CONNECT to the user.

A TEMPORARY tablespace is used for temporary objects such as sort STRUCTURES while permanent TABLESPACES are used to store those objects MEANT to be used as the TRUE objects of the database.

A temporary tablespace is used for temporary objects such as sort structures while permanent tablespaces are used to store those objects meant to be used as the true objects of the database.

Coalescing is only VALID for dictionary-managed tablespaces and de-fragments space by combining neighboring free EXTENTS into LARGE single extents.

Coalescing is only valid for dictionary-managed tablespaces and de-fragments space by combining neighboring free extents into large single extents.

ALTER SYSTEM SWITCH LOGFILE;

ALTER SYSTEM SWITCH LOGFILE;

Redo logs are logical and physical structures that are DESIGNED to hold all the changes made to a DATABASE and are INTENDED to aid in the RECOVERY of a database.

Redo logs are logical and physical structures that are designed to hold all the changes made to a database and are intended to aid in the recovery of a database.

USE of V$SESSION and V$SESSION_WAIT.

Use of V$SESSION and V$SESSION_WAIT.

The JOB QUEUE PROCESSES.

The Job Queue Processes.

PMON.

PMON.

In UNIX $ORACLE_HOME/rdbms/audit, in WINDOWS the EVENT VIEWER.

In unix $ORACLE_HOME/rdbms/audit, in Windows the event viewer.

SELECT DBTIMEZONE from DUAL;

select DBTIMEZONE from dual;

You get this error when you get a snapshot too OLD within rollback. It can usually be SOLVED by increasing the undo retention or increasing the SIZE of ROLLBACKS. You should also look at the logic involved in the application getting the error message.

You get this error when you get a snapshot too old within rollback. It can usually be solved by increasing the undo retention or increasing the size of rollbacks. You should also look at the logic involved in the application getting the error message.

A data block is the smallest unit of logical storage for a database object. As objects grow they TAKE chunks of ADDITIONAL storage that are composed of contiguous data blocks. These groupings of contiguous data blocks are called EXTENTS. All the extents that an object takes when grouped TOGETHER are considered the segment of the database object.

A data block is the smallest unit of logical storage for a database object. As objects grow they take chunks of additional storage that are composed of contiguous data blocks. These groupings of contiguous data blocks are called extents. All the extents that an object takes when grouped together are considered the segment of the database object.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.

Yes.