Académique Documents
Professionnel Documents
Culture Documents
When a tablespace is put into advancement mode, Oracle will address absolute blocks to accommodate rather than the accepted change vectors. For this reason,
do not accomplish a hot advancement during periods of abundant database action - it could advance to a lot of annal logs actuality created.
This action will put all tablespaces into advancement approach at the aforementioned time. If the antecedent database is absolutely ample and you anticipate that
it ability booty a continued time to copy, accede artful the tablespaces one at a time, or in groups.
While the advancement is in progress, it will not be accessible to booty the tablespaces offline commonly or shut bottomward the instance
spool e:\oracle\beginbackup.sql
spool off
spool e:\oracle\endbackup.sql
spool off
3.Put the source database into backup mode using beginbackup.sql file. This will put all of the databases tablespaces into backup mode.
SQL> @beginbackup.sql
4.Copy the files to the new location copy, scp or ftp the files from the source database/machine to the target.
5.Take the source database out of backup modeOnce the file copy has been completed, take the source database out of backup mode.
SQL> @endbackup.sql
http://naeemsheeraz.blogspot.com/search/label/Backup 1/3
23/11/2017 Oracle DBA -Tutorials: Backup
Then, identify which archive log files are required. When run, the following query will ask for a change number. This is the number noted in
9.Add a new entry to oratab and source the environment (Only Linux)
Edit the /etc/oratab (or /opt/oracle/oratab) and add an entry for the new database.Source the new environment with '. oraenv' and verify that it has worked by
issuing the following
command:
echo $ORACLE_SID
If all goes to plan you will see the instance start and then the message 'Control file created'.
Check that the database has opened with: The status should be 'OPEN'
http://naeemsheeraz.blogspot.com/search/label/Backup 2/3
23/11/2017 Oracle DBA -Tutorials: Backup
select status from v$instance;
It should return only ONLINE and SYSTEM. Take a quick look at the alert log too.
shutdown immediate
startup mount
NID will ask if you want to change the ID. Respond with 'Y'. Once it has finished, start the database up again in sqlplus:
shutdown immediate
startup mount
alter database open resetlogs
18.Configure TNS Add entries for new database in the listener.ora and tnsnames.ora as necessary.
Posted byNaeem SheerazatTuesday, January 19, 2010 0 comments
Labels:Backup
http://naeemsheeraz.blogspot.com/search/label/Backup 3/3