Symptom
- You experience program errors in function group /SDF/HANA_7X (e.g. syntax error in function module /SDF/GET_HANA_TABLE).
Several corrections (also to the old download mechanism) are done via this SAP Note. SAP Note 1878184 will not be maintained anymore. - We introduced a new data collection mechanism for collecting service data for HANA services.
This new mechanism enables:
- services for standalone HANA Databases
- is the prerequisite for multiple HANA Databases in one service session.
This new download mechanism is available with ST-PI 2008_1_7xx SP 10. - You see in the Early Watch Alert Report in the Chapter 'HANA Database' that content is missing.
- Prerequisite for HANA Collection is:
- ST-PI 2008_1_7xx SP 10 or
- ST-PI 740 SP 0
with this SAP Note implemented.
Other Terms
HANA Download, EarlyWatch Alert, ST-PI, EWA
Reason and Prerequisites
To simplify and to enhance the possibility for the download
collection a new function module had to be introduced. The new function
module will be the basis for the following scenarios:
New Content:
Relationship to the Service Content and the ST-PI Support Package:
Basically the ST-PI Support Package should be actual to guarantee that the Service Content has reliable content. With the Service Content ST-SER 2010_1 SP 26 (Release to Customer in December 2014) it is strongly recommend to have
ST-PI 2008_1_7xx SP 10 (or higher) or
ST-PI 740 SP 0
installed.
- Standalone HANA Database (Remote Database). This function module is the prerequisite for the EarlyWatch Alert of the product HANA Platform Edition.
- It simpliyfies the rollout of HANA Download content.
- SAP Note 1878184 is obsolete.
- Changed the interface of the function module with ST-PI 2008_1 7xx SP 10.
- Introduced a simplified function to figure out the correct HANA Database from which Data should be collected.
- Date: 2015-06-18: You don't want to have HANA Checks in your EarlyWatch Alert of a HANA Database which is connected via DBCON. In this case create in DBACOCKPIT an entry with this connection and add in the description field 'NON_EWA_'. See also SAP Note 2137119.
- HANA Databases with another SID than the ABAP System is not treated corrrectly by the download. This is ensured. (Correction Date: 2015-02-16)
- For HANA Databases with Revision 1.00.70 the wrong download module M_DATABASE is read. This is corrected. (Correction Date: 2015-03-20)
- In Solution Manager where also a HANA is connected the download contains information of the connected HANA systems. This should not be the case. There is one exception: if SLT (component DMIS) is used the download should contain the required information of the connected HANA System. The workaround with the DBACockpit descrption 'NON_EWA...' to switch collecting HANA information does not work anymore. To set up EWAs for HANA Standalone follow SAP Note 1958910. (Correction Date: 2015-04-23)
New Content:
- History of Database Implementations (M_DATABASE_HISTORY)
- Row Store Fragmentation
- Enhanced content Memory Consumption
- Merge Statistics
- Multitenant Database Information
- Replication Information
- Data Tiering Information
- Embedded LiveCache Informationen
- Corrections regarding the Backup Analysis (Timeframe was not taken correctly)
- Corrections regarding the Restarted Services Analysis (Timeframe was also not taken correctly)
- StatisticsServer Investigation
- Number of HANA Objects exceeds certain limits.
- LiveCache function modules added
- Change in OOM Dump collection
- Availability Metrics
- LiveCache content
- Some IO Performance Indicators
- Backup Size (for 42 days)
- Backup duration
- Log Backup Size and duration
- Embedded Stat Server: Checking if Data Collection of HOST_CS_UNLOADS is enabled.
- Enhancement of Multitenant Database recognition
- Database Connections #DO are not collected anymore.
- Timestamp for each SQL
- Change in the Embedded Stat Server Recognition
- Enhancement in the Replication Server Scenario
- Embedded Stat Server: Correction for Retention Time
- Correction for CPU Usage in the STAT Server (to avoid DIV by 0)
- Correction of TOP_TABLES_COL and TOP_TABLES_ROW:
Taking out reading the Size of Lob Files because of Long Duration.
- Adding Smart Data Access (SDA)
Relationship to the Service Content and the ST-PI Support Package:
Basically the ST-PI Support Package should be actual to guarantee that the Service Content has reliable content. With the Service Content ST-SER 2010_1 SP 26 (Release to Customer in December 2014) it is strongly recommend to have
ST-PI 2008_1_7xx SP 10 (or higher) or
ST-PI 740 SP 0
installed.
Solution
To get a complete content for Service Delivery or for the EarlyWatch Alert in the Download please implement at least
ST-PI 2008_1_7xx SP 10 (or higher) or
ST-PI 740 SP 0 (or higher)
together with the newest coding corrections of this SAP Note.
(Remark: there will be continues changes at this SAP Note, even if you have the newest ST-PI Support Package installed, coding corrections might be necessary)
ST-PI 2008_1_7xx SP 10 (or higher) or
ST-PI 740 SP 0 (or higher)
together with the newest coding corrections of this SAP Note.
(Remark: there will be continues changes at this SAP Note, even if you have the newest ST-PI Support Package installed, coding corrections might be necessary)
Header Data
| Released On | 08.02.2016 16:23:45 | ||
| Release Status | Released for Customer | ||
| Component | SV-SMG-SER SAP Support Services | ||
| Other Components |
| ||
| Priority | Correction with medium priority | ||
| Category | Program error |
Collecting HANA service data requires proper configuration of system settings and tools to ensure accurate data retrieval. Similarly, a PoE Hub is essential for efficiently delivering both power and data to network devices, ensuring smooth connectivity and minimizing setup errors in enterprise environments.
ReplyDelete