Sap Hana rename

[viper1986]

Hello, 

I recover Sap Hana server from backup and change hostname.

In /hana/data and /hana/log there is not .dat files since we exclude them in backup.

I try to rename system but I got errors.

When I perform this operation in last year I was able to rename system and recover SYSTEMDB.

Logs:
13:44:45.885 - INFO: Renaming instance...
13:44:45.896 - INFO: Testing conversion of topology...
13:44:45.896 - INFO: Updating /hana/shared/HRP/HDB90/hostname01n/sapprofile.ini...
13:44:45.896 - INFO: Updating value 'SAPLOCALHOST' in section '' ('hostname01n' => 'hostname01nres')
13:44:45.896 - INFO: File '/hana/shared/HRP/HDB90/hostname01n/sapprofile.ini' updated
13:44:45.896 - INFO: Checking -convertTopology result...
13:44:45.962 - INFO: Switching to user id 1001 and group id 601.
13:44:45.962 - INFO: Starting external program /hana/shared/HRP/HDB90/exe/hdbnsutil
13:44:45.962 - INFO: Command line is: /hana/shared/HRP/HDB90/exe/hdbnsutil -convertTopology --oldHost=hostname01n --newHost=hostname01nres --test
13:44:46.797 - INFO: Output line 1: nameserver hostname01nres:39001 not responding.
13:44:46.798 - INFO: Output line 2: Opening persistence ...
13:44:46.834 - INFO: Output line 3: assign failed with persistence startup error. exception 1: no.3020151 (DataAccess/PageAccess/impl/DataVolumePartitionFiles.cpp:151) TID: 64328
13:44:46.834 - INFO: Output line 4: No DataVolume files found in path "/hana/data/HRP/mnt00001/hdb00001/"
13:44:46.834 - INFO: Output line 5: exception throw location:
13:44:46.834 - INFO: Output line 6: 1: 0x00007fff927188b0 in PageAccess::DataVolumePartitionImpl::init(Configuration::ConfigurationHandler&, Diagnose::StatisticsData const*, PageAccess::ExtendedDataVolumePartitionInfo const&, bool
)+0x17e0 at DataVolumePartitionFiles.cpp:151 (libhdbdataaccess.so)
13:44:46.835 - INFO: Output line 7: 2: 0x00007fff92723370 in PageAccess::DataVolumePartition::createInstance(ltt::allocator&, Configuration::ConfigurationHandler&, Diagnose::StatisticsData const*, PageAccess::ExtendedDataVolumePar
titionInfo const&, bool, bool)+0x1b0 at DataVolumePartitionImpl.cpp:114 (libhdbdataaccess.so)
13:44:46.835 - INFO: Output line 8: 3: 0x00007fff92733bb8 in PageAccess::DataVolumeImpl::addPartition(unsigned int, ltt::basic_string<char, ltt::char_traits<char>, ltt::integral_constant<int, 64> > const&, bool, bool, bool)+0xe8 a
t DataVolumeImpl.cpp:464 (libhdbdataaccess.so)
13:44:46.835 - INFO: Output line 9: 4: 0x00007fff92734c0c in PageAccess::DataVolumeSPI::createInstance(ltt::allocator&, Configuration::ConfigurationHandler&, Diagnose::StatisticsData const*, PageAccess::PageIO const&, PageAccess::ExtendedDataVolumeInfo const&)+0x30c at DataVolumeImpl.cpp:434 (libhdbdataaccess.so)
13:44:46.835 - INFO: Output line 10: 5: 0x00007fff926a5980 in PageAccess::PageIO::createInstance(ltt::allocator&, Configuration::ConfigurationHandler&, Diagnose::StatisticsData const*, PageAccess::ExtendedDataVolumeInfo const&)+0x240 at PageIOImpl.cpp:766 (libhdbdataaccess.so)
13:44:46.835 - INFO: Output line 11: 6: 0x00007fff92b5c2a0 in DataAccess::PersistenceManagerImpl::createInstance(ltt::refcounted_handle<DataAccess::PersistenceConfigurationSPI>&, bool, bool, bool)+0x1650 at PersistenceManagerImpl.cpp:1954 (libhdbdataaccess.so)
13:44:46.835 - INFO: Output line 12: 7: 0x00007fff92b80180 in DataAccess::PersistenceManager::open(ltt::refcounted_handle<DataAccess::PersistenceConfiguration> const&, bool)+0xc0 at PersistenceManager.cpp:164 (libhdbdataaccess.so)
13:44:46.835 - INFO: Output line 13: 8: 0x00007fff958e9d48 in PersistenceLayer::PersistenceSystem::initialize(NameServer::ServiceStartInfo const&, bool, PersistenceLayer::PERSISTENCE_MODE)+0x788 at PersistenceSystem.cpp:456 (libhdbpersistence.so)
13:44:46.835 - INFO: Output line 14: 9: 0x00007fff95892bf8 in PersistenceLayer::PersistenceFactory::initPersistence(PersistenceLayer::PERSISTENCE_MODE, DataAccess::TransactionCallback*, NameServer::ServiceStartInfo&, ltt::refcounted_handle<TransactionManager::TransactionControlBlockFactory>&, bool, ltt::smartptr_handle<DataAccess::DisasterRecoverySecondaryCallback>&, bool)+0x6d8 at PersistenceFactory.cpp:463 (libhdbpersistence.so)
13:44:46.835 - INFO: Output line 15: 10: 0x00007fff8f086ad4 in PersistenceController::startup(PersistenceLayer::PERSISTENCE_MODE, NameServer::ServiceStartInfo*, bool, DataAccess::TablePreloadWriteCallback*, DataAccess::TablePreloadReadCallback*, Backup::RecoverCbc_Federation*)+0x1434 at PersistenceController.cpp:611 (libhdblogger.so)
13:44:46.836 - INFO: Output line 16: 11: 0x00007fff9c414268 in NameServer::Topology::startPersistence(NameServer::ServiceStartInfo&, bool) const+0x28 at Topology.cpp:280 (libhdbns.so)
13:44:46.836 - INFO: Output line 17: 12: 0x00007fff9c41bffc in NameServer::Topology::initPersistence(NameServer::ServiceStartInfo&, bool, bool, TREX_ERROR::TRexError*, bool, ltt_adp::basic_string<char, ltt::char_traits<char>, ltt::integral_constant<bool, true> >, NameServer::ServiceStartInfo::RequestAction)+0x3ac at Topology.cpp:393 (libhdbns.so)
13:44:46.836 - INFO: Output line 18: 13: 0x00007fff9c41d350 in NameServer::Topology::initPersistence(bool, bool, TREX_ERROR::TRexError*, bool, ltt_adp::basic_string<char, ltt::char_traits<char>, ltt::integral_constant<bool, true> >, NameServer::ServiceStartInfo::RequestAction)+0x250 at Topology.cpp:275 (libhdbns.so)
13:44:46.836 - INFO: Output line 19: 14: 0x0000000125c98538 in NameServerCmd::CommonHostAction::initPersistence(bool, TREX_ERROR::TRexError*, ltt::smart_ptr<NameServer::Topology, ltt::integral_constant<bool, false>, ltt::integral_constant<bool, false> >, bool, ltt_adp::basic_string<char, ltt::char_traits<char>, ltt::integral_constant<bool, true> >, NameServer::ServiceStartInfo::RequestAction)+0x78 at host.cpp:302 (hdbnsutil)
13:44:46.836 - INFO: Output line 20: 15: 0x0000000125bf04f4 in NameServerCmd::TopologyAttachGuard::initPersistence(bool, TREX_ERROR::TRexError*, bool, ltt_adp::basic_string<char, ltt::char_traits<char>, ltt::integral_constant<bool, true> >, NameServer::ServiceStartInfo::RequestAction) [clone .constprop.0]+0xc4 at TopologyAttachGuard.h:57 (hdbnsutil)
13:44:46.836 - INFO: Output line 21: 16: 0x0000000125c32ffc in NameServerCmd::CmdActionConvertTopology::performCommand()+0x1fc at convertTopology.cpp:107 (hdbnsutil)
13:44:46.836 - INFO: Output line 22: 17: 0x0000000125be66c8 in main+0x998 at TopologyCmdAction.cpp:29 (hdbnsutil)
13:44:46.836 - INFO: Output line 23: 18: 0x00007fff90626fe0 in System::mainWrapper(int, char**, char**, void*)+0x50 at IsInMain.cpp:339 (libhdbbasis.so)
13:44:46.836 - INFO: Output line 24: 19: 0x00007fff8f346620 in generic_start_main.isra.0+0x140 (libc.so.6)
13:44:46.836 - INFO: Output line 25: 20: 0x00007fff8f346834 in __libc_start_main+0xb4 (libc.so.6)
13:44:46.836 - INFO: Output line 26: 21: 0x00007fff9061dc0c in __libc_start_main+0xac at IsInMain.cpp:369 (libhdbbasis.so)
13:44:46.836 - INFO: Output line 27: 22: 0x0000000000000000 in <no symbol>+0x0 (<unknown>)
13:44:46.836 - INFO: Output line 28:
13:44:46.836 - INFO: Output line 29: exception type information:
13:44:46.837 - INFO: Output line 30: - 0: public ltt::exception@0x7fff9016f140
13:44:46.837 - INFO: Output line 31: stopping service...
13:44:46.837 - INFO: Output line 32: error: Unknown persistence layer error
13:44:46.837 - INFO: Output line 33: failed.
13:44:47.086 - INFO: Program terminated with exit code 1

[S_Sriram]

Hi After restoring the DB in a different host you may have to run the swpm to build the system.

[umasaral]

Hi 

Please try the below steps

1. Check Data Files: Ensure the required `.dat` files are present in `/hana/data`. They may have been excluded from the backup.

2. Validate Backup: Confirm the backup is complete and includes all necessary files.

3. Update Configurations: Verify that `sapprofile.ini` is correctly updated with the new hostname.

4. Run NameServer Check: Use `hdbnsutil -sr_check` to ensure the NameServer is operational.

5. Review Logs: Look for additional errors in `/hana/shared/<SID>/trace/` for more context.

6. Restore Missing Files: If needed, restore from a backup that includes the missing data files.

7. Consult SAP Notes: Check for any relevant SAP Notes for your HANA version regarding recovery issues.

8. Contact SAP Support: If unresolved, reach out to SAP Support with your logs.

9. Documentation: Review official SAP documentation for specific recovery procedures.

10. Backup Strategy: Consider adjusting your backup strategy to include all necessary files in future backups.