October 17, 2013

SAP NetWeaver 7.0 Dual Stack Refresh Procedure -4

SAP NetWeaver 7.0 Dual Stack Refresh Procedure -Part 4

8.1.5 Export Java using SAPINST from Source System

Run the Java export at same time as standard database backup if possible

Ensure the latest SAPINST is available.

login as troot
su – sroot

Optionally, copy Master DVD to local file system – There have been issues in the past running SAPINST over an NFS mount. This may or may not still be the case. Also, if SAPINST crashes, a core file cannot be written over the NFS mount, so some details will be missing during diagnosis of the problem.

export DISPLAY=<IP of local PC>:0.0
export JAVA_HOME=/usr/java14_64
export SAPINST_JRE_HOME=/usr/java14_64
export PATH=/usr/java14_64/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin
export LIBPATH=/usr/lib:/lib:/usr/sap/QBI/SYS/exe/run
umask 022

cd /<DVD path>/IM_AIX_PPC64

Run the Database and Central Instance Export step

Netweaver 7.0 SR3 discs do not prompt for Typical or Custom apparently based on the latest execution.


 sapr3 for BW systems

 sap<sid>db for most systems

Ensure the checkbox is selected for “Stop running system”. I have not been prompted to stop the source system. It is unclear what this is actually for, but all documentation requires it to be checked.

Remove the pack directory if it already exists. The SAPINST process attempts to create it and throws an error if it already exists. The pack directory exists under the /usr/sap/<SID>/<INSTANCE>/SDM/program directory. There is a prestep to cover the removal of this directory, and should have been completed at this point.

The export steps should run about 40 minutes to an hour.

8.1.6 Copy export files to target system

cd /usr/sap/put

cp -r * /<NFS mount accessible on target>/

If the Master DVD was copied to a local file system, remove it at this time.


 Will update soon... Check next post...

No comments:

Post a Comment