On Windows NT the change of the hostname requires the installation of a new SAP license !!Before changing hostname perform in R/3:
- finish all jobs and cancel already released jobs
(use transaction SM37; reason: after change of hostname they have to be rescheduled with new hostname)
- check SM13 for any outstanding update requests and either post resp. delete them (errorneous ones)
- stop R/3 and database
Actions in Operating system:
UNIX host:
UNIX host:
1. user root:
a) change hostname in /etc/hosts:
CAUTION: If Yellow Pages or Name Server active change the hostname in the corresponding location !
a) change hostname in /etc/hosts:
CAUTION: If Yellow Pages or Name Server active change the hostname in the corresponding location !
b) If pd hostname = systemname, this must also be changed to the new hostname:
check by command: uname -a
change as user root
c) Windows NT (not feasible for a domain PDC or BDC):
check by command: uname -a
change as user root
c) Windows NT (not feasible for a domain PDC or BDC):
- adapt network settings in the contrp panel
- adapt IP name respution resources
(DNS, HOSTS file, LMHOSTS file)
- adapt SAP service definitions in the registry
- adapt enviroment settings for interactive session and
for R/3 kernel in the registry
2. user <SID>adm on UNIX host:
a) Adapt Instance-Profiles:
- cd /usr/sap/<SID>/SYS/profile
- check R/3 profiles: <SID>_DVEBMGS00, DEFAULT.PFL and START_DVEBMGS00
NOTE:
It is assumed that instance profile maintenance is not performed with CCMS ! (see topic 6.)
The following is valid for ORACLE only:
For other databases please adapt accordingly.
It is assumed that instance profile maintenance is not performed with CCMS ! (see topic 6.)
The following is valid for ORACLE only:
For other databases please adapt accordingly.
b) User <SID>adm and ora<SID>:
- check by "env" if variable TWO_TASK has been set
- check profiles .cshrc and .kshrc, .dbenv.csh and .dbenv.sh
c) User <SID>adm:
change name of:
change name of:
- startsap_<pdhost>_00 --> startsap_<newhost>_00
- stopsap_<pdhost>_00 --> stopsap_<newhost>_00
- change alias for "stopsap" and "startsap" in .cshrc and .kshrc
3. Work on your frontends (most PC's):
a) update HOSTS-File
b) adapt SAPLOGON/SAPGUI configurations
c) adapt configuration of external RFC application
4. Further adaptions:
a) configuration files:
b) adapt SAPLOGON/SAPGUI configurations
c) adapt configuration of external RFC application
4. Further adaptions:
a) configuration files:
- /usr/sap/trans/.sapconf
- /etc/sapconf
b) environment for transport and put:
/usr/sap/trans/bin: TPPARAM
check: tp connect <SID> must be ok
/usr/sap/put/bin : TPPARAM or similar (if present)
/usr/sap/trans/bin: TPPARAM
check: tp connect <SID> must be ok
/usr/sap/put/bin : TPPARAM or similar (if present)
The following c) is valid for DB2 on OS/390 only:a) Check additionally bound DB2/390 plans. The hostname of the application server is part of planname. Therfore it might be necessary to bind new plans.
1. Check if R/3 can be started with new hostname:
startsap
ps -ef I grep dw.sap<SID>: several processes must run !
1. Check if R/3 can be started with new hostname:
startsap
ps -ef I grep dw.sap<SID>: several processes must run !
2. Adaptations in R/3:
a) R/3 Rel. >= 4.0A only: adapt table INSTVERS
b) adapt table THOST and TXCOM
c) adapt all RFC destinations (Transcation SM59)
d) adapt server definitions for R/3 operation modes
e) CCMS: Operation Modes - Profiles - Job definition -
a) R/3 Rel. >= 4.0A only: adapt table INSTVERS
b) adapt table THOST and TXCOM
c) adapt all RFC destinations (Transcation SM59)
d) adapt server definitions for R/3 operation modes
e) CCMS: Operation Modes - Profiles - Job definition -
- Logon Groups
NOTE:
If you use instance profile maintenance with CCMS, RZ10 (30x), please import the adapted profile(s) into CCMS database using RZ10,profile maint, "Import"-Function
f) reschedule periodic batch jobs (see above)
g) adapt printer definitions in SPAD
h) adapt Service Connection and SAProuter configuration
i) adapt SAPLOGON/SAPGUI configurations
If you use instance profile maintenance with CCMS, RZ10 (30x), please import the adapted profile(s) into CCMS database using RZ10,profile maint, "Import"-Function
f) reschedule periodic batch jobs (see above)
g) adapt printer definitions in SPAD
h) adapt Service Connection and SAProuter configuration
i) adapt SAPLOGON/SAPGUI configurations
No comments:
Post a Comment