- Oracle Database 12c Backup and Recovery Survival Guide
- Francisco Munoz Alvarez Aman Sharma
- 179字
- 2021-04-02 10:19:59
Backups and NOLOGGING
If it is required that the data loaded using the NOLOGGING option needs to be recovered in the case of a disaster situation, your only solution is making a backup as soon as the NOLOGGING operation is made. Otherwise, the data cannot be recovered in the event of a media failure because it has not been logged.
Sometimes you will not be able to run a full backup of the database until later in the day. In this situation, you can make use of the following strategies:
- Hot backup
- In order to recover any additional data or modification to the table after the bulk insert using
NOLOGGINGis complete, you must at least perform a hot backup of the datafiles in which the objects are located. Remember that your database continues generating redo for the DML transactions over the objects, even if they are still using theNOLOGGINGoption, but you are strongly advised to place them inLOGGINGafter theNOLOGGINGmode is no longer required, to avoid any possibility of unrecoverability in the future.
推薦閱讀
- Unreal Engine Physics Essentials
- Java 9 Programming Blueprints
- Learning Python by Building Games
- Building Microservices with .NET Core
- Python圖形化編程（微課版）
- iPhone應用開發(fā)從入門到精通
- Julia for Data Science
- Practical Game Design with Unity and Playmaker
- C編程技巧：117個問題解決方案示例
- OpenCV Android Programming By Example
- 深入淺出 HTTPS：從原理到實戰(zhàn)
- JSP應用與開發(fā)技術（第3版）
- Roslyn Cookbook
- C#教程
- Python程序設計案例教程：從入門到機器學習（微課版）