Solution : https://service.sap.com/sap/support/notes/147243 (SAP Service marketplace login required)
Summary :
This SAP Note outlines a non-traditional method for copying an SAP system to another computer without using R3LOAD, focusing on direct database file transfers via backup/restore processes. Key prerequisites include ensuring SAP Data Dictionary and database consistencies. Steps involve system halts, SQL script generations for control files, appropriate NLS_LANG settings, and installation adjustments using specific SAP setups or templates. Post-setup adjustments include logging, stopping services, and editing the init configuration. Critical reminders about restarting database services to ensure systematic component updates are emphasized.
Key words :
svrmgrl connect internal shutdown normal startup alter database backup controlfile, svrmgrl connect internal startup nomount @< pfad>\control, oracle<oraclehomename>agent windows service, sql statement create controlfile remains, sql alter database open resetlogs, alter system switch logfile, create controlfile reuse database, create controlfile set database, \users\<sid>adm\install, online redolog files <drive>
Related Notes :
| 578004 | Win 32-Bit: Install. SAP Systems w/ Oracle 9.2.0 w/ R3SETUP |
| 554112 | Important Changes in Oracle9i |
| 381674 | Oracle and NT: NLS_LANG must be set |
| 101215 | INST: 3.1I R/3 Inst. - Homogeneous System Copy |
| 71254 | Using BRBACKUP/BRRESTORE to copy a database |