Restore database in no archivelog mode

hello all,
Our DB version is 10.2.2.0
Os is Linux RHL4
Our Database is in noarchive log mode.
i am performing Recovery of DB from previous cold backup.
so, apart from datafile and controlfile ,do i need to restore the online redolog file also from the backup to its original location?
or do i keep the current redolog files intact?
need help ..
thanks

Redologs should be flushed when you do a proper shutdown for the cold backup, so you do not need to restore them. In fact, it can be a bad habit, as you inevitably encounter a situation where you overwrite some that are needed because of an improper shutdown, (usually after you move to hot backups). And if you are restoring after a crash, you can't do media recovery with noarchivelogmode. Except, if you are doing [url http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmrecov.htm#CACGEAEE]incrementals, you can do limited recovery, then you definitely don't want to restore the redo, because you will lose activity after the last incremental backup.
Do an alter database backup controlfile to trace; and look at the resultant trace file. See how there are both noresetlog and resetlog versions? You use the resetlog to create the new one if you are in some situation where you lost the controlfiles and redo. It's real handy to have that type of controlfile backup, you might consider keeping it every time you make a backup. Google for scripts that figure out the tracefile name so you can put it in some known file.

Similar Messages

Would you use scripts to take database out of archivelog mode?

Background: we do not use RMAN for this production database and we do cold backups each night.
I've been asked to take one of our databases out of archivelog mode for a few days and then to put it back into archivelog mode.
Being somewhat neurotic about these things - I've only ever done it manually - so that I can make sure nothing goes wrong and to check that there was a last successful cold backup prior to the switch.
However, management have asked that it be done automatically by scripts after the backup.
Whilst I can create a script that will do this - the question I'd like to ask the forum is - have you and would you?

I do not agree with taking any Oracle database out of archivelog mode and I do not approve of management's decision and have told them why and all the risks they run.
This is not a test database - it IS a production database and other users do make changes daily.
What I did not reveal until now is that I have also been asked to take this database out of archivelog mode for 5 days and suspend all cold back-ups for the whole server (with 3 other instances on the server - also impacted) - and have warned them accordingly.
However, management have been swayed by someone who feels they know better - who claims to be a qualified Oracle DBA - I'm OCP but seems to have little sway since this person has convinced management that my 6 years experience and qualification is less than his application experience in GIS.
They want to run an upload which will take around 5 days to do - I'm somewhat miffed that an upload can take that length of time and question whether a GIS system should need such an upload for such a length of time.
Let's no go into the problem with tablespaces and space within the tablespaces - the upload will fail because they do not understand that if the tablespace fills up - the upload will fail - but despite asking - I've been told that there is no problem - there will be a problem - since I refuse to allow autoextend on this database - because of the potential to run out of disk space.
I've explained until I'm blue in the face - never mind that even if the upload is successful - the cold backup tape won't be able to backup the data because it'll be potentially over the limit.
I've even warned of my past experience x 3 - when a RAID controller failed - literally died in front of my eyes - I just happened to be standing next to one of the servers talking to someone - and the whole server was lost - but because we had the archivelogs - and the previous day's backup - we got it up and running after Dell replaced the RAID controller - within 1 hour.
That's the joy of Oracle - nothing is lost other than the last archivelog - depending on the time you set the switch.
I love this system - it's so recoverable - it such a joy to work with.
But then when I get told to suspend cold backups and then at the same time suspend archivelog mode - I go mad.
Don't get me started - I've gone down the usual path of why hire an OCP when you won't listen to what I say, etc.
Management are demanding I switch it automatically out of archivelog mode etc.
I can do it - but my question is still - have you guys?
And why did you do it?
All I can say is that I hope that the server has a RAID contoller failure and finally they listen to me - the chances of that are minimal - so management are saying - do it or else.
Oh and by the way - the GIS team have asked for this to be bi-monthly - automated.
And have said that:
"You can not rollback or recover the loading process using the log files because it involves a far more complex operation that would most likely not be successful."
Nice phrase that to an OCP.
I welcome your comments - as I really am in a hole here.
Thanks.

How to use OEM grid control to find any database not in archivelog mode?

Hello,
currently we have 130 databases, say, if I want to pick out any database currently NOT in archivelog mode, is there a quick way to find out ?
by using OEM grid control
or
some trick similar,
but really don't need to check each database manually.
thank you very much!

This query works in 12c - please run as SYSMAN.
It is based on undocumented assumptions though +( AND key_value = 'NOARCHIVELOG')+.
SELECT *
FROM SYSMAN.MGMT$GROUP_DERIVED_MEMBERSHIPS O ,
    SYSMAN.MGMT$TARGET T ,
    sysman.MGMT$AVAILABILITY_CURRENT st
WHERE
o.member_target_type     IN ('oracle_database', 'rac_database')
AND ( t.target_type           ='rac_database'
OR (t.target_type             ='oracle_database'
AND t.type_qualifier3        != 'RACINST'))
AND o. member_target_guid     = t.target_guid
AND t.target_guid             = st.target_guid
AND st.availability_status    = 'Target Up'
AND ( EXISTS
    (SELECT *
    FROM sysman.mgmt$metric_current i
    WHERE I.TARGET_GUID = O.MEMBER_TARGET_GUID
    AND metric_name     = 'archFull'
    AND Metric_Column   = 'archTotal'
    AND metric_label    = 'Archive Area'
    AND column_label    = 'Total Archive Area (KB)'
    AND key_value       = 'NOARCHIVELOG'
    ));Another way to achieve the goal is to push extended metrics (SELECT LOG_MODE FROM V$DATABASE) on each DB, and monitor the values they return to the repository. This is an example for a (slightly) different problem - http://iiotzov.wordpress.com/2012/08/08/how-to-use-the-new-oem-12c-metric-extensions-to-enforce-enterprise-wide-custom-policies .
OEM Repository has many other great uses as well - http://iiotzov.files.wordpress.com/2012/05/oem-repository-a-second-look.doc , http://iiotzov.files.wordpress.com/2011/08/iotzov_oem_repository.pdf
Iordan Iotzov
http://iiotzov.wordpress.com/

Estimating the Database Size using Archivelog mode

Dear OTN Forum,
I need to find guidelines to estimate the additional space needed for a database in order to operate in archivelog mode.
I've estimated the size of a database (Tables + indexes= 450 GB + 270 GB) operating in nonarchivelog mode, but I didn't know how to estimate the additional space needed to operate the database in archivelog mode.
Please any kind of information will be well received!
(paper, technical bulletins, metalink, etc.)
Best regards,
Alfredo

The space required for archive logs does not depend on the size of your database. It is dependent on 3 factors.
1. The size of your redo log members. Each archive log will be the same size as a redo log file.
2. The number of transactions you do in the database. Each transaction writes information to the redo logs, and each redo log is archived when it is full.
3. How laong a period you want to keep the archive logs available on disk for.
For example, one of our systems is a very active OLTP system with about 500 users at peak times and around 100 fairly constantly. The database is about 40Gb, but it spins 15 - 20 64Mb archive logs each day. Typically, we keep 2 days worth of logs on-line at any given time. so, this system requires between 1.8 and 2.5 GB for archive logs.
Another system, used mostly for reporting purposes, is over 100GB, but typically generates 5 - 6 32MB archive logs each week. So, it requires less than 200Mb for archive logs.
HTH
John

Database in Archivelog mode

Hi
All,
I have oracle 9.2.0.6 at my workplace.right now my database running in ARCHIVELOG MODE. I want to set it to NOARCHIVELOG MODE.
can I do on the fly? in other way, Do I need to shutdown and restart database?
Any help will be appreciated.
Thanks,
Vishal

Hi,
Issue the following commands to put a database into NOARCHVELOG mode:
1) Take Back up of Present SPfile by creating pfile
create pfile from present spfile.
2) Shutdown the database by SUTDOWN IMMEDIATE.
3) Take Cold backup of the database.
4) Change the parameter in the pfile.
log_archive_start = FALSE
#log_archive_dest_1 = 'LOCATION='Your location'
log_archive_dest_state_1 = DISABLE
#log_archive_format = %d_%t_%s.arc
5) And make a spfile from the modified pfile in default location .
6) Start the database with spfile.
SQL> CONNECT sys AS SYSDBA
SQL> STARTUP MOUNT ;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE OPEN;
NOTE 1: Remember to take a baseline database backup right after disabling archivelog mode. Without it one would not be able to recover.
Regards
Jafar

Archivelog mode during Database upgrade

I have database that needs to be upgraded (from 8.1.7 to 10.2.0.4) and this database runs in ARCHIVELOG MODE. My question should I turn archivelog mode off during upgrade? Do you see any benefits or issues with that?

Better option to put database in no archivelog mode. Take a backup and then put database in noarchivelog mode.
Log_archive_format will be different in 10g so while enable you may need to change this parameter.

Force logging in archivelog mode

Hi !!!
What happen if I have "force_logging" parameter set to true when the database is in archivelog mode ?
Thanks.

rarain wrote:
Hi Juamd,
You should only use this option when it is really required because this option will forcibly generate redo for all Nologging operations that means you might find more archives and you need to setup more space for archive.
Normally we use this option when we need to replicate data changes from one database to another database like in standby configuration, Golden Gate replication etc. I would suggest you to monitor Redo amount generated after enabling this option and accordingly estimate archive space and backup space for archive.
Thanks...Ah, don't agree with that at all. You can compromise your recovery if you happen to want to restore to a point-in-time when there was a NOLOGGING operation going on. Fine, if it's an index, but if it happens to be on a table...
(Yes, been there, done that - with a non-Production database, thankfully)
This is one of the 'must haves', IMO, for Production - set it at the database-level and it overrides any tablespace or object setting.
Archivelogs are generated for a reason. If you have a particular operation that really does massively benefit from NOLOGGING and is something you are sure that you simply re-run/re-create yourself, fine. If not, by default, you really should FORCE LOGGING.

Restore database

Hi,
I try learn how restore database.
Case:
Database is in archivelog mode and hot backup runs every night at 2:00am by cron job and backup.sh
I drop table using
drop table mytbl purge;So I can not get it from recyclebin.
Or I do some other mistake and I like restore whole database to state where it was in certain time
I have try read all kind documents and experiment how to do this without luck.
If someone could give me steps to do restore
Thanks advance
Br,Jari

Here is a full scenario with RMAN.
First backup database with RMAN:
C:\oraclexe\oradata\XE>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Thu May 13 20:26:46 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: XE (DBID=2584040801)
RMAN> backup database plus archivelog;
Starting backup at 13-MAY-10
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=38 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=166 recid=165 stamp=718921614
channel ORA_DISK_1: starting piece 1 at 13-MAY-10
channel ORA_DISK_1: finished piece 1 at 13-MAY-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_05_13\
O1_MF_ANNNN_TAG20100513T202656_5YRK3KKF_.BKP tag=TAG20100513T202656 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 13-MAY-10
Starting backup at 13-MAY-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
input datafile fno=00003 name=C:\ORACLEXE\ORADATA\XE\SYSAUX.DBF
input datafile fno=00002 name=C:\ORACLEXE\ORADATA\XE\UNDO.DBF
input datafile fno=00004 name=C:\ORACLEXE\ORADATA\XE\USERS.DBF
input datafile fno=00005 name=C:\TMP\DF1
channel ORA_DISK_1: starting piece 1 at 13-MAY-10
channel ORA_DISK_1: finished piece 1 at 13-MAY-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_05_13\
O1_MF_NNNDF_TAG20100513T202658_5YRK3LWO_.BKP tag=TAG20100513T202658 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 13-MAY-10
channel ORA_DISK_1: finished piece 1 at 13-MAY-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_05_13\
O1_MF_NCSNF_TAG20100513T202658_5YRK4FH7_.BKP tag=TAG20100513T202658 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 13-MAY-10
Starting backup at 13-MAY-10
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=167 recid=166 stamp=718921646
channel ORA_DISK_1: starting piece 1 at 13-MAY-10
channel ORA_DISK_1: finished piece 1 at 13-MAY-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_05_13\
O1_MF_ANNNN_TAG20100513T202726_5YRK4HRM_.BKP tag=TAG20100513T202726 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 13-MAY-10
RMAN> exit
Recovery Manager complete.Drop the table:
C:\oraclexe\oradata\XE>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu May 13 20:27:34 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> select to_char(sysdate,'YYYY-MM-DD:HH24:MI:SS') time_now from dual;
TIME_NOW
2010-05-13:20:27:38
SQL> select count(*) from test.t;
COUNT(*)
         1
SQL> select to_char(sysdate,'YYYY-MM-DD:HH24:MI:SS') time_now from dual;
TIME_NOW
2010-05-13:20:27:56
SQL> drop table test.t purge;
Table dropped.
SQL> select to_char(sysdate,'YYYY-MM-DD:HH24:MI:SS') time_now from dual;
TIME_NOW
2010-05-13:20:28:10Stop database instance, restart database in MOUNT mode (this is the missing step in your last message)
and restore database (RMAN will use last backup by default):
SQL> shutdown abort
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Produ
ction
C:\oraclexe\oradata\XE>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Thu May 13 20:28:34 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup mount;
Oracle instance started
database mounted
Total System Global Area     805306368 bytes
Fixed Size                     1289996 bytes
Variable Size                213909748 bytes
Database Buffers             587202560 bytes
Redo Buffers                   2904064 bytes
RMAN> restore database;
Starting restore at 13-MAY-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=35 devtype=DISK
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
restoring datafile 00002 to C:\ORACLEXE\ORADATA\XE\UNDO.DBF
restoring datafile 00003 to C:\ORACLEXE\ORADATA\XE\SYSAUX.DBF
restoring datafile 00004 to C:\ORACLEXE\ORADATA\XE\USERS.DBF
restoring datafile 00005 to C:\TMP\DF1
channel ORA_DISK_1: reading from backup piece C:\ORACLEXE\APP\ORACLE\FLASH_RECOV
ERY_AREA\XE\BACKUPSET\2010_05_13\O1_MF_NNNDF_TAG20100513T202658_5YRK3LWO_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_05_13\
O1_MF_NNNDF_TAG20100513T202658_5YRK3LWO_.BKP tag=TAG20100513T202658
channel ORA_DISK_1: restore complete, elapsed time: 00:00:36
Finished restore at 13-MAY-10Recover database to a point in time before DROP TABLE
RMAN> recover database until time "to_date('2010-05-13:20:27:00','YYYY-MM-DD:HH2
4:MI:SS')";
Starting recover at 13-MAY-10
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:01
Finished recover at 13-MAY-10Open the database and check that dropped table is back:
RMAN> alter database open resetlogs;
database opened
RMAN> exit
Recovery Manager complete.
C:\oraclexe\oradata\XE>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu May 13 20:34:24 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> select count(*) from test.t;
COUNT(*)
         1
SQL>

Unable to restore database using RMAN in oracle 10g

Hi Everyone!!!!!!!
I have following scenario. In which I don't want to drop newly created tablespace (test). So, let me know how to restore database from existing backup without dropping new tablespace and taking new backup?
1. I took database backup as
RMAN > backup database;
2. Create one tablespace "test"
3. Then I tried to restore database as (In mount mode)
RMAN > restore database
4. But I can't restore database. Even I tried after taking "test" tablespace offline , It returns error as follow
ORA-01119: error in creating database file 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTCAT\TEST.DBF'
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
Please suggest me step/way so that I can restore database without taking new backup or dropping new tablespace (test).........

Hello;
Rename this datafile :
D:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTCAT\TEST.DBF
Then try the restore again.
If this isn't a test database stop and think about how you will recover if this does not work. That is how will you recover from the recover if it goes bad?
Best Regards
mseberg

No archivelog mode and logging option

hi i am having a database 9i on windows 2000 adv server. my database is in no archivelog mode. i am creating a table with logging option as follows
create table x(no number(1))
logging;
table created
please let me know where the information will be logged? whether into trace files because database is in no archivelog mode.

Logging information is always recorded in your redolog files, irrespective whether your database is in ARCHIVELOG mode or NOARCHIVELOG mode.
By default a table is created in LOGGING mode, you don't have to explicitly specify it.
Here is an example:
SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            /u10/app/oracle/product/oracle10g/dbs/arch
Oldest online log sequence     11
Current log sequence           13
SQL> create table t(a number);
Table created.
SQL> select logging from user_tables where table_name = 'T';
LOG
YES

ARCHIVELOG MODE --- Please assist

dear experts,
I have this doubt in my mind and would like you guys to advise on.
Is it true that when a database is in ARCHIVELOG MODE, database recovery using archived logs & hotbackup is possible to the last commit?
probably using the command: recover database using backup controlfile until cancel; (to apply all the arhive logs to last hotbackup)
From my point of view, i feel that the database recovery using the ARCHIVED LOGS and hotbackup is possible only up to the last redo log switch. In order to recover the database to the last commit, I have to recover the database using both the ARCHIVED LOGS as well as the last ACTIVE REDO LOG.
It is because the most recent commited transactions on the current redo log might not be written to archive log (as the active log is not full and no alter system switch logfile performed) at the point of time when the db crashed.
Please advise.
thanks all!

Also, by using RMAN you can approach more to the last commit with RMAN parameters like SCN, etc.
It's quite easy!

