Database Reference
In-Depth Information
Detailed Import Procedure When Target System Is Already Installed
The following steps must be performed in the source and target systems using the Oracle
offline backup method.
Target System Steps In the target system, make sure that there is enough disk space to copy
the source system database files. If needed, request more disk space ahead of time. Execute
the following preparatory steps in the target system.
1. Stop the SAP system by issuing stopsap with the <sid>adm user account.
2. Log in as ora<sid> and issue sqlplus /as sysdba.
3. Get a control file list by issuing the following SQL command: select name from v$-
controlfile;.
4. Get the datafiles list by issuing the following SQL command: select file_name from
v$datafile;.
5. Get the logfile list by issuing the following SQL command: select group#, member
from v$logfile;.
6. Shut down the Oracle Database by issuing the command shutdown immediate;.
7. Take a full offline backup of the database in case you need to restore it later.
8. Stop the listener by issuing the command LSNRCTL stop.
9. Delete all the control files, datafiles, and logfiles listed in these commands at the oper-
ating system level.
Prepare the Source System and Generate the Control File The following steps have to
be executed in the source system by copying the database files, logfiles, and the generated
control file to the target system and restarting the database in the target system with the new
control file.
1. Complete any open updates in the source system using transaction code SM13.
2. Work closely with the project team to perform any transports to the source system that
would be needed in the target system after the copy.
3.NotethelogicalsystemnamesintransactioncodeSCC4.Thisinformationwillbeuse-
ful in executing the BDLS (conversion of logical systems) post-database copy step.
4. Stop the SAP application by issuing the stopsap R3 command as <sid>adm.
Search WWH ::




Custom Search