Back then on HANA SP31 we noticed that when upgrading SAP HANA CLIENT (AIX) in one of our replication source systems (ECC), sometimes you face an installation error in one of the source system application servers, random, sometimes this app servers, sometimes the other one:
ERR: Installation Failed
ERR: Error checking installation
ERR: Preinstall check failed
ERR: There are files locked locked by the following processes:
ERR: |Process Id |
ERR: |23445646 |
ERR: |23434546 |
SAP says that to upgrade, the SAP HANA CLIENT in sources systems and SLT systems don’t need to be down. And as I mentioned, sometimes you can upgrade the SAP HANA CLIENT and it will be upgraded fine, but sometimes we might face this installation error above in one of app servers from the Source system. When this happens, we have to shutdown the app server and run the HANA Client upgrade again in order to complete the upgrade.
Since we can’t gamble when i.e. upgrading the whole HANA Landscape (HANA DB upgrade, SLT DMIS patch and HANA Client, Source systems DMIS patch and HANA Client) in Production, the project requires that ECC system must be shutdown to have the SAP HANA CLIENT upgraded in all its app servers to assure that upgrade error above do not occur. And every time we did like that it worked fine. The problem of doing that way is
that it hard to get approved maintenance windows to execute HANA upgrades as we want to since the business can’t afford to shutdown ECC often.
The desire is to assure that error would not never occur while the source system is still u when executing the SAP HANA CLIENT upgrade.
This is the scenario when this error eventually happens:
- The replication jobs between source system- slt- HANA is stopped
- The ECC source systems have also COPA Accelerator, for that reason you need the SAP HANA CLIENT installed in the source systems, so ECC can connect to HANA and fetch the data for the COPA reports
- The systems are quiet, users locked and jobs on ice, there is no activity
- HANA SP07 revision 741
It looks like this is caused by the COPA Accelerator, the user runs the COPA reports in ECC and HANA DB Client open the connection to HANA DB servers. It looks like that communication “bridge” between source system and HANA DB remains open, and maybe for that reason, when trying to upgrade the HANA Client it throws that precheck error, like something is still in use/open, not allowing the HANA CLIENT UPGRADE to be executed.
Somehow the HANA CLIENT install/upgrade media by SAP can’t manage to handle that situation. As explained in the scenario, everything is quiet, it could perfectly ignore it and force the upgrade, or provide an option for it. The hope was with the new HANA SPS, the new SAP HANA CLIENT install versions the installation script would better or overcome such problem.
Does anyone have ever experienced this problem when upgrade the SAP HANA CLIENT in a source system? If so, how to manage this problem without having to shutdown the application server?
Thanks,
Rod