Scribd
Upload
3 views

db02

This SAP Knowledge Base Article details how to check the Database Size History for SAP HANA in DBACockpit, including the necessary support package versions and steps for data collection. It outlines two cases for data collection based on the presence of an ABAP Stack and provides troubleshooting tips for accessing historical data. Additionally, it includes instructions for creating a custom ABAP program for older support package versions and common errors encountered during the process.

Uploaded by

ramesh bandari bandari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

db02

This SAP Knowledge Base Article details how to check the Database Size History for SAP HANA in DBACockpit, including the necessary support package versions and steps for data collection. It outlines two cases for data collection based on the presence of an ABAP Stack and provides troubleshooting tips for accessing historical data. Additionally, it includes instructions for creating a custom ABAP program for older support package versions and common errors encountered during the process.

Uploaded by

ramesh bandari bandari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

SAP Knowledge Base Article

2453269 - DB Size History for SAP HANA in DBACockpit


Component: BC-DB-HDB-CCM (Basis Components > Database Interface, Database Platforms > Use HAN-DB*.
Here CCMS, Porting, DB Interface issues only > CCMS / Database Monitors for SAP HANA), Version: 12,
Released On: 01.10.2024

Symptom
You want to check the Database Size History for SAP HANA database in DBACockpit transaction.

Environment
SAP HANA database;
SAP systems based on SAP ABAP system.

Reproducing the Issue


Open the history information from DBACOCKPIT.

Cause
You want to check the historical data of one of the following metrics from DBACockpit > Current Status > Overview
Memory Used (GB);
Data Volume Size (GB);
Log Volume Size (GB);
Trace Files Size (GB).

Resolution
This feature was introduced recently in DBACOCKPIT and is available once you import the following (or higher) SAP
NetWeaver Support Package Stack:
7.51 SP1
7.50 SP6
7.40 SP17
7.31 SP20
7.30 SP17
7.02 SP19
You can also use this feature in older SPS versions than above. You can find more details later on this KBA, check Collecting
the data in Older SPS.
How the data is collected?
CASE A: There is an ABAP Stack installed on the monitored HANA. In this case the data is collected by the ABAP job
SAP_COLLECTOR_FOR_PERFMONITOR. The job runs in every system automatically. You can influence the days and
the time when SAP_COLLECTOR_FOR_PERFMONITOR should collect the DB Size History by changing with
transaction SE16 the entry RSSDBDLY of table TCOLL. Example:

With the seven X in field DAYOW you establish that the DB Size History is collected every day (one X for each day
of a week);
With the X in field TIMOD, you establish that the DB Size History is collected at 06:00 o'clock. An X in the position
N stands for (N-1) o'clock;
If one of the fields DAYOW/TIMOD is empty or if the above entry does not exist in table TCOLL, no DB Size
History will be collected.
RENUM column specified how often the report to be called, usually set to 1, SYTYP column specifies system type.
CASE B: There is no ABAP Stack installed on the monitored HANA. You need to access the transaction SM36 and
schedule a periodic job (with period “once a day” or “once a week”) for the ABAP report RSHDB_DB_SIZE_HISTORY.
Accessing the collected data
You can access it in DBACockpit transaction > System Information > DB Size History as follows:

There you will find 3 different aggregation options:

And the screen looks like the following:


