神马文学网[Laskey99] Section 13.2.2 ALTER DATABASE ARCHIVELOG
来源：百度文库 编辑：神马文学网 时间：2024/04/28 08:27:29
ALTER DATABASE ARCHIVELOG
ALTER DATABASE [ dbname] ARCHIVELOG |
NOARCHIVELOG
Specifies whether Oracle will attempt to archive redo log files forthe database dbname after a redo log switch.
Keywords
ARCHIVELOG
Specifies that a redo log group mustbe archived before it can be reused. If the group has not beenarchived, the database halts until archiving occurs successfully.This mode is required in order to perform media recovery.
NOARCHIVELOG
Specifies that redo log groups willnot be archived and may be reused immediately by Oracle.
Notes
The database must be mounted in EXCLUSIVE mode and not open in orderto issue this command. You must have the OSDBA role to issue thiscommand.
Create Bookmark (Key: b)Create Bookmark
Create Note or Tag (Key: t)Create Note or Tag
Download (Key: d)Download
Email This Page (Key: e)Email This Page
PrintPrint
Html View (Key: h)Html View
Zoom Out (Key: -)Zoom Out
Zoom In (Key: +)Zoom In
Toggle to Full Screen (Key: f)
Previous (Key: p)Previous
Next (Key: n)Next
Related Content
The sysadmin database
From: Migrating from Oracle . . . to IBM Informix Dynamic Server on Linux, Unix, and Windows
The sysmaster database
From: Customizing the Informix Dynamic Server for Your Environment
The sysadmin database
From: Customizing the Informix Dynamic Server for Your Environment
Database
From: Enterprise Security Architecture Using IBM Tivoli Security Solutions
Database security
From: Introduction to the New Mainframe: Security
Database reorganization
From: IBM Tivoli Storage Manager Version 5.3 Technical Guide
Databases
From: Building Internet Firewalls, 2nd Edition
Database Systems
From: CISSP Video Course Domain 9 – Application Security
Securing Databases
From: Security for Microsoft Visual Basic .NET
Database server
From: Informix Dynamic Server 11: Extending Availability and Replication
ALTER DATABASE [ dbname] ARCHIVELOG |
NOARCHIVELOG
Specifies whether Oracle will attempt to archive redo log files forthe database dbname after a redo log switch.
Keywords
ARCHIVELOG
Specifies that a redo log group mustbe archived before it can be reused. If the group has not beenarchived, the database halts until archiving occurs successfully.This mode is required in order to perform media recovery.
NOARCHIVELOG
Specifies that redo log groups willnot be archived and may be reused immediately by Oracle.
Notes
The database must be mounted in EXCLUSIVE mode and not open in orderto issue this command. You must have the OSDBA role to issue thiscommand.
Create Bookmark (Key: b)Create Bookmark
Create Note or Tag (Key: t)Create Note or Tag
Download (Key: d)Download
Email This Page (Key: e)Email This Page
PrintPrint
Html View (Key: h)Html View
Zoom Out (Key: -)Zoom Out
Zoom In (Key: +)Zoom In
Toggle to Full Screen (Key: f)
Previous (Key: p)Previous
Next (Key: n)Next
Related Content
The sysadmin database
From: Migrating from Oracle . . . to IBM Informix Dynamic Server on Linux, Unix, and Windows
The sysmaster database
From: Customizing the Informix Dynamic Server for Your Environment
The sysadmin database
From: Customizing the Informix Dynamic Server for Your Environment
Database
From: Enterprise Security Architecture Using IBM Tivoli Security Solutions
Database security
From: Introduction to the New Mainframe: Security
Database reorganization
From: IBM Tivoli Storage Manager Version 5.3 Technical Guide
Databases
From: Building Internet Firewalls, 2nd Edition
Database Systems
From: CISSP Video Course Domain 9 – Application Security
Securing Databases
From: Security for Microsoft Visual Basic .NET
Database server
From: Informix Dynamic Server 11: Extending Availability and Replication
[Laskey99] Section 13.2.2 ALTER DATABASE ARCHIVELOG
[Laskey99] Section 13.2.3 ALTER DATABASE MOUNT
[Laskey99] Section 13.2.19 Alter System
[Laskey99] Section 4.2. Database Backup
[Laskey99] Section 4.3. Database Recovery
[Laskey99] Section 3.5. Sizing and Configuring Database Objects
[Laskey99] Section 9.4. SQLDBA
[Laskey99] Section 11.2. Oracle Tablespaces
[Laskey99] Section 11.3. Disk Allocation
[Laskey99] Section 2.6. Critical Decisions
[Laskey99] Section 9.2. SQL*Plus
[Laskey99] Section 4.4. Automated Utilities
[Laskey99] Section 4.5. Practice Scenarios
[Laskey99] Section 3.4. Configuring Oracle
[Laskey99] Section 3.6. Tuning Oracle
[Laskey99] Section 5.2. Oracle Names
[Laskey99] Section 5.3. MultiProtocol Interchange
[Laskey99] Section 15.2. System Privileges
[Laskey99] Chapter 11. The Oracle Database
[Laskey99] Section 9.3. Oracle Server Manager
[Laskey99] Section 9.5. Oracle Network Manager
[Laskey99] Section 9.7. Oracle Enterprise Manager
[Laskey99] Section 9.8. Third-Party Tools
[Laskey99] Section 3.2. Achieving Maximum Performance