Solution : https://service.sap.com/sap/support/notes/604680 (SAP Service marketplace login required)
Summary :
This SAP Note details the steps necessary to rename an SAP DB or liveCache instance on systems running versions up to 7.7. For later versions, refer to Note 1427931. The procedure applies both to Windows, using the 'ren' command, and Unix-like systems, utilizing 'mv'. Key stages include stopping the instance, unregistering and re-registering services, renaming directories and files, and updating the system configuration to reference the new instance name. It's crucial to use the WITHOUTFILES option when dropping the old database to avoid file deletion. The comprehensive steps ensure a smooth transition to a new instance name without data loss.
Key words :
log_mode single maxarchivelogs 2 maxdatadevspaces 2 maxdatapages 12800 archive_log_001 3840, \sapdb\data\wrk\trg param_put diag_history_path <drive>, \sapdb\trg\sapdata\dat_0001 param_put archive_log_001, \sapdb\data\wrk\trg\diaghistory param_commitsession 12, \sapdb\trg\sapdata\dat_0001 param_put log_volume_name_001, dbs/ada/schema=sap<src>note, \sapdb\trg\db db_create trg <dbm_user>, <sysdba_user_password> sql_execute rename user sap<src>, profile parameter dbs/ada/schema, \sapdb\trg\dbsys\sys_001 param_commitsessionas
Related Notes :
| 1427931 | Renaming a MaxDB or liveCache instance as of Version 7.8 |
| 1377148 | FAQ: SAP MaxDB backup/recovery |
| 500843 | Composite SAP note for COM and SAP liveCache 7.2 or higher |
| 489615 | SAP DB or liveCache system copies via remote pipe |
| 371247 | MaxDB and "Split Mirror" techniques |
| 129352 | Homogeneous system copy with MaxDB (SAP DB) |