SAP SYSTEM RENAME SCENARIOS #ATR

[AJAYTR_ATR66]

#ATR (22) Informative Note:

• Created this blog to provide information on System Rename Scenarios.
• SAP System Rename can be used mostly in scenarios whether we require SID Name Change, Incorrect Hostname Change, FQDN – DNS Problems, SIDADM User Problems.
• Mostly, we will run HDBLCM & SWPM - System Rename post Appliance/IDES Installation since it will be installed with Default SIDs (S4H) and Virtual Host (vhcals4h).

• We will work on the scenarios.

                CASE 1: SIDADM User Problems

                CASE 2: System SID Rename - ABAP/HANA DB (TENANT&SYSTEM)

CASE 1: SIDADM USER PROBLEMS

• Consider, SIDADM user entirely corrupted/deleted or configuration changed during OS level activity.
• I have removed/deleted both ABAP and HANA DB SIDADM user of my SAP System.

• Even if we create manually post SIDADM corrupted/deleted, it won’t be acted as SAP System/HANA Administrator which Environment variables of SIDADM won’t reflect properly resulting in SAP System Stoppage.

INFORMATIVE NOTE:

• We can’t recreate HANA SIDADM user via SWPM. HDBLCM can be used to rename Hana Database which includes Hana user creation as well.
• We can run Operating System Users and Groups – System Rename Option to create ABAP SIDADM user even if DB in Stopped state/DB SIDADM User does not exist.
• We can also run Master System Rename Run for recreating ABAP SIDADM user as well, but DB should be up and running fine to run system rename.

• HANA DB - Make sure to change some properties – Instance Number which will be the priority choice. Else, System Rename won’t occur.

• I have deleted home directory of SIDADM user as well to recreate from scratch.
• ABAP - /home/SIDADM || HANA DB - /usr/sap/SID/home

HANA DB SIDADM User Creation - Run HDBLCM System Rename:

• Select “Rename Hana Database System” - hdblcm.

• Make sure to provide correct User ID of SIDADM. Find UID from any HDB path (EX - /hana/data/HDB)

• Hana DB SIDADM user created successfully and environment variables reflected fine.

• We can also rerun – Rename System once again to change instance number back from 3 to 2.

ABAP SIDADM User Creation – Operating System Users and Groups:

• Mine -> S4HANA System. Hence, I have chosen SWPM 2.0. Choose your SWPM version accordingly w.r.t your SAP System.

Define Parameters:

• Provide corresponding User ID of SID user.

• Choose “Clean up OS users – Removes from sapinst group” accordingly – Optional

Review Parameters:

• It’s just reviewing our provided parameters.

Execute Service:

• ABAP SIDADM user created successfully. Environment variables reflected fine as well.

• We have successfully created both ABAP and HANA SIDADM user.

Establishing ABAP and DB Connection:

• My goal is to showcase scenario when users were completely deleted/corrupted, and configuration needs to be done from Scratch. Hence, Deleted SIDADM Home Directory as well.
• Environment variables – dbms_type and hdbclient alone won’t reflect since it won’t come by default after user recreation.
• Hence, DBMS_TYPE and HDBCLIENT path needs to be set manually.
• HDBUSERSTORE Entry needs to be added for ABAP to connect Hana Database.

Error 1:

• Set dbms_type accordingly and try again. Mine -> HDB.

Error 2:

• Add HDBClient path in LD_LIBARARY_PATH. Mine -> /sapmnt/SID/exe/uc/linuxx86_64/hdbclient – Linux. Hence, Added in Default tab.
• For Others AIX, HP* - Add it in corresponding tab.

Need more information on How to Connect ABAP with HANA DB?

 Please review below blog.

HANA Secondary Database Connection Issues on ECC Oracle system #ATR

Error 3:

• Delete existing/corrupted HDBUSERSTORE DEFAULT Key and Add once again.

• R3trans connection looks fine now. ABAP System runs fine.

WE HAVE SUCCESSFULLY CREATED ABAP/HANA SIDADM Users and Re-established connection with DB.

CASE 2: SYSTEM SID CHANGE:

CHANGING ABAP SID and TENANT DB SID via SWPM SYSTEM RENAME:

• We are going to rename both ABAP SID and HANA TENANT/SYSTEM SID.
• For System Rename run, ensure to run with Short DNS instead of IP/FQDN if SAPINST_USE_HOSTNAME used.
• SWPM will pick our provided value which results in Prerequisite Check Failure and IP assignment to Profiles if IP/FQDN provided.

SWPM System Rename Run

• Run “SWPM” and Select “System Rename” in SWPM.

Define Parameters:

• Enter Source SID and Target SID.

• If this run used for recreating SIDADM users, we can provide same SID for both Source and Target SID.
• Current Scenario – To do actual System Rename.

• Make sure to check whether host reflected correctly as same as DNS Name.

• Provide Hana DB Instance Number and System User (TENANT) Database Password.
• Make sure to have DB up and running fine.

• Database should be up and running fine as already mentioned in “INFO”.

• We can change SAPHANADB, DBACOCKPIT, SYSTEM user password if required. Mine -> I’M just renaming TENANT DB SID only. Passwords can remain same,

• Provide SAPHANADB schema password.

• We can rename TENANT DB SID if required. Mine -> Renaming to H** to H4B. Just making Naming Convention – ABAP – S4B and HANA – H4B.
• Provide SYSTEM (DB) user password.

• Using default HANA Secure User Store (hdbuserstore).

• Provide SIDADM (S4BADM) password.
• Leaving UID/GID/Home Directory as default.

• Chosen “Default Key” – Maintained in our HDBUSERSTORE list.

• Make sure to provide correct FQDN.

• We need to install license key now/ as soon as system rename completed. Mine -> As soon as System Rename completed.
• We can’t able to connect ABAP and DB if license key not applied. Also, Full operations won’t be available while accessing DB via HANA Cockpit/Studio.

• Cleanup OS users (removes sapinst group) – Optional.

Review Parameters:

• It’s just reviewing parameters.

Execute Service:

• We have successfully changed ABAP SID (to S4B) and HANA DB TENANT SID (to H4B) using System Rename run.

CHANGING SYSTEMDB SID via HDBLCM System Rename:

• SWPM – System Rename run can be used to rename ABAP SID and HANA TENANT DBSID only.
• Use HDBLCM System Rename run to change HANA SYSTEM DB SID with SIDADM Users/File directories.

 WE HAVE SUCCESSFULLY CHANGED ABAP SID TO S4B & HANA TENANT/SYSTEM DB SID TO H4B

License Key:

• R3trans will result in License Key Error once system DB SID changed – “only commands for license handling are allowed in current state”.

Wanna know how to apply license key?

Please refer below blog.

SAP LICENSE RENEWAL FROM BASIS END #ATR

Thanks for Visiting!

Please do connect and follow my Linked In Profile.

https://www.linkedin.com/in/ajaytr66/