Collecting the data in Older SPS
If you want to use this feature in a Support Package which is older than the SPs mentioned earlier, proceed as follows:
1. In SE38 transaction, create the ABAP program ZRSHDB_DB_SIZE_HISTORY which you can find in the attachment of
this KBA;
2. Afterwards create a variant for this program. In the selection screen of your variant enter the following value for field
'CON_NAME'. Possible values are:
DEFAULT: with this value the program will collect the DB size history of the local DB (= the HANA Database
where the SAP system is installed on);
The name of an external HANA database: enter the name which you see in the column "Connection Name"
on the first screen of transaction DBACOCKPIT.
3. Afterwards with transaction SM36 create a job with a name of your choice;
4. Under "Step" enter the program name ZRSHDB_DB_SIZE_HISTORY and the name of your variant;
5. Under "Start condition" choose "Date/Time" and enter a date and a time of your choice;
6. Then mark the flag "Periodic job" and click "Period values" and select "Daily".
Following above steps, your job will run once a day. During each run, it will collect the data described in this KBA and store it
in a table called DB_SIZE_HISTORY_FOR_COCKPIT. This table is created by the first run of the job.
In case you upgrade your system to a most recent SPS or another product version, you have to terminate the scheduled job for
program ZRSHDB_DB_SIZE_HISTORY. The data collection will be done by SAP_COLLECTOR_FOR_PERFMONITOR job
(for local systems) or schedule the job for the ABAP report "RSHDB_DB_SIZE_HISTORY" as explained earlier.
Accessing the collected data in Older SPS
You can only access the data after your job ran successfully at least once.
To access the collected data, go into the SQL Editor of DBACOCKPIT or HANA Studio and execute the following query:
SELECT * FROM <the schema used by transaction DBACOCKPIT>.DB_SIZE_HISTORY_FOR_COCKPIT
If you don’t know the <the schema used by transaction DBACOCKPIT>, you can fetch it by calling transaction DBACOCKPIT
and executing the following query:
SELECT current_schema FROM sys.dummy
If there is only partially data not shown in DB02, you can have check list as following:
1. Browse table TCOLL with transaction SE16 and look at the entry RSSDBDLY. Look at the column DAYOW. The first “X”
stands for Monday, the second “X” stands for Tuesday, etc. This column must have seven “X” so that the collector is
executed every day. If this is not the case, you must change this column accordingly.
2. Look at the column TIMOD. This column tells you the time when the DB Size history collector job should run. An X in
the position N stands for (N-1) o'clock. This column must have at least one “X”. If this is not the case, you must change
this column accordingly.
3. Check if the SAP system was online at the time from step 2. If the SAP system was offline at this time: Then you have
found the reason for the problem: The job did not run because the SAP system was offline at this time. Solution: Modify
table TCOLL by entering in the field TIMOD a time when the SAP system is always online.
4. With transaction SM37 check if the job SAP_COLLECTOR_FOR_PERFMONITOR runs hourly. If this is not the case: It
is mandatory that this job runs hourly in every SAP system. Solution: set up the mandatory SAP jobs as explained in SAP
note 16083. If you require help with this note, please open a ticket for component BC-CCM-BTC.
5. With transaction SM37 check if the job SDB_MONITORING_DATA_AUTO_ACTIONS did run at the hour from above
step 2. FYI: The job SDB_MONITORING_DATA_AUTO_ACTIONS is submitted automatically by
SAP_COLLECTOR_FOR_PERFMONITOR. But this is not done on every hourly run of
SAP_COLLECTOR_FOR_PERFMONITOR, but only on the run from the time which is specified in table TCOLL. If the
job SDB_MONITORING_DATA_AUTO_ACTIONS did not run at the hour from above step 2, then most likely one of
the above problems 1) - 4) applies.
6. If both jobs did run at the hour from above step 2: Then there is an issue with the collector. Solution: Look at the SM37
job log of SDB_MONITORING_DATA_AUTO_ACTIONS. Here you will see an error message telling you why the
collector failed. FYI: The collector (which is executed by the job SDB_MONITORING_DATA_AUTO_ACTIONS) is the
program RSSDBMONACT. This program does different things (e.g. clean up data) and among others it executes the
program RSHDB_DB_SIZE_HISTORY which collect the DB Size history
7. The most frequent error in the collector log is “Missing authorization S_DBCON” . This error means that the SAP User
which runs the job SAP_COLLECTOR_FOR_PERFMONITOR doesn’t have the authorization to collect the DB size
history. Solution: Grant the SAP role SAP_BC_S_DBCON_USER to the SAP user which executes the job
SAP_COLLECTOR_FOR_PERFMONITOR.
8. Another known error in the collector log is “Missing HANA privilege CATALOG READ”. Solution: Grant the HANA
privilege CATALOG READ to the DB user which is used by DBACOCKPIT.
9. In case of other SQL Errors, the SQL Error Code and the SQL Error text will appear in the collector log.
10. Another known problem is: The table DB_SIZE_HISTORY_FOR_COCKPIT (this is where the DB size history is stored)
is not defined in the SAP DDIC and instead it is created in the schema of the DB User which is used by DBACOCKPIT. If
you change the DB user which is used by DBACOCKPIT, then there will be two tables
DB_SIZE_HISTORY_FOR_COCKPIT in two different schemas and the screen System Information --> DB Size History
can only show the content of one of these two tables. Solution: Check if there are two tables
DB_SIZE_HISTORY_FOR_COCKPIT in two different schemas and if both tables contain data. If this is the case and if
you want to see the data from both tables on the screen System Information --> DB Size History, what you could do is to
copy the entries from the old table into the new table and afterwards drop the old table. For copying the entries you
could do something like this via the SQL Editor:
INSERT INTO <new_schema>. DB_SIZE_HISTORY_FOR_COCKPIT ( SELECT * FROM <old_schema>.
DB_SIZE_HISTORY_FOR_COCKPIT )
In order to be able to execute this SQL statement, you will need to use a DB user which has the privilege for both schemas.

Keywords
History data, volume, disk size, aggregation, db size history, aggregation, dbacockpit, dba cockpit, historical, old data,
SAP_COLLECTOR_FOR_PERFMONITOR, RSHDB_DB_SIZE_HISTORY

Attributes
Key Value

Other Components SAP HANA > SAP HANA Database > SAP HANA Monitoring (HAN-DB-MON)

Products
Products

SAP NetWeaver 7.3

SAP NetWeaver 7.4

SAP NetWeaver 7.5

SAP enhancement package 1 for SAP NetWeaver 7.3

SAP enhancement package 2 for SAP NetWeaver 7.0

This document is referenced by


SAP Component Title
Note/KBA

3468066 DB Size History menu element is missing in DBACockpit

3121227 BC-DB-HDB- DB Size History is not displayed in DBACOCKPIT even if standard job
CCM 'SAP_COLLECTOR_FOR_PERFMONITOR' was scheduled

3206525 BC-DB-HDB- DB Size History in DB02 is not updating


CCM

3006773 HAN-DB-PER How to check DB SIZE HISTORY

2976877 BC-DB-HDB- No DB Size History in DBACOCKPIT


CCM

2222220 HAN-DB-ENG FAQ: SAP HANA DBACOCKPIT

3136173 HAN-DB-ENG DB Size History: Memory of the Tenant


Attachments
File Name File Size Mime Type

zrshdb_db_size_history.txt 6 text/plain

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy