Monday, February 13, 2012

System Copy of (Duel stack) ABAP+JAVA engine NW2004s in sap screen shots System Copy of ABAP+JAVA engine NW2004s :


Homogeneous system copy :  ( DB Specific Method )
Technical Details:
OS = Windows2003
Database = Oracle 10.2.0.2.0

Source System : (S)
  S_SAPSID               = VRR
  S_Hostname             = SDB     
  S_FQHN                  = SDB.sapdatabase.net
  S_DBNAME            = VRR

Technical Preparation: (S)

-     Check kernel version and patches of S_system update if required
Go to menu bar System à Status
Patch level:






Kernel version:










Check JAVA_HOME (JDK version)
Execute T.C SM13 (check for any canceled or pending updates)
Specify wild card in Client , User  & time

















Re schedule/delete the canceled/pending jobs
Check they are properly deleted/finished in table VBDATA in T.C SE16 or manually delete them from VBDATA
Execute T.C SM37 ( change status of the released jobs to scheduled )

















Execute SM63 (Check the Operation Mode time table)
Make sure operation mode switch does not occur in source system while doing system copy(export preparation etc.,)







Click on “Display”
Execute T.C SALE ( Note all Logical System names)






before doing export in S we need to check whether there is enough space in 
/usr/sap/<SAP SID>/<Instance Dir>/SDM/program/…
Because during Export it generates lot of Archives in program/… sub directories and SAPInst aborts if there is no enough space.
Take Offline full backup using BRTOOLS/DB13





EXPORT Preparation: (S)

Initialize SAPInst   ---- Execute  sapinst.exe 
Or the following command
Go to the location where installation master executable (sapinst.exe) & execute the following command











when you perform DB Specific Method of system copy then select “SAP NetWeaver 2004s Support Release 2 
Additional Software Life-Cycle Tasks 
 System Copy 
Source System Central System 
 Based on AS ABAP and AS Java 
 Database and Central Instance Export” 























If we check Use database specific tools option following contents are exported from source system

  • Export Directory Structure with LABLE files
  • Archives SDM Content ( usr\sap\<sap sid>\DVEBMGS##\SDM\..... )
  • Archives file system content

 In DB specific system copy we to manually backup SAPDB content( which is used for restoring db in target system)













Generate CONTROL file and init<DB SID>.ora in source system:

-          We can generate CONTROL file in two ways

-          One by generating trace file at OS level and changing the trace file according target system specifications. ( here we cant generate init<db sid>.ora , we need to copy the existing file in source system and change it according to target system.)

-          By using ORABRCOPY tool.
It will generate CONTROL.SQL , CONTROL.TRC & init<DB SID>.ora

-          generating control file using ORABRCOPY tool
     
      - ORABRCOPY is a java tool used to generate CONTROL.SQL file ,         CONTROL.TRC & init<DB SID>.ora
      - ORABRCOPY is available as .SAR file in ‘SAP Installation master DVD’
      - < Installation masterDVD>\COMMON\INSTALL\ORA\ORABRCOPY.SAR
            - create a <new directory> at OS level (full permission), copy ORABRCOPY.SAR file into it.
            - uncar the file using SAPCAR

            - execute the command
ora_br_copy.bat –generateFiles –forceLogSwitches –tragetSid <T_SID> -password <SYSTEM users password> -listnerPort <S_SYSTEM port>

Then it will generate CONTROL.SQL , CONTROL.TRC & init<DB SID>.ora 
for the targe system in <new directory>.
compare CONTROL.SQL with CONTROL.TRC ( and alter if any changes)
compare below elements 
   
 
 CONTROL.SQL

    CONTROL.TRC     


MAXLOGFILES 255
MAXLOGMEMBERS 3
MAXDATAFILES 1022
MAXINSTANCES 50
MAXLOGHISTORY 1168

*************************************

LOGFILE
GROUP 1 (
'E:\ORACLE\PI7\ORIGLOGA\LOG_G11M1.DBF',
'E:\ORACLE\PI7\MIRRLOGA\LOG_G11M2.DBF'
) SIZE 50M,
GROUP 2 (
'E:\ORACLE\PI7\ORIGLOGB\LOG_G12M1.DBF',
'E:\ORACLE\PI7\MIRRLOGB\LOG_G12M2.DBF'
) SIZE 50M,
GROUP 3 (
'E:\ORACLE\PI7\ORIGLOGA\LOG_G13M1.DBF',
'E:\ORACLE\PI7\MIRRLOGA\LOG_G13M2.DBF'
) SIZE 50M,
GROUP 4 (
'E:\ORACLE\PI7\ORIGLOGB\LOG_G14M1.DBF',
'E:\ORACLE\PI7\MIRRLOGB\LOG_G14M2.DBF'
) SIZE 50M



**********************************

DATAFILE
'E:\ORACLE\PI7\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',
'E:\ORACLE\PI7\SAPDATA1\UNDO_1\UNDO.DATA1',
'E:\ORACLE\PI7\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',
'E:\ORACLE\PI7\SAPDATA2\SR3_1\SR3.DATA1',
'E:\ORACLE\PI7\SAPDATA2\SR3_2\SR3.DATA2',
'E:\ORACLE\PI7\SAPDATA2\SR3_3\SR3.DATA3',
'E:\ORACLE\PI7\SAPDATA2\SR3_4\SR3.DATA4',
'E:\ORACLE\PI7\SAPDATA3\SR3700_1\SR3700.DATA1',
'E:\ORACLE\PI7\SAPDATA3\SR3700_2\SR3700.DATA2',
'E:\ORACLE\PI7\SAPDATA3\SR3700_3\SR3700.DATA3',
'E:\ORACLE\PI7\SAPDATA3\SR3700_4\SR3700.DATA4',
'E:\ORACLE\PI7\SAPDATA4\SR3USR_1\SR3USR.DATA1',
'E:\ORACLE\PI7\SAPDATA4\SR3DB_1\SR3DB.DATA1',
'E:\ORACLE\PI7\SAPDATA4\SR3DB_2\SR3DB.DATA2',
'E:\ORACLE\PI7\SAPDATA4\SR3DB_3\SR3DB.DATA3'
;
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'E:\ORACLE\PI7\SAPDATA1\TEMP_1\TEMP.DATA1'
  SIZE 1000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M;
   
    MAXLOGFILES 255
    MAXLOGMEMBERS 3
    MAXDATAFILES 254
    MAXINSTANCES 50
    MAXLOGHISTORY 1168

****************************************

LOGFILE
GROUP 1 (
'E:\ORACLE\PI7\ORIGLOGA\LOG_G11M1.DBF',
'E:\ORACLE\PI7\MIRRLOGA\LOG_G11M2.DBF'
) SIZE 50M,
GROUP 2 (
'E:\ORACLE\PI7\ORIGLOGB\LOG_G12M1.DBF',
'E:\ORACLE\PI7\MIRRLOGB\LOG_G12M2.DBF'
) SIZE 50M,
GROUP 3 (
'E:\ORACLE\PI7\ORIGLOGA\LOG_G13M1.DBF',
'E:\ORACLE\PI7\MIRRLOGA\LOG_G13M2.DBF'
) SIZE 50M,
GROUP 4 (
'E:\ORACLE\PI7\ORIGLOGB\LOG_G14M1.DBF',
'E:\ORACLE\PI7\MIRRLOGB\LOG_G14M2.DBF'
) SIZE 50M



***************************************

DATAFILE
'E:\ORACLE\WXI\SAPDATA1\SYSTEM_1\SYSTEM.DATA1', 'E:\ORACLE\WXI\SAPDATA1\UNDO_1\UNDO.DATA1', 'E:\ORACLE\WXI\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',
'E:\ORACLE\WXI\SAPDATA2\SR3_1\SR3.DATA1',
'E:\ORACLE\WXI\SAPDATA2\SR3_2\SR3.DATA2',
'E:\ORACLE\WXI\SAPDATA2\SR3_3\SR3.DATA3',
'E:\ORACLE\WXI\SAPDATA2\SR3_4\SR3.DATA4',
'E:\ORACLE\WXI\SAPDATA3\SR3700_1\SR3700.DATA1', 'E:\ORACLE\WXI\SAPDATA3\SR3700_2\SR3700.DATA2',
'E:\ORACLE\WXI\SAPDATA3\SR3700_3\SR3700.DATA3', 'E:\ORACLE\WXI\SAPDATA3\SR3700_4\SR3700.DATA4',  'E:\ORACLE\WXI\SAPDATA4\SR3USR_1\SR3USR.DATA1', 'E:\ORACLE\WXI\SAPDATA4\SR3DB_1\SR3DB.DATA1', 'E:\ORACLE\WXI\SAPDATA4\SR3DB_2\SR3DB.DATA2', 'E:\ORACLE\WXI\SAPDATA4\SR3DB_3\SR3DB.DATA3’

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'E:\ORACLE\WXI\SAPDATA1\TEMP_1\TEMP.DATA1'
  SIZE 1048576000  REUSE AUTOEXTEND ON NEXT 20971520  MAXSIZE 10000M;



Target System Preparation :

-      install OS (same as S_System)
-          install Oracle (same patch level as S_System)
-          perform all the prerequisites that you do before general installation

-    Initialize SAPInst   ---- Execute  sapinst.exe
Or run the following command
Go to the location where installation master executable (sapinst.exe) & execute the following command














Go to installation dir (\ProgramFiles\sapinst_instdir\NW04S\LM\COPY\ORA\SYSTEM\CENTRAL\AS)
Edit control.xml
Search for update ORACHECK_PAR and delete line row.createDb = false; 
After deleting the line control.xml should like below screen








Stop the installation and restart it again















Copy init<DB SID>.sap from source system, Replace S_SID to T_SID
Place it in /oracle/<DB SID>/102/database/

Similarly copy init<DB SID>.ora that is generated while creating control file in source system using ORABRCOPY tool and Place it in /oracle/<DB SID>/102/database/

Copy the CONTROL.SQL file and place it in 
\Program Files\sapinst_instdir\NW04S\LM\COPY\ORA\SYSTEM\CENTRAL\AS\

Change the S_SID to T_SID in b******.afd in log that is generated while taking offline backup.

Create the file structure that are mentioned below in \oracle\<DB SID>\


Copy the backup of source system and keep it in target system.Switch to the user <SID>ADM and restore the database using the commandNOTE: Use –k yes only if  backup is in compressed modeUse –b <b******.afd> the backup log that is generated during backup and you must change this log according to target system specifications. You can also manually copy the files from source system to target system


Target System Preparation:execute T.C BDLS ( to change logical system names)

Select the profile (old) and delete the profile Import the profile (new)
Go to T.C SM36 
Delete all old jobs

Register the system in SLD
run the URL http://<hostname>:50000/sld ( register ABAP/JAVA)
T.C RZ70 ( ABAP)
NWA tool (ABAP/JAVA)


































   





Reactions:

0 comments:

Post a Comment