Comming out from archivelog mode

Hi,
I have a database which is in archive log mode. How can I come back to non archive log mode ?
Many thanks.

Setting log_archive_start = true in init.ora file enables automatic archiving of redo log files.
You will disable automatic archiving if you say.
SQL> ALTER SYSTEM ARCHIVE LOG STOP;
Now you have to archive the redo log manually. If the database is in archivelog mode and automatic archiving is disabled and if log switch happens then LGWR cannot overwrite the redo log file which is not yet archived. I experimented on my test machine and database operation hang up as follows.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> alter system switch logfile;
System altered.
SQL> /
hanged here.
If you say the following then database will not be in archivelog mode. LGWR will overwrite the redolog files and will not wait for archiving as the database is in noarchivelog mode.
SQL> startup mount
SQL> alter database noarchivelog;
Now it depends upon your requirement. Do you want to stop the current archivelog mode temporarily or permanent ?
aijaz

Enable archivelog mode while datbase is open

Hi everybody
Kindly I need to ask if possible to enable archivelog mode while database in open status for oracle 11g? and if yes .. what is the statment?
Thanks in advance
Edited by: user11254543 on Jun 8, 2011 11:51 PM

You cant enable the archivelog mode when the database is in nomount state because the archive log information is kept in Control file like db in archivelog mode or not,log sequence number,SCNs,logfiles members,etc.. When we start the database in nomount state then only the pfile/spfile is read and sga is allocated and background processes are started but no controlfile is read ..to read the controlfile the database must be started in mount state..Why we require a controlfile is because it stores critical information about the database...If we start the database in mount state then it recognizes whether database is in archivelog mode or not , If it is in archivelog mode then it sees whether an instance recovery is needed or not by verifying the log sequence numbers in controlfile,redologfile & the datafile ..If an instance recovery is required then it performs the instance recovery by calling smon background process or if a datafile header is not up to date then we have to perform the media recovery using the redo logfiles...
For open state you have to post the reply..it will help you to explore yourself...Good Luck!

Archivelog Mode Disadvantages

Hello,
We have a 9i DB running Bussiness Objects taking up 15 TB of space.
We need to take hot backups, therefore we need to switch to Archivelog mode.
What are the main disadvantages of doing that? (Performance, Space, etc.)
Please do let me know what info you need regarding the performance of the DB so you can make an arpox estimation.
Thank you in advance.

Chinar wrote:
You have 15 TB database with NOARCHIVELOG mode and that is very dangerous.That decision can only be made given the requirement and risk analysis of the content of that database.
The nature of data in the database is very much relevant here. Not all data is critical business data. Data can be transient in nature - in other words, data with a short TTL (time-to-live). And transient data is often pretty large in volume too (think along the lines of telemetry type data where the requirement is for a 5 minute semi-realtime processing window) .
Yes, the majority of corporate information systems are not like this. But one cannot make a blanket statement that a database not running archivelog mode, is "+dangerous+".
Oracle is not just used in the run-of-the-mill databases dealing with HR, financials and the like. Archive logging should be a conscious decision taking requirements and risks into account - and not an automatic mandatory requirement. Yes, in most cases archive logging will be decided on. And that is not the issue - the issue is that the decision was based on actual requirement analysis and not a "+rule of thumb+" that seems to be a good idea..

Restore database in archivelog mode

Hello everyone.
I've been looking on google, how to restore my database on archivelog mode, but i did not succeed.
I made my backup using this mode, and now i need to know what is the command need to use to restore this.
Somebody can write the command here please ?
Thanks for help.
Regards,
Dan
ps: Using Oracle 10g XE on Win XP.

user8973191 wrote:
Oh, ok Vijayaraghavan K.
Thx for u help.
And about the users ?
i need to create the "same" user in another machine ?
For example:
In this machine i using the "system" user, where i have my tables.
Another machine, when i restore, my tables will go to the "system" user too? or i can choice? or i need to create one?A true backup is a copy of the data files at the file/block level. The restore is therefore a restore of the data files/blocks. Applying the redo (archive logs) is also done at the block level. None of that knows or cares (or needs to know or care) about logical objects (such as users, tablespaces, tables, rows, etc) within the database. so if you do a proper restore, you are restoring files to a consistent state and thus everything that was defined within those files will be there when restored.

Restore database in no archivelog mode

Similar Messages

Maybe you are looking for