1/19/2021

AMC - Administration and Management

Console for SAP ASE
Generated on: 2021-01-19 19:29:44 GMT+0000

SAP Adaptive Server Enterprise | SAP Adaptive Server Enterprise 16.0

PUBLIC

Original content: https://help.sap.com/viewer/87b823ef964e4cb2a22b4fe995f26e52/CURRENT_VERSION/en-US

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/viewer/disclaimer.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 1/27
1/19/2021

Document History

Version Date Comments

1.0 2020 - 09 - 10 Initial Version

1.1 2020 - 10 - 30 Updated Version of Con guring the AMC

1.2 2020 - 11 - 16 Updated Version ofCon guring the AMC

Introduction
This guide describes the Administration and Management Console (AMC) for SAP Adaptive Server Enterprise (SAP ASE). It is a
Web-based tool that provides a graphical user interface for the administration and management options of your SAP ASE servers.

About AMC

The Administration and Management Console (AMC) for SAP Adaptive Server Enterprise (SAP ASE) is a Web-based tool for
managing and administering your SAP ASE servers. The AMC is supported as of SAP ASE version 16.0 SP04. While the AMC is
primarily designed to run on desktop devices, you can also access it on tablets.

AMC provides a graphical user interface for displaying and changing the database server con guration, managing the databases
of an SAP ASE database server, and controlling the use of main memory.

Use AMC to set up and use the SAP ASE Workload Analyzer. With the Workload Analyzer, you can capture workloads on your SAP
database server, replay them on other servers, and compare the results to analyze the impact of different con gurations.

In addition, the AMC is closely integrated with the Built-In ASE Longterm Data Repository (BALDR), which provides access to
historical performance data for your SAP ASE database server and provides functionality to automate table reorganizations and
statistical updates with Automated Table Maintenance (ATM).

Getting Started with the User Interface

In the following chapters you can learn more about important elements of the AMC user interface, which are also referenced in
other help topics.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 2/27
1/19/2021

Related Information
Time Selection
Table Controls
Error Messages
Accessibility Information

Time Selection
For screens in AMC that display historical information, you can set a time frame. Only data from this time frame is then displayed.
There are multiple prede ned time frames that can be selected from a dropdown menu (for example, Last 24 Hours or Last 7
Days). You can also choose Custom Selection and specify the time stamps for both the start and end date. After selecting the
time frame, you can choose Go to apply the current settings and refresh the displayed data.

At the top of the topic screen, you will be shown when you have the option to make a time selection. After you have made your
settings, you can collapse the time selection to free space up on your display and see more results. If you always want to see the
current time selection when you scroll through the results, you can also mark it as sticky.

Table Controls
Many of the AMC topic screens contain tables to display data. At the top right of the table you can see the controls available for
this speci c table.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 3/27
1/19/2021
From left to right:

Refresh data in the table

Create a new entry

Delete the selected entry

Sort Dialog

Settings/Columns Dialog

Export

Related Information
Sort Dialog
Columns Dialog
Export Popup

Sort Dialog
The Sort dialog allows you to specify a custom sort order for the data of a table.

Columns Dialog
In the Columns dialog, you can de ne which data columns should be displayed and in which order they should be displayed on the
screen. As some of the topic screens provide access to many columns, not all columns are active on all screens by default.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 4/27
1/19/2021

Export Popup
The Export control starts a download of the table data to your device. A dialog box is displayed while the process is running. The
data can then be analyzed with other software or stored for later use.

Error Messages
In case of errors or warnings these are displayed in a small popup on the screen.

Accessibility Information
AMC uses the SAPUI5 technology and makes use of its accessibility offerings. With SAPUI5, you get the up-to-date SAP user
interface (UI) technology, which is based on HTML5. The screens are built according to SAP Fiori design principles, with a focus on
usability and responsive design.

For more information, see the SAPUI5 documentation .

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 5/27
1/19/2021

Getting Started with AMC

Learn how to start and con gure the Administration and Management Console for your SAP ASE servers.

Related Information
Components of AMC

Components of AMC
The following picture shows the main components of AMC:

Related Information
AMC.jar
AMC.properties
Scripts Directory
Built-In ASE Longterm Data Repository (BALDR)

AMC.jar
The core component of AMC is a Java archive named AMC.jar. It runs on the same host as the SAP ASE database server and can
be accessed by the end user through a Web browser. AMC.jar is the only component of AMC that must be accessible from the
end user device. All communication with the front-end is via http on a con gurable port.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 6/27
1/19/2021
The AMC.jar component serves the user interface to the browser, processes user requests, and communicates with SAP ASE via
JDBC. This component can also execute scripts from the AMC script directory.

Since AMC.jar contains all necessary UI libraries, it is not necessary for the end user device to be connected to the public
internet. The only exceptions to this are the following features

1. The SAP WebAssistant, which provides integrated documentation, requires access to the public internet

2. The links on the Important Links screen only work if the user's device has access to the internet.

In any case, the database server does not need access to the public internet.

AMC.properties
The AMC.properties le contains all information to con gure AMC. For more information, see Con guring the AMC.

Scripts Directory
The AMC scripts directory contains a set of scripts required to prepare SAP ASE for providing all the data required for AMC.
Scripts are also required to start and stop your SAP ASE database server from AMC.

Built-In ASE Longterm Data Repository (BALDR)

BALDR stands for the Built-In ASE Longterm Data Repository. SAP ASE database servers that have installed BALDR contain a
saptools database. This database contains several stored procedures that are executed by the SAP ASE job scheduler to collect
a performance history. It also offers views to access this performance history. Also, it contains the Automated Table Maintenance
(ATM) feature, that offers automated runs of table reorganizations and statistical updates based on con gurable thresholds and
rules. The AMC also uses the saptools database to store information required for the Workload Analyzer.

BALDR can be installed as part of the SAP ASE installation, by AMC, or by manually running the instbaldr.sql script from the
SAP ASE scripts directory.

 Note
You need a sapsa user before you can run the instbaldr.sql script. For more information, see sapsa login

For more information about BALDR, see section BALDR

Installation
AMC is installed as part of an SAP ASE server installation. It is licensed free of charge to customers who have a paid license for
SAP ASE. For detailed information about installation, see the documentation Installation Guide for SAP Adaptive Server
Enterprise.

There are several ways to install and con gure the AMC component.

1. GUI Installation

If you use the SAP ASE installer, you can choose between

Typical mode

Full mode

Customer mode

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 7/27
1/19/2021
In Typical mode AMC is not installed. In Full mode, AMC is installed automatically, and using Custom mode, you have
to select Administration and Management Console and check the box as next step on the second con guration
screen.

2. Console Installation and Con guration

The AMC installation via the console is similar to the GUI installation. You can choose again between Typical, Full, and
Custom mode. Using the Custom mode, you have to select Administration and Management Console under
SAP Adaptive Server Enterprise. As next step you are asked to enable AMC. The AMC Server Port is 8080 per default, but if
needed you can change to another usable port.

3. Silent Installation and Con guration

You can also install the AMC component via silent installation. To do this, you should add the following variables in the
response le:

SY_CFG_ASE_AMC_ENABLE=true

SY_CFG_ASE_AMC_PORT_NUMBER=8081

If you don’t want to install AMC, just leave SY_CFG_ASE_AMC_ENABLE as false or blank. A usable port can be set as
SY_CFG_ASE_AMC_PORT_NUMBER.

Related Information
Starting and Stopping the AMC
Con guring the AMC
Logging in to AMC
Logging out of AMC
Logging

Starting and Stopping the AMC

Navigate to the SAP ASE installation directory. Here you can see a directory called AMC containing AMC.jar,
AMC.properties, and a directory called scripts. Open a command prompt or terminal and then change to the scripts directory.
Now run the command start_AMC.bat (or start_AMC.sh on Linux). This runs the AMC application in an embedded Tomcat server.
You can access the AMC user interface at http://localhost:8080/. To stop the AMC application, run the command
stop_AMC.bat or stop_AMC.sh on Linux.

Con guring the AMC

AMC offers a set of con guration properties. The AMC directory contains a AMC.properties le, that can be edited with any
text editor to con gure AMC.

Lines starting with a # character contain comments, properties are set in the format property=value.

Available properties are

Property Default Value Description

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 8/27
1/19/2021

Property Default Value Description

ase.host <hostname> The hostname of the database server SAP

ASE and AMC are running on

ase.port <port> The port number SAP ASE is listening on

ase.server.ssl.enabled false Whether SAP ASE has SSL enabled or not.

Valid values are true or false. If set to true,
JDBC calls made by AMC will use SSL.

server_name <servername> The name of your SAP ASE server

scripts_dir $SYBASE/AMC/scripts The directory scripts used by AMC are

stored

server.address This property is optional To bind AMC to a speci c IP address or a

and commented by default (virtual) hostname specify it here.

logging.file.path $SYBASE/AMC The directory AMC stores logging

information

logging.file.name AMC.log The name of the le AMC stores logging

information

logging.level.com.sap.ase.nanna INFO The log level used by AMC.

Possible values are

DEBUG

INFO

WARN

ERROR

FATAL

logging.file.max-history 7 Maximum number of archive log les to keep

logging.file.clean-history-on-start true Whether the archive log les should be

cleaned up when the AMC is started

server.servlet.session.timeout 900 Duration in seconds after which user session

will timeout if there is no activity by the user.

server.port 8080 The port number AMC is listening on

server.ssl.enabled false Whether to enable SSL/HTTPS support for

AMC. We recommend setting this to true. If
you set server.ssl.enabled=true provide valid
values for the below server.ssl.* properties
as they are required.

server.ssl.key-store-type <ssl_key_store_type> The format used for the keystore. It could be

set to JKS in case it is a JKS le or PKCS12.

server.ssl.key-store <ssl_key_store_file_path> The path to the keystore containing the

certi cate

server.ssl.key-store-password <ssl_key_store_password> The password used to generate the

certi cate

server.ssl.key-alias <key_alias> Alias that identi es the key in the keystore

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c2970… 9/27
1/19/2021

Property Default Value Description

server.ssl.protocol <TLS> SSL protocol to be used by AMC

server.ssl.enabled-protocols <TLSv1.2, TLSv1.3> Enabled SSL protocols for AMC

During installation, the properties are lled with default values. In most cases there is no need to change the values but depending
on your setup you may want to enable HTTPS or use a custom port for AMC.

Logging in to AMC
Open a Web browser on your device and enter the URL to access AMC. For information about supported browsers and platforms,
see SAPUI5 - Browser and Platform Support.

The URL for accessing the AMC consists of the database host name and the port to which the AMC listens. Both parameters can
be con gured in the AMC.properties le, as described in Con guring the AMC. A typical URL for accessing AMC is
http://dbhostname:8080/.

Your browser loads the AMC login screen. Enter a database username and the password for this user. Continue with Log In to
access the AMC. You will be directed to the At a Glance screen.

Logging out of AMC

Select Logout in the User Menu to be logged out of AMC. As a result, you will see a screen informing you that the logout was
successful and giving you the option to log in again.

Logging
AMC writes a log of its operation. This log can be especially helpful in analyzing issues with AMC and SAP Support can ask you to
provide the AMC log in support cases. In some cases, it will be necessary to increase the log level to get a more detailed
application log.

The log le name, location, and log level are con gured in the AMC.properties le, as described in Con guring the AMC.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 10/27
1/19/2021

Managing your SAP ASE

Learn about the AMC features and how to manage your SAP ASE database using the navigation pane on the left side of the home
screen.

Related Information
At a Glance
Space
Con guration
Backup and Recovery
Diagnostics

At a Glance

Related Information
Server Overview

Server Overview
Get detailed information about the SAP ASE server being administered. It also allows you to start, shutdown, and restart the SAP
ASE server.

Space

Related Information
Databases
Create Databases

Databases
Get detailed information about the data and log space, the available free space, and the durability level of all databases of your
SAP ASE database server.

Monitoring the space that is consumed by the database requires you not only to check the current space consumption, but also
consider the progress of the space growth.

To display detailed information, select the entry you want to analyze in the overview table.

The section Status displays all database options for each selected database. These options are retrieved from the status column
of the sp_helpdb command. If you change database options with the sp_dboption command, the changes are re ected here.

You can create a new SAP ASE device and database and expand the storage space of the existing database using the Create
wizard.

Related Information
Durability Level
Space Usage

Durability Level

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 11/27
1/19/2021
The Durability Level can have one of the following values:

Durability Level Description

Full All transactions are written to disk. This is the default if you do not
specify a durability level when you create the database and ensures
full recovery from a server failure. All system databases use this
durability level (the traditional durability level for disk-resident
databases).

 Note
It is of high importance that the <SID> database of an SAP
installation has this durability level.

no_recovery Transactions are not durable to disk and all changes are lost if the
server fails or is shut down. For disk-based databases, Adaptive
Server periodically writes data to the disk devices at runtime, but in
an uncontrolled manner. After any shutdown (polite, impolite, or
server failure and restart) a database created with no_recovery is
not recovered but is re-created from the model or template
database.

at_shutdown Transactions are durable while the server is running and after a
polite shutdown. All durability is lost if the server fails.

Space Usage
With the AMC UI you can monitor the space usage of your database, including database objects such as tables and indexes. You
can analyze space allocation and perform administration activities to change the storage layout of your database.

If you neglect space management, normal database growth can cause downtime when database objects ll up. In this case,
applications cannot write to the database, and you need to make more storage space available quickly. Therefore, it is much better
to anticipate the problem by monitoring and proactively managing the disk space in your database.

The following example shows how disk space can be allocated on different devices and explains the terms Assigned, Free, and
Used. This helps you to understand how to monitor memory usage in the AMC user interface.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 12/27
1/19/2021

Create Databases
You can access the Create Database wizard using the add (create) button. This guided procedure allows you to create a device and
then create and assign a database to the device. The created database will be inserted into the master.sysdatabases table.

Your rst step is Create Device and it includes the following input parameters:

Device name

Path

Size

Direct IO method and

Skip Allocation option

Next, you will be directed to the nal step Create Database, where the inputs include:

Database name

Size

Type (log or data)

Option for default and temporary

Durability mode and

Compression level

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 13/27
1/19/2021
In addition, the databases list provides a delete button which allows you to drop a chosen database. Not all databases have this
option available, as the following applies:

Only the database owner can drop a database.

You must be in the master database to drop a database.

You cannot drop a database that is open for reading or writing by a user.

Con guration

Related Information
ATM
Memory Management
Server Con guration
BALDR
Workload Analyzer

ATM
Learn more about the Maintenance Windows, Pro les for Automatic Statistics Updates, Pro les for Automatic Table
Reorganization, and more.

The following sections provide detailed information about Automatic Table Maintenance:

The ATM Framework

Setup and Maintenance of the ATM Framework

ATM Pro les

ATM Windows

Related Information
The ATM Framework
Setup and Maintenance of the ATM Framework
ATM Pro les
ATM Windows

The ATM Framework

Sophisticated business applications like the SAP Business Suite execute millions of DML statements a day. In a data warehouse
scenario, for example, reports are constantly being generated to determine whether business targets are being met while the
background tasks are executed to load collected data into data cubes or to delete obsolete data. This constant manipulation of
data sets causes data fragmentation, leaves behind non-reusable free space, and, nally, invalidates optimizer statistics, which
can end up in poor query performance.

The SAP AMC for SAP ASE introduces a exible framework that allows you to set up and control automatic table maintenance (in
the following referred to as ATM). Considering the thousands of tables and indexes a typical SAP system creates on the database,
this framework dramatically reduces manual administrative activities and thus signi cantly reduces the TCO of the SAP on SAP
ASE solution.

Terminology Used in the Context of Automatic Table Maintenance:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 14/27
1/19/2021

Term Description

ATM pro le An ATM pro le de nes the objects that ATM should monitor as well as the maintenance activities that
should be executed once de ned thresholds are violated.

ATM window An ATM window de nes a time frame within which ATM can evaluate and maintain objects. ATM pro les
are assigned to ATM windows to control which objects are to be maintained in a certain time window and
which are not.

ATM queue Objects that require maintenance are stored in the ATM queue. ATM might not be able to maintain all
identi ed objects before an ATM window expires. In this case, ATM will continue to process queued
objects during the next ATM window.

ATM history Objects that were maintained by ATM are dropped from the ATM queue, but, at the same time activities
are logged in the ATM history. Thus, the ATM history allows monitoring of past ATM activities.

Job Scheduler ATM makes use of the job scheduler that is built into the SAP ASE DBMS.

The following graph provides a general overview of how ATM operates on an SAP ASE DBMS:

The SAP AMC acts as the central point to:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 15/27
1/19/2021
Set up ATM on SAP ASE DBMS

Con gure ATM windows and ATM pro les

Monitor the ATM queue and ATM history

Monitor ATM execution

All objects of the ATM framework are thereby created in a private database named saptools.

The job scheduler (JS) executes a stored procedure that is created and scheduled by the SAP AMC, as de ned by ATM windows.
This stored procedure evaluates maintenance requirements that are de ned by ATM pro les, and, in a second step, it also
executes maintenance commands on identi ed objects.

 Note
ATM is not supported for SAP ASE releases older than 15.5. In addition, system and proxy tables are excluded from automatic
maintenance.

Setup and Maintenance of the ATM Framework

Deploying ATM on SAP ASE is very easy. When you setup BALDR, it also sets up ATM. All required tables, routines, and procedures
are created in the saptools database. In addition, a default ATM con guration is created that immediately enables the system for
automatic table maintenance.

For more information about setting up BALDR, see BALDR.

Related Information
Default ATM Con guration
Default ATM Pro les
Default ATM Windows
Miscellaneous Settings

Default ATM Con guration

The default ATM con guration that is created when you initially deploy ATM on an SAP ASE DBMS tries to automate table
maintenance, without risking negative impact on the applications that are connected to SAP ASE. This means objects only
undergo lightweight maintenance activities on regular business days. More costly maintenance activities are executed during the
weekend, with very large objects being excluded from such maintenance activities entirely. The default ATM con guration also
ensures full availability of all objects at any time.

Default ATM Pro les

ATM pro le Small Tables for update statistics:

Includes tables containing 100 up to 9999 rows

Triggers update of index statistics if data change exceeds 20%

Commands are executed with low priority

ATM pro le Medium Tables for update statistics:

Includes tables containing 10000 up to 999999 rows

Triggers update of index statistics if data change exceeds 20%

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 16/27
1/19/2021
Commands are executed with low priority

ATM pro le Large Tables for update statistics:

Includes tables containing 1000000 up to 999999999999 rows

Triggers update of index statistics if data change exceeds 20%

Commands are executed with low priority

 Note
If an SAP application database is found on the DBMS, special objects in that database are excluded from getting updated
statistics as known from best practices through additional exclusion pro les.

ATM pro le All Tables – Remove Row Forwarding for reorganization:

Includes all tables

Triggers reorganization using sub-command compact if the percentage of forwarded rows exceeds 10%

Commands are executed with low priority

ATM pro le All Tables – Reclaim Space for reorganization:

Includes all tables

Triggers reorganization with sub-command compact if the space utilization falls below 90%

Commands are executed with low priority

ATM pro le Small to Medium Tables – Rebuild Indexes for reorganization:

Includes tables with up to 10GB of reserved space

Triggers rebuild of all indexes that have an index page cluster ratio below 90%

Commands are executed with low priority

Default ATM Windows

ATM window 24 hours all day

Starts Monday at 00:00 and ends Sunday 23:30.

ATM pro les are applied repeatedly on an hourly basis until the ATM window expires.

Two ATM pro les are assigned by default:

Update statistics pro le Small Tables

Update statistics pro le Medium Tables

ATM window Weekend

Starts Sunday at 02:00 and ends Monday 05:00.

ATM pro les are applied only once or until the ATM window expires.

Four ATM pro les are assigned by default:

Update statistics pro le Large Tables

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 17/27
1/19/2021
Reorganization pro le All Tables – Remove Row Forwarding

Reorganization pro le All Tables – Reclaim Space

Reorganization pro le Small to Medium Tables – Rebuild Indexes

Miscellaneous Settings
In the Miscellaneous tab of the ATM Con guration screen, you can con gure options such as the number of days the ATM history
should span, or you can set the log level.

ATM Pro les

Related Information
ATM Pro le Types
Maintaining ATM Pro les
Creating ATM Pro les

ATM Pro le Types

ATM pro les are separated by the type of maintenance operation concerned, which is either update statistics or reorganization.
For each of the two maintenance operations, there are in total three types of ATM pro les that can be de ned:

Standard ATM Pro les

Tables are identi ed by a characteristic, such as row count or size. Standard ATM pro les are used to maintain all tables that do
not require special care.

ATM Pro les for Special Objects

Tables are identi ed by a full, quali ed name (supporting a wildcard at the right end of the table’s name). This type of ATM pro le
is used for tables that do require special care- for example, due to the size of the table or its need for special maintenance options.
Tables matching any active ATM pro le of type ATM Pro le for Special Objects will be excluded from any Standard ATM Pro le.

ATM Pro les for Excluding Objects from ATM

Tables are identi ed by a full, quali ed name (supporting a wildcard at the right end of the table’s name). This type of ATM pro le
is used for tables that should be excluded from either update statistics or reorganization. This means that tables matching any
active ATM pro le of type ATM Pro le to Exclude Objects from ATM will be excluded from any Standard ATM Pro le or ATM
Pro le for Special Objects. Examples are queue tables that are constantly undergoing a massive data change, causing
continuously inaccurate statistics.

 Note
A single object can qualify for multiple ATM pro les of the same type. You may for example want to de ne an ATM pro le that
initiates sampled statistics with low priority if data change exceeds 20%. But for the same set of objects, you can de ne
another ATM pro le that initiates full statistics with high priority if data change exceeds 50%.

Maintaining ATM Pro les

The ATM Con guration screen allows you to

De ne new ATM pro les

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 18/27
1/19/2021
Change existing ATM pro les

Delete existing ATM pro les

Activate or deactivate ATM pro les

Creating ATM Pro les

1. Choose Create

2. Enter values for Pro le Metadata, Object Selection, and Maintenance Options.

Example
Choose the following values, if you want to initiate sampled update statistics on all index columns once data change of a table has
exceeded a value of 5 %:

Input Field Value

Pro le Type ATM Pro le for Special Objects

Type of Threshold Data Change

Threshold Value 5%

Evaluate Threshold per Data Partition Yes

Type of Statistics Collect Statistics on all Index Columns

Number of Histogram Steps 20

Number of Consumers 1

Collect Sampled Statistic Yes

Sampling Rate 25%

SAP ASE Execution Priority Medium

There are two types of priorities that can be con gured for an ATM pro le. With the so-called maintenance priority, you de ne the
importance the requested maintenance operation has compared to maintenance operations de ned by other ATM pro les. With
the so-called SAP ASE execution priority, you specify the amount of CPU resources that should be assigned to the maintenance
operations while they are being executed.

Some applications, especially data warehouse applications, make use of SAP ASE’s partitioning feature. Depending on the
dimensions used to partition the data, some data partitions may undergo heavy data changes, while some other data partitions
may remain mostly or completely unchanged. In such cases, it does not make sense to update statistics on all partitions or to
reorganize the whole object. If you check Evaluate Threshold per Data Partition, ATM evaluates thresholds for each data and
index partition individually, and maintenance operations are also executed individually, as required by an individual data or index
partition

ATM Windows
With ATM windows, you de ne what type of table maintenance requirements and operations are evaluated and executed on
certain objects within a de ned time frame. You may, for example, want to ensure accurate optimizer statistics on certain objects
during regular business time, while update statistics on other, usually very large objects, should be maintained outside regular
business time. You may also want to move table or index reorganization into the weekend, while wanting to run update statistics at
any time.

Related Information
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 19/27
1/19/2021
Maintaining ATM Windows
Processing ATM Windows and Assigned ATM Pro les
Preparation Phase
Evaluation Phase
Execution Phase
Cleanup Phase

Maintaining ATM Windows

The ATM Con guration screen allows you to:

De ne new ATM windows

Change existing ATM windows

Delete existing ATM windows

Activate or deactivate ATM windows

Assign ATM pro les to an ATM window or remove assigned ATM pro les from an ATM window

ATM windows are scheduled jobs in the SAP ASE job scheduler. Deactivation of an ATM window will unschedule the job for further
executions and, if appropriate, cancel current executions. Changing an ATM window will reschedule the respective job.

ATM windows can be con gured to repeatedly apply ATM pro les until the window expires. In this case, the ATM job will not
complete execution after the evaluation of maintenance requirements has nished and no objects remain in the ATM queue.
Instead, the ATM job will go into sleep mode and wake up once every hour to re-evaluate and re-execute maintenance
requirements continuously until the ATM window nally expires.

Temporary overlapping between ATM windows is permitted. In addition, a single ATM pro le can be assigned to multiple ATM
windows. Details on how ATM windows and assigned ATM pro les are processed are given in the section Processing ATM Windows
and Assigned ATM Pro les.

 Note
ATM pro les of type ATM Pro les for Excluding Objects from ATM cannot be assigned to speci c ATM windows. Those ATM
pro les are valid for all ATM windows by de nition.

Processing ATM Windows and Assigned ATM Pro les

While con guration and monitoring of ATM is completely done from the SAP AMC, actual execution of ATM activities is completely
done through the job scheduler that is provided by SAP ASE. Jobs named SAP_ATM_W<window_ID> are scheduled as de ned
by active ATM windows. Each job then crosses over into the phases described in the following subsections.

Preparation Phase
During this initial phase of an ATM window, ATM checks whether all con guration prerequisites are ful lled and whether ATM
pro les assigned to the ATM window are valid. In addition, con guration options are read for the ATM window (like, for example, its
expiration time or whether the evaluation and cleanup phase are going to be executed with low execution priority).

Evaluation Phase
A standard installation of SAP ERP 6 including Enhancement Package 5 creates around 75000 tables and around 90000 indexes
on the database. Nevertheless, as usually only certain scenarios of the SAP ERP are exploited in a speci c installation, only a small
amount of these objects is accessed.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 20/27
1/19/2021
The rst thing ATM does is to restrict the number of tables, indexes, and partitions that are going to be evaluated for maintenance.
This is done in the following way:

1. Determination of the minimum of all timestamps any assigned ATM pro le has been evaluated the last time.

2. Creation of a temporary table containing all user tables of any user database that were either touched since that time
(according systabstats), or that are currently opened by SAP ASE and have undergone at least one write operation.

3. Creation of additional temporary tables containing all indexes and data partitions of the tables that have been determined.

This mechanism will greatly restrict the number of objects that are evaluated in an SAP environment. The only exception here are
new ATM pro les and newly con gured systems, where ATM needs to initially evaluate all objects.

After the number of objects has been restricted, ATM reads all ATM pro les of type ATM Pro le to Exclude Objects from ATM and
type ATM Pro le for Special Objects and ags matching objects for either no maintenance or special maintenance.

The selection of objects for ATM pro les of type Standard ATM pro le is done by specifying a range of either row count or size.
Therefore, for all objects that are neither agged for no maintenance nor special maintenance, ATM determines the current row
count and size.

Up to now, the number of objects that ATM looks at has been reduced to a level where maintenance evaluation is reasonable. In
addition, all remaining objects have been agged according to the assigned ATM pro les for either no maintenance, special
maintenance, or standard maintenance.

ATM then processes all assigned ATM pro les of type Standard ATM pro le or ATM Pro le for Special Objects. Each object that
is agged for the respective type of ATM pro le and that matches the pro le object selection conditions is evaluated according to
the ATM pro le’s threshold conditions. Depending on the exact de nition of the ATM pro le, evaluation may happen on individual
data partitions and/or indexes instead of on the object as a whole. If de ned threshold are violated, maintenance for the object (or
one or more of its data partition or indexes) is initiated by generating a corresponding maintenance command and inserting it into
the ATM queue.

While ATM creates new entries in the ATM queue, it may happen that the same object or some of its data partitions or indexes are
already contained in the ATM queue. Such cases are handled as follows:

1. Identi ed object is a table:

Drop entries from ATM queue that have a lower maintenance priority than the newly identi ed requirement
(including individual data partitions of the table).

Drop entries from ATM queue that have an equal maintenance priority, but whose planned maintenance operation is
less weighty* than the newly identi ed requirement (including individual data partitions of the table).

Drop individual data partitions from ATM queue that have a completely identical maintenance requirement than just
identi ed for the complete table.

Insert table into ATM queue, but only if:

The table is not already contained in the ATM queue with higher maintenance priority.

The table is not already contained in the ATM queue with equal maintenance priority but higher or equal
command weight*.

 Note
Data partitions with higher maintenance priority (or identical maintenance priority but higher command weight) will
stay queued in parallel.

2. Identi ed object is an index:

Drop entries from ATM queue that have a lower maintenance priority than the newly identi ed requirement
(including individual index partitions).

Drop entries from ATM queue that have an equal maintenance priority, but whose planned maintenance operation is
less weighty* than the newly identi ed requirement (including individual index partitions).
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 21/27
1/19/2021
Drop individual index partitions from ATM queue that have a completely identical maintenance requirement than
just identi ed for the complete index.

Insert table into ATM queue, but only if:

The index is not already contained in the ATM queue with higher maintenance priority.

The index is not already contained in the ATM queue with equal maintenance priority but higher or equal
command weight*.

 Note
Index partitions with higher maintenance priority (or identical maintenance priority but higher command weight) will
stay queued in parallel.

3. Identi ed object is a data partition:

Drop entries from ATM queue that have a lower maintenance priority than the newly identi ed requirement
(excluding other data partitions or the table itself).

Drop entries from ATM queue that have an equal maintenance priority, but whose planned maintenance operation is
less weighty* than the newly identi ed requirement (excluding other data partitions or the table itself).

Insert data partitions into ATM queue, but only if:

The data partition or table is not already contained in the ATM queue with higher maintenance priority.

The data partition or table is not already contained in the ATM queue with equal maintenance priority but
higher or equal command weight*.

4. Identi ed object is a data partition:

Drop entries from ATM queue that have a lower maintenance priority than the newly identi ed requirement
(excluding other index partitions or the index itself).

Drop entries from ATM queue that have an equal maintenance priority, but whose planned maintenance operation is
less weighty* than the newly identi ed requirement (excluding other index partitions or the index itself).

Insert data partition into ATM queue, but only if:

The index partition or index is not already contained in the ATM queue with higher maintenance priority.

The index partition or index is not already contained in the ATM queue with equal maintenance priority but
higher or equal command weight*.

* Weighting of maintenance operations is done as follows:

Update statistics with sampling of 50% or full update statistics has more weight than update statistics with sampling of
20%.

reorg compact has more weight than reorg reclaim_space or reorg forwarded_rows.

reorg rebuild has more weight than reorg compact or reorg rebuild for an individual index.

Execution Phase
Execution of maintenance is now purely based on entries found in the ATM queue. If the ATM window has not yet expired and as
long as there are still entries remaining in the ATM queue, required maintenance operations are read from the ATM queue
according their maintenance priority and are being executed using the requested SAP ASE execution priority.

After maintenance has been executed on a certain object, it gets moved from the ATM queue into the ATM history. Runtime
measurements and the exact maintenance command are recorded in the ATM history for later analysis.

If no objects are remaining in the ATM queue, but the ATM window is con gured to repeatedly apply ATM pro les and the ATM
window has not yet expired, the ATM window will go into sleep mode until exactly one hour has elapsed since the last evaluation.

Cleanup Phase

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 22/27
1/19/2021
Before an ATM window completes execution, old data is deleted from the ATM history and ATM log as con gured through the SAP
AMC.

Memory Management
Memory Management allows you to monitor and con gure server parameters associated with Memory Usage. When you open the
functionality, you see an interactive chart representation of the parameters that contribute to the total logical memory of the
server. You can then switch to the table representation of the parameters by either switching tabs or selecting the parameter from
the chart.

By specifying the unit of the parameter, you get a range (maximum and minimum) and a short description of the parameter, which
helps you to decide on a valid new value.

Depending on the type of parameter (static, dynamic, read-only), the newly con gured values may not be displayed until you
restart your server.

Prerequisites
The functionality performs a check to see if stored procedure sp_con gure_amc exists on saptools database. If the stored
procedure is missing, it attempts at installing it.

To change the database server con guration, you need a database user with sufficient privileges. While most database
con guration parameters require an sa role, some require an sso role. For more information, see section Required Authorizations.

Server Con guration

This functionality allows you to view or change all server con guration parameters connected to your SAP ASE database.

Get an overview of the con guration parameters by group, their current values, their non-default value settings, the value to which
they have most recently been set, and the amount of memory used by this setting. It only displays the parameters whose display
level is equal to or lower than yours.

By specifying the unit of the parameter, you get a range (maximum and minimum) and a short description of the parameter, which
helps you to decide on a valid new value.

Depending on the type of parameter (static, dynamic, read-only), the newly con gured values may not be displayed until you
restart your server.

Prerequisites
Depending on your role you are authorized to view or change different con guration parameters. For more information see
Required Authorizations.

Furthermore, the Server Con guration also performs a check to see if stored procedures sp_con gure_amc, amc_con g exists on
saptools database. If the stored procedure is missing, it attempts at installing it.

Related Information
Required Authorizations

Required Authorizations
To change the database server con guration, you need enough privileges. While most database con guration parameters require
sa role for System Administrators, some require sso role for System Security Officers.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 23/27
1/19/2021
Display information about parameters and their current values can be viewed by all users. While con guration parameters can
only be modi ed by System Administrators (sa role) and System Security Officers (sso role). All other parameters can be modi ed
by the System Administrators (sa role).

Parameter System Administrator System Security Officer

(sa role) (sso role)

allow procedure grouping No Yes

allow select on syscomments.text No Yes

allow updates No Yes

auditing No Yes

current audit table No Yes

enable encrypted columns No Yes

enable logins during recovery Yes No

enable semantic partitioning Yes No

max concurrently recovered db Yes No

number of checkpoint tasks Yes No

remote access No Yes

restricted decrypt permission No Yes

suspend auditing when full No Yes

systemwide password expiration No Yes

BALDR
BALDR is the monitoring system for AMC. It creates the saptools database in which the monitoring data is stored.

The saptools database requires 2 GB data memory and 200 MB memory log, which should be available on your SAP ASE
server. The standard SAP ASE data cache should also be more than 20 MB. The maximum nesting level should be more than 100.

Apart from this, you must have the Job Scheduler installed.

If this prerequisites are met, you can start installing BALDR using AMC. To do this, navigate to the topicscreen BALDR, which is
part of the Con guration menu and use the Setup BALDR button to install the instbaldr.sql script. You can view the
installation log in the Installation Log tab, located next to the Data Collector and Admin Procedure tab. After successful
installation, you can see the BALDR properties such as BALDR version, status, and con guration owner.

Below the BALDR properties you can also start the Job Scheduler, setup message log level, and Transfer Ownership.

Workload Analyzer
Workload analyzer option for the SAP Adaptive Server Enterprise allows you to capture, analyze, and replay a production workload
non-disruptively. You can then use the captured workload to diagnose problems, and understand and manage con guration
changes. Workload analyzer also allows you to replay captured workloads to measure and analyze application performance under
different conditions.

Identify problematic queries, such as queries with a long response time.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 24/27
1/19/2021
Identify client activity patterns, such as the number of requests per IP address.

Measure the performance of captured workloads in different server con gurations.

Compare query and overall workload performance between different server con gurations.

Evaluate database upgrades and understand the bene ts from new options.

Diagnose product problems by replaying functionality in a controlled environment.

Pinpoint potential issues such as why certain queries are running slowly.

Determine the longest running query.

Test new features and run them against a captured workload to verify performance.

Capture the workload on the target server that is running the replay to compare performance against its original replay.

Prerequisites
To use the workload analyzer feature, make sure you have sa/sso role and meet these requirements:

Requirement Description

ASE_WORKLOADANALYZER license Purchase the ASE_WORKLOADANALYZER license so you can install

