What are complete recovery and incomplete recovery in Oracle
In Oracle, complete recovery means that when the data file fails due to media failure, use the os command to copy the data file backup and restore it to the latest time point before the failure; incomplete recovery means that when the database fails due to media failure or user error, During operation, use backed up data, archived log files, etc. to restore the database to a time point before the latest time point before the failure.
The operating environment of this tutorial: Windows 10 system, Oracle 11g version, Dell G3 computer.
What are full recovery and incomplete recovery in Oracle
Full recovery: Use redo logs or incremental backups to restore data blocks to the time closest to the current time point. It is called a full recovery because Oracle applies all modifications in the archive logs and online redo logs.
When a media failure occurs in a data file, use the os command to copy the data file backup, and use the SQL recovery command to apply archive logs and redo logs, and finally restore the data file to the state of the failure point. That is, restore to the most recent point in time before the failure.
Incomplete recovery: Use backup to generate a non-current version of the database. In other words, all redo logs generated after the backup will not be used during the recovery process
When a media failure or user misoperation occurs in the database, the backed up data files, archive log files and redo logs will be used Restore the database to its state at a time between the backup point and the point of failure. That is, restore to a time point before the most recent time point before the failure.
Incomplete recovery of the entire database is usually generated under the following circumstances
1: Media failure damaged several or all online redo log files;
2: User Data loss caused by operations, for example, the user accidentally deleted a table;
3: Complete recovery cannot be performed due to the loss of individual archive log files;
4: Loss of current control file, the database must be opened using the backed up control file.
In order to perform incomplete media recovery, the data files must be restored using backups before the recovery time point
Recommended tutorial: "Oracle Video Tutorial"
The above is the detailed content of What are complete recovery and incomplete recovery in Oracle. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Solutions to Oracle cannot be opened include: 1. Start the database service; 2. Start the listener; 3. Check port conflicts; 4. Set environment variables correctly; 5. Make sure the firewall or antivirus software does not block the connection; 6. Check whether the server is closed; 7. Use RMAN to recover corrupt files; 8. Check whether the TNS service name is correct; 9. Check network connection; 10. Reinstall Oracle software.

The method to solve the Oracle cursor closure problem includes: explicitly closing the cursor using the CLOSE statement. Declare the cursor in the FOR UPDATE clause so that it automatically closes after the scope is ended. Declare the cursor in the USING clause so that it automatically closes when the associated PL/SQL variable is closed. Use exception handling to ensure that the cursor is closed in any exception situation. Use the connection pool to automatically close the cursor. Disable automatic submission and delay cursor closing.

In Oracle, the FOR LOOP loop can create cursors dynamically. The steps are: 1. Define the cursor type; 2. Create the loop; 3. Create the cursor dynamically; 4. Execute the cursor; 5. Close the cursor. Example: A cursor can be created cycle-by-circuit to display the names and salaries of the top 10 employees.

Oracle database paging uses ROWNUM pseudo-columns or FETCH statements to implement: ROWNUM pseudo-columns are used to filter results by row numbers and are suitable for complex queries. The FETCH statement is used to get the specified number of first rows and is suitable for simple queries.

To stop an Oracle database, perform the following steps: 1. Connect to the database; 2. Shutdown immediately; 3. Shutdown abort completely.

Building a Hadoop Distributed File System (HDFS) on a CentOS system requires multiple steps. This article provides a brief configuration guide. 1. Prepare to install JDK in the early stage: Install JavaDevelopmentKit (JDK) on all nodes, and the version must be compatible with Hadoop. The installation package can be downloaded from the Oracle official website. Environment variable configuration: Edit /etc/profile file, set Java and Hadoop environment variables, so that the system can find the installation path of JDK and Hadoop. 2. Security configuration: SSH password-free login to generate SSH key: Use the ssh-keygen command on each node

SQL statements can be created and executed based on runtime input by using Oracle's dynamic SQL. The steps include: preparing an empty string variable to store dynamically generated SQL statements. Use the EXECUTE IMMEDIATE or PREPARE statement to compile and execute dynamic SQL statements. Use bind variable to pass user input or other dynamic values to dynamic SQL. Use EXECUTE IMMEDIATE or EXECUTE to execute dynamic SQL statements.

Oracle garbled problems can be solved by checking the database character set to ensure they match the data. Set the client character set to match the database. Convert data or modify column character sets to match database character sets. Use Unicode character sets and avoid multibyte character sets. Check that the language settings of the database and client are correct.
