Explore topic-wise InterviewSolutions in .

The NAME of the FILE which LOG of the EXPORT will be WRITTEN.

The name of the file which log of the export will be written.

The NAME of the FILE from which IMPORT should be PERFORMED.

The name of the file from which import should be performed.

A flag to INDICATE whether file content should be DISPLAYED or not.

A flag to indicate whether file content should be displayed or not.

A FLAG to INDICATE whether GRANTS on DATABASE objects will be imported.

A flag to indicate whether grants on database objects will be imported.

A FLAG to INDICATE WHETHER IMPORT should import index on tables or not.

A flag to indicate whether import should import index on tables or not.

A flag to indicate whether ROWS should be imported. If this is SET to 'N' then only DDL for DATABASE OBJECTS will be EXECUTED.

A flag to indicate whether rows should be imported. If this is set to 'N' then only DDL for database objects will be executed.

For Incremental exports, the flag INDIRECTS whether a record will be STORES DATA DICTIONARY TABLES recording the export.

For Incremental exports, the flag indirects whether a record will be stores data dictionary tables recording the export.

Type EXPORT should be performed COMPLETE,CUMULATIVE,INCREMENTAL

Type export should be performed COMPLETE,CUMULATIVE,INCREMENTAL

RECORD LENGTH in BYTES.

Record length in bytes.

LIST of TABLES should be EXPORTED.

List of tables should be exported.

LIST of table ACCOUNTS should be EXPORTED.

List of table accounts should be exported.

A flag to INDICATE whether FULL DATABSE EXPORT should be PERFORMED.

A flag to indicate whether full databse export should be performed.

A flag to indicate WHETHER statistical information about the exported objects should be written to EXPORT DUMP file.

A flag to indicate whether statistical information about the exported objects should be written to export dump file.

NAME of the PARAMETER FILE to be PASSED for EXPORT.

Name of the parameter file to be passed for export.

Flag to indicate WHETHER table rows should be exported. If 'N' only DDL STATEMENTS for the database OBJECTS will be created.

Flag to indicate whether table rows should be exported. If 'N' only DDL statements for the database objects will be created.

A FLAG to indicate whether INDEXES on tables will be EXPORTED.

A flag to indicate whether indexes on tables will be exported.

A FLAG to indicate WHETHER GRANTS on databse objects will be exported or not. Value is 'Y' or 'N'.

A flag to indicate whether grants on databse objects will be exported or not. Value is 'Y' or 'N'.

To GIVE the EXPORT FILE NAME.

To give the export file name.

LOGICAL BACKUP INVOLVES reading a set of DATABASE records and WRITING them into a file. Export utility is used for taking backup and Import utility is used to recover from backup.

Logical backup involves reading a set of database records and writing them into a file. Export utility is used for taking backup and Import utility is used to recover from backup.

Cold backup is TAKING backup of all PHYSICAL files after NORMAL shutdown of database. We need to TAKE.

• All Data files.
• All Control files.
• All on-line REDO log files.
• The init.ora file (Optional)

Cold backup is taking backup of all physical files after normal shutdown of database. We need to take.

• FULL back - Complete database
• Incremental - Only AFFECTED tables from LAST incremental date/full backup date.
• CUMULATIVE backup - Only affected table from the last cumulative date/full backup date.

The data DICTIONARY cache is stored in an AREA in SGA CALLED the Shared SQL Pool. This will allow sharing of parsed SQL statements among concurrent USERS.

The data dictionary cache is stored in an area in SGA called the Shared SQL Pool. This will allow sharing of parsed SQL statements among concurrent users.

The System Global Area in a Oracle database is the area in memory to FACILITATES the transfer of INFORMATION between users. It holds the most recently requested structural information between users. It holds the most recently requested structural information about the database. The structure is Database buffers, DICTIONARY CACHE, Redo Log Buffer and SHARED SQL pool (ver 7.0 only) area.

The System Global Area in a Oracle database is the area in memory to facilitates the transfer of information between users. It holds the most recently requested structural information between users. It holds the most recently requested structural information about the database. The structure is Database buffers, Dictionary cache, Redo Log Buffer and Shared SQL pool (ver 7.0 only) area.

Multiplexing Redo LOG FILE CALLED MIRRORING. ( Keeping multiple copies in DIFFERENT disks)

Multiplexing Redo log file called Mirroring. ( Keeping multiple copies in different disks)

LGWR PROCESS writes all CHANGE vectors from the redo log BUFFER to ONLINE redo log file sequentially.

LGWR process writes all change vectors from the redo log buffer to online redo log file sequentially.

By USING DICTIONARY VIEWS CALLED V$rollstat,dba_rollback_segs.

By using dictionary views called v$rollstat,dba_rollback_segs.

• Calculate the total header SIZE
• Calculate the available dataspace PER DATA block
• Calculate the combined column lengths of the average row
• Calculate the total average row size.
• Calculate the average NUMBER rows that can fit in a block
• Calculate the number of blocks and bytes required for the table.

After arriving the calculation, add 10 % additional space to calculate the initial EXTENT size for a working table.

After arriving the calculation, add 10 % additional space to calculate the initial extent size for a working table.

STORE DATA in tablespaces to avoid DISK contension.system tablespace-recursive callsuserdata-users objectsindex tablespace-for indexesrollback segmnets-undo tablespace or MANUAL ROLLBACK segmentsplace application specific data in respective tablespaces.Place all these tablespaces in saperate disks.Try to implement raid-0 (striping) for better performance.

Store data in tablespaces to avoid disk contension.system tablespace-recursive callsuserdata-users objectsindex tablespace-for indexesrollback segmnets-undo tablespace or manual rollback segmentsplace application specific data in respective tablespaces.Place all these tablespaces in saperate disks.Try to implement raid-0 (striping) for better performance.

• Due to INSUFFICIENT Shared SQL POOL size.
• MONITOR the ratio of the reloads TAKES PLACE while executing SQL statements. If the ratio is greater than 1 then increase the SHARED_POOL_SIZE.