• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

How to Perform Manual Archiving in Oracle Database

by admin

You can configure your database for manual archiving only. To operate your database in manual archiving mode, follow the procedure below:

1. Shut down the database instance.

SQL> SHUTDOWN

An open database must first be closed and any associated instances shut down before you can switch the database archiving mode. You cannot change the mode from ARCHIVELOG to NOARCHIVELOG if any data files need media recovery.

2. Back up the database.

Before making any major change to a database, always back up the database to protect against any problems. This will be your final backup of the database in NOARCHIVELOG mode and can be used if something goes wrong during the change to ARCHIVELOG mode.

3. Edit the initialization parameter file to include the initialization parameters that specify the destinations for the archived redo log files.

4. Start a new instance and mount, but do not open, the database.

SQL> STARTUP MOUNT

To enable or disable archiving, the database must be mounted but not open.

5. Change the database archiving mode. Then open the database for normal operations.

SQL> ALTER DATABASE ARCHIVELOG MANUAL;
SQL> ALTER DATABASE OPEN;

6. Shut down the database.

SQL> SHUTDOWN IMMEDIATE

7. Back up the database.

Changing the database archiving mode updates the control file. After changing the database archiving mode, you must back up all of your database files and control file. Any previous backup is no longer usable because it was taken in NOARCHIVELOG mode.

When you operate your database in manual ARCHIVELOG mode, you must archive inactive groups of filled redo log files or your database operation can be temporarily suspended. To archive a filled redo log group manually, connect with administrator privileges. Ensure that the database is either mounted or open. Use the ALTER SYSTEM statement with the ARCHIVE LOG clause to manually archive filled redo log files. The following statement archives all unarchived log files:

SQL> ALTER SYSTEM ARCHIVE LOG ALL;

Filed Under: oracle

Some more articles you might also be interested in …

  1. WebLogic Server Domain: How To Disable the HTTP methods other than GET and POST (such as PUT, DELETE, etc.)
  2. How to determine which user is using what rollback segment?
  3. Oracle Database 12c New Feature – RMAN “RECOVER TABLE”
  4. PL/SQL Nested Blocks
  5. How to use Flashback Database in Oracle Data Guard Configuration
  6. Beginners Guide to Oracle Password Management Policy
  7. How to find current SQL statement being executed by particular session in Oracle
  8. How to Identify the Last and Next Refresh Dates for a Materialized View
  9. How to duplicate a Oracle Database to a previous Incarnation
  10. CentOS / RHEL 7 : How to set udev rules for ASM on multipath disks

You May Also Like

Primary Sidebar

Recent Posts

  • “aws secretsmanager” Command Examples
  • “aws s3api” Command Examples
  • “aws s3” Command Examples
  • “aws s3 rm” Command Examples

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright