Solution : https://service.sap.com/sap/support/notes/1427931 (SAP Service marketplace login required)
Summary :
SAP Note outlines the process for renaming a MaxDB or liveCache instance starting from Version 7.8, with guidance also provided for earlier versions using Note 604680. The renaming involves several steps, including stopping the database, renaming installation directories and files, updating configurations, and re-registering components under the new name. Detailed instructions cater to both Windows and Unix environments, adjusting commands accordingly. Modifications to the run directory and database volume names are crucial to ensure system continuity. The note also covers adjustments to the user profiles and system tables, particularly for database users and client installations.
Key words :
\sapdb\clients\trg\data\installations\cl_src cl_trg 19, \sapdb\trg\data\installations\src trg 8, \sapdb\trg\data\wrk\src trg> dbmcli -, \sapdb\trg\data\config\src trg 6, <sysdba_user_password> db_execute rename user sap<src>, \sapdb\trg\db -sw_kernel -start_listener 9, <password> param_getvolsallokusemirroredlog nomaxlogvolumes 2maxdatavolumes 11logvolumename001 12800, \sapdb\trg\data\wrk\trg 10, dbs/ada/schema=sap<src>, profile parameter dbs/ada/schema
Related Notes :
| 1377148 | FAQ: SAP MaxDB backup/recovery |
| 604680 | Renaming an SAP DB or liveCache instance |
| 489615 | SAP DB or liveCache system copies via remote pipe |
| 371247 | MaxDB and "Split Mirror" techniques |
| 129352 | Homogeneous system copy with MaxDB (SAP DB) |