Uploaded by Ivy Rose Javier

163218 2024 - Not possible to recover all allocated space from HANA DB table

advertisement
Incident: 163218 / 2024 - Not possible to recover all allocated space from
HANA DB table
ID
Customer
Installation
System
Component
Status
Priority
002075129400001632182024
860401 - SM Investments Corp. (SMIC)
0021134912 - S/4HANA Installation-SMRI
H2T - SMRI New Quality Server HANA Database
SAP HANA Database Persistence (HAN-DB-PER)
In Processing by SAP
High
Communication
14.02.2024 19:47:17 UTC+8 - Problem Description: Ivy Javier (S0021774598)
--- Product/Function --No predicted product
User selected product: SAP HANA, platform edition (Recent)
No predicted product function
User selected product function: SAP HANA, platform edition > SAP HANA Database > Database Performance
Predicted component: HAN-DB-PERF (Product Function)
Component: HAN-DB (Support Assistant)
Product: SAP HANA, platform edition (Support Assistant)
Product function: SAP HANA, platform edition > SAP HANA Database > Database Engine (Support Assistant)
No predicted product function
Component: HAN-DB-PERF (Support Assistant)
Product: SAP HANA, platform edition (Support Assistant)
Product function: SAP HANA, platform edition > SAP HANA Database > Database Performance (Support Assistant)
No predicted product function
--- Support Assistant --Path Taken
Query / Job / Application Slow
Application
S/4 HANA
SAP Standard Application
Questions Answered
Q: Which HANA Revision and S/4 Version are you operating on?
A: 2.00.059.11.1700553860
Q: Is the issue reproducible (provide steps) and do you observe a different behavior on any other system in your landscape?
A: Yes
Q: Did you already try to isolate and trace the problematic DB request? (see recommended content: SQL Trace, PlanViz Trace etc.)
SQL Trace
A: N/A
--- TagID/AreaID --TagID: #3
AreaID: 00109B36D6221EDBB0C0294B430500E8
--- Steps to Reproduce --Please see the attached file for the details.
*Note To SAP:
I give approval for SAP Support to use these Steps to Reproduce, while connected to my impacted non-production environments, even if the
steps result in a change being made and my approval remains valid until the issue is resolved, unless I inform SAP Support otherwise.
--- Description --Hello SAP,
Good day!
We deleted entries in the DBTABLOG table for log entries of the custom table using RSTBPDEL.
After the deletion, the following commands have been executed:
ALTER SYSTEM RECLAIM COLUMN LOB SPACE;
CALL CHECK_TABLE_CONSISTENCY('REPAIR_HYBRID_LOB_OVERHEAD', 'SAPHANADB', 'DBTABLOG');
ALTER SYSTEM RECLAIM DATAVOLUME 120 DEFRAGMENT;
hdbcons 'dvol shrink -o 120'
hdbcons "dvol sbtouch -n 100" then hdbcons 'dvol shrink -o 120'
Additional steps:
a. MERGE DELTA OF "DBTABLOG" FORCE REBUILD;
b. UPDATE "DBTABLOG" WITH PARAMETERS ('OPTIMIZE_COMPRESSION' = 'FORCE');
c. ALTER SYSTEM RECLAIM DATAVOLUME 120 DEFRAGMENT;
Despite all commands, the /hana/data is still the same.
Please see the attached file for reference.
Thank you.
14.02.2024 19:47:18 UTC+8 - Business Impact: Ivy Javier (S0021774598)
The company is losing money by not reclaiming disk space, which results in paying higher AWS storage fees.
14.02.2024 22:08:25 UTC+8 - Info for Customer: SAP
Dear Customer,
I would like to inform you that I have changed the component to HAN-DB-PER for further processing.
My colleagues will contact you shortly.
Best Regards,
Zsolt
Product Support - Business Technology Platform | BTP HANA
SAP Support
15.02.2024 14:54:10 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Hello SAP,
Good day!
Just an update: I executed the command:
a. MERGE DELTA OF "DBTABLOG" FORCE REBUILD;
b. UPDATE "DBTABLOG" WITH PARAMETERS ('OPTIMIZE_COMPRESSION' = 'FORCE');
c. ALTER SYSTEM RECLAIM DATAVOLUME 110 DEFRAGMENT;
197 GB reclaimed
However, I deleted some table entries again. They were the same number as yesterday, but nothing was reclaimed (disk space).
15.02.2024 17:22:53 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Attachment uploaded
15.02.2024 17:23:33 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Hello SAP,
Good day.
Already tried to execute the commands based on the SAP Note 3028886 - Table size on disk does not decrease after data archiving but is still
the same.
Kindly see the attached files for the SQL results.
Thank you.
16.02.2024 11:14:16 UTC+8 - Info for Customer: SAP
Your interaction with SAP Support
Contact name: Ivy Rose
Contact phone or email: +63-9228619044
Channel: Call from customer
Interaction summary:
Requester name: Ivy Rose
Request: speed up
Business impact:
Go-live project issue;
Go-live date is not definite, 1st quarter 2024;
Customer are in the TEST environment, deadline for the test phase is Feb 23, 2024;
5 project members are working for this;
Not a showstopper;
No workaround.
Additional comments:
Contact name, contact details:
Ivy Rose +63-9228619044
16.02.2024 18:39:48 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Hello SAP,
I already reviewed SAP Notes:
3248201 - Size on disk hardly changes after cleanup table DBTABLOG
execute the steps in 3028886 - Table size on disk does not decrease after data archiving
check 2731449 - After table deletion and successful Delta Merge, table size Is not decreased
check 2976166 - Not possible to recover all allocated space from HANA DB table
However, no further space has been reclaimed after the 1st attempt.
Please check. Thank you.
19.02.2024 09:42:57 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Hello SAP,
Good morning.
May I kindly request an update on the issue at hand? Your findings would be greatly appreciated and will assist me in resolving the matter
effectively.
Thank you.
Ivy
19.02.2024 10:00:52 UTC+8 - Info for Customer: SAP
Your interaction with SAP Support
Contact name: Ivy Rose
Contact phone or email: +63-9228619044
Channel: Call from customer
Interaction summary:
Requester name: Ivy Rose
Request: Speed up
Business impact: (updated)
Go-live project issue;
Product: S4 HANA FICO related module;
Go-live date: Mar 2024;
Testing phase now, deadline for the test phase is Feb 23, 2024;
5 consultants are working for this;
Not a showstopper;
No workaround.
Additional comments: Asked the processor for any feedback please.
Contact name, contact details: Ivy Rose +63-9228619044
19.02.2024 16:30:47 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Hello SAP,
Good afternoon.
May I kindly request an update on the issue at hand? Your findings would be greatly appreciated and will assist me in resolving the matter
effectively.
Thank you.
Ivy
19.02.2024 18:04:58 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Hello SAP,
Good evening.
I deleted ~20 million entries and executed the following commands:
MERGE DELTA OF "DBTABLOG" FORCE REBUILD;
b. UPDATE "DBTABLOG" WITH PARAMETERS ('OPTIMIZE_COMPRESSION' = 'FORCE');
c. ALTER SYSTEM RECLAIM DATAVOLUME 110 DEFRAGMENT;
ALTER SYSTEM RECLAIM COLUMN LOB SPACE;
CALL CHECK_TABLE_CONSISTENCY('REPAIR_HYBRID_LOB_OVERHEAD', 'SAPHANADB', 'DBTABLOG');
However, no further disk space has been reclaimed.
Please check the attached file for additional information.
Thank you.
20.02.2024 09:45:12 UTC+8 - Info for SAP: Ivy Javier (S0021774598)
Hello SAP,
Good afternoon.
May I kindly request an update on the issue at hand? Your findings would be greatly appreciated and will assist me in resolving the matter
effectively.
Thank you.
Ivy
Contacts
Role
Reporter
Name
Ivy Javier
(S0021774598)
SECONDARY
24h Contact
System Opener
Attachments
Time Zone
Primary Phone
Secondary Phone
E-Mail
ivy.javier@sminvestme
nts.com
UTC+08
UTC
Ivy Javier
(S0021774598)
UTC+8
UTC
+63-9228619044
ivy.javier@sminvestme
nts.com
File Name
Description
File Type
File Size
Created By
Created On
Clean-up.docx
S0021774598 2/14/2024, 7:53:26 PM
DOCX
2.8 MB
Ivy Javier
(S0021774598)
14.02.2024 19:53:26
UTC+8
HANA SQL Reports.zip
S0021774598 2/15/2024, 5:22:52 PM
APPLICATION/ZIP
104.8 KB
Ivy Javier
(S0021774598)
15.02.2024 17:22:52
UTC+8
Action Log
Changed On
Wednesday 14.02.202
4
Thursday 15.02.2024
Friday 16.02.2024
Monday 19.02.2024
Changed At
Changed By
Action
Old Value
New Value
19:47:17 UTC+8
Ivy Javier
(S0021774598)
Priority changed
19:47:17 UTC+8
Ivy Javier
(S0021774598)
Incident created
0020751294
0000163218 2024
19:47:17 UTC+8
Ivy Javier
(S0021774598)
Component
HAN-DB-PERF
19:47:36 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Problem Description
Problem Description
19:47:51 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Problem Description
Problem Description
19:48:00 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Problem Description
Problem Description
19:48:09 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Problem Description
Problem Description
19:48:09 UTC+8
Ivy Javier
(S0021774598)
Component
HAN-DB-PERF
HAN-DB
19:50:34 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Problem Description
Problem Description
19:50:34 UTC+8
Ivy Javier
(S0021774598)
Component
HAN-DB
HAN-DB-PERF
19:53:26 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Problem Description
Problem Description
19:53:26 UTC+8
Ivy Javier
(S0021774598)
Status
Not Sent to SAP
Sent to SAP
20:04:15 UTC+8
SAP
Status
Sent to SAP
In Processing by SAP
22:08:27 UTC+8
SAP
Memo/Text changed
22:08:27 UTC+8
SAP
Component
14:54:10 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
17:22:53 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
17:23:33 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
11:14:16 UTC+8
SAP
Memo/Text changed
Info for Customer
18:39:48 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
09:42:57 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
10:00:52 UTC+8
SAP
Memo/Text changed
Info for Customer
Medium
High
Info for Customer
HAN-DB-PERF
HAN-DB-PER
Tuesday 20.02.2024
16:30:47 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
18:04:58 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
09:45:12 UTC+8
Ivy Javier
(S0021774598)
Memo/Text changed
Info for SAP
20.02.2024 14:38:14 UTC+8
Download