Skip to Content

Rename SAP-SID

Hi experts,

we would like to rename our sap testsystems <sid> and also the instance number.

What do I have to do for this WITHOUT USING SAPINST->COPY!

Is it enough to do the following:

1. Renaming the database <SID>

2. Rename /usr/sap/<NEW SID>/DVEBMGS<new instance number>.

3. Maintain the following files in /sapmnt/<SID>/profile (change SID and instance number)

3.a <SID>_DVEBMGS<NO>_host


Is this enough?

Or what else do I have to do.

Thx in advace

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 05, 2012 at 12:56 PM


    If the OS is Unix it is easier but if it Windows it is lot more difficult because of registry getting involved !! And you have to be really a master at knowing what all is dependent of <SID> and Instacne number.

    I have done it on Windows also as well on Unix without SAPinst but trust me it can be painful. Further the list you have published is incomplete. Theoratically you don't need to change DBSID. And is so you are basically doing a system refresh kind of activity involving <sid> change which means control file trace,change of OP$mechansim etc. (if it Oracle). In case of MS-SQL you may not need DB<sid> change but schema change might be needed. Anyways your list in heavily incomplete. You might want never OS level users and even if you don't want that you still need to change environment variables. Lot of files would using SAP<sid> and DB<sid>. You need to change all those. For ex: SAPServices, couple of Oracle files.. Lot of things. Even the new profile files that you create need to be changed. There will be SAP<sid>, DB<SID> and Instance parameters they need to be changed. Better approach is either forget it or else use SAPinst !!



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 05, 2012 at 12:46 PM

    You will have tough time if you proceed with above, I don’t see any other way without SAPInst.


    Sreenivas .Y

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 05, 2012 at 02:45 PM

    Hi Christian,

    Be aware that rebuild of D Systems is not recommended, because you will loose all versiondata of own programms (if you do not transport them to P).

    Also you will have sensible producitve data in D, which must be guarded by authorizations. But this is not possible in an DEV system.

    As a fact, SAP does not recommend rebuilding a D system out of a P.

    SAP does not recommend or support SID renameing for productive systems, but on DEV or Quality.. its ok on your own risk. We rebuild our Q as a DB Copy of our P twice a year. And we rename the SID from e.g. PRD to QUA.

    Dont forget e.g.

    - Renaming of DB and DB Schema

    - BDLS

    - SE03

    - STRUST

    - SCUA SCUG (if ZBV)

    - SPAD

    - BD64

    - WE20

    - WE21

    - SM59

    - SCOT

    - SMT1 SMT2

    - RZ03 RZ04

    - STMS



    ... dunno your exact configuration but you have to check all of these systemdependent things.

    Kind regards


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Christian,

      No sure how useful a crash course would be. But this is what I would suggest assuming DB is Oracle ..Is it ?

      1. To start with shutdown SAP and DB.

      2. Take a complete backup of all relevant SAP/DB file systems.

      3. . Start DB in Mount state and execute as per the system copy guide. Else create controlfile trace usimg SQLplus. All info is in System Copy guides (for database specific section). Change controlfile trace to adapt it to new DB<SID.

      3. Uninstall SAP and DB (retain data files though).Clean up Oracle Home as well and other directories except datafile directories.Cleanup existing SAP directories though take backup of profiles so as to have a reference for parameter values.

      4. Next create new mount points for new SID and mount existing file systems (currently mounted on mount points for old SID).

      4.Next start SAPinst-->System Copy-->Target system Import.. This is akin to installing a new system but not using standard SAP export but your own DB export/DB datafiles.

      5. Choose Backup/Restore method when it asks you for it.

      6. Let it run and take actions as asked.

      7. SAPinst would take care of various OS/DB level activites that you would have to perform otherwisedoing a standard DB refresh.

      8. Once it is done execute application level post refresh steps as mentioned by Manuel.It is in the guide as well.

      Finally and foremost go through the system copy guide to have a clear idea of what needs to be done.

      Point is the steps I have mentioned are recalled from memory and not exhaustive necessarily. Standard guide in marketplace plus OSS notes are very important to read before you start.

      And if it is sucessful transfer $1000 to my Bank A/C for the crash course 🤣..(just kidding 😀)



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.