Introduction
Introduction.Basis Administration in the Age of SAP HANA require a new skills from SAP Basis Administrators. One of them HANA DB Maintenance & Upgrade. For example: DB-revisions should be installed at regular intervals to avoid errors and to keep your Database up to date
Prerequisites for HANA DB Upgrade
You want install new revision on SAP HANA database. For example in EWA report you found “A critical SAP Note exists for your current SAP HANA revision”
Resolution
Find correction on SAP Launchpad. For example if you want upgrade Rev037_1 to Rev037_3
Don’t forget about installed plugins. Check installed Plug-ins in Hana Studio or in DBACockpit transaction.
Download SAR archives with correct version from Launchpad too
NB: For HANA DB Rev037_3 ->LCAPPS plugin must be 037.03 version too
Let’s start update process in Dev landscape.
Extract files from SAR archives.
NB: Very important moment. Structure after extracting procedure must be separated
Stop SAP systems. ERS – ASCS (SCS) – Dialog Instance (-es)
NB: stopsap j2ee *for Java systems
stopsap R3 *for ABAP systems
Make backup for SYSTEMDB and ALL tenants
Stop HANA DB
NB: su <sidadm>
/usr/sap/<sid>/<sid><instance>/HDB stop
NB: Average time for HANA DB stopping: 5-20 minutes (this measure depends on the DB-size).
Now we are ready for upgrade
Run command from root privileges from folder with extacted HANA Revision files,
NB:For example OS-path may be:
/<path>/SAP_HANA_DATABASE/hdblcm –ignore=check_signature_file
NB: Installation process must be from SYSTEM (SAP HANA initial DB super user)
If you lock this user for security reasons ->
Unblock SYSTEM user for this task
Updating process…
Updating process (continious)
Check Hana NEW version after updating procedure.
NB: /usr/sap/<sid>/<sid><instance>/HDB version
HANA DB already started automaticaly at this point so time to start application server in reserve sequence
ERS – ASCS (SCS) – Dialog Instance(es).
NB: startsap j2ee *for Java systems
startsap R3 *for ABAP systems
Log-in in your SAP system to 000 client and check ouput of transaction SICK
NB:Result must be – no errors reported.
Repeat steps above for HANA DB in QAS system and after additional approvals in PROD landscape.
No comments:
Post a Comment