...does not work after a system copy?
Check note 1886616! :smile:
SAP Netweaver based systems uses two different variables sets, environment and profile variables.
During a system copy those variables should be updated.
If only the profile variables (<Unit>:\usr\sap\<SID>\SYS\profile\DEFAULT.PFL) are updated, you will be able to start your SAP system but some tools (e.g. tp) which uses the environment variables of your <sid>adm user will not work.
To exemplify:
You have a SAP system ERM located on host VM-MSS-OLD with default database instance, the database variables should be:
- C:\usr\sap\ERM\SYS\profile\DEFAULT.PFL
- dbms/type = mss
- dbs/mss/dbname = ERM
- dbs/mss/schema = erm
- dbs/mss/server = VM-MSS-OLD
- Environment variables of user ermadm:
- DBMS_TYPE=mss
- MSSQL_DBNAME=ERM
- MSSQL_SCHEMA=erm
- MSSQL_SERVER=VM-MSS-OLD
After a system copy of system ERM to host VM-MSS with default database instance, the database variables should be:
- C:\usr\sap\ERM\SYS\profile\DEFAULT.PFL
- dbms/type = mss
- dbs/mss/dbname = ERM
- dbs/mss/schema = erm
- dbs/mss/server = VM-MSS
- Environment variables of user ermadm:
- DBMS_TYPE=mss
- MSSQL_DBNAME=ERM
- MSSQL_SCHEMA=erm
- MSSQL_SERVER=VM-MSS
If a mismatch in the server variable is observed, this could be the cause of the issue:
- C:\usr\sap\ERM\SYS\profile\DEFAULT.PFL
- dbms/type = mss
- dbs/mss/dbname = ERM
- dbs/mss/schema = erm
- dbs/mss/server = VM-MSS
- Environment variables of user ermadm:
- DBMS_TYPE=mss
- MSSQL_DBNAME=ERM
- MSSQL_SCHEMA=erm
- MSSQL_SERVER=VM-MSS-OLD
If the system <SID> is changed during the system copy, all database variables must be updated.
This variables mismatch might affect other SAP procedures, as other tools (e.g. R3trans) also uses the <sid>adm user variables.
Hope you like this blog and any comments/suggestions are welcome!
Regards,
Eduardo Rezende
