tailieunhanh - 4 Creating a Configuration and Physical Standby Database by Using Enterprise Manager

FORCE đăng nhập lực lượng làm lại được tạo ra ngay cả khi Các hoạt động nologging được thực thi. • tablespaces tạm thời và các phân đoạn tạm thời không đăng nhập. • FORCE khai thác gỗ được khuyến khích cho cả thể chất và cơ sở dữ liệu dự phòng hợp lý. • Ban hành các lệnh sau đây trên cơ sở dữ liệu chính: | Creating a Configuration and Physical Standby Database by Using Enterprise Manager Oracle Database 10g: Data Guard Administration 4 - Objectives After completing this lesson, you should be able to do the following: Enable FORCE LOGGING Use Enterprise Manager to create a broker configuration Use Enterprise Manager to monitor the broker configuration Oracle Database 10g: Data Guard Administration 4 - Enabling FORCE LOGGING Mode Forced logging is recommended to ensure data consistency. FORCE LOGGING forces redo to be generated even when NOLOGGING operations are executed. Temporary tablespaces and temporary segments are not logged. FORCE LOGGING is recommended for both physical and logical standby databases. Issue the following command on the primary database: SQL> ALTER DATABASE FORCE LOGGING; Enabling FORCE LOGGING Mode FORCE LOGGING mode determines whether or not the Oracle database server logs all changes in the database, except for changes to temporary tablespaces and . | Creating a Configuration and Physical Standby Database by Using Enterprise Manager Oracle Database 10g: Data Guard Administration 4 - Objectives After completing this lesson, you should be able to do the following: Enable FORCE LOGGING Use Enterprise Manager to create a broker configuration Use Enterprise Manager to monitor the broker configuration Oracle Database 10g: Data Guard Administration 4 - Enabling FORCE LOGGING Mode Forced logging is recommended to ensure data consistency. FORCE LOGGING forces redo to be generated even when NOLOGGING operations are executed. Temporary tablespaces and temporary segments are not logged. FORCE LOGGING is recommended for both physical and logical standby databases. Issue the following command on the primary database: SQL> ALTER DATABASE FORCE LOGGING; Enabling FORCE LOGGING Mode FORCE LOGGING mode determines whether or not the Oracle database server logs all changes in the database, except for changes to temporary tablespaces and temporary segments. The [NO]FORCE LOGGING clause of the ALTER DATABASE command contains the following settings: FORCE LOGGING: This setting takes precedence over (and is independent of) any NOLOGGING or FORCE LOGGING settings that you specify for individual tablespaces and any NOLOGGING setting that you specify for individual database objects. All ongoing, unlogged operations must finish before forced logging can begin. NOFORCE LOGGING: Places the database in NOFORCE LOGGING mode. This is the default. The FORCE_LOGGING column in V$DATABASE contains a value of YES if the database is in FORCE LOGGING mode. Oracle Database 10g: Data Guard Administration 4 - Enabling FORCE LOGGING Mode (continued) Although the database can be placed in FORCE LOGGING mode when the database is OPEN, the mode does not change until any operation that is currently running in NOLOGGING mode has completed. Therefore, it is recommended that you enable FORCE LOGGING mode when the database is in the MOUNT state. Note:

TỪ KHÓA LIÊN QUAN
crossorigin="anonymous">
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.