Clone database with no archive log mode and downtime with new file structure

We need to clone database with following business requirements :
No downtime at all can be afford
databases are in no archive log mode
data-file locations need to be change to new mount points while cloning for space management factor
Please suggest the best possible methods for same ?

Can you post your version of oracle in 4 digits and OS for better understandig
I dont think you can move the No Archive database to a new location without shutting down.
You just want to move them to the new mount points is it?
1. How big are your datafiles are?
2.How do you backup this DB?
When you move the datafilles then it becomes inconsistent and you need redo logs and probably archive logs to be there to make the file consistent or else it would be prompting for recovery. The chances are your redolog will be overwritten and hence you wont be able to recover.
You need downtime.

Similar Messages

  • When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode

    Question :
    When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode ?
    Example:
    Create Tablespace
    CREATE SMALLFILE TABLESPACE "TEST_DATA"
    LOGGING
    DATAFILE '+DG_TEST_DATA_01(DATAFILE)' SIZE 10G
    AUTOEXTEND ON NEXT  500K MAXSIZE 31000M
    EXTENT MANAGEMENT LOCAL
    SEGMENT SPACE MANAGEMENT AUTO;
    LOGGING: Generate redo logs for creation of tables, indexes and  partitions, and for subsequent inserts. Recoverable
    Are they not logged and not recoverable if we do not enable LOGGING? What is that ARCHIVELOG mode does?

    What is that ARCHIVELOG Mode Does?
    Whenever your database is in archive log mode , Oracle will backup the redo log files in the form of Archives so that we can recover the database to the consistent state in case of any failure.
    Archive logging is essential for production databases where the loss of a transaction might be fatal.
    Why Logging?
    Logging is safest method to ensure that all the changes made at the tablespace will be captured and available for recovery in the redo logs.
    It is just the level at which we defines:
    Force Logging at DB level
    Logging at Tablespace Level
    Logging at schema Level
    Before the existence of FORCE LOGGING, Oracle provided logging and nologging options. These two options have higher precedence at the schema object level than the tablespace level; therefore, it was possible to override the logging settings at the tablespace level with nologging setting at schema object level.

  • Switching database to archive log mode

    1.When I switch the database to archive log mode,
    I have to do full offline(consistent) backup.
    2.When the database is working in archive log mode
    I can do inconsistent(online) backups.
    Why is there consistent backup needed after swiching
    to archive log mode, is there not inconsistent backup
    enough after switching (the databease operates
    in archive log mode and as in point 2 I can make inconsistent backups).

    Hello,
    Oracle recommands to do offline backup after switching to archivelog as an immediate crash-recovery procedure. Look at the following example:
    1/ You switch your base to archivelog.
    2/ Work is started right away.
    3/ Your DB crashes => You got your archived redo logs, but none of the other files.
    Now, let's put a
    1b/ Backup (offline) your database.
    Now, in 3, youg got everything you need to restore the base, because 3 can happen WHILE your are ONLINE Backing up the base.
    That's the point.
    Regards,
    Yoann.

  • Archive log mode required for async. CDC?

    Hello there,
    I have tried to set up asyn. HotLog CDC on my 10g database but after creating a publisher I get the following error Message when creating a change set with the publisher:
    BEGIN
    DBMS_CDC_PUBLISH.CREATE_CHANGE_SET(
    change_set_name => 'MY_CHANGESET',
    description => 'First Change set',
    change_source_name => 'HOTLOG_SOURCE',
    stop_on_ddl => 'y',
    begin_date => sysdate,
    end_date => sysdate+20);
    END;
    following Error-Message:
    BEGIN
    ERROR at line 1:
    ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
    ORA-06512: at "SYS.DBMS_CAPTURE_ADM_INTERNAL", line 115
    ORA-06512: at line 1
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 57
    ORA-06512: at line 2
    Does this mean that I have to activate the ARCHIVE LOG-mode, and if yes, how do I do this with the Enterprise Manager?
    I already set the LOG_ARCHIVE_START initparam to "true".
    Klaus

    To place a database in archivelog mode you must:
    Be sure that the log_archive_start and log_archive_dest
    parameters are set in the init file.
    Shut the instance down.
    startup mount;
    alter database archivelog;
    alter database open;

  • Disabling Log_Archive_Start in Archive Log Mode

    Guys,
    I have a Database running in Archive Log mode.
    I have a situation where in I have to do bunch of bulk updates for which I dont want any logs generated.
    sO I was thinking to set the intialization parameter log_archive_start to false before I run the DML updates
    ALTER SYSTEM SET log_archive_start = false
    after the DML is run I will turn it back on
    ALTER SYSTEM SET log_archive_start = True
    Do you think if this is the right to go about or would I have to switch from Archive Log Mode to No Archive Log Mode
    run the DML update and then switch back to Archive Log Mode
    Any comments/suggestions/inputs woo

    Hello,
    I would use some other way to get a full nologing behaviour.
    First, ensure your tablespace is in force logging mode.
    ALTER TABLESPACE data FORCE LOGGING NOLOGGING;
    ALTER TABLESPACE index FORCE LOGGING NOLOGGING;
    This will ensure that you're usually logging.
    Set all tables/indexes to be nologging
    BEGIN
    FOR vRes IN (SELECT OWNER,TABLE_NAME FROM DBA_TABLES WHERE TABLESPACE_NAME='data')
    LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || vRes.OWNER || '.' || vRes.TABLE_NAME ' NOLOGGING';
    END LOOP;
    END;
    Do even for indexes.
    From now on, when you want to do your huge amount of updates/... targetting objects in tablespaces data and index, jou just have to:
    ALTER TABLESPACE data NO FORCE LOGGING;
    ALTER TABLESPACE indexes NO FORCE LOGGING;
    - Your DML
    ALTER TABLESPACE data FORCE LOGGING;
    ALTER TABLESPACE indexes FORCE LOGGING.
    4 commands to disable logging for every object in the tablespace.
    Beware, when in NOLOGGING mode, you won't be able to "RECOVER" any of the tables. Thiis is not crash-friendly, but you'll have no redo info generated, which is what you require.
    Regards,
    Yoann.

  • Archive log mode Turn off

    Hi all DBA guys, Have a Nice day all
    If i change archive log mode to no archive log mode, internally whats happen my database?.
    Is this old archive log backup use for future if again convert no archive to archive log mode?
    What's happen flashback if i change archive log mode to no archive log mode?
    Regards
    S.Azar

    azarmohds wrote:
    Thanx lot,
    why i asked this question means, rightnow you posted, this is feature of 10g i.e flashback database confiured when archive log mode is enabled...,so in this case
    What's happen flashback if i change archive log mode to no archive log mode?S.Azar,
    You should be clear about things that when you read notes from web, there can be a language mismatch. So the best is that search first over the oracle docs.
    Now about your doubt, its a terminology mismatch which is happening here. To enable Flashback Database feature which is more persistent copy of the undo data , stored seperately in a FLB file, you MUST have to have archivelog mode configured in your db. Without this, you can't enable the Flashback Database feature. And you can't switch to noarchive log mode as well if you have Flashback Database mode on.
    The other thing ( which I guess Anurag was mentioning ) is the normal Flashback feature which relies on Undo data stored in the undo tablespace. This solely is based on teh undo data and doesn't depend on the archive/nonarchive log mode of the database. But this is limited to that data and to that time period up till which you can store the undo data in your undo tablespace.
    HTH
    Aman....

  • Archive log mode doubt

    Hi All,
    We have 10g R2 database running on RHEL 4 OS. In order to set the archive log mode for the database, if we set only log_archive_dest_n parameter is only enough or we have to set db_recovery_file_dest_size and db_recovery_file_dest also? i know that these 2 parameters are required to configure the flash_recovery_area. my doubt is whether, do we need to set flash_recovery_area parameters and log_archive_dest_n parameters to take backup of databases or set only the log_archive_dest_n parameter and enable archive log mode and take backup using RMAN?
    Thanks,
    Praveen.

    Hi,
    To use RMAN to take a hot backup you need only set LOG_ARCHIVE_DEST_n and place the database in archive log mode. RMAN can be used to backup changed data even after a nologging operation, and you can move away from archivelog mode.
    http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10726/configbp.htm
    There is also the new "block change tracking" B&R that does not need archivelog mode:
    http://www.dba-oracle.com/t_block_change_tracking.htm

  • OEM 9.2.0.1.0 Archive Log Mode

    I've done this numerous times, but cannot remember how to bring a database up in Archive Log Mode so I can use Dataguard Manager. Can anyone refresh my memory?

    Using OEM 9.2.0.1 and have various events registered
    but noticed that the minimum threshold value for the
    Broken Jobs event test is 1, whereas all the
    documentation and help refers to it being 0. I only
    noticed because we have 1 broken job and no alert for
    it.
    Has anyone come across this before as I can't find
    any references to it.
    Thanks
    NeilI do not know about "all the documentation and help refers to it being 0" because I have not checked, but the minimum Critical Threshold is 1.
    I do not know why anyone would want to set it to 0 because it is equivalent to not setting the Broken Job test

  • Is the only way to import large amount of data and database objects into a primary database is to shutdown the standby, turn off archive log mode, do the import, then rebuild the standby?

    I have a primary database that need to import large amount of data and database objects. 1.) Do I shutdown the standby? 2.) Turn off archive log mode? 3.) Perform the import? 4.) Rebuild the standby? or is there a better way or best practice?

    Instead of rebuilding the (whole) standby, you take an incremental (from SCN) backup from the Primary and restore it on the Standby.  That way, if, for example
    a. Only two out of 12 tablespaces are affected by the import, the incremental backup would effectively be only the blocks changed in those two tablespaces (and some other changes in system and undo) {provided that there are no other changes in the other ten tablespaces}
    b. if the size of the import is only 15% of the database, the incremental backup to restore to the standby is small
    Hemant K Chitale

  • Archive log mode  in 3 node rac database

    Sir I am using oracle 10.2.0.1 and created 3 node cluster setup on.OS i am using linux 4
    I am too much confuse in setting up this cluster in archive log mode bec why we need to false cluater_database parameter to setup cluster in archive log mode.
    I have search lot of documents but all are saying we not need setting this parameter flase perior to 10.2.But what is the actual concept behind setting this parameter to false in early release and why we need not to set it false.Please help me.
    I know how to set up in archive log mode but this parameter create confusion.
    Thanks sir in advance

    I also dont't know all the details about this but I'll try to explain what I know. Setting cluster_database to false in a rac environment is usually done when you need to mount the database from one instance exclusively. This is still needed when you upgrade the catalog, for example during release update (from 10.2.0.1 to 10.2.0.4 for example). Now with switching archivelog mode someone at oracle must have discovered that it is sufficient when the database is mounted by only one instance and you can actually save one step.
    As I (and propably most of you) don't switch archiving on or off on a daily basis, I don't worry about this a lot, simply turn this on when I create a new database and then leave it on forever.
    Bjoern

  • Backup with Exp,  Can  It used in DB with Archive Log Mode ??

    I need information about if When I activate Archive log mode in my database ,after This I will use all before backups with Exp in full,Table,user ...recovery mode .
    any advice are welcome
    thanks
    Jimmy

    If you are using archive log mode, you should back up your database by regularly backing up
    your data files. If you lose a tablespace due to a defecitve disk or need to do a point-in-time recovery due to a user error, you restore your latest copy (if doing point-in-time the latest copy before the
    user error) of the relevant data files an then roll forward using the archived log.
    You can not restore your database from an export and then roll forward using the archived
    logs.
    HTH
    Marcus Geselle

  • Changing archive log mode without shutting down database

    Hi all,
    Is there any way to set the database to archive log mode before shutting down the database and when the database shuts and starts, the database should be automatically in archive log mode?
    because we can not shutdown the database in weekdays and we have system reboot on weekend and we are not here on that day. So is there a way to set the database in archive log at the memory level so that when the database reboots, it should automatically start in archive log mode.
    my environment is windows server 2008 R2 with oracle 11.2.0.3
    Thanks in advance.
    Edited by: 931643 on Dec 5, 2012 10:37 AM

    931643 wrote:
    thank you for the reply Max Seleznev,
    First I thought of writing script in order to include in that process. But we can not run any commands in the sqlplus using the windows jobs. for eg:
    you can write a batch file as below:
    cd \
    sqlplus / as sysdba
    select name,open_mode from v$database;
    when you run this, it will open until sqlplus prompt but then will not execute the query.
    What did you expect? Well, actually, I know what you expected. But think about it for a second. You have a batch file with the mentioned three lines. How does that batch file get processed .. what is happening when it is being processed?
    It is not being processed by sqlplus, it is being processed by the windows command processor. Just like the cmd.exe. Each line is read by the command processor and executed accordingly. So ....
    cd \the command processor calls 'cd' , and passes the value '\' to do with as it sees fit. 'cd' then changes the current directory of the session to whatever is indicated by the passed parameter. in this case, that value is '\' , so the resulting current directory is the base (root, in *nix terms) of the current drive.  When 'cd' has finished, it returns control to the command processor, who then reads the next line ....
    sqlplus / as sysdbathe command processor calls sqlplus.exe and passes it the command line parms '/ as sysdba' to do with as it (sqlplus) sees fit. sqlplus does whatever it does with what it has been given In this case it tries to connect to whatever local database is indicated by the value of ORACLE_SID, then waits for more input. Whenever sqlplus exits (how does it know to exit?) it returns control to the command processor, who then reads the next line ....
    select name,open_mode from v$database;The command processor will read this line and attempt to find an executable file named 'select' and pass it the rest of the command line 'name,open_mode from v$database;'
    Hmm, what do you suppose will happen with that operation?
    that is the reason I am figuring out whether there is an alternate way.yes but you have to use the proper technique. And since you are building this into a production stop/start without testing the actual stop/start commands ... what do you suppose will be the outcome if something goes wrong?
    After hours and weekend work is one reason DBA's make more money than developers.
    >
    Thanks

  • Standby Database (Archive Log Mode)

    I'm going to be setting up a standby database.
    I understand that the primary database must be in archive log mode.
    Is there any reason for the standby database to be in archivelog mode?

    Since your primary Db is in archive log mode, so will be your standby, when it is made primary.But. you can use STANDBY REDO LOGS from 9i version, where these Standby Redo Logs then store the information received from the Primary Database.
    As per metalink:-
    >
    Standby Redo Logs are only supported for the Physical Standby Database in Oracle 9i and as well for Logical Standby Databases in 10g. Standby Redo Logs are only used if you have the LGWR activated for archival to the Remote Standby Database.If you have Standby Redo Logs, the RFS process will write into the Standby RedoLog as mentioned above and when a log switch occurs, the Archiver Process of the Standby Database will archive this Standby Redo Log to an Archived Redo Log, while the MRP process applies the information to the Standby Database. In a Failover situation, you will also have access to the information already written in the Standby Redo Logs, so the information will not be lost.
    >
    Check metalink Doc ID: Note:219344.1
    Regards,
    Anand

  • SGEN & database archive log mode

    Hi Experts,
    To apply ABAP support packs, I disabled archive log mode of databse and successfully applied support packs.
    As post processing, I kicked off SGEN.
    Is it required that database be in "NO Archive log mode"  while SGEN is running or can I enable it.
    Thanks
    Putla

    Not sure what database it is.. but if it is ORACLE...
    $sqlplus / as sysdba
    SQL> shutdown immediate;
    SQL> startup mount;
    SQL> Alter database noarchivelog;
    SQL> alter database open;
    After the completion of SGEN.....
    $sqlplus / as sysdba
    SQL> shutdown immediate;
    SQL> alter database mount;
    SQL> alter database archivelog;
    SQL> alter database open;

  • For streams , database in Archive log mode or non archive log mode?

    Hello ,
    I have a basic question,
    To set up oracle streams, what should be the the database mode (archive log or non archive log mode)?
    Thanks in advance,
    Raj

    It needs to be in archive log mode..thts the place frm where it captures the necessary information....
    Kapil

Maybe you are looking for