the workload analyzer option on your SAP ASE production server,
from where you plan to capture the workload. With the license, you
can enable the feature by setting the enable workload analyzer
con guration parameter to 1 (on). This con guration is dependent
on the existence of the ASE_WORKLOADANALYZER license.

enable workload analyzer con guration parameter After obtaining the ASE_WORKLOADANALYZER license, enable the
feature by setting the enable workload analyzer con guration
parameter to 1 (on).

Repository server In addition to the SAP ASE server with the workload you plan to
analyze, install an additional server from which to perform your
workload replay and analysis. Having a separate nonproduction
server helps to avoid performance contention issues. The license for
the Workload Analyzer feature includes entitlement to use an
additional SAP ASE server for the purpose of hosting the Workload
Analyzer repository database. The SAP ASE server license provided
with the Workload Analyzer feature includes all the capabilities
required to support the Workload Analyzer repository database.

Semantic partitioning The sybcatdb database that is installed on the repository server
requires semanticsbased partitioning, a licensed feature.

Synchronizing SUIDs As part of the overall server and database environment, the replay
server and the copy of the application database on that server —
that is, the database used by the operations contained in the
captured workload that will be replayed, and not system databases
such as master or model, or from other databases that might reside
on your SAP ASE server that you have loaded the application
database onto — should have the same characteristics as on the
source production server. The application login must be a user in
the application database, and the SUID for that user must be the
same in the master and application databases. This requirement is
not unique to replay. Synchronizing SUIDs is a common
administrative requirement that our customers often encounter any
time a databases is restored to a new server.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 25/27
1/19/2021

Requirement Description

Operating system logins Whenever you use this option, make sure to start both SAP ASE and
AMC using the same operating system login. AMC must be able to
read the pcap les that SAP ASE generates, and AMC creates the
output directories for the pcap les and SAP ASE must be able to
write to those directories. Because access to the directories and
les are automatically restricted to the operating system login that
creates them, AMC cannot perform a workload analysis unless
cockpit is running under the same operating system login as the
SAP ASE server.

Setting login default database Make sure to con gure the attributes of all logins that use the
application to explicitly be able to use the application database.

Furthermore, the Workload Analyzer tool also performs a check to see if table AMC_REPO_SERVER exists on saptools
database. If the table is missing, it asks to run Setup BALDR.

 Note
For the process of setting up sybcatdb database for the rst time using the repository server wizard, the repository server
user must be the system administrator.

Using the Add button in the Repository Server tab, system administrators (sa/sso) can install the repository server if it is missing
in SAP ASE systems.

Backup and Recovery

Backup and Recovery allows you to monitor your backups, as well as schedule either a database or a transaction dump. To create
a dump, you can use the Create button which navigates you to a wizard.

This wizard allows for database/transaction dump using either a manual or a pre-existing dump con guration. You can also save a
manual con guration and use that as a template for later dumps. The creation of the dump is handled by the Job Scheduler using
an immediate scheduled job.

Other options which are also provided include, cumulative (database) or standby access (transaction) checkboxes, as well as
compression level, number of stripes and veri cation method.

Prerequisites
The dump process is handled by two stored procedures which are delivered as part of BALDR. These are SP_ADM_DUMPDB and
SP_ADM_DUMPTXN.

In order to schedule a dump, this functionality requires an up and running Job Scheduler (JS Agent), as the dump procedure is
scheduled as a job.

Diagnostics

Related Information
ATM History
ATM Log
ATM Queue

ATM History
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 26/27
1/19/2021
Get an overview of all Automatic Table Maintenance (ATM) operations that have been executed by ATM in the past days and
weeks. This information allows you to ne tune your ATM con guration and to ensure proper behavior of ATM in the respective
application environment.

By selecting one of the records shown, the maintenance command that was executed is shown in the details page, as well as the
ATM pro le that initiated maintenance of the object.

By default, the ATM history spans 8 weeks. A different ATM history size can be con gured in the Miscellaneous tab of the
Con guration -> ATM Con guration screen.

Prerequisites
In order to see data on the ATM History screen, Automatic Table Maintenance must have been run.

ATM Log
ATM writes its own message log while evaluating maintenance requirements and nally executing maintenance operations. While
its main target group is SAP support, this message log can also help DBAs understand error conditions and performance related
issues.

By default, ATM logs for the last 14 days are kept. This number of days as well as the number of messages being written into the
ATM log can be con gured in the Miscellaneous tab of the Con guration -> ATM Con guration screen.

Prerequisites
In order to see data on the ATM Log screen, Automatic Table Maintenance must have been run.

ATM Queue
Automatic Table Maintenance (ATM) is executed in two phases. Phase 1 identi es objects that require maintenance according to
the de ned ATM pro le and put those objects into an ATM queue. Phase 2 nally execute maintenance, as de ned in the ATM
queue until the ATM window has expired or no entry can be found in the ATM queue.

If the ATM windows are too short to process all identi ed maintenance requirement, the ATM queue lls up and the required
maintenance operations are not executed. The Diagnostics -> ATM Queue screen allows you to monitor the current ATM queue.

By selecting one of the records shown, the maintenance command that is going to be executed is shown in the details page, as
well as the ATM pro le that initiated maintenance of the object.

Prerequisites
In order to see data on the ATM Queue screen, Automatic Table Maintenance must have been run.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23374454&topics=144a0c46823749dca380f3c297… 27/27