Explore topic-wise InterviewSolutions in Current Affairs.

A FULL backup is an OPERATING SYSTEM backup of all DATA files, on-line redo log files and control FILE that constitute ORACLE database and the parameter.

A full backup is an operating system backup of all data files, on-line redo log files and control file that constitute ORACLE database and the parameter.

Shutdown IMMEDIATE. Because without shutdown, we can't perform online backup of DATABASE, which running on NOARCHIVELOG mode. We should NEED to take cold backup of database. After CLEAN shutdown database copy of all datafiles, control files, redo log files, password file, and parameter files.

Shutdown immediate. Because without shutdown, we can't perform online backup of database, which running on NOARCHIVELOG mode. We should need to take cold backup of database. After clean shutdown database copy of all datafiles, control files, redo log files, password file, and parameter files.

2 months BACK, a potential table was dropped by an APPLICATION developer on our large 24/7 RUNNING production database. Immediately he informed US. We have standby database for our production database. We checked that archives didn’t apply to standby database up to dropped timing. We stopped archive applying on standby immediately and open database read only. Took export of dropped table and imported in production database. After finishing appropriate CHECKING of table, again we started archive applying in standby database for refreshing.

2 months back, a potential table was dropped by an application developer on our large 24/7 running production database. Immediately he informed us. We have standby database for our production database. We checked that archives didn’t apply to standby database up to dropped timing. We stopped archive applying on standby immediately and open database read only. Took export of dropped table and imported in production database. After finishing appropriate checking of table, again we started archive applying in standby database for refreshing.

Export and datapump dump file doesn't backup or contain any physical structure of database like datafile, control file, redo LOG file, parameter file, PASSWORD file. Instead of physical structure, export dump contains logical structure of database like DEFINITION of tablespaces, SEGMENTS, schemas, data of segments etc. DUE to these reasons export and datapump dump is called as logical backup.

Export and datapump dump file doesn't backup or contain any physical structure of database like datafile, control file, redo log file, parameter file, password file. Instead of physical structure, export dump contains logical structure of database like definition of tablespaces, segments, schemas, data of segments etc. Due to these reasons export and datapump dump is called as logical backup.

When we are performing incomplete recovery it means we bring database to past time or REWIND PERIOD of time using change based, cancel based or time based recovery. These all recovery make database in prior state of database. The forward SEQUENCE number already available after performing recovery, due to mismatching of this sequence numbers and prior state of database, it needs to open database with new sequence number of Redo LOG and archive logs.

When we are performing incomplete recovery it means we bring database to past time or rewind period of time using change based, cancel based or time based recovery. These all recovery make database in prior state of database. The forward sequence number already available after performing recovery, due to mismatching of this sequence numbers and prior state of database, it needs to open database with new sequence number of Redo log and archive logs.

During this recovery we are applying all database changes using archives log and make it to up to DATE. Complete recovery can be done full database level or datafile level or tablespace level. Main concept is to APPLY all DATA changes using ARCHIVE logs and bring database up to recent TIME.

During this recovery we are applying all database changes using archives log and make it to up to date. Complete recovery can be done full database level or datafile level or tablespace level. Main concept is to apply all data changes using archive logs and bring database up to recent time.

We can PERFORM this recovery in 2 ways. One is open database mode and another is database mount mode. After taking OFFLINE lost datafile, we can bring database open and after that RESTORE lost datafile from last backup. After restoration of datafile we can perform datafile level recovery for applying ARCHIVE logs and make it online. In database mount mode, we can restore datafile from backup and perform datafile recovery using "Recover datafile" command.

We can perform this recovery in 2 ways. One is open database mode and another is database mount mode. After taking offline lost datafile, we can bring database open and after that restore lost datafile from last backup. After restoration of datafile we can perform datafile level recovery for applying archive logs and make it online. In database mount mode, we can restore datafile from backup and perform datafile recovery using "Recover datafile" command.

There are lots of reason behind increasing size of archives LIKE If more database changes were performed using batch jobs or any SPECIAL task like merging 2 database or data ETC. You can investigate exact root CAUSE using enabling Log Minor UTILITY.

There are lots of reason behind increasing size of archives like If more database changes were performed using batch jobs or any special task like merging 2 database or data etc. You can investigate exact root cause using enabling Log Minor utility.

Create index file of export dump file USING IMPORT with index file command. A TEXT file will be generating with all table and index object name with NUMBER of rows. You can confirm your require table object from this text file. If you are using datapump then there is parameter CALLED "sqlfile" in impdp.

Create index file of export dump file using import with index file command. A text file will be generating with all table and index object name with number of rows. You can confirm your require table object from this text file. If you are using datapump then there is parameter called "sqlfile" in impdp.

When use LGWR with SYNC, it MEANS once NETWORK I/O initiated, LGWR has to wait for COMPLETION of network I/O before WRITE processing. LGWR with ASYNC means LGWR doesn’t wait to finish network I/O and continuing write processing.

When use LGWR with SYNC, it means once network I/O initiated, LGWR has to wait for completion of network I/O before write processing. LGWR with ASYNC means LGWR doesn’t wait to finish network I/O and continuing write processing.

Yes. You can. It is not RECOMMENDED because your production database is large database and running 24/7 ENVIRONMENT. Restoration and recovery will take downtime. It is BETTER to perform restoration and recovery process on UAT or TEST database.

Yes. You can. It is not recommended because your production database is large database and running 24/7 environment. Restoration and recovery will take downtime. It is better to perform restoration and recovery process on UAT or Test database.

Then you should need to RESTORE backup on your UAT or test DATABASE server and enable time based recovery for applying all ARCHIVES before drop command execution. For an instance, APPLY archives up to 3:55 PM here.

Then you should need to restore backup on your UAT or test database server and enable time based recovery for applying all archives before drop command execution. For an instance, apply archives up to 3:55 PM here.

If your database is RUNNING on Oracle 10g/11g/12c version then there is NEW feature available called RECYCLE bin. You can recover dropped table from user_recyclebin or dba_recyclebin.

If your database is running on Oracle 10g/11g/12c version then there is new feature available called Recycle bin. You can recover dropped table from user_recyclebin or dba_recyclebin.

We can ENABLE DISABLE recording INCREMENTAL checkpoint in alert.log .We can enable/disable recording USING parameter log_checkpoints_to_alert=true/false.

We can enable disable recording incremental checkpoint in alert.log .We can enable/disable recording using parameter log_checkpoints_to_alert=true/false.

In incremental checkpoint process, CKPT process records lowest Low RBA to the CONTROL FILE to keep advancing the Buffer checkpoint Queue (BCQ) to MAKE easy and FASTEST Active Checkpoint Queue (ACQ).

In incremental checkpoint process, CKPT process records lowest Low RBA to the control file to keep advancing the Buffer checkpoint Queue (BCQ) to make easy and fastest Active Checkpoint Queue (ACQ).

If one of your control file is missing or corrupted then we have 2 options to recover it. Check alert.log for exact name and location of corrupted control file. DELETE it manually and COPY from available rest of control file and rename it and start database. Another OPTION is delete corrupted control file and remove name from parameter file/ spfile. After removing SAID control file from spfile, start your database.

If one of your control file is missing or corrupted then we have 2 options to recover it. Check alert.log for exact name and location of corrupted control file. Delete it manually and copy from available rest of control file and rename it and start database. Another option is delete corrupted control file and remove name from parameter file/ spfile. After removing said control file from spfile, start your database.