Database Administration (MOSC)

MOSC Banner

Risk of bundling multiple db changes together when switching to ArchiveLog Mode and approach to rest

edited Jan 21, 2014 4:35AM in Database Administration (MOSC) 2 commentsAnswered ✓
Source Production DB running in NOARCHIVELOG in Oracle 10GR2 has never been backed up.

1. Completed schema level expdp of all schemas except SYS in Source DB

2. Planning to switch over Source DB to ArchiveLog Mode and increase DB_FILES parameter from 300 to 500.

    ALTER  system set db_files=500 scope=both;

   


 ALTER SYSTEM SET log_archive_dest_1='location=/u01/oradata/MYSID/archive/' SCOPE=both;
 ALTER SYSTEM SET log_archive_format='arch_%t_%s_%r.arc' SCOPE=both;

     SHUTDOWN IMMEDIATE;
     STARTUP MOUNT;
     ALTER DATABASE ARCHIVELOG;
     ALTER DATABASE OPEN;


3. In unlikely event of database is unable to start up and as a last resort is the following approach a feasible way to

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center