Guide DBA Sybase

Database Administration Guide: SAP on Sybase ASETarget Audience n System Administrators n Technical Consultants PUBLIC Document version: 1.1 ‒ 12/18/2012 Document History Caution Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/instguides. The following table provides an overview of the most important document changes. Version Date Description 1.0 5/22/2012 Initial version 1.1 12/18/2012 Minor changes 2/116 PUBLIC 12/18/2012 Table of Contents Chapter 1 Introduction Chapter 2 2.1 2.2 2.3 2.4 Architecture Overview . . . SAP Application Server for ABAP . SAP Application Server for Java . Sybase ASE Components . . . . Sybase ASE Data Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9 10 11 11 Chapter 3 3.1 3.2 3.3 3.4 3.5 3.6 User Administration and Authentication Operating System Users . . . . . . . . Database Logins . . . . . . . . . . . SAP System Users . . . . . . . . . . Network and Communication Security . . File System Permissions . . . . . . . . Maintenance Actions in the DBA Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14 15 15 17 18 19 Chapter 4 4.1 4.2 4.3 4.4 4.5 4.6 4.6.1 4.6.2 The DBA Cockpit . . . . . . . . . . . . . . . . . . . . . . The DBA Cockpit on a Local System and on SAP Solution Manager . . . . DBA Cockpit: User Interface . . . . . . . . . . . . . . . . . . The EXPLAIN Access Plan . . . . . . . . . . . . . . . . . . . SQL Command Line . . . . . . . . . . . . . . . . . . . . . Scheduling an Action . . . . . . . . . . . . . . . . . . . . . Managing the System Landscape . . . . . . . . . . . . . . . . . Configuration of Systems for Remote Monitoring . . . . . . . . . . Architecture Overview: End-to-End Monitoring and Alerting in SAP Solution Manager and DBA Cockpit . . . . . . . . . . . . . . . . . . . Setting Up Database Monitoring and Alerting in SAP Solution Manager . . Configuring Systems for Remote Monitoring Manually . . . . . . . . Enabling the Database for the Data Collection Framework . . . . . . . Setting Up the Data Collection Framework (DCF) Manually . . . . . . Configuring Database Connections . . . . . . . . . . . . . . . . Configuring Systems for Remote Monitoring Using the System Landscape Directory (SLD) . . . . . . . . . . . . . . . . . . . . . . . Using the Central Calendar . . . . . . . . . . . . . . . . . . . Performance . . . . . . . . . . . . . . . . . . . . . . . . 4.6.3 4.6.4 4.6.5 4.6.6 4.6.7 4.6.8 4.6.9 4.7 12/18/2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . PUBLIC . . . . . . . . . . 7 23 24 25 30 32 73 33 33 34 36 37 40 41 42 44 46 48 3/116 . . . . . . . . . . . . . .7. . . . .1 4.11.10. . .1 4. . . .11. . . . Configuration . . . . . . . . . .10. . . . . . .1 4. . Configuration: Server Configuration . . Troubleshooting . . . . . .5 4. . . . . . . . Performance: Temporary Database Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9. . . 48 49 51 52 53 54 55 56 57 58 59 60 61 62 63 63 65 65 66 68 71 71 73 73 74 75 76 76 77 77 77 77 79 81 83 84 84 84 85 88 88 89 12/18/2012 . . . . . . . . . . . . . . . . . . . . . .2 4.6 4. . . . . .9. . . . . . . . . . . Diagnostics: Audit Log . . . . . . . . . Setup and Maintenance of the ATM Framework . . . . . . . . . . .10 4. .8 4. . . . . .10. .3 4. . . . . Space: Databases . . . . . . . . . . . . .10. Performance: System Load . .7. . .9 4. . Performance: Data Cache Usage . . Space: Tables and Indexes . . . . . . . . . . . . .4 4. . Diagnostics: Lock-Wait Events . . . . . . Jobs: DBA Planning Calendar . .9 4. . . . . . . . . . . . . . .8. . . . . . .10. . . . . . . . . . . . . . Automatic Table Maintenance . . . . . . . Displaying Scheduled Actions . . . .2 4. . . . . . . Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostics: Automatic Table Maintenance ‒ ATM History Diagnostics: Automatic Table Maintenance ‒ ATM Queue Diagnostics: Automatic Table Maintenance ‒ ATM Log . . . . . . . . . . . . . . . . . . . Performance: Threads . . . . . . . . Data Collection Framework: Collector Configuration . . . . . . .7 4. . .4. . . . . . . Performance: Tables . Performance: Procedure Cache Usage . . . . . . . . . . . . . . . . . . Space: Devices .3 4. . . . . . . . . . . . . . . . . . . .8. . . . . . . . . .7. . . . Executing an Action . . . .3 4. . .7 4. . . . .6 4. . . . .7. . . . . . . .6 4. . .11. . .11. . . . . .1 4. . . Processing ATM Windows and Assigned ATM Profiles . .2 4. . . . .7. ATM Windows . Deleting an Action . . . PUBLIC . . . . . . . . .10. . . . .2 4/116 Performance: ASE Server . . . . . . . .11. . Data Collection Framework: Template Definition . . . . . . . . . . . . . . . Performance: System Waits . Jobs: DBA Log . . . . .11 4. . . . . . .12. . . . The ATM Framework .2 4. .7. . . . . . .10. . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Space . . . . . . .7. . .8 4. . . . . . . . . Configuration: Data Collection Framework . . . . . . . .1 4. . .8 4. . . . . . . . . Jobs . . . . .12 4.8. .2 4.10 4. .11. . Configuration: Data Caches . . . . .10. . . . .7 4. . .10. . . .7. . .4 4. . . . . . . . . . . . . . . . . . . . . . .5 4. . . . . . . . . . . . . . . . . . . . .4 4. . . . .11.5 4. . .9. . .7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance: SQL Statements . . Changing an Action . . .9. . . . Setting Up and Working with the DBA Planning Calendar Scheduling an Action . . . . . . . . . . . . . . . .8 4. . . . . . . . . . . . . . . .9 4. . . . . . . . . . . . . . . . . ATM Profiles . . .4 4. . . . . .9.7. . Performance: Processes . . . . . . . . . .12. . . . . . . . . .3 4. . . . .3 4.5 4. . .11. . . . . . . . . . . The Main SAP Documentation Types .12. . . . . Diagnostics: ASE Status . . . . . . . . 90 91 91 5/116 . . . . .1 Reference . . . . . . . . . . . . . . .1 5. Diagnostics: Error Log . . . Chapter 5 5. 93 93 95 101 Chapter A A. . . . . . . . .3 4. .12. . . . . . . . . . . . . . . .3 Backup and Recovery . . . . . . . . . . . . . . . Ensuring Recoverability for Sybase ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Restore a Sybase ASE Database Server (Windows) How to Restore a Sybase ASE Database Server (UNIX) .2 5. . . . . . . . . . 109 109 12/18/2012 PUBLIC . . . . . . .4 4. . . . . . .5 Diagnostics: Missing Tables and Indexes . .4. . . . . . . . . . . . . .12. 6/116 PUBLIC 12/18/2012 . Additionally.com SAP NetWeaver SAP NetWeaver <Release> SAP Library English SAP NetWeaver Library: Function-Oriented View Application Server Application Server Infrastructure Architecture Naming Conventions In this documentation the following naming conventions apply: SAP NetWeaver System / SAP System SAP NetWeaver system is referred to as SAP system. A basic understanding of the fundamental database concepts and an elementary knowledge of SAP system administration is required.sap. and maintain SAP systems on the database.7) in an SAP environment. It also helps you to plan. for example. In addition. any product of the SAP Business Suite. install.1 Introduction 1 Introduction This document provides specific information about the administration of Sybase Adaptive Server Enterprise (Version 15. For more information. the term SAP system also refers to any application system that is based on SAP NetWeaver. This guide is primarily intended for database administrators and SAP system administrators who need to install and maintain an SAP system on the database. 12/18/2012 PUBLIC 7/116 . it provides references to additional documentation and guidelines as well as recommendations from SAP that are only available in this document. refer to: http:help. This page is left blank for documents that are printed on both sides. . 12/18/2012 PUBLIC 9/116 . n Native SQL Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary. Figure 1: AS ABAP AS ABAP The ABAP language offers the following options to communicate with the database: n Open SQL for ABAP Open SQL allows you to access database tables declared in the ABAP Dictionary regardless of the database platform that your SAP system is using. and therefore integrate data that is not part of the SAP system.1 SAP Application Server for ABAP The following figure provides an overview of how the SAP application server for ABAP (AS ABAP) connects to the database.2 Architecture Overview 2 Architecture Overview 2. JDO. the DBSL shared library dynamically loads the Sybase ASE ODBC libraries while bypassing the driver manager. To use the ODBC driver. The DBSL is part of the SAP kernel and is developed in C. The database interface provides Java applications with the following options to communicate with the database: n Open SQL for Java (SAP’s database-independent SQL dialect) n Native SQL (database-dependent) 10/116 PUBLIC 12/18/2012 .*) uses the Sybase ASE ODBC driver to communicate with the database management system (DBMS). The database interface also performs the database platform-specific mapping between ABAP data types and database data types.2 SAP Application Server for Java The following figure provides an overview of how the SAP application server for Java (AS Java) connects to the database. Each database platform provides a platform-specific database interface library (DBSL). The DBSL shared library for Sybase ASE (dbsybslib. 2. or JPA.2 2.2 Architecture Overview SAP Application Server for Java The ABAP processor uses a database interface to connect to the database. The database interface provides a database platform abstraction layer and translates all Open SQL statements from the ABAP processor into native database-specific SQL statements. SQLJ. Figure 2: AS Java AS Java Java programs that run inside the Application Server for Java can use various standardized APIs to access the database ‒ for example. Each SAP application server can use the driver files directly from this directory or copy them to a local directory on the application server during startup. For the Java stack the connection information for the SAP system is stored in the connection URL. 2.3 Architecture Overview Sybase ASE Components The Application Server for Java uses various services that assist in the communication with the DBMS. which supports connection validation. and easy configuration. This setup simplifies software maintenance because you only need to keep the driver files in the shared directory. All communication with the DBMS is done using the Sybase ASE jConnect JDBC driver . the DBPool service. The ODBC driver and the JDBC driver files are located in a shared directory. we can distinguish the following components: n The Sybase ASE server software You can have multiple Sybase ASE installations on one host. 2. time-based expiry. n The ASE server which contains several system databases and zero or more user databases n The ASE backup server n The user database itself. there is one SAP user database that holds the SAP data. For the ABAP stack.2 2. The ODBC Driver Manager is not used.4 Sybase ASE Data Access To connect to the database. the connection information for the SAP system is stored in the SAP system environment and profile parameters.3 Sybase ASE Components With regard to Sybase ASE itself. for example. which contains the data and is managed by the DBMS Note In an SAP system installation. which in turn is stored in the Java Secure Store.a pure Java Type 4 JDBC driver that is based on the TDS (Tabular Data Stream) protocol and uses TCP/IP as its network protocol. The following figure shows the directory structure of the Sybase ASE client connectivity in a newly installed ABAP and Java system on a UNIX operating system: 12/18/2012 PUBLIC 11/116 . an SAP application server requires the following components: n The ODBC libraries for the ABAP stack n The JDBC driver for the Java stack n The database name and connection port for the primary database These components together enable the client connectivity or data access. DBPool is a Java-based database connection pooling utility. During the installation of the database instance. This takes place during startup of the application server. /usr/sap/<SAPSID>/<Instance Name>/exe. the Sybase ASE driver files are copied by the utility sapcpe to a local directory on the application server. 12/116 PUBLIC 12/18/2012 . you can maintain and exchange the Sybase ASE driver files in the shared directory while the application servers are running. The SAP application servers automatically use the new driver files after the next restart. The DBSL shared library looks for the Sybase ASE ODBC driver as specified by the environment settings for the operating system library path.2 2. If you install a new application server. With this copy mechanism. The main release level of the Sybase ASE driver must be higher than or equal to the one of the software release levels of the database server.4 Architecture Overview Sybase ASE Data Access Figure 3: Directory Structure of the Database Client for an ABAP and Java system The Sybase ASE driver files are located in the directory /usr/sap/<SAPSID>/SYS/global/syb/<od platform>/syb [odbc|jdbc]. for example. The call can be found in the SAP instance profile. During startup of the application server. the Sybase ASE driver for this operating system is also automatically added by SAPinst if it is not already available in the global directory. the current SAP installation tool automatically installs the Sybase ASE driver for the operating system of the database server. and EARLYWATCH in client 066.sap. Instead. not to users SAP*. if a user was copied as part of the client copy). you need to change the passwords in all the relevant SAP sytem clients. n Java: http:help. be aware that SAP system users might exist in multiple SAP system clients (for example. by default.com SAP NetWeaver SAP NetWeaver <Release> Application Help SAP Library English SAP NetWeaver Security Guide Security Guides for SAP NetWeaver Functional Units Security Guides for the AS Java . DDIC. we include information about user administration and authentication that specifically applies to SAP on Sybase ASE. SAPinst has applied the master password to users SAP* and DDIC only for SAP system clients 000 and 001. Therefore. The table below lists these users: n Operating system users n Database logins n SAP system users SAPinst will. If you change user passwords. SAPinst always assigns the following passwords to these users in client 066: SAP*: 06071992 EARLYWATCH: support 12/18/2012 PUBLIC 13/116 . Therefore. have assigned the master password to all users that were created. unless you specified other passwords.com In addition to these guidelines.3 User Administration and Authentication 3 User Administration and Authentication SAP on Sybase ASE uses the user management and authentication mechanisms provided with the SAP NetWeaver Application Server platform. http:help.sap. You need to ensure the security of the users that SAPinst created during installation. the security recommendations and guidelines for user administration and authentication also apply to SAP on Sybase ASE: n ABAP: SAP NetWeaver SAP NetWeaver <Release> Application Help SAP Library English SAP NetWeaver Security Guide Security Guides for SAP NetWeaver Functional Units Security Guides for the AS ABAP . PUBLIC 12/18/2012 .1 Operating System Users During the installation. SAP system administrator <sapsid>adm sapsys (sapinst as secondary group) Diagnostics agent administrator <dasid>adm sapsys (sapinst as secondary group) Host agent administrator sapadm sapsys (sapinst as secondary group) syb<dbsid> sapsys (sapinst as secondary group) Users and Groups of the Host agent: User: Primary Group: Additional Group: Comment: sapadm sapsys sapinst Host Agent administrator Note We recommend changing the user IDs and passwords for users that are automatically created during installation. User Management Engine with SAP NetWeaver AS Java 14/116 For more information.3 3. PFCG (user and role maintenance For more information. If not. SAPService<SAPSID> This user is the Windows account that is used to run the SAP system and is not a member of the local Administrators group.com SAP NetWeaver <Release> with SAP NetWeaver AS ABAP) Application Help SAP Library English SAP NetWeaver SAP NetWeaver Security Guide Security Guide for SAP NetWeaver Functional Units Secuirty Guides for the AS ABAP SAP NetWeaver Application Server ABAP Secuirty Guide User Authentication .sap. SAPinst checks all required accounts (users.sap.com SAP NetWeaver <Release> Application Help SAP Library English SAP NetWeaver SAP NetWeaver Security Guide Security Guide for SAP NetWeaver Functional Units Secuirty Guides for the AS Java SAP NetWeaver Application Server Java Secuirty Guide User Administration and Authentication . SAPinst creates the following new users and groups: User: Primary Group: UNIX superuser root No primary group assigned by SAPinst (group sapinst is assigned as secondary group).1 User Administration and Authentication Operating System Users 3. groups) and services on the local machine. SAPinst checks whether the required users and groups already exist. see http:help. The table below shows the tools to use for user management and user administration: Tool: Detailed Description: Transactions SU01. see http:help. 001. Proceed as described in SAP Note 1706410 to change the passwords for users SAPSR3. sapsso.2 User Administration and Authentication Database Logins 3. sapsa. sap_adm.3 SAP System Users After installation. 3. We recommend that you use strong password and auditing policies for this user. the Adaptive Server default login sa is locked by SAPinst after installation has been completed.2 Database Logins During installation. sybase_ts_role Database Administrator sapsso sso_role Database Security Officer SAPSR3 sap_mon ABAP connect / database login SAPSR3DB sap_mon Java connect / database login Note For security reasons. and 066 of the ABAP system. DDIC This user exists in at least clients 000. EARLYWATCH This user exists in at least client 066 of the ABAP system. ABAP and Java system users are available. The following table shows these users. 001. 12/18/2012 PUBLIC 15/116 .3 3. together with recommendations on how you can ensure the security of these users: User: User Name: Comment: SAP system user SAP* This user exists in at least clients 000. We recommend that you use strong password and auditing policies for this user. and sa on the database server. SAPSR3DB. and 066 of the ABAP system. SAPinst creates the following database users: Login: Roles: Comment: sapsa sa_role. SAPCPIC This user exists in at least client 000 and 001 of the ABAP system. Communication user for the J2EE engine The name that you gave this user during installation or the default name SAPJSF This user exists in at least clients 000 and 001 of the ABAP system and in the User Management Engine (UME) of the Java system. User for Adobe Document Services ADSUser (ADS) Data supplier user for System Landscape Directory (SLD) (optional) This user exists in at least clients 000 and 001 of the ABAP system and in the User Management Engine (UME) of the Java system. It is used for basic authentication. Guest The name that you gave this user during installation or the default name J2EE_GUEST This user exists in at least clients 000 and 001 of the ABAP system and in the User Management Engine (UME) of the Java system. The recommended name is SLDDSUSER. 16/116 PUBLIC 12/18/2012 . ADS_AGENT This user exists in at least clients 000 and 001 of the ABAP system and in the User Management Engine (UME) of the Java system. It is used for remote function calls (RFC) between the ABAP system and the Java SDM SDM This user is used to access the Software Deployment Manager (SDM) in the Java system.3 User Administration and Authentication SAP System Users User: User Name: Comment: Administrator The name that you gave this user during installation or the default name J2EE_ADMIN This user exists in at least clients 000 and 001 of the ABAP system and in the User Management Engine (UME) of the Java system. The name that you gave this user during installation. Note SAPinst created this user automatically if you chose Configure local SLD during the installation. We recommend that you use strong password and auditing policies for this user.3 3. It is used for processing forms between an ABAP and a Java environment. It is used for anonymous access. This user exists in at least clients 000 and 001 of the ABAP system and in the User Management Engine (UME) of the Java system. It has administrative permissions for user management. A well-defined network topology can eliminate many security threats based on software flaws (at both the operating system level and application level) or network attacks such as eavesdropping. For more information. 3. see http:help. The network topology for SAP on Sybase ASE is based on the topology used by the SAP NetWeaver platform. they cannot exploit well-known bugs and security holes in network services on the server machines. there is no way that intruders can compromise the machines and gain access to the backend system’s database or files.com SAP NetWeaver <Release> Application Help SAP Library English SAP NetWeaver SAP NetWeaver Security Guide Security Guide for SAP NetWeaver Functional Units Secuirty Guides for the AS ABAP SAP NetWeaver Application Server ABAP Secuirty Guide User Authentication . Therefore.3 3.com SAP NetWeaver <Release> Application Help SAP Library English SAP NetWeaver SAP NetWeaver Security Guide Security Guide for SAP NetWeaver Functional Units Secuirty Guides for the AS Java SAP NetWeaver Application Server Java Security Guide User Administration and Authentication . the security guidelines and recommendations described in the SAP NetWeaver Security Guide also apply.sap. PFCG (user and role maintenance with SAP NetWeaver AS ABAP) For more information. Your network needs to support the communication necessary for your business needs. either by using the Secure Sockets Layer (SSL) protcol for HTTP connections or Secure Network Communications (SNC) for the SAP protocols dialog and RFC. User Management Engine with SAP NetWeaver For more information. If users cannot log on to your application or database servers at the operating system or database layer. Additionally.4 Network and Communication Security Your network infrastructure is extremely important in protecting your system. Therefore. UserID and password are encoded only when transported across the network.sap. we recommend using encryption at the network layer. The table below shows the tools to use for user management and user administration: Tool: Detailed Description: Transactions SU01. see: n Network and Transport Layer Security 12/18/2012 PUBLIC 17/116 . see AS Java http:help. if users are not able to connect to the server LAN (local area network). without allowing unauthorized access.4 User Administration and Authentication Network and Communication Security Note We recommend changing the user IDs and passwords for users that are automatically created during installation. SYSTEM.sap. SAPLocalAdmin 18/116 PUBLIC 12/18/2012 .3 3. SAPLocalAdmin <drive>:\sybase\<DBSID>\sybtemp syb<dbsid>. Administrators.5 User Administration and Authentication File System Permissions SAP NetWeaver <Release> Application Help SAP Library English SAP NetWeaver SAP NetWeaver Security Guide Network and Communication Security n Security Guides for Connectivity and Interoperability Technologies http://help.com 3. SAPinst creates them automatically. SAPLocalAdmin <drive>:\sybase\<DBSID>\sybsystem syb<dbsid>. Otherwise.sap. SYSTEM. Administrators. SYSTEM.com SAP NetWeaver <Release> Application Help SAP Library English SAP NetWeaver SAP NetWeaver Security Guide Security Guides for Connectivity and Interoperability Technologies http:help.5 File System Permissions The file systems and logical volumes must have the permissions and owners shown in the following table. File System Permissions ‒ UNIX File System/Logical Volume: Permissions: Owner: Group: /sybase/<DBSID> 750 syb<dbsid> sapsys /sybase/<DBSID>/ sybsystem 750 syb<dbsid> sapsys /sybase/<DBSID>/ sybtemp 750 syb<dbsid> sapsys /sybase/<DBSID>/ sapdiag 750 syb<dbsid> sapsys /sybase/<DBSID>/ sapdata_<n> 750 syb<dbsid> sapsys /sybase/<DBSID>/ saplog_<n> 750 syb<dbsid> sapsys File System Permissions ‒ Windows File System / Logical Volume: Access Privilege Full Control for User/Group <drive>:\sybase\<DBSID> syb<dbsid>. Note You can create the owners and groups manually if they do not exist. Administrators. SAPinst sets the required permissions and owners. The maintenance actions provided in the DBA Cockpit set locks to prevent parallel processing. secure location ‒ such as DVD ‒ and then delete the installation directory. Administrators. SYSTEM. the SAP user requires some additional authorizations. 3. To be able to perform these actions. A user must first have the global authorization and then. The following sections provide information about how global and system-specific authorizations are checked and what you need to do to gain the required authorizations. SAPLocalAdmin After installation For security reasons. You can enable or disable database maintenance in general using the profile parameter dbs/dba/ccms_maintenance. Administrators.6 User Administration and Authentication Maintenance Actions in the DBA Cockpit File System / Logical Volume: Access Privilege Full Control for User/Group <drive>:\sybase\<DBSID>\sapdiag syb<dbsid>. Global Authorization Check When you start the DBA Cockpit or switch to another system in the DBA Cockpit. the following authorization checks exist: n If the profile parameter is set to 0. the appropriate system-specific permission. depending on their personal permission for the authorization object S_RZL_ADM. If this profile parameter is not set in the instance profile. Administrators. For example. SAPLocalAdmin <drive>:\sybase\<DBSID>\sybdata_<n> syb<dbsid>. an authorization check is performed. n If the profile parameter is set to 1. The attribute ACTVT of this authorization object defines whether a user may maintain or only monitor objects.6 Maintenance Actions in the DBA Cockpit The DBA Cockpit provides a set of actions for monitoring and maintaining the database.3 3. the user must have authorization S_RZL_ADM and the system-specific authorization for maintenance. SYSTEM. 12/18/2012 PUBLIC 19/116 . regardless of their personal permissions. you also need to copy the installation directory to a separate. SAPLocalAdmin <drive>:\sybase\<DBSID>\saplog_<n> syb<dbsid>. to administrate a system. All changes to the database are recorded in an audit log file. SAP users cannot perform any maintenance actions. SYSTEM. in addition. Depending on the setting for profile parameter dbs/dba/ccms_maintenance. SAP users can perform maintenance actions. the default value 1 is used. The attributes DBA_DBHOST. You enable or disable the system-specific permission checks using the profile parameter dbs/dba/ccms_security_level. including special maintenance screens. This role does not include the value Extended Maintenance. the default value 0 is used. You can grant authorizations for using the DBA Cockpit with the following roles: n SAP_BC_S_DBCON_USER Read-only role that allows monitoring access to all systems configured within the DBA Cockpit. you can restrict access to specific systems that were configured in the DBA Cockpit. SAP system users can perform actions. n SAP_BC_S_DBCON_ADMIN Additionally grants administration rights to the user for all systems. 23 Maintain Enables read and maintenance access to all screens of the DBA Cockpit. Note The only screen for which extended maintenance permission is required is the SQL Command Line screen that you can access in the Favorites list of the DBA Cockpit. DBA_DBSID. and DBA_DBUSER must match the corresponding attributes for the database connection that was assigned to the selected system.6 User Administration and Authentication Maintenance Actions in the DBA Cockpit System-specific Authorization Check In addition to the permissions that are granted globally. depending on their personal permission for the authorization object S_DBCON. n If parameter dbs/dba/ccms_security_level is set to 1. If this profile parameter is not set in the instance profile.3 3. The special value <LOCAL System> for the attribute DBA_DBSID is used to identify the local system itself. no additional system-specific check is performed. 20/116 PUBLIC 12/18/2012 . except those that require extended maintenance permissions. 36 Extended maintenance Enables read and maintenance access to all screens of the DBA Cockpit. The attribute ACTVT of this S_DBCON authorization object defines the level of permitted actions and can have the following values: Value Description 03 Display Enables read access to all screens of the DBA Cockpit except those that only have maintenance mode and no read-only mode. Depending on the setting for profile parameter dbs/dba/ccms_security_level. the following authorization checks are performed when you select a system in the DBA Cockpit: n If parameter dbs/dba/ccms_security_level is set to 0. In this case. the user that is used for monitoring must have sufficient authorizations: n If you want to connect to remote systems running on Sybase ASE. see the appropriate DBA Cockpit documentation for the platform. you can select any user for monitoring. This connection is called +++SYBADM and is automatically generated.6 User Administration and Authentication Maintenance Actions in the DBA Cockpit Note Make sure that you have maintained the authorizations for your DBA user and for all batch users that either run jobs of the DBA Planning Calendar or the SAP standard jobs SAP_COLLECTOR_FOR_PERFMONITOR and SAP_CCMS_MONI_BATCH_DP. you are asked for the password of the sapsa login. all administrative actions of the DBA Cockpit are disabled. Granting Database Permissions To access the database.3 3. which is mandatory for background tasks that require administrative permissions. When you start the DBA Cockpit and the administration connection does not have yet a user assigned. You can display this audit log in the DBA Cockpit. we recommend that you use the sapsa login when adding remote systems because only sapsa has sufficient authorizations to execute administrative tasks. You can change the user and password for the administrative connection. 12/18/2012 PUBLIC 21/116 . n If you want to connect to remote systems running on any other database platform. n Local systems use a special administration connection. If you do not supply the correct user credentials. a standard connection with the SAP connect user is used instead of the administration connection. Auditing of Maintenance Actions When you make changes that affect database objects such as Adaptive Server configuration parameters. an audit log is written. However. This page is left blank for documents that are printed on both sides. . Central Monitoring of the Databases in an SAP System Landscape The DBA Cockpit is part of SAP NetWeaver systems and integrated into SAP Solution Manager. you can display performance and workload statistics. You can run the DBA Cockpit as part of your system adaministration activities in SAP Solution Manager. n Database configuration In this area. You can analyze space allocation and perform administration activities to change the storage layout of your database. You can administer and monitor remote databases from the DBA Cockpit using remote database connections. you can display information about archived log files and about logging parameters. The DBA Cockpit is optimized for handling administration and monitoring the databases of your entire system landscape from a central system.4 The DBA Cockpit 4 The DBA Cockpit The DBA Cockpit is a platform-independent tool that you can use to monitor and administer your database. you can use the DBA Cockpit to handle configuration of databases centrally. or display snapshots of database objects. The DBA Cockpit eases the work of database administrators because all important performance tuning. indexes. the functions of the DBA Cockpit especially support database administrators in adapting their databases for the workload of SAP systems. n Backup and recovery overview You get an overview of all performed database backups and recoveries. you get an overview of your database configuration. n Space monitoring and administration The DBA Cockpit allows you to watch the space consumption of your database. Including database objects such as tables. and administration tasks are available in a single transaction. perform time spent analysis. Therefore. In particular. monitoring. the following functions are available: n Performance monitoring For example. or tablespaces. Administration and Monitoring Functions for Sybase ASE If you administer and monitor Sybase ASE databases with the DBA Cockpit. In addition. n Job Scheduling 12/18/2012 PUBLIC 23/116 . analyze top SQL statements. The advantage of using the DBA Cockpit is that it has been specifically designed for the administration and monitoring of databases in an SAP system landscape. You can change the database configuration or the data collection framework. where you can access all databases in your system landscape using remote connections. this allows you to update and administrate all databases from a central system rather than logging on to each individual system separately. You can run the DBA Cockpit locally on an SAP NetWeaver-based system by calling the DBACOCKPIT transaction. such as lock-wait events or missing tables and indexes. scheduled tasks. n Alert Monitoring You can view alerts in the alert monitor and enable notifications for violations of database alert thresholds. you can run the DBA Cockpit on your SAP Solution Manager system. 24/116 PUBLIC 12/18/2012 .4 The DBA Cockpit Direct access to the DBA Planing Calendar. If you use the DBA Cockpit as part of the SAP Solution Manager system. and other tools allow you to plan and keep track of all important jobs for the databases. n Diagnostics Various diagnostic functions allow you to identify critical situations in your database. the DBA log. The local system is configured automatically when you start the DBA Cockpit for the first time. you must configure the system you want to monitor. more actions are required to configure the database monitor and to set up database administration. Alternatively. The DBA Cockpit allows you to: n Navigate between different actions n Change to another action without closing the previous action and still hold all data retrieved by this action n Handle central configuration n Monitor remote systems using remote database connections To use the functions offered for remote monitoring. After having configured the connection and depending on the database. The DBA Cockpit on a Local System and on SAP Solution Manager The DBA Cockpit is part of every SAP NetWeaver-based system. SAP Solution Manager is typically installed on a separate system. implementation. which provide high-level overviews of possible database issues. The DBA Cockpit not only provides more tools for the expert database administrator. the DBA Cockpit serves as an in-depth analysis tool for database-related issues. and reporting. including alerting functions. SAP Solution Manager offers a range of tools for root cause analysis.2 The DBA Cockpit DBA Cockpit: User Interface Figure 4: DBA Cockpit on an SAP Solution Manager System SAP Solution Manager is an SAP toolset in your system landscape to monitor the full stack of an SAP system: from the operating system up to the business process.2 DBA Cockpit: User Interface Layout of the Web Browser-Based User Interface The entry screen of the DBA Cockpit with the Web browser-based user interface is divided into the following areas: 12/18/2012 PUBLIC 25/116 . For database administrators. where it provides central access to tools.4 4. The tools of the DBA Cockpit complement the available SAP Solution Manager tools. but it also plays an important part in the SAP Solution Manager infrastructure. 4. and preconfigured contents that you can use during the evaluation. methods. and operations of your systems. In addition to the high-level overviews of SAP Solution Manager. These metrics are then passed on to the different applications in SAP Solution Manager. alerting. The remote database monitoring infrastructure of the DBA Cockpit is used by SAP Solution Manager to extract metrics from remote databases. for example. System Landscape Selector. the second-level navigation part provides a simplified system selection field with an F4 help. Your chosen screen layout is stored in the user settings and restored at the next start of the DBA Cockpit. If the launchpad is collapsed. these main task areas provide pull-down menus corresponding to the related detail levels. space management. to log off from the DBA Cockpit or to customize the layout.4 4. and job scheduling. performance monitoring.2 The DBA Cockpit DBA Cockpit: User Interface Figure 5: Navigation and Screen Layout of the Web Browser-Based User Interface Area Description Common header area Provides a standard set of functions. for example. Top level navigation including second-level navigation In the top level navigation. For fast navigation. the main task areas of database administration are provided. You can hide the areas Detail Navigation. you can switch between the following areas: n Cross-system area on the System Landscape tab page Provides information about the overall system landscape n Database-specific area on the Database tab page Provides information about the selected database In the second-level navigation. 26/116 PUBLIC 12/18/2012 . and Favorites by choosing the Expand or Collapse Launchpad pushbutton on the left side of the top level navigation area. Central system data This area is common to most actions providing. choose Personalize Add Favorite in the common header area. Useful links Contains the following useful links to: n SAP on Sybase ASE in SDN By choosing this link. When a new message is generated. for example. you can directly access the SDN homepage of SAP on Sybase ASE. the main actions become available. In addition. this window contains a complete history of all messages that are sent during the session. such as Performance Warehouse. n Sybase ASE Infocenter (Version 15. see Special Tools in the Favorites List. you can directly access the documentation for the Adaptive Server. Favorites list Contains a list of favorite links to special tools and actions. You can rename or delete favorites by choosing Personalize Organize Favorites .4 4. the time of the last refresh. a subset of related actions is available. the subactions Reporting and Configuration become available. This area is described in more detail under Customizing of the System Landscape Selector later in this section. If you choose Performance Warehouse. Global toolbar The global toolbar provides a set of globally available functions for navigation and content-related functions like Refresh. Framework message window Displays the message window that is provided by the framework. Note By default. Time Spent Analysis. the startup time. and the database name. For more information.2 The DBA Cockpit DBA Cockpit: User Interface Area Description Detail navigation Contains the main actions of the main task areas. the message window is collapsed. you can: n Collapse or expand the window by choosing Expand Message Window or Collapse Message Window. Example If you choose Performance in the top level navigation area. An entry is added to your list of favorites.7) By choosing this link. n Check if a long text for a message is available by double-clicking the message or by choosing Details. Depending on the selected main action. System landscape selector Provides a quick overview of all configured systems. and others. 12/18/2012 PUBLIC 27/116 . it is automatically expanded. To provide quick access to specific tools and actions. Unlike the classic SAP GUI message processing. 4 4. In addition. this can include the following: n Current details of the table entry (Summary tab page) n History data of the table entry (History tab page) n Graphical display of history data (History ‒ Graphical View tab page) 28/116 PUBLIC 12/18/2012 . totals or execution times n The content. Typically. which depends on the screen and action you have chosen You can refresh the content by choosing the Refresh pushbutton in the global toolbar or by changing the selection criteria and then choosing the Apply Selection pushbutton in the Selection area. you can use the Chart Type.2 The DBA Cockpit DBA Cockpit: User Interface Area Description Content area Displays details of the currently selected action. Depending on the area in the DBA Cockpit. Chart view in the content area Some reports are displayed as a chart. for example. To modify the chart view. Content detail area Only appears with certain actions and displays additional information that is related to the selected action. you can open a detailed table view by choosing the Toggle Table Display pushbutton. and Chart Size menu buttons that are optionally available depending on the screen. you can specify the width and height of the chart to be displayed. The content area is divided into the following areas that are optionally available depending on the chosen action: n The Selection area where you can enter selection criteria for the content to be displayed n The Summary area that provides views of data. By choosing the Chart Size menu button. this area shows details that are related to the information provided in the main content area. you can select a table row and display more details of this table entry in the detail area. Layout of the Content Detail Area If the content in the content area is displayed as a table. Values. 2 The DBA Cockpit DBA Cockpit: User Interface Figure 6: Detail Area: Layout The graphical view of the history complements the detail view of history data. The graphical view of the history is based on the time series that you can see in the history. For each configured system. Note You can switch off the display of the graphical view of history data in the personalization of the DBA Cockpit screens. all systems are displayed without any grouping or filtering. Customizing the System Landscape Selector By default. The following menu buttons are available for the list of systems: n Refresh System Landscape You can refresh the information about the available systems in the list.4 4. the name of the system and its database host is displayed. which contains all data in table format. n Group Systems by Selected Criteria You can customize the displayed list of systems by grouping them according to the selected criteria: l Database Platform 12/18/2012 PUBLIC 29/116 . the alert status. the Favorites list contains the following links that cannot be removed: n EXPLAIN Access Plan n Schedule an Action You can extend the Favorites list. You filter.3 The DBA Cockpit The EXPLAIN Access Plan l Name l Custom l Alerts To use a custom grouping. n Filter Systems by Selected Criteria You can filter the list of available systems to show only those systems that match the filter criteria. If no comments are specified. information about the SQL statement text is provided on the following tab pages: 30/116 PUBLIC 12/18/2012 . Specify a name for the custom group and assign the systems of your choice. <position> ). add and organize favorites by choosing Personalize Favorite or Personalize Organize Favorite in the common header area. Add 4. By default. n Search Systems Provides an input field where you can search for a specific system in the list. the statements are explained using the default <optlevel> and the default <query_degree> for the work process. As soon as you have added a custom group. In the Favorites list of the Web browser-based user interface. choose Add Group from the pop-up menu of the menu button Group Systems by Selected Criteria. You can access the Web browser-based version of the EXPLAIN function. Note The statements might contain optional comments. To do so. which lets you maintain an already existing group. If a statement was explained successfully.3 The EXPLAIN Access Plan You can use EXPLAIN to review the access plans of all SELECT.such as --OPTLEVEL( <optlevel> ) --QUERY_DEGREE(< query_degree> --LOCATION( <report> .4 4. INSERT. for example. the option Organize Groups becomes available in the pop-up menu of the menu button Group Systems by Selected Criteria. by the alert status of the systems. UPDATE or DELETE statements. choose Explain Access Plan. you must first define and add a custom group to the list. Special Tools in the Favorites List The Favorites list provides easy access to important tools and actions. that is. You can: n Display or hide details of an operator by choosing the Open Node or Close Node icon on the respective node n Expand or collapse subtrees by choosing the Show Child Node icon or the Hide Child Node icon respectively n View operation details by double-clicking an operator in the graphical tree Global details about an operator are displayed on the following tab pages: l General Displays global details about the access plan l Operator <Name of operator> Displays details for the selected operator l Catalog Information (Optional) Displays details for the respective catalog object of the selected operator l Predicates (Optional) Displays filter predicates for the selected operator n Search for operators in a complex statement by choosing Find Nodes for Labels n Open an extra navigation window for complex access plans by choosing Toggle Navigation Window n Print the graphic by choosing Print the Current Model n Configure the graphic before you print it by choosing Configure the Printout n Display or hide the quick details of all operators by choosing Collapse or Expand n Display global details about the access plan by choosing View Details n Display information about the JNet version used (can be required by SAP Support) by choosing the help button Note For each index used in the access plan. 12/18/2012 PUBLIC 31/116 .4 4. the number of key columns that were really used within the access plan is displayed. In the appropriate tool tip.3 The DBA Cockpit The EXPLAIN Access Plan Tab Page Description Original Statement Displays the original SQL statement Access Plan Displays the access plan that was generated by the Adaptive Server Using the Access Plan The access plan shows all database operations that are performed when the statement is executed. Volatile tables and indexes of volatile tables are marked with an extra volatile label. choose Edit Statement. To change and re-explain the SQL statement. the used index field names are also displayed. It is displayed as a graphical tree and each node in the tree represents an operator of the access plan. This screen provides a virtual command line processor. n Choose Schedule an Action in your Favorites. If you enter any SQL command. or enter the basic parameters for the action. you can do one of the following: n Click a calendar cell.4 4.4 The DBA Cockpit SQL Command Line 4.4 SQL Command Line This screen provides a virtual command line processor. 4. you now have to enter a recurrence pattern in the Recurrence step. 4. n Position the cursor on a calendar cell and choose the Add pushbutton. The Schedule an Action wizard appears. Optional: If you previously selected the Start as Recurring Action option in the Job Selection step. Start on Specifies the date and time when the action is to start Start as Recurring Action Activates the Recurrence step where you can further specify a recurrence pattern for this job as described later on in this section 3. You can access the SQL Command Line screen by calling the DBA Cockpit and choosing SQL Command Line in the Favorites list of the DBA Cockpit. To add new actions to the DBA Planning Calendar. the output is returned by the Sybase ASE command line processor. do the following: a) Choose the job that you want to schedule from the Action dropdown list. 2. change. In the Parameter step. The SQL Command Line screen appears in a separate Web browser.5 Scheduling an Action 1. In the Job Selection step. The following table describes the parameters to be specified in more detail: 32/116 PUBLIC 12/18/2012 . b) Specify one of the following options: Option: Description: Start Immediately The job starts immediately in the background after you have completed the required steps in the wizard. 4. choose System Configuration on the System Landscape tab page of the DBA Cockpit. for a specific time interval or for a limited number of occurrences. A table of all monitored systems is displayed.6 Managing the System Landscape The following sections provide information about how to manage your system landscape. the days of the week for weekly periods and the hours of the day for a daily period. In the first column. If the DBA Cockpit is used as part of Solution Manager Diagnostics. Alternatively. You must decide whether the actions might conflict in terms of database access or performance. review the specified parameters and schedule the job by choosing the Execute pushbutton. 5.6 The DBA Cockpit Managing the System Landscape Parameter: Description: Recurrence Pattern Interval for the action in weeks. 6. The system does not check for conflicts between actions with identical start times but checks for actions within a range of approximately 30 minutes. an icon indicates the current status of each system. Recurrence Range Range of time where the action recurs. This means that when you integrate systems into the SAP Solution Manager landscape. you have to configure those systems in the DBA Cockpit. days. you need to specify the pattern in more detail. the action is executed only once. but it does not prevent you from inserting the new action.1 Configuration of Systems for Remote Monitoring To be able to use the DBA Cockpit to monitor remote systems. 4.6. Caution The system warns you if there is a conflict with an existing action. the DBA Cockpit setup is part of the SAP Solution Manager setup. If you select Once only. you can configure your database system either using database information that is stored in the SLD for automatic generation and update of system entries or by manually creating database connections and system configuration entries. To access the System Configuration screen. The action is repeated at the interval that you enter. that is. that is. On the Summary screen. 12/18/2012 PUBLIC 33/116 . or hours Depending on the selected recurrence pattern.4 4. the related databases are configured in the DBA Cockpit and no DBA Cockpit-specific setup is required anymore. Exit the Schedule an Action wizard. not with the DBA Cockpit. n RFC connection (additional option for SAP ABAP systems only) For this method. To monitor a system remotely. when you start the DBA Cockpit. Architecture Overview: End-to-End Monitoring and Alerting in SAP Solution Manager and DBA Cockpit The architecture of SAP Solution Manager comprises a number of tools and frameworks that collect detail data about databases and their statuses automatically. This means that the DBA Cockpit uses the RFC connection in parallel to the database connection for the same system. you have to assign an RFC connection to your system. It is the main access method for monitoring and administration tasks and it is mandatory. Note You can only maintain RFC connections with transaction SM59.4 4.6 The DBA Cockpit Managing the System Landscape Normally. you use the following methods: n Remote database connections (mandatory) This method uses additional connections. To change this setting. You can specify remote connections for any database and maintain the connections using the DBA Cockpit. RFC connections are available for SAP ABAP systems only. for example. the Diagnostics Agent. You can use RFC connections as an optional access path for ABAP-related monitoring functions. for the consistency check of the ABAP Dictionary. the local system is set as default system. select a system from the list and choose Default System. Note This setting only applies to the user that is currently logged on to the system. It is not a system-wide setting. and the extractor framework: 34/116 PUBLIC 12/18/2012 . The tools and frameworks for automatic discovery of databases and database details include the landscape management database (LMDB). This kind of information mapped in the LMDB with the data provided by the SLD. the database type and its name. This includes information about the availability of the database and its host. gathers information from the managed systems and reports the information to the SAP Solution Manager system. to the SLD. The LMDB copies available data from the SLD. such as the database host. Extractor Framework. such as performance KPIs. but it enriches the data copied from SLD with additional information. The Diagnostics Agent uses SAP Host Agent to discover all databases installed on a host. and properties required for a remote database connection to the LMDB. or data cache hit ratio. space. the Diagnostics Agent reports technical attributes like cluster topology. The core task of the LMDB is to provide information about the entire system landscape at a central location.4 4. and thus is able to generate historical data (time series). In addition. database release.and mid-term developments in 12/18/2012 PUBLIC 35/116 . DBA Cockpit Backend.6 The DBA Cockpit Managing the System Landscape Figure 7: Data Collection and Database Monitoring and Alerting with SAP Solution Manager Landscape Management Database (LMDB) In SAP Solution Manager. Information about databases that do not run with an SAP system are also pushed to the LMDB by the Diagnostics Agent. The Diagnostics Agent and the SAP Host Agent transfer some basic information. Diagnostics Agent The Solution Manager Diagnostics Agent (Diagnostics Agent). and Data Flow The DBA Cockpit backend performs data collection via remote database connection and calculates the metrics of the monitored databases. which is installed on every local system of your system landscape. which allows database administrators to keep track of short. The DBA Cockpit takes snapshots of database statuses. all elements of a system landscape are modeled in the LMDB. 4 4. The extracted data is reused by the following engines and stores: n Alert Calculation Engine (ACE) n Metric-Event-Alert (MEA) Store n SAP NetWeaver BW for reporting These engines and stores further process the raw data taken from the databases and generate alerts and metrics for BW reporting. you need to provide the port and the host of the SLD. the central infrastructure for SAP Solution Manager for data collection and distribution. Database Type and Database Name at defined periods. The Diagnostics Agent gathers information from the managed systems and reports them to the SAP Solution Manager system. Use the transaction System Landscape Directory: Local Administration (RZ70) to configure SLD data suppliers in the system landscape. reporting functions and also the BW reporting screens in the DBA Cockpit. Configure data suppliers in the SLD. 2. incidents and notifications are then automatically triggered. You can use the SAP installation tool SAPinst to install the Diagnostics Agent. This also includes information about the availability of the database and its host. they push database attributes from the database to the SLD. You need to perform the following steps: 1. Connect the Diagnostics Agent to SAP Solution Manager. such as the alert inbox. Depending on the defined threshold values.6 The DBA Cockpit Managing the System Landscape the database. events. Data collected by the DBA Cockpit backend is also fed into the extractor framework. 36/116 PUBLIC 12/18/2012 . 3. You need to install a Diagnostics Agent on each server (virtual hostname) that you want to monitor. Once the SLD data suppliers are up and running. you use the standard transactions for setting up SAP Solution Manager. The SLD data suppliers are programs that collect the database attributes Database Host. Setting Up Database Monitoring and Alerting in SAP Solution Manager To set up the end-to-end monitoring and alerting infrastructure. Install the Diagnostics Agent on your database systems. For Sybase ASE databases. Here. events or alerts (MEA). which are then passed on to the different SAP Solution Manager applications. Predefined Alerting Templates Shipped by SAP During the SAP Solution Manager setup. you can find predefined monitoring and alerting templates that contain the definitions or values of metrics. predefined metrics. and alerts are available for the following: n Database availability n Database exceptions The availability of the end-to-end alerting in SAP Solution Manager depends on your support license. The SAP templates have predefined settings.com/solutionmanager n Additional database-specific setup steps: SAP Note 1027146 4. Configure the systems managed by SAP Solution Manager. n Recipients and recipient lists of auto-notifications n Assignment of monitoring templates to selected systems in scope for monitoring Monitoring templates contain the definitions or values of metrics. events. e-mail notifications) about database alerts As a default.6. see Enabling the Database for the Data Collection Framework [page 40]. including alerting. More Information n Complete setup of SAP Solution Manager: Documentation for SAP Solution Manager on SAP Help Portal at http://help. Use the transaction SAP Solution Manager Configuration (SOLMAN_SETUP) Technical Monitoring to set up the technical monitoring of databases in SAP Solution Manager.4 4.4 Configuring Systems for Remote Monitoring Manually You use this procedure to configure systems that you want to monitor using remote database connections. so only a password is required here. are automatically detected by the Diagnostics Agent. You set up the following: n Activation or deactivation of auto-notifications (for example. such as hosts or ports. 12/18/2012 PUBLIC 37/116 . n Trigger automatic configuration activities This includes the setup of database extractors.6 The DBA Cockpit Managing the System Landscape Use the transaction SAP Solution Manager Configuration (SOLMAN_SETUP) System Preparation to connect the SAP Diagnostics Agent to SAP Solution Manager. which collect data for monitoring the databases in SAP Solution Manager. 4. but you can also adapt the templates to your customer-specific needs. and alerts (MEA) that trigger incidents and notifications. but you perform only a basic setup that is necessary to connect to the monitored database. auto-notification is activated. Use the transaction SAP Solution Manager Configuration (SOLMAN_SETUP) Managed System Configuration to perform the following activities: n Connect the SAP Diagnostics Agent to the managed databases n Specify system parameters required to configure the managed databases Most of these parameters. A manual system configuration is only necessary if the monitored database has not been configured during the integration of a system using SAP Solution Manager.sap. 5. For subsequent configuration steps. The configuration does not include the setup of the monitoring infrastructure. Set up technical monitoring. some options might not be available. 1. n The user for the database connection must have sufficient database permissions. Prerequisites n The system(s) that you want to monitor must have a database release that is compatible with the database release of your local database. The following table lists the steps and recommended actions: Step Name Action Introduction Provides an overview of the configuration steps No action to be taken System Characteristics Specify the following: n Name of the system that you want to monitor Note This name is a unique ID and does not have to be the SAP system ID. n Description of the monitored system n Connection type Choose between the following connection types: l Remote Database Connection l Remote Database Connection and RFC Destination l Remote Database Connection via RFC Destination 38/116 PUBLIC 12/18/2012 . see Maintenance Actions in the DBA Cockpit. the local system is automatically added to the list of all available systems. 2. The System Configuration screen appears displaying a list of all available systems with a Configuration Status icon that indicates the current system status. Choose the Add pushbutton. you cannot enter any data in the corresponding fields. At least one system entry is displayed. Note When you start the DBA Cockpit for the first time. The wizard Integrate a System appears. In this case. For more information. You can choose any name except the SAP system ID of the local system that is reserved for the local system entry.4 4. Call the DBA Cockpit.6 The DBA Cockpit Managing the System Landscape Note Depending on the database platform of the selected system. this option should not be used anymore. 12/18/2012 PUBLIC 39/116 . select the Data Collection by Remote System checkbox. the E2E alerting of SAP Solution Manager is used that requires no specific setup in the DBA Cockpit. select the Activate Alert Monitoring checkbox. In this case. n If the monitoring data is to be collected by the remote system. Note If you are using the DBA Cockpit in SAP Solution Manager 7. confirm the selected name using the Enter key to prefill the connection attributes. you have chosen a connection type that requires an RFC destination. Database Connection Specify the following: n Name of the database connection This is a unique name that you can freely choose.6 The DBA Cockpit Managing the System Landscape Step Name Action RFC Destination (Optional step that is only necessary if.4 4.) Specify the name of the RFC destination to be used Note The specified RFC destination must already exist and be available.1. If the connection is not working. n Database platform of the monitored database n Connection maximum that limits the parallel use of this connection by the kernel n Connection optimum that sets the optimum number of open connections Note You should set this value to 0 to ensure that the kernel closes connections if they are no longer used. in the previous step. You can test the destination by choosing the Test Connection pushbutton. Instead. n User name and password for the user that is used for monitoring n List of connection parameters that are required to identify the database Monitoring Settings Specify how you want to collect monitoring data: n If alerts are to be provided for the RZ20 alert monitor. you can search for an already existing connection name using the related search help. you can only proceed if you select the Ignore Communication Errors checkbox. Alternatively. 4 4. only a subset of options might be available. Instead. n Deprecated option: If data about the performance or the size of database objects is to be collected. Execution Protocol Summarizes all performed actions including error messages To exit the wizard. 4. choose the Delete pushbutton and confirm the deletion. a separate schema is created in the monitored database that contains all relevant monitoring objects. proceed as described in Enabling the Database for the Data Collection Framework [page 40]. Summary Summarizes all actions to be performed To save your entries. 3. Optional: If you want to delete a configuration entry. select the Show Scheduled Jobs in Central Planning Calendar checkbox. the database to be monitored needs additional instrumentation to enable the time-based collection and evaluation of data related to performance. select the Collect Space and Performance History Data checkbox. and space.6 The DBA Cockpit Managing the System Landscape Step Name Action n If data for the Central Planning Calendar is to be provided. select the system entry in the overview list. enter and save your changes. configuration. In the dialog box Change System Configuration Entry. Optional: If you want to change an existing configuration entry. Note This option has been deprecated and should not be used anymore. select the system entry in the overview list and choose the Change pushbutton. such as: n A set of tables that keep the history 40/116 PUBLIC 12/18/2012 . Depending on the selected database platform. choose the Execute pushbutton.5 Enabling the Database for the Data Collection Framework After a system has been configured in the DBA Cockpit. To instrument this data collection framework (DCF).6. 4. choose the Finish pushbutton and return to the System Configuration screen. the DBA Cockpit initially displays the appropriate configuration screen where you can perform the required setup steps as described in Setting Up the Data Collection Framework (DCF) Manually. All settings for the instrumentation. For more information. you can influence the automatic setup of the DCF. recurrence patterns for the scheduled data collectors and the amount of data to be collected are determined by templates. and on the Database tab page. you can either use a template or activate and configure individual history data collectors. 4. Recommendation We recommend that you use templates to ensure that data is collected homogeneously in your system landscape. Only in rare cases. the existence of the DCF is checked. Regardless whether the database has been configured for monitoring using SAP Solution Manager or using the DBA Cockpit. choose Framework Collector Configuration .4 4. By modifying these templates. If the DCF cannot automatically be set up because of missing tablespaces or insufficient privileges of the monitoring user. 1. Call the DBA Cockpit. it is automatically set up if the database is enabled for automatic storage management or the required tablespaces have already been created.6. If the DCF does not yet exist..6 Setting Up the Data Collection Framework (DCF) Manually The DCF is set up individually for each database based on the database version. the first time you select a database system for monitoring in the DBA Cockpit. To set up the DCF manually. 12/18/2012 PUBLIC Configuration Data Collection 41/116 . n SAP Detailed Most of the data collectors run quarter-hourly. The sliding window is set to two weeks except for the most important tables and indexes. The sliding window is set to two weeks except for the most important tables and indexes.6 The DBA Cockpit Managing the System Landscape n Tablespaces to store these monitoring tables n A set of stored procedures to collect data on a regular basis n In case of an SAP system. the usage type of the database. it might be advisable that you configure individual history data collectors. for example. SAP provides the following standard templates: n SAP Default Most of the data collectors run hourly. and the SAP coding. a work process-based workload management configuration is applied. see Maintaining Templates for the DCF [page ]. To set up the template in the monitored database. new connections are created during the system configuration on the System Configuration screen as described in Configuring Systems for Remote Monitoring Manually [page 37] and.6. 1. Call the DBA Cockpit and on the System Landscape tab page. therefore. deselect the relevant checkboxes. do not have to be created on the Database Connections screen. The Implement Template dialog box appears.6 The DBA Cockpit Managing the System Landscape The Collector Configuration screen appears. Note The option to disable deprecated functions or to keep them is only available if there are deprecated functions that are currently active but recommended for disabling. choose Database Connections. 2. for example.7 Configuring Database Connections This section describes how you set and maintain technical attributes for remote database connections on the Database Connections screen in the DBA Cockpit. choose the Implement pushbutton. 3. The Database Connections screen appears displaying a list of all available database connection definitions grouped by database platform: Column Description Remote Database Connection Name of the database connection Note This is a unique name that you can freely choose. DB Name Name of the database DB Host Name of the database host DB Schema Name of the database schema to be monitored User Name Name of the connect user 42/116 PUBLIC 12/18/2012 . 4. For more information. for the access to external data resources by BW. The DBA Cockpit uses these connections for administration and monitoring or for application programs that use secondary connections to external databases. Usually. refer to Configuration: Data Collection Framework. If you want to keep any old settings. By default. The default template is marked with an asterisk (*).4 4. You can also use the Database Connections screen to set up database connections that are used for non-monitoring components. deprecated functions are preselected for disabling. Choose the Implement Template pushbutton. Connections Maximum allowed number of open connections Opt. choose the Add pushbutton.6 The DBA Cockpit Managing the System Landscape Column Description Permanent Specifies whether the connect user must be permanently available Max. 2. specify the name of the connection. In the Add Connection Entry dialog box. This parameter defines the availability of the database connection. see Maintenance Actions in the DBA Cockpit. To add a database connection. Make sure that you choose a user with the appropriate authorizations. n In the Connection Maximum field. It is then handled in the same way as the local default connection. 3. These can be. n In the Password field.4 4. This value is a more flexible limit that can be exceeded. administrator connections or connections that are used by systems from the system landscape directory (SLD). for example. that is. enter an appropriate value. For more information. enter the name of the connect user. enter the following: n In the Connection Name field. n In the Connection Optimum field. if this database connection is not available for a work process. the database connections that are defined in the local system are displayed. n In the User Name field. Caution You should set this parameter only if the connection is absolutely required to run your SAP system. The SAP system does not let you exceed this limit. Connections Optimal number of connections By default. specify the following additional database-specific parameter values: Attribute Description Database Name Name of the database 12/18/2012 PUBLIC 43/116 . Note This name is a unique ID that you can choose freely except for names that are reserved by SAP for generated connections. select the Permanent checkbox. This value limits the number of database connections that are currently held by the SAP system. enter an appropriate value. the work process of the SAP system cannot run. select the name of the database platform from the dropdown list. enter a password for the connect user and confirm it in the appropriate field. The Add Connection Entry dialog box appears. n In the parameter table. n If you want the connection to be mandatory for the SAP system. n In the Database System field. select a connection and choose the Test pushbutton. select a connection and choose the Delete pushbutton. you can test a database connection. To delete a connection.6 The DBA Cockpit Managing the System Landscape Attribute Description Service Name Name or number of the service This value corresponds to the parameter SVCENAME of the database manager configuration (DBM) of the remote database. During production operation.6. you use the procedure to synchronize the data between the SLD and the DBA Cockpit periodically.4 4. you cannot delete it. To do so. 6. choose the Add pushbutton. 5. expand the respective database platform in the Remote Database Connection column. To check if you have entered the correct user and password information as well as the correct technical connection data. 8. the name of the SAP connect user is used as schema. 4. select a connection. The test result is displayed in the Connection Test Protocol in the content detail area. Enter your changes in the appropriate fields and choose Save. You can use this data to set up the system configuration in the DBA Cockpit instead of setting it up manually or using SAP Solution Manager. Database Host Name of the remote database server Schema Name Name of the schema to be monitored Note If you omit this field. To save your entries. To change a database connection. you use this procedure to import the appropriate data from the SLD. and choose the Change pushbutton. The Change Connection Entry dialog box appears. Caution If the selected database connection is still used by a system that is registered in the DBA Cockpit. When you set up the DBA Cockpit for the first time. 7.8 Configuring Systems for Remote Monitoring Using the System Landscape Directory (SLD) The system landscape directory (SLD) contains data from all database systems that are available in your system landscape. 4. 44/116 PUBLIC 12/18/2012 . 1.6 The DBA Cockpit Managing the System Landscape Note We recommend that you only use the SLD for the setup of your system landscape if SAP Solution Manager is not available. 2. choose the Change pushbutton. Note Each database system is described as follows: <Name (system ID) of the database system> on <main database host> ( <database platform> ) 3. The SLD System Import screen appears. one or more of the following nodes are displayed: n New Database Systems in the SLD All database systems that are registered in the SLD and that so far have been unknown to the DBA Cockpit are displayed. To import database system data. The selected actions are executed. n Changed Systems From Earlier SLD Imports All database systems for which the main data differs between the SLD and the DBA Cockpit are displayed. n Unsupported Database Systems in the SLD All database systems that are registered in the SLD but not supported by the DBA Cockpit are displayed. Depending on the system landscape. The actions allowed for each database system are displayed in the second column of the tree. call the DBA Cockpit. 12/18/2012 PUBLIC 45/116 .4 4. On the System Landscape tab page. 4. n Systems No Longer Registered in the SLD All systems that were originally imported from the SLD into the DBA Cockpit but that are no longer registered in the SLD are displayed. only the import of new database systems is selected. choose SLD System Import. n Systems Identical in the SLD and in the DBA Cockpit All systems that are registered in the SLD and that are identical in the DBA Cockpit are displayed. By default. A short message for each executed action is displayed in the content detail area. To import database connection data from the SLD. Select the actions that you want to execute for the selected database systems and choose the Import pushbutton. the DBA Cockpit checks the completeness of the configured system. password. Start the Central Calendar from the DBA Cockpit by choosing Jobs Central Calendar . enter the required data as described in Configuring Database Connections [page 42]. Prerequisites n You have defined the systems to be displayed in the Central Calendar by double-clicking the required system in the screen DBA Cockpit: System Configuration Maintenance and selecting Collect Central Planning Calendar Data. FUD and FIB: 3 FUD 2 4 FIB 1 46/116 PUBLIC 12/18/2012 . if necessary. 1.9 Using the Central Calendar You can use the Central Calendar in the DBA Cockpit to view actions on all the databases of your SAP Systems. and connection information. This collects information from the defined remote systems for display in the Central Calendar. If you have already run or planned actions. Here is an example of entries for Thursday February. n User or password data is not available via SLD. see Setting Up the DBA Planning Calendar. 4. you have planned the action Central Calendar Log Collector to run regularly. n In the DBA Planning Calendar of the DBA Cockpit where you call the Central Calendar.6.6 The DBA Cockpit Managing the System Landscape Note Connection data that is retrieved from the SLD might not be complete for one of the following reasons: n Depending on the data provided by a system to the SLD. The Central Calendar is displayed. some connection data can be incomplete. you see entries by day. 08 (for example) affecting two systems. This means that you are prompted for user. For more information. When you establish the connection to an imported system for the first time. If additional connection information is required. one for each system.4 4. in which case the entry for FUD is displayed with a yellow background. 4. double-click the day header. To refresh the display for the system from which you called the Central Calendar. You can perform all usual functions in the DBA Planning Calendar. You can remotely refresh the display as follows: 12/18/2012 PUBLIC 47/116 . This means that two actions ended with a warning. one of which ended with the highest severity. double-click the entry for the system on the required day. there were three actions planned. which you can also see by choosing Legend: Color Status Light blue Planned Dark blue Running Green Finished successfully Yellow Finished with warning Red Finished with error Dark yellow No longer available Dark red Scheduling failed 2. To see the individual actions for a system. the highest severity for FIB might be "Finished with error". as in the following example: Example: System Total No longer available FUD 3 1 FIB 4 Scheduled Running Finished Warning Error Overdue 2 3 1 3. You see the relevant day in the DBA Planning Calendar. The system displays a summary of the actions and status for each system on the day you selected. To refresh the display for all systems. two of which had the highest status severity. For example. The following table shows the color-coded statuses in the Central Calendar. For example. This means that one action ended with an error. 5. in which case the entry for FIB is displayed with a red background. choose Refresh.6 The DBA Cockpit Managing the System Landscape Note On system FUD for Thursday 8th January. the highest status severity for FUD might be "Finished with warning".4 4. On system FIB for the same day. To see a summary of the actions for a day. choose Remote Refresh. there were four actions planned. 7. This in no way restricts the planning of actions in the DBA Planning Calendar. If required. or month view by choosing Administration View Day . which can take a long time. c) Choose Save Settings and change Number of Weeks or Entries per Day in the display.7 Performance The following sections provide information about the main task areas that are available under Performance on the Database tab page of the DBA Cockpit.1 Performance: ASE Server You can access information about system threads by calling the DBA Cockpit and choosing Performance ASE Server on the Database tab page of the DBA Cockpit. Holidays are displayed in the same background color as weekend days. so not recommended Start immediately Runs immediately in the background as a job Schedule at Runs in the background at the time that you specify Recommendation We recommend that you schedule action Central Calendar Log Collector to run regularly. 48/116 PUBLIC 12/18/2012 .4 4. Administration View Week .7 The DBA Cockpit Performance Method How the Refresh Runs Run in Dialog Runs in dialog mode. n n n n n n n n n n ASE Server Threads Processes System Waits System Load Temporary Database Activity Data Cache Usage Tables Procedure Cache Usage SQL Statements 4. week. 6. b) Switch to day. 4. you can customize the calendar display as follows: a) Specify a factory calendar in Calendar ID. or Administration View Month . as described above in "Prerequisites". see Data Collection Framework: Collector Configuration [page 66]. see Data Collection Framework: Collector Configuration [page 66]. If the DCF is not available or set up incorrectly. Note To monitor data on the Threads screen.2 Performance: Threads You can access information about system threads by calling the DBA Cockpit and choosing Performance Threads on the Database tab page of the DBA Cockpit. For more information. and process 12/18/2012 PUBLIC 49/116 . There you can perform the required steps. a warning is displayed with a link to the Collector Configuration screen. run specific jobs. a warning is displayed with a link to the Collector Configuration screen.7. Threads host engines that execute user tasks. and contain threads used to execute Sybase ASE tasks associated with that thread pool. If the DCF is not available or set up incorrectly.4 4. In the Selection area. For more information. you have to make sure that the data collection framework (DCF) is set up correctly. There you can perform the required steps. you have to make sure that the data collection framework (DCF) is set up correctly. you can specify the time frame for which you want the performance overview to be displayed. Figure 8: ASE Server Overview 4. Thread pools group CPU resources.7 The DBA Cockpit Performance Note To monitor data on the ASE Server screen. Sybase ASE includes the folowing system-defined thread pools: Thread pool: Description: syb_default_pool The default engine thread pool. if present. Adaptive Server contains system-defined thread pools and. which are normally operating system calls that may cause a multiplexed ‒ or engine ‒ thread to block for an unacceptable amount of time. syb_system_pool contains at least one thread for the system clock and other asynchronous signals. the following information is displayed: Column: Description: Thread Pool Name Only system thread pools can start with the syb_ prefix. Thread pools are available only when Sybase ASE is configured for threaded mode. you can specify the time frame for which you want system threads to be displayed. Task: Runs Threads are used to execute Adaptive Server tasks associated with the thread pools. syb_blocking_pool Syb_blocking_pool is used to process blocking call requests from multiplexed tasks. However.4 4. To review the performance of aggregated threads. Threads in syb_blocking_pool typically consume very few CPU resources. you can review the threads that occurred in the given time frame and that were captured by the related data collector. Each thread in syb_default_pool is an engine. For each system thread.7 The DBA Cockpit Performance requests from a work queue. Idle Percentage share of idle time Sleep Amount of time (in %) that the thread has waited for an event Busy Amount of time (in %) that the thread has run User Time (ms) Thread user CPU time in milliseconds System Time (ms) Thread system CPU time in milliseconds 50/116 PUBLIC 12/18/2012 . choose Group Threads by Pool Name. All I/O handling threads run in syb_system_pool. you can move some tasks out of syb_default_pool by creating additional thread pools. user-created thread pools. All user tasks and all multiplexed system tasks (such as the housekeeper) run in syb_default_pool. After having applied your selection. The number shows how often these tasks have been executed. syb_system_pool Each thread in syb_system_pool is a system thread and is dedicated to run a specific task. In the Selection area. To analyze performance data for database processes.4 4. The detail data is displayed in the Details area below the overview table.sybase. You specify the task type. the server process ID of a process that is blocking this one (if any).3 Performance: Processes You can access information about database processes by calling the DBA Cockpit and choosing Performance Processes on the Database tab page of the DBA Cockpit. 3.7 The DBA Cockpit Performance To display detailed information. The Summary tab contains general information. In Process. 2. You can analyze Internal Applications (database internal processes) or External Applications (work processes of the SAP application server.com/help/index.sybase. Completed or Closed CPU CPU Sample Engine Number Unique identifier of the engine that the process is executing on Priority Priority at which the process is executing Bocking SPID Server process identifier of the process holding the lock that this process has requested. the name of the host. for example). if waiting for a lock 12/18/2012 PUBLIC 51/116 . The Details tab provides an overview on an hourly. You identify the task type of the processes. the real login name. The following information is displayed for each process: Column: Description: SPID Server Process Identifier Statement Runtime Statement Runtime in seconds Transaction Runtime (sec) Transaction Runitme in seconds Transaction State The following statuses are displayed: Open. the description of the thread and the recommended action.7. the name of the database. the login name of the process user. The Chart tab shows the details of the thread analysis in a graphical representation. and the command being run are displayed. you choose the Apply Selection pushbutton. For each process the processing time. daily or weekly basis.infocenter. you proceed as follows: 1.htm 4. To refresh the monitoring data.dc31644.1570/html/sag2/BABCAJGF. CPU usage.jsp?topic= /com. you select the appropriate entry that you want to analyze in the overview table. More Information http://infocenter. 7. Note To monitor data on the System Waits screen. n Review system wait events that are currently occurring on the database server. the following information is displayed: 52/116 PUBLIC 12/18/2012 .7 The DBA Cockpit Performance Column: Description: Application Application name SAP Proc. a warning is displayed with a link to the Collector Configuration screen. If the DCF is not available or set up incorrectly. the client metadata and the transaction. Use EXPLAIN to analyze the EXPLAIN access plan. The detail data is displayed in the Process Details area below the overview table.4 Performance: System Waits You can access information about system wait events by calling the DBA Cockpit and choosing Performance System Waits on the Database tab page of the DBA Cockpit. Type / Transaction Code Process type of SAP transaction SAP Program Name of the SAP program Host Name Client host name Client OSPID OS process identifier of the client application Login Login user name 4. After having applied your selection. For more information. you select the appropriate entry that you want to analyze in the overview table. The Process tab shows information on the process metadata. you have to make sure that the data collection framework (DCF) is set up correctly. For more information. To display detailed information. refer to The EXPLAIN Access Plan [page 30]. For more information. you can specify the time frame for which you want system-wait events to be displayed. you can: n Review system wait events that occurred in the past and that were captured by the related data collector. Using the information provided on this screen. There you can perform the required steps. Choose the Statement tab for further details on the SQL statement. see Data Collection Framework: Collector Configuration [page 66]. see Data Collection Framework: Collector Configuration [page 66]. the total number of system-wait events that occurred and that you selected is displayed. For each system-wait event.4 4. 4. In the Selection area. To analyze the system load. 4. The Details tab provides an hourly overview for the wait event.4 4.7. You can change the granularity of the time frame. the description of the system wait and the recommended action.5 Performance: System Load You can access information about system load statistics by calling the DBA Cockpit and choosing Performance System Load on the Database tab page of the DBA Cockpit. you proceed as follows: 1. waiting for a disk read to complete). To refresh the monitoring data. The detail data is displayed in the Details area below the overview table.7 The DBA Cockpit Performance Column: Description: Wait Event Description of the wait event Wait Class Provides a textual description for all of the wait classes (for example. You specify one particular or all engines 3. 2. You identify the Time Frame. All wait events have been grouped into wait classes that classify the type of event that a process is waiting for Typical Cause Further explanation on the probable cause of the wait event Wait time (sec) Amount of time (in milliseconds) that the process has waited for the event Waits Avg Number of times the process has waited for the event Wait Time Average amount of time (in milliseconds) that the process has waited for the event compared to similar system-wait events To display detailed information. you select the appropriate entry that you want to analyze in the overview table. The Summary tab shows general information. The following statistics are displayed for each engine: n percent user busy n percent system busy n percent i/o busy n run queue length n kernel run queue length n outstanding disk I/Os n disk reads per second n disk writes per second n network reads per second 12/18/2012 PUBLIC 53/116 . you choose the Apply Selection push button. To display detailed information. If the DCF is not available or set up incorrectly. The Summary 54/116 PUBLIC 12/18/2012 . Note To monitor data on the Temporary Database Activity screen. see Data Collection Framework: Collector Configuration [page 66]. a warning is displayed including a link to the Collector Configuration screen where you can perform the required steps. The detail data is displayed in the Details area below the overview table. you select the appropriate entry that you want to analyze in the overview table.4 4. DB Size (KB) Temporary database size Unreserved Space (KB) Unreserved space in temporary database Reserved Space (KB) Reserved space in temporary database Max. n Review temporary database activities that are currently occurring on the database server. Using the information provided on this screen.7. you select the appropriate entry that you want to analyze in the overview table. daily. Column: Description: Temp. In the Selection area. For more information. Reserved Space (KB) Maximal size of reserved space Logical Reads Total number of buffer reads Physical Reads Number of buffer reads from disk Physical Waits Total number of buffers written to disk Pages Read (Pages) Total number of pages read Pages Written (Pages) Total number of pages written to disk To display detailed information. weekly or monthly basis. The Summary tab shows details on the chosen statistic. you have to make sure that the data collection framework (DCF) is set up correctly. 4.7 The DBA Cockpit Performance n network writes per second 4. You can analyze the statistic on an hourly. you can: n Review temporary database activity that occurred in the past and that were captured by the related data collector.6 Performance: Temporary Database Activity You can access information about temporary database performance by calling the DBA Cockpit and choosing Performance Temporary Database Activity on the Database tab page of the DBA Cockpit. The detail data is displayed in the Details area below the overview table. Choose the Details tab for further information. you can specify the time frame for which you want database activities to be displayed. The following information is displayed for each database: Column: Description: Cache ID Unique identifier for the cache Cache Name Name of the cache I/O Buffer Size (KB) Size of the I/O buffer for the cachepool Physical Reads The number of buffers that have been read from disk into the pool Stalls Number of ’dirty’ buffer retrievals Pages Touched (Pages) Number of pages used within the pool Pages Read The number of buffers that were fetched Buffers to MRU The number of buffers that were fetched and replaced at the Most Recently Used (MRU) portion of the pool Buffers to LRU The number of buffers that were fetched and replaced at the Last Recently Used (LRU) portion of the pool: fetch-and-discard 12/18/2012 PUBLIC 55/116 . After having applied your selection.7 Performance: Data Cache Usage You can access information about data cache’s usage by calling the DBA Cockpit and choosing Performance Data Cache Usage on the Database tab page of the DBA Cockpit. TheDetails tab provides an overview for the database activities according to the time frame you have chosen.7. If the DCF is not available or wrongly set up. the data cache usage is displayed. n Review the data cache usage that is currently occurring on the database server In the Selection area. you can: n Review data cache usage that occurred in the past and that were captured by the data collector. you have to make sure that the data collector framework (DCF) is set up correctly. see Data Collection Framework: Collector Configuration [page 66]. Using the information provided on this screen. you can specify the time frame for which you want the data cache usage to be displayed. 4. a warning is displayed including a link to the Collector Configuration screen where you can perform the required steps.4 4. For more information. Note To monitor data on the Data Cache Usage screen.7 The DBA Cockpit Performance tab shows general information on the database and additional metrics. 4. The Tables screen provides information that you can use to analyze tables under the following aspects: n Which tables are accessed the most and require extra tuning? n Which tables have frequent update operations and are. you can specify the time frame and other criteria for which you want the tables to be displayed. See the Sybase System Administration Guide (Section Caches in Adaptive Server) for more information on the usage of caches in Adaptive Server. therefore. The Summary tab shows general information on the data cache usage. The Details tab provides an overview for the data cache usage according to the time frame you have chosen.7 The DBA Cockpit Performance To display detailed information. you select the appropriate entry that you want to analyze in the overview table. you proceed as follows: 56/116 PUBLIC 12/18/2012 .7.8 Performance: Tables The Tables screen displays information on all tables of the database. You can access the Tables screen by calling the DBA Cockpit and choosing Performance Tables in the navigation frame of the DBA Cockpit.4 4. such as the number of rows read. The detail data is displayed in the details area below the overview table. the number of rows written and so on. In the Selection area. potential candidates for new statistics? n Which tables are candidates for reorganization due to space fragmentation? Figure 9: Performance: Tables To analyze table data. 4 4.7 The DBA Cockpit Performance 1. You identify the time period where you experienced performance problems for example, long running batch jobs, threshold violations detected by workload management, and bad user response time. 2. In the Selection area, you specify the appropriate time frame. 3. You restrict the result set in the overview table, for example, by limiting the maximum number of rows, by using wildcards. 4. To refresh table data, you choose the Apply pushbutton. The following information is displayed: Column: Description: Logical Reads Total number of buffers read Physical Reads Number of physical read operations Physical Writes Number of buffers read from disk Hit Ratio Hit Ratio in % Operations Number of times that the object was accessed Rows Inserted Number of rows inserted Rows Updated Number of updates Rows Deleted Number of rows deleted Lock Waits Number of times a task waited for a lock for the object Last Used Date Last date the index was used in plan during execution 5. To display data, you select a line in the overview table. The data is displayed in the Details content area. 6. To isloate the time frame during which the performance problem occurred, you use the data in the Details tab. 4.7.9 Performance: Procedure Cache Usage You can access information about the usage of the procedure cache by calling the DBA Cockpit and choosing Performance Procedure Cache Usage on the Database tab page of the DBA Cockpit. Note To monitor data on the Procedure Cache Usage screen, you have to make sure that the data collection framework (DCF) is set up correctly. If the DCF is not available or set up incorrectly, a warning is displayed including a link to the Collector Configuration screen where you can perform the required steps. For more information, see Data Collection Framework: Collector Configuration [page 66].. 12/18/2012 PUBLIC 57/116 4 4.7 The DBA Cockpit Performance To analyze procedure cache data, you proceed as follows: 1. You identify the time period where you experienced performance problems. 2. To refresh table data, you choose the Apply Selection pushbutton The following information is displayed: Column: Description: Module ID A unique ID of a procedure cache allocating module Module Name Name of the procedure cache allocating module Active (Pages) Number of memory pages allocated at the moment for the module Change Active Change in the number of memory pages allocated for the module HWM High Water Mark: Maximum number of pages allocated Num Pages Reused Number of procedure cache pages for this module replaced by another request 3. To display data, you select a line in the overview table. The data is displayed in the Details content area. 4. To isloate the time frame during which the performance problem occurred, you use the data in the Details tab. 4.7.10 Performance: SQL Statements You can access information about the SQL statements by calling the DBA Cockpit and choosing Performance SQL Statements on the Database tab page of the DBA Cockpit. Statement Cache You can access information about the SQL statement cache by choosing Performance SQL Statements Statement Cache on the Database tab page of the DBA Cockpit. This function provides monitoring capability for all prepared SQL statements that reside in the global SQL statement cache. The information about the cached statements is gathered during their preparation and execution. Statistics information for cached statements is invaluable for performance tuning on the level of individual SQL statements. Filtering The global SQL statement cache of an SAP system may contain thousands of entries. By selecting a criteria from the Top SQL Statements by drop down list box, only the most expensive entries for that criteria are displayed. By default, the output is limited to the top 100 entries, but can be changed easily. The Custom filter allows you to do a more specific filtering based on multiple threshold values as well as a text filter on the SQL statement text (a table name, for example). 58/116 PUBLIC 12/18/2012 4 4.8 The DBA Cockpit Space The Adaptive Server will return information about all statements that exceed the given value for the selected statistics field. Choose Apply Selection to refresh the display. SQL Statement Details and Explain Function The records displayed provide identifying information, statistics, and part of the SQL statement text. Due to the potential size of the SQL statement text, only the first 150 characters are shown. If you want to see the entire statement text as well as detailed execution statistics for a particular statement, select the respective entry in the table. SQL Statement Details are shown in the lower part of the screen. Statement Text Displays the full SQL statement text in a formatted fashion (including any attached comments or optimization hints). In case the SQL statement text is tagged with source code information by the application that has prepared the SQL statement, you can jump into the source code by choosing Show Source. Statement Metrics Provides detailed information on the statement and its execution statistics. A quick info is displayed when you move the cursor over a field, explaining the purpose of the field. Cached Query Plans Overview of query plans. As ASE uses non sharable access plans, multiple identical or varying access plans may exist for a single SQL statement. Do display detailed information for an access plan, select a plan from the list and choose Show Plan. For more information, see EXPLAIN in section The EXPLAIN Access Plan [page 30] Statement Cache Usage You can access information about the usage of the procedure cache by calling the DBA Cockpit and choosing Performance SQL Statements Statement Cache Usage on theDatabase tab page of the DBA Cockpit. In the Selection area, you can specify the time frame for which you want the statement cache usage to be displayed. The Summary tab shows general information on the statement cache and additional metrics. The Details tab provides an overview for the statement cache activities according to the time frame you have chosen. 4.8 Space The following sections provide information about the main task areas that are available under Space on the Database tab page of the DBA Cockpit: 12/18/2012 PUBLIC 59/116 Column: Description: Device Number Device identification number Name Name of device Name of device Physical Device Name Device Size Size of device in MB Device Size Used Size of all fragments on this device in MB Creation Date Date and time of creation Resize Date Date and time of resize Direct I/O enabled Yes/No Using dsync Device uses dsync setting (writes occur directly to physical media) Skip Header Yes/No To display detailed information. Choose the device for which you want information on available space to be displayed. 60/116 PUBLIC 12/18/2012 . The detail data is displayed in the Device Details area below the overview table: n The Device tab shows general information on the device and additional metrics. you can specify the Device Status.8.1 Space: Devices You can access information about database devices by calling the DBA Cockpit and choosing Space Devices on the Database tab page of the DBA Cockpit. refer to Overview of Disk Resource Issues and Creating and Using Segments in the Sybase System Administration Guide. you choose the Apply Selection pushbutton. In the Selection area. For Adaptive Server. while segments provide a logical map of database objects to devices. devices provide a logical map of a database to physical storage. you select the appropriate entry that you want to analyze in the overview table. it is important that you understand the interplay between these logical layers. A database can occupy all available space on the device. or other databases can share space on the device. Segments (logical groupings of storage within a database) allow you to keep some data logically or physically separate from other data. To achieve your space allocation goals.8 The DBA Cockpit Space n Devices n Databases n Tables and Indexes 4. The term “device” does not only refer to a distinct physical device: it can refer to any piece of a disk (such as a disk partition) or a file in the file system that is used to store databases and their objects. or any combination of the two. To refresh the monitoring data. For more information.4 4. The Database screen provides information on the Database Size. Monitoring the space that is consumed by the database does not only require that you check the current space consumption but also that you consider the progress of the space growth to answer questions such as the following: n Is data continuously growing and is it predictable that the database runs out of space? n Did archiving operations or reorganizations successfully reduce the space consumption? n Can I identify any short-term growth that is related to specific activities of an application. n The Segments tab shows information about the used segments.2 Space: Databases You can access information about all databases of a Sybase ASE database server by calling the DBA Cockpit and choosing Space Databases on the Database tab page of the DBA Cockpit. n Shows all databases that use this device. For disk-based databases. For information on the Databases tab.8 The DBA Cockpit Space n The Fragments tab provides an overview on “disk pieces”. Adaptive Server creates and uses three of these segments: l system segment‒ contains most system catalogs l default segment ‒ used if no segment is specified. the Durability Level the Unseparated Log (database has some portion of the log that is not on a log-only device). but is re-created from the model or template database. Each database can have up to 32 named segments. This segment is used by SAP to store the data l logsegment ‒ stores the transaction log. such as client copy. but in an uncontrolled manner. refer to Space: Databases [page 61]. the size of pages that are not part of an allocated extent. You can store user tables in the system segment. and ensures full recovery from a server failure. The Durability Level can have one of the following values: n full ‒ all transactions are written to disk.4 4. Adaptive Server periodically writes data at runtime to the disk devices. but the logsegment is reserved entirely for the log. This is the default if you do not specify a durability level when you create the database. n no_recovery ‒ transactions are not durable to disk and all changes are lost if the server fails or is shut down. After any shutdown (polite. Fragments permit storage for the same group of segments. for example. 12/18/2012 PUBLIC 61/116 . All system databases use this durability level (the traditional durability level for disk-resident databases). Fragments are a group of logical pages on the same device. 4. and the Durability Level. Note It is of high importance that the <SID>database of an SAP installation has this durability level. or server failure and restart) a database created with no_recovery is not recovered. impolite.8. you can specify the time frame and other criteria for which you want the tables to be displayed. you select the appropriate entry that you want to analyze in the overview table. In the Selection area. 2. The detail data is displayed in the Database Details area below the overview table. forwarded. To refresh table data. the number of rows. Adaptive Server creates and uses three of these segments: n system segment‒ contains most system catalogs n default segment ‒ used if you do not specify one when creating an object. The Segments tab shows information about the used segments. Fragments permit storage for the same group of segments. Each database can have up to 32 named segments.4 4.8 The DBA Cockpit Space n at_shutdown ‒ transactions are durable while the server is running and after a polite shutdown. The Tables screen displays information on all tables of the database. you proceed as follows: 1.3 Space: Tables and Indexes You can access the Tables screen by calling the DBA Cockpit and choosing Space Tables in the navigation frame of the DBA Cockpit. Fragments are a group of logical pages on the same device. To analyze table data. The Database and Device tab shows general information and additional metrics. and so on. The Fragments tab provides an overview on “disk pieces”. The following information is displayed: Column: Description: Database Name of the database Table Owner Name of the table owner Table Name Name of the table Reserved Total (KB) Space reserved for future inserts Used Total Total amount of space used in KB Unused Total Total amount of unused space in KB Data Total (KB) Amount of data for this table in KB Data Utilized Total Amount of utilized data for this table in KB Number of Rows Table rows 62/116 PUBLIC 12/18/2012 . All durability is lost if the server fails.8. such as the used. the number of rows deleted. unused or reserved space. You specify the time frame and other criteria for which you want the tables to be displayed. you choose the Apply Selection push button. To display detailed information. This segment is used by SAP to store all data n logsegment ‒ stores the transaction log 4. 4 4.9 The DBA Cockpit Configuration Column: Description: Data Change Percentage of data change since the last statistics update was performed on the object Data Cluster Ratio Data cluster ratio in % Large IO Efficiency Information about I/O efficiency Deleted Rows Number of data records that were deleted Forwarded Rows Rows that grow in length with subsequent updates To display further details of the selected table, you select a line in the overview table and choose Table Details. By analyzing and maintaining single tables, you can optimize tables and indexes to: n Save disk space by releasing unused space n Improve access to a table by keeping statistics up-to-date or by reorganizing fragmented tables or indexes The Single Table Analysis screen consists of the following areas: n A selection area, where you specify the schema and name of the table to be analyzed n Tab pages with detail information that is relevant for tables and indexes 4.9 Configuration The following sections provide information about the main task areas that are available under Configuration on the Database tab page of the DBA Cockpit: n n n n Server Configuration Data Caches ATM Configuration Data Collection Framework 4.9.1 Configuration: Server Configuration You can access information about the configuration of a Sybase ASE database server by calling the DBA Cockpit and choosing Configuration Server Configuration on the Database tab page of the DBA Cockpit. The tab page displays all groups, their associated parameters, and the current values for the parameters. Configuration parameters are user-definable settings that control various aspects of Adaptive Server’s behavior. Adaptive Server supplies default values for all configuration parameters. You can use configuration parameters to tailor Adaptive Server for an installation’s particular needs. 12/18/2012 PUBLIC 63/116 4 4.9 The DBA Cockpit Configuration Configuration parameters are used for a wide range of services, from basic to specific server operations, and for performance tuning. Note Change configuration parameters with caution. Arbitrary changes in parameter values can adversely affect Adaptive Server performance and other aspects of server operation. Configuration parameters are grouped according to the area of Adaptive Server behavior they affect. This makes it easier to identify all parameters that you might need to tune to improve a particular area of Adaptive Server performance. Note For more information, see chapter The parameter hierarchy in the Sybase Administration Manual. Parameter values are displayed in the following columns: Parameter Value: Description: Run Value The value Adaptive Server is currently using. It changes when you modify a dynamic parameter’s value and, for static parameters, after you restart Adaptive Server. Config Value Most recent value to which the configuration parameter has been set. When you modify a dynamic parameter: n The configuration and run values are updated. n The configuration file is updated. n The change takes effect immediately. When you modify a static parameter: n The configuration value is updated. n The configuration file is updated. n The change takes effect only when you restart Adaptive Server. Default Value The value Adaptive Server is shipped with. If you do not explicitly reconfigure a parameter, it retains its default value. Memory Used The amount of memory used (in kilobytes) by the parameter at its current value. Some related parameters draw from the same memory pool. For instance, the memory used for stack size and stack guard size is already accounted for in the memory used for number of user connections. If you added the memory used by each of these parameters separately, it would total more than the amount actually used. In the Memory Used column, parameters that “share” memory with other parameters are marked with a hash mark (“#”). 64/116 PUBLIC 12/18/2012 4 4.9 The DBA Cockpit Configuration Parameter Value: Description: Unit The unit value in which the configuration parameter is displayed. Type Displays whether the configuration option is static or dynamic. Changes to static parameters require that you restart Adaptive Server for the changes to take effect. Changes to dynamic parameters take effect immediately without having to restart Adaptive Server. Parameters of type read-only are not changeable. How to Modify Configuration Parameters Set or change configuration parameters in the following way: 1. Select the parameter. 2. Choose Change. 3. Enter the new value in the Change Configuration Parameter quick activity. The value range indicates the range of allowed values. To get help information on configuration parameters, select the parameter and read the configuration parameter details in the lower part of the screen. For more information, see the chapter Configuration Parameters in the Sybase System Administration Manual and the Sybase Performance and Tuning Guide. 4.9.2 Configuration: Data Caches You can access information about the configuration of data caches and cache pools by calling the DBA Cockpit and choosing Configuration Data Caches on the Database tab page of the DBA Cockpit. For more information on data cache configuration, refer to the Sybase Administration Manual, chapter Configuring Data Caches. 4.9.3 Configuration: Data Collection Framework The section Data Collection Framework: Collector Configuration [page 66] provides information about how to use the data collection framework (DCF) to collect history data of the monitored databases. Note The DCF is based on pre-defined templates. For information about these templates, see Data Collection Framework: Template Definition [page 68]. 12/18/2012 PUBLIC 65/116 You can access information about the history data collectors by calling the DBA Cockpit and choosing Configuration Data Collection Framework Collector Configuration on the Database tab page of the DBA Cockpit. This means that the installed data collection framework is checked once daily. We recommend that you repair the data collector. the name refers to the data that is collected ‒ for example. the automatic back-end update function is enabled.9.4 4. In the content area. the following information is displayed: Column Description Data Collector Name of the data collector Typically. but a cleanup job for the messages generated by the above mentioned data collector types. status messages are displayed that provide information such as the following: n Wether back-end automatic update is enabled or disabled By default. the Sybase ASE Job Scheduler is used to execute the stored procedures regularly. n Yellow: The data collector is not set up properly.9 The DBA Cockpit Configuration 4. n Cleanup of Message Logs (STP) The Framework data collector is not a typical data collector type.4 Data Collection Framework: Collector Configuration The Collector Configuration screen provides an overview of the state of the installed history data collectors. these updates are performed automatically. 66/116 PUBLIC 12/18/2012 . you can set up the data collection framework (DCF) using templates as described in Setting Up the Data Collection Framework Manually. You can use this screen to change the configuration of specific data collectors. n Which task scheduler is used By default. If it needs to be updated due to SAP code changes or database changes. In the central system data area of the Collector Configuration screen. the data collector Tables stores table-related metrics in the history tables. Type Type of data collector The following collector types are possible: n SAP Data Collection and Preparation (STP) These data collectors have their own mechanism to calculate the delta of the different snapshots. Setup Indicates the setup status The following values are possible: n Green: The data collector is set up as intended. Furthermore. Note You must set up the Framework collector before all other data collectors. Depending on your setup status. Set up the data collector according to the assigned template. starting now Days Kept in History Number of days the sliding history window contains the data The data in the history is deleted after this set time.4 4. change. the Configuration and Data Collector Log tab pages appear with the relevant data collector details displayed. In the content detail area of the Collector Configuration screen. Collection Interval Schedule of the data collector Available Days Availability of the collected data for a given number of days. you can proceed with the following maintenance actions: Action Setup Status Steps to Be Performed Setting up a single history data collector Grey or red as the data collector is not set up yet On the Configuration tab page. to be repaired PUBLIC 67/116 . Repairing a single history data collector 12/18/2012 Yellow as the data collector is set On the Configuration tab page. n Grey: The data collector is not set up and the assigned template also flags this data collector to be deactivated. or analyze them. choose the Set Up pushbutton. choose up but should be updated or needs the Repair pushbutton. or to remove data from them ‒ choose a data collector from the list. to set them up. Size on Disk (MB) Space consumption in the local history of the data that is stored by the data collector Errors Number of errors that the data collector has captured and the scheduler has recorded Warnings Number of warnings that the data collector has captured and the scheduler has recorded Maintaining History Data Collectors To maintain data collectors ‒ for example.9 The DBA Cockpit Configuration n Red: The data collector is not set up. the templates are available for use but cannot be maintained. To apply your changes. you can perform the following actions: n n n n Create new templates Change single history data collectors in a template Set a default template Delete a template Note In the SAP Solution Manager setup wizard for managed systems for the database. the collected data and the generated messages of the data collector are removed.9 The DBA Cockpit Configuration Action Setup Status Steps to Be Performed Changing a single history data collector Green 1. Dropping a single history data collector Yellow or green On the Configuration tab page.5 Data Collection Framework: Template Definition The data collection framework is based on pre-defined templates. 2. By doing so. You can only maintain these templates on the Template Definition screen in the DBA Cockpit. Analyzing a single history data collector Yellow or green On the Data Collector Log tab page. On the Template Definition screen. you can choose between the following pushbuttons: n Show Error Messages n Show Warnings n Show Information Messages 4. Removing data of a single history data collector Yellow or green On the Configuration tab page. choose the Prune pushbutton. You can access the Template Definition screen by calling the DBA Cockpit and choosing Configuration Data Collection Framework Template Definition on the Database tab page of the DBA Cockpit. 68/116 PUBLIC 12/18/2012 . choose the Reset Changes pushbutton. choose the Apply Changes pushbutton. These templates ensure a homogeneous setup of the history data collectors in your system landscape. If you want to discard your changes. choose the Drop pushbutton. choose the Change Settings pushbutton and enter your changes.4 4.9. On the Configuration tab page. Release (min) Minimum database release required for the history data collector Release (max) Maximum database release supported by the history data collector Setup Indicates the setup status: n Green: The history data collector is set up as intended. the name refers to the data that is collected. n Red: The history data collector is not set up. for example. Creating a New Data Collector Template You can create a new data collector template either by copying an existing template or by generating a template that is based on the configuration of an individual system as follows: n Copying an existing template: 12/18/2012 PUBLIC 69/116 . Collection Interval Schedule of the history data collector Days Kept in History Number of days of the sliding history window The data in the history is deleted after this number of days. Type The following data collector types are available: n SAP Data Collection and Preparation (STP) These history data collectors have their own mechanism for delta calculation of the different snapshots. n Cleanup of Message Logs (STP) The Framework data collector is not a typical data collector type. the data collector Tables stores table-related metrics in the history tables. but a cleanup job for the messages generated by the above mentioned data collector types.4 4. n Yellow: The history data collector is not set up properly. The following information is displayed: Column Description Data Collector Name of the history data collector Typically. choose the appropriate template for your setup.9 The DBA Cockpit Configuration From the Template dropdown list. Set up the history data collector according to the assigned template. We recommend that you repair it. n Grey: The history data collector is not set up and the assigned template also marks this data collector to be deactivated. choose the Reset Changes pushbutton. you can create a custom template based on the SAP template and change this newly created template. 2. In the Save As New Template dialog box. On the Configuration tab page in the content detail area. In the content detail area. n Creating a template based on a system configuration: 1. choose the Save as New Template pushbutton. 4. To change a default template. Save the template. On the Template Definition screen. Changing a Single History Data Collector in a Template The Setup status of the history data collector must be green. On the Collector Configuration screen. 3. choose a template from the Template dropdown list and choose the Save As New Template pushbutton. enter your changes in the respective fields. This means that every new template must determine a finer granularity or a longer retention time for the history data than the SAP Default template does. enter a unique name and a description of the new template. 3. Instead. Note If you want to discard your changes. 4. 1. choose Configuration Data Collection Framework Collector Configuration . Note The Save As New Template pushbutton is only enabled if the respective system configuration fulfills the minimum template requirements of SAP that are defined by the SAP Default template. choose the Change Settings pushbutton. Apply your changes. Enter a unique name and a description of the new template. Note You cannot change an SAP template. On the Database tab page of the DBA Cockpit. Choose a non-SAP template from the Template dropdown list. Setting a Default Template The default template is preselected in the template-based setup and in the SAP Solution Manager setup wizard for managed systems.4 4.9 The DBA Cockpit Configuration 1. The Save As New Template dialog box appears. Save the template. 2. 2. 3. choose a template from the Template dropdown list and choose the Set As Default pushbutton. 70/116 PUBLIC 12/18/2012 . you have to make sure in advance that the necessary resources are available.10 Jobs Note The current default template is marked with an asterisk (*). If there are entries in the list.1 Jobs: DBA Planning Calendar You use the DBA Planning Calendar to automate database administration actions that have to be performed regularly. the Set As Default pushbutton is disabled.10 Jobs The following sections provide information about the main task areas that are available under Jobs on the Database tab page of the DBA Cockpit. The main function of the DBA Planning Calendar is to define the start times and parameters for database actions. A list of all systems is displayed that are assigned to this template. You can schedule operations such as online backups which are then automatically performed.10. 4. If the default template is currently selected. If you want to delete the current default template.4 The DBA Cockpit 4. the default template is assigned to these systems before the template is deleted. Deleting a Template You can delete a template by choosing it from the Template dropdown list and choosing the Delete pushbutton. n DBA Planning Calendar n DBA Log 4. Integration The DBA Planning Calendar is part of the DBA Cockpit. You can start the DBA Planning Calendar by calling the DBA Cockpit and choosing Jobs DBA Planning Calendar on the Database tab page of the DBA Cockpit. you first have to unmark it as the default by setting a different template as the new default. Since these actions run without administrator interaction. Note You cannot delete SAP templates or the current default template. and you can check whether the operations were successful. 12/18/2012 PUBLIC 71/116 . regardless of how they have been scheduled. ‒ Yellow Finished with warning The action has finished with Check the job log for details. n Select a factory calendar Specifying a factory calendar only has an impact on the calendar display. The Selection Area The Selection area contains all information and parameters required for selecting the set of actions to be displayed. on performance or history.10 Jobs Features The initial screen of the DBA Planning Calendar consists of a Selection area and the calendar. ‒ Dark blue Running The action has not yet finished. To navigate to another week. l All Actions These are all plannable actions. l DB Collectors These are actions that are automatically selected by the system to collect data. In the following. ‒ Green Finished successfully The action has run successfully. choose the Legend pushbutton. The Calendar The calendar displays all scheduled jobs. both are described in more detail. The following information is displayed: Color Status Description Action Light blue Planned The action has not yet started. Red Finished with error An error has occurred and the action was interrupted. use the F4 help. and they are only available for RFC-monitored systems. Holidays are the same color as weekend days. l External Actions These are plannable actions that have not been started through the DBA Planning Calendar but have been started manually or by external job schedulers.4 The DBA Cockpit 4. 72/116 PUBLIC Check the job log for details and reschedule the action. This does not result in any restrictions on planned actions. a warning. To display the meaning of each color. n Select the week to be displayed The default is the current week. for example. The status of each job is indicated using different colors. You can: n Select the category of an action: l DBA Actions These are plannable actions. 12/18/2012 . To switch to editing mode. n Position the cursor on a calendar cell and choose the Add pushbutton. b) Specify one of the following options: Option: Description: Start Immediately The job starts immediately in the background after you have completed the required steps in the wizard. there is no status available and the action is overdue.10. that is. do the following: a) Choose the job that you want to schedule from the Action dropdown list. The Schedule an Action wizard appears.3 Scheduling an Action 1. you can do one of the following: n Click a calendar cell.10. To add new actions to the DBA Planning Calendar. ‒ Note By default.2 Setting Up and Working with the DBA Planning Calendar The following sections provide information about how you initially set up the DBA Planning Calendar and how you perform standard actions. In the Job Selection step. ‒ Dark red Scheduling failed Scheduling failed.10 Jobs Color Status Description Action Dark yellow No longer available No more information is available. n Choose Schedule an Action in your Favorites. 2. 4. such as: n n n n n n Scheduling an Action [page 73] Changing an Action [page 74] Deleting an Action [page 75] Executing an Action [page 76] Displaying Scheduled Actions [page 76] Troubleshooting [page 77] 4. the DBA Planning Calendar appears in display mode. 12/18/2012 PUBLIC 73/116 .4 The DBA Cockpit 4. choose the Change pushbutton in the global toolbar. and one the new action. 6. 4. The action is split into two actions. that is. Optional: If you previously selected the Start as Recurring Action option in the Job Selection step. Note If you want to change a recurring action. or hours Depending on the selected recurrence pattern. If you select Once only. the changes only affect recurrences of the action in the future. 4. Exit the Schedule an Action wizard. On the Summary screen. one describing the old action. Recurrence Range Range of time where the action recurs.10 Jobs Option: Description: Start on Specifies the date and time when the action is to start Start as Recurring Action Activates the Recurrence step where you can further specify a recurrence pattern for this job as described later on in this section 3. you need to specify the pattern in more detail. change. the action is executed only once. that is. The system does not check for conflicts between actions with identical start times but checks for actions within a range of approximately 30 minutes.4 The DBA Cockpit 4.10. 5. The following table describes the parameters to be specified in more detail: Parameter: Description: Recurrence Pattern Interval for the action in weeks. You must decide whether the actions might conflict in terms of database access or performance. but it does not prevent you from inserting the new action. 74/116 PUBLIC 12/18/2012 . for a specific time interval or for a limited number of occurrences Caution The system warns you if there is a conflict with an existing action. days. In the Parameter step. The action is repeated at the interval that you enter. or enter the basic parameters for the action.4 Changing an Action This section tells you how to change an action in the DBA Planning Calendar. the days of the week for weekly periods and the hours of the day for a daily period. you now have to enter a recurrence pattern in the Recurrence step. review the specified parameters and schedule the job by choosing the Execute pushbutton. 4. choose one of the following options: n If you want to delete the currently selected occurrence only. not already executed). click a calendar cell that contains an action. if available. Note If an action has already been executed. choose All Occurrences.10 Jobs Prerequisites The action to be changed must be in the state Planned (that is. From the Change menu button. you can only display it. Procedure 1. 2. if available. 2. the recurrence pattern. n If you want to delete all occurrences of a recurring job.5 Deleting an Action This section tells you how to delete an action from the DBA Planning Calendar. the recurrence pattern.10. If an action has already been executed. Procedure 1. choose one of the following options: n If you want to edit the currently selected occurrence only. The Action Description detail area appears displaying the action parameters and. if available. The Change Scheduled Action dialog box appears displaying the action parameters and.4 The DBA Cockpit 4. Apply and save your changes. choose Selected Occurrence. 12/18/2012 PUBLIC 75/116 . choose Selected Occurrence. In the DBA Planning Calendar. For more information. In the DBA Planning Calendar. 3. the recurrence patterns. click a calendar cell that contains the action to be deleted. it must be in the state Planned (that is. Prerequisites If you want to delete an action from the DBA Planning Calendar. you can only display it. see Displaying Scheduled Actions [page 76]. not already executed). n If you want to change all occurrences of a recurring job. choose All Occurrences. The Action Description detail area appears displaying the action parameters and. From the Delete menu button. 10 Jobs 4. The Action Description detail area of the action appears where you can check the action parameters.7 Displaying Scheduled Actions From the DBA Planning Calendar. If such a program log exists. Procedure To display a scheduled action. you can view all action-related information. for example. 4.4 The DBA Cockpit 4. The Action Description detail area appears displaying scheduling information or the return status of a finished action. it is displayed on this tab page. n Program Log Some actions write log files onto the database server. Choose the Re-Execute pushbutton.10. Result The action is rescheduled starting at the current time. 2. if any are available. To display long texts.6 Executing an Action You might have to reschedule an action. click a calendar cell that contains an action.10. Procedure 1. This includes: n Action parameters n Job logs if the action has already run These logs provide detailed information on the results of an action. after it has failed or if there is a resource bottleneck that needs immediate reaction. double-click a message. All messages that have been written by the background job are also displayed. 76/116 PUBLIC 12/18/2012 . n Recurrence patterns The status of an action is indicated by the color of the calendar cell where an action is inserted. Click the action that you want to re-execute. The following tab pages are displayed: n Action Parameters Displays the parameters of the action n Recurrence Displays the recurrence patterns and only appears if the action is part of a recurring action n Job Log The background processing job log generated by the action is displayed under Job Log. Note If you want to completely clean up your jobs. 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. Check the status of the job in the DBA Calendar. The status of a job is indicated by different colors. In a data warehouse scenario. If the job finished successfully. the calendar cell is marked green. This deletes all jobs. all scheduling data. for example. Procedure 1. When you access the DBA log for the first time. If the job terminated with a warning. and all related protocol records. 4.10. 4.11.8 Troubleshooting Since any action scheduled in the DBA Planning Calendar can fail. You can display information about previous weeks by using the F4 help of the From field in the Selection area.4 The DBA Cockpit 4. an error. consult the job log. the system displays the log information for the current week.11 Automatic Table Maintenance 4.9 Jobs: DBA Log The DBA log provides information about protocol records that are written by all database-related programs of the CCMS and database administration tools. We recommend that you clean up after an SAP system upgrade or if jobs have become corrupt. You can access the DBA log by calling the DBA Cockpit and choosing Jobs DBA Log on the Database tab page of the DBA Cockpit. 2.10. you must at least check the more critical actions such as database backups.1 The ATM Framework Sophisticated business applications like the SAP Business Suite execute millions of DML statements a day.11 Automatic Table Maintenance 4. choose the Cleanup pushbutton. This constant manipulation of data sets causes data 12/18/2012 PUBLIC 77/116 . The following steps describe how you check whether a job was executed correctly and how to proceed if it failed. It also resets the DBA Planning Calendar to its initial state. this framework dramatically reduces manual administrative activities and thus significantly reduces the TCO of the SAP on Sybase ASE solution. The job scheduler (JS) executes a stored procedure that is created and scheduled by the DBA Cockpit. This stored procedure evaluates maintenance requirements that are defined by ATM profiles. ATM history Objects that were maintained by ATM are dropped from the ATM queue.11 Automatic Table Maintenance fragmentation. the ATM history allows monitoring of past ATM activities.4 The DBA Cockpit 4. invalidates optimizer statistics. it also executes maintenance commands on identified objects. Terminology used in the context of Automatic Table Maintenance: Term: Description. in a second step. leaves non-reusable free space behind. but. ATM queue Objects that require maintenance are stored in the ATM queue. and. Job scheduler ATM makes use of the job scheduler that is built in to the Sybase ASE DBMS. finally. which is also used by the DBA Cockpit to store historical performance data and space information. Thus. as defined by ATM windows. ATM might not be able to maintain all identified objects before an ATM window expires. ATM profiles are assigned to ATM windows to control which objects are to be maintained in a certain time window and which are not. ATM will continue to process queued objects during the next ATM window. ATM window An ATM window defines a time frame within which ATM is allowed to evaluate and maintain objects. Considering the thousands of tables and indexes a typical SAP system creates on the database. The DBA Cockpit for Sybase ASE introduces a flexible framework that allows you to set up and control automatic table maintenance (in the following referred to as ATM) on Sybase ASE database systems. In this case. The DBA Cockpit acts as the central point to: n n n n Set up ATM on any remote Sybase ASE DBMS Configure ATM windows and ATM profiles 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. at the same time. which can end up in poor query performance. and. 78/116 PUBLIC 12/18/2012 . ATM profile An ATM profile defines the objects that ATM should monitor as well as the maintenance activities that should be executed once defined thresholds are violated. activities are logged in the ATM history. This means objects only undergo lightweight maintenance activities on regular business days. ATM profile Large Tables for update statistics: 12/18/2012 PUBLIC 79/116 . In addition. and procedures are created in the saptools database. the DBA Cockpit will recognize a version mismatch and will ask you to update ATM by choosing Repair ATM. n Commands are executed with low priority. the saptools database needs to be created manually (see also SAP Note 1593987 ). Updates and fixes for ATM are provided through SAP Support Packages and SAP Notes.4 The DBA Cockpit 4. The default ATM configuration also ensures full availability of all objects at any time. a default ATM configuration is created that immediately enables the system for automatic table maintenance. In addition. Default ATM Configuration The default ATM configuration that is created when you initially deploy ATM on a Sybase ASE DBMS tries to automate table maintenance. ATM profile Medium Tables for update statistics: n Includes tables containing 10000 up to 999999 rows. n Triggers update of index statistics if data change exceeds 20%. all required tables. with very large objects being excluded from such maintenance activities entirely.5. Note The saptools database is available on every SAP system by default. routines. n Commands are executed with low priority.11. without risking negative impact on the applications that are connected to ASE. If ATM is going to be deployed on a non-SAP system.2 Setup and Maintenance of the ATM Framework Deploying ATM on Sybase ASE is very easy. 4. The DBA Cockpit detects that ATM has not yet been set up on the system.11 Automatic Table Maintenance Note ATM is not supported for ASE releases older than 15. More costly maintenance activities are executed during the weekend. When you click the Setup ATM button. All you need to do is make the system known to the DBA Cockpit and initiate the setup process in the Configuration ATM Configuration screen. If the ATM framework that was already set up on a system requires an update. n Triggers update of index statistics if data change exceeds 20%. Default ATM Profiles ATM profile Small Tables for update statistics: n Includes tables containing 100 up to 9999 rows. system and proxy tables are excluded from automatic maintenance. n Commands are executed with low priority. n Triggers update of index statistics if data change exceeds 20%. n ATM profiles are applied repeatedly on an hourly basis until the ATM window expires. n Two ATM profiles are assigned by default l Update statistics profile Small Tables l Update statistics profile Medium Tables ATM window “Weekend” n Starts Sunday at 02:00 and ends Monday 05:00. ATM profile All Tables ‒ Remove Row Forwarding for reorganization: n Includes all tables n Triggers reorganization using the subcommand “compact” if the percentage of forwarded rows exceeds 10%. special objects in that database are excluded from getting updated statistics as known from best practices through additional exclusion profiles. n Commands are executed with low priority. n ATM profiles are applied only once or until the ATM window expires. ATM profileAll Tables ‒ Reclaim Space for reorganization: n Includes all tables. n Commands are executed with low priority. ATM profile Small to Medium Tables ‒ Rebuild Indexes for reorganization n Includes tables with up to 10GB of reserved space. special objects in that database are excluded from getting updated statistics as known from best practices through additional exclusion profiles. n Commands are executed with low priority. Default ATM Windows ATM window 24 hours all day n Starts Monday at 00:00 and ends Sunday 23:30.11 Automatic Table Maintenance n Includes tables containing 1000000 up to 999999999999 rows.4 The DBA Cockpit 4. Note If an SAP application database is found on the DBMS. n Triggers rebuild of all indexes that have an index page cluster ratio below 90%. If an SAP application database is found on the DBMS. n Four ATM profiles are assigned by default: l Update statistics profile Large Tables l Reorganization profile All Tables ‒ Remove Row Forwarding l Reorganization profile All Tables ‒ Reclaim Space 80/116 PUBLIC 12/18/2012 . n Triggers reorganization using the subcommand “compact” if space utilization falls below 90%. you can configure options like the number of days 4. This type of ATM profile is used for tables that should be excluded from either update statistics or reorganization. qualified name (supporting a wildcard at the right end of the table’s name).11 Automatic Table Maintenance l Reorganization profile Small to Medium Tables ‒ Rebuild Indexes Miscellanous Settings In the Miscellaneous tab of the ATM Configuration screen. But for the same set of objects. which is either update statistics or reorganization. You may. Note A single object can qualify for multiple ATM profiles of the same type. ATM Profiles for Excluding Objects from ATM Tables are identified by a full. This means that tables matching any active ATM profile of type ATM Profile to Exclude Objects from ATM will be excluded from any Standard ATM Profile or ATM Profile for Special Objects. there are in total three types of ATM profiles that can be defined: Standard ATM Profiles Tables are identified by a characteristic. Standard ATM profiles are used to maintain all tables that do not require special care. This type of ATM profile is used for tables that require special care ‒ for example. due to the size of the table or its need for special maintenance options. for example. qualified name (supporting a wildcard at the right end of the table’s name). Examples are queue tables that are constantly undergoing a massive data change.11.3 ATM Profiles ATM Profile Types ATM profiles are separated by the type of maintenance operation concerned.4 The DBA Cockpit 4. want to define an ATM profile that initiates sampled statistics with low priority if data change exceeds 20%. Maintaining ATM Profiles The Configuration ATM Configuration screen allows you to n Define new ATM profiles 12/18/2012 PUBLIC 81/116 . such as row count or size. Tables matching any active ATM profile of type ATM Profile for Special Objects will be excluded from any Standard ATM Profile. causing continuously inaccurate statistics. For each of the two maintenance operations. ATM Profiles for Special Objects Tables are identified by a full. you are able to define another ATM profile that initiates full statistics with high priority if data change exceeds 50%. ATM will evaluate thresholds for each data 82/116 PUBLIC 12/18/2012 . Indexes are rebuilt as soon as the index page cluster ratio falls below 90%. make use of Sybase ASE’s partitioning feature. while some other data partitions may remain mostly or completely unchanged. This ATM profile is limited to tables with a size of 0 to 10000MB. you define the importance the requested maintenance operation has compared to maintenance operations defined by other ATM profiles. some data partitions may undergo heavy data changes. using a reduced ASE execution priority. With the so-called maintenance priority. you specify the amount of CPU resources that should be assigned to the maintenance operations while they are being executed.11 Automatic Table Maintenance n Change existing ATM profiles n Delete existing ATM profiles n Activate or deactivate ATM profiles Creating ATM Profiles 1. especially data warehouse applications. . it does not make sense to update statistics on all partitions or to reorganize the whole object. The next example shows a dialog for changing an existing ATM profile of type Standard ATM Profile for reorganization. Example Choose the following values. If you check Evaluate Threshold per Data Partition. 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: Profile Type ATM Profile for Special Objects Type or 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% ASE Execution Priority Medium There are two types of priorities that can be configured for an ATM profile.4 The DBA Cockpit 4. Some applications. Object Selection. In such cases. and Maintenance Options. Chosse Create. Enter values for Profile Metadata. 2. Depending on the dimensions used to partition the data. With the so-called ASE execution priority. 4 ATM Windows With ATM windows. the ATM job will not complete execution after the evaluation of maintenance requirements has finished and no objects remain in the ATM queue. Instead. for example. as required by an individual data or index partition. In addition. Temporary overlapping between ATM windows is permitted.4 The DBA Cockpit 4.11 Automatic Table Maintenance and index partition individually. if appropriate. 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 finally expires. Note ATM profiles of type ATM Profiles for Excluding Objects from ATM cannot be assigned to specific ATM windows. Changing an ATM window will reschedule the respective job. Details on how ATM windows and assigned ATM profiles are processed are given in the chapter Processing ATM Windows and Assigned ATM Profiles. cancel current executions. Maintaining ATM Windows The Configuration n n n n n ATM Configuration screen allows you to: Define new ATM windows Change existing ATM windows Delete existing ATM windows Activate or deactivate ATM windows Assign ATM profiles to an ATM window or remove assigned ATM profiles from an ATM window ATM windows are scheduled jobs in the ASE job scheduler. want to ensure accurate optimizer statistics on certain objects during regular business time. while wanting to run update statistics at any time. should be maintained outside regular business time. Deactivation of an ATM window will unschedule the job for further executions and. 4. and maintenance operations will also be executed individually. 12/18/2012 PUBLIC 83/116 . Those ATM profiles are valid for all ATM windows by definition. usually very large objects.11. you define what type of table maintenance requirements and operations are evaluated and executed on certain objects within a defined time frame. In this case. while update statistics on other. a single ATM profile can be assigned to multiple ATM windows. You may. ATM windows can be configured to repeatedly apply ATM profiles until the window expires. You may also want to move table or index reorganization into the weekend. This information allows you to fine-tune your ATM configuration and to ensure correct behavior of ATM in the respective application environment. You can access the ATM log by navigating into the Diagnostics Automatic Table Maintenance ATM Log screen of the DBA Cockpit . Phase 1 will identify objects that require maintenance according to the defined ATM profile and put those objects into an ATM queue. Phase 2. By default. the maintenance command that was executed as well as the ATM profile that initiated maintenance of the object will be displayed (see details section below). as defined in the ATM queue. 84/116 PUBLIC 12/18/2012 . Note In addition to the ATM Queue and ATM History screen.5 Diagnostics: Automatic Table Maintenance ‒ ATM History The Diagnostics Automatic Table Maintenance ATM History screen shows all maintenance operations that have been executed by ATM in the previous days and weeks. the maintenance command that is going to be executed as well as the ATM profile that initiated maintenance of the object will be displayed.7 Diagnostics: Automatic Table Maintenance ‒ ATM Log ATM writes its own message log while evaluating maintenance requirements and finally executing maintenance operations. will execute maintenance. A different ATM history size can be configured in the Miscellaneous tab of the Configuration ATM Configuration screen. finally. When you select one of the records shown. When you select one of the records shown. ATM logs for the last 14 days are kept. If the ATM windows are too short to process all identified maintenance requirements.4 The DBA Cockpit 4.11. This number of days as well as the number of messages being written into the ATM log can be configured in the Miscellaneous tab of the Configuration ATM Configuration screen. this message log can also help DBAs understand error conditions and performance-related issues.11 Automatic Table Maintenance 4. ATM is executed in two phases.11.6 Diagnostics: Automatic Table Maintenance ‒ ATM Queue As described in the chapter entitled Processing ATM Windows and Assigned ATM Profiles.11. the ATM history spans 8 weeks. until the ATM window has expired or no entry can be found in the ATM queue. The screen Diagnostics Automatic Table Maintenance ATM Queue screen allows you to monitor the current ATM queue. the ATM queue will fill up and the required maintenance operations will not be executed. details regarding ATM for a single table can also be reviewed using the Space Tables and Indexes Single Table Analysis 4. While its main target group is SAP support. (dangling modifier !) By default. 4. actual execution of ATM activities is performed entirely through the job scheduler that is provided by Sybase ASE. or are currently opened by ASE and have undergone at least one write operation.11. The only exceptions in this case are new ATM profiles and newly configured systems where ATM needs to initially evaluate all objects. Each object that is flagged for the respective type of ATM profile and that matches the profile object selection conditions is evaluated according to the ATM profile’s threshold conditions. ATM determines the current row count and size. ATM checks whether all configuration prerequisites are fulfilled and whether ATM profiles assigned to the ATM are valid. Jobs named SAP_ATM_W <window_ID> are scheduled. Preparation Phase During the initial phase of an ATM window. special maintenance. Depending on the exact definition of the ATM profile. creates around 75000 tables and around 90000 indexes on the database. The first thing ATM does is to restrict the amount of tables. In addition. Up to now.8 Processing ATM Windows and Assigned ATM Profiles While configuration and monitoring of ATM is done completely from the DBA Cockpit. If defined thresholds are violated. Evaluation Phase A standard installation of SAP ERP 6. for all objects that are neither flagged for no maintenance nor special maintenance. Create a temporary table containing all user tables of any user database that were either accessed? since that time (according systabstats). Determine the minimum of all timestamps any assigned ATM profile has been evaluated the last time 2. Nevertheless. and partitions that are going to be evaluated for maintenance. configuration options are read for the ATM window /for example. 12/18/2012 PUBLIC 85/116 . Each job then crosses over in to the phases described in the following subsections. In addition. including Enhancement Package 5. its expiration time or whether the evaluation and cleanup phase are going to be executed with low execution priority. as defined by active ATM windows. as usually only certain scenarios of the SAP ERP are exploited in a specific installation. ATM then reads all assigned ATM profiles of type Standard ATM profile or ATM Profile for Special Objects. Create additional temporary tables containing all indexes and data partitions of the tables that have been determined. only a small amount of these objects is accessed. So. 3. evaluation may happen on individual data partitions and/or indexes instead of on the object as a whole. or standard maintenance. the number of objects that ATM looks at has been reduced to a level where maintenance evaluation is reasonable. all remaining objects have been flagged according to the assigned ATM profiles for either no maintenance.11 Automatic Table Maintenance 4.4 The DBA Cockpit 4. This mechanism will greatly restrict the amount of objects that are evaluated in an SAP environment. This is done in the following way: 1. The selection of objects for ATM profiles of type Standard ATM profile is done by specifying a range of either row count or size. indexes. l Table is not already contained in the ATM queue with equal maintenance priority but higher or equal command weight*. but whose planned maintenance operation is less weighty than the newly identified requirement (including individual index partitions). but whose planned maintenance operation is less weighty than the newly identified requirement (including individual data partitions of the table). While ATM creates new entries in the ATM queue. Identified object is a data partition: n Drop entries from the ATM queue that have a lower maintenance priority than the newly identified requirement (excluding other data partitions or the table itself). Note Index partitions with higher maintenance priority (or identical maintenance priority but higher command weight) will stay queued in parallel. Indentified object is a table: n Drop entries from the ATM queue that have a lower maintenance priority than the newly identified requirement (including individual data partitions of the table). Identified object is a data partition: n Drop entries from the ATM queue that have a lower maintenance priority than the newly identified requirement (including individual index partitions).11 Automatic Table Maintenance 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. n Drop entries from the ATM queue that have an equal maintenance priority. n Drop individual index partitions from the ATM queue that have a completely identical maintenance requirement than just identified for the complete index. but only if: l Table is not already contained in the ATM queue with higher maintenance priority. 2.4 The DBA Cockpit 4. n Insert table into ATM queue. n Drop individual data partitions from the ATM queue that have a completely identical maintenance requirement than just indentified for the complete table. 3. Note Data partitions with higher maintenance priority (or identical maintenance priority but higher command weight) will stay queued in parallel. but only if: l Index is not already contained in the ATM queue with higher maintenance priority. 86/116 PUBLIC 12/18/2012 . n Drop entries theATM queue that have an equal maintenance priority. Such cases are handled as follows: 1. l Index is not already contained in the ATM queue with equal maintenance priority but higher or equal command weight*. it may happen that the same object or some of its data partitions or indexes is already contained in the ATM queue. n Insert table into ATM queue. 4 The DBA Cockpit 4. required maintenance operations are read in from the ATM queue according to their maintenance priority and are executed using the requested ASE execution priority. it gets moved from the ATM queue into the ATM history. Cleanup Phase Before an ATM window completes execution.). but whose planned maintenance operation is less weighty than the newly identified requirement (excluding other data partitions or the table itself. * Weighting of maintenance operations is done as follows: n Update statistics with sampling of 50% or full update statistics has more weight than update statistics with sampling of 20%. 4. As long as the ATM window has not yet expired and as long as entries still remain in the ATM queue.11 Automatic Table Maintenance n Drop entries from the ATM queue that have an equal maintenance priority. old data is deleted from the ATM history and ATM log as configured through the DBA Cockpit. n reorg compact has more weight than reorg reclaim_space or reorg forwarded_rows. Identified object is a data partition: n Drop entries from the ATM queue that have a lower maintenance priority than the newly identified requirement (excluding other index partitions or the index itself). n Insert data partition into the ATM queue. but only if: l Index partition or index is not already contained in the ATM queue with higher maintenance priority. but only if: l Data partition or table is not already contained in the ATM queue with higher maintenance priority. n reorg rebuild has more weight than reorg compact or reorg rebuild for an individual index. n Drop entries from the ATM queue that have an equal maintenance priority.). 12/18/2012 PUBLIC 87/116 . After maintenance has been executed on a certain object. If no objects remain in the ATM queue. the ATM window will go into sleep mode until exactly one hour has elapsed since the last evaluation. but whose planned maintenance operation is less weighty than the newly identified requirement (excluding other index partitions or the index itself. n Insert data partition into the ATM queue. l Index partition or index is not already contained in the ATM queue with equal maintenance priority but higher or equal command weight*. l Data partition or table is not already contained in the ATM queue with equal maintenance priority but higher or equal command weight*. Execution Phase Execution of maintenance is now purely based on entries found in the ATM queue. but the ATM window is configured to repeatedly apply ATM profiles and the ATM window has not yet expired. Runtime measurements and the exact maintenance command are recorded in the ATM history for later analysis. 12 Diagnostics The following sections provide information about the main task areas that are available under Diagnostics on the Database tab page of the DBA Cockpit: n n n n n n Audit Log Lock-Wait Events Missing Tables and Indexes Error Log Automatic Table Maintenance ASE Status Note For more information on Automatic Table Maintenance Diagnostics. 4.12. using native database commands ‒ are not displayed here. refer to the chapters above.1 Diagnostics: Audit Log You can track changes to the database made from the DBA Cockpit and to the monitoring setup using the maintenance actions provided in the DBA Cockpit. The Audit Log screen appears displaying the following information Field Description Date Start date of the action Time Start time of the action System Target system on which the action was performed Action Type of action (name of the action in the DBA Cockpit) Command Type of command (for example. Procedure 1. 4. Call the DBA Cockpit and choose Diagnostics Audit Log on the Database tab page of the DBA Cockpit.4 The DBA Cockpit 4. ADD.12 Diagnostics After the amount of objects has been restricted. Changes made from outside ‒ for example. DELETE or EDIT) 88/116 PUBLIC 12/18/2012 . ATM imports all ATM profiles of type ATM Profile to Exclude Objects from ATM and type ATM Profile for Special Objects and flags matching objects for either no maintenance or special maintenance. see Data Collection Framework: Collector Configuration [page 66]. Using the information provided on this screen. which can be a lock wait. the status displayed is Still Existing. a lock timeout or a deadlock Event Occurrence Time when the lock event first occurred Event Resolution Time when the lock event was solved Note For events that are still existing. By default. lock waits. 3. the system displays all audit entries logged during the current week. For more information. you can specify the time frame for which you want lock-wait events to be displayed as well as the type of lock-wait event. Involved Agents 12/18/2012 Number of agents involved in the lock event PUBLIC 89/116 .2 Diagnostics: Lock-Wait Events You can access information about lock-wait events by calling the DBA Cockpit and choosing Diagnostics Lock-Wait Events on the Database tab page of the DBA Cockpit. For each lock-wait event. and lock waits with a specific lock time out. the total number of lock-wait events that occurred and that you selected in the Selection area is displayed in the Summary area. After having applied your selection. n Review lock wait events that are currently occurring on the database server. use the F4 help of the From field. To display the details of an action. you can change the value in the field Number of Days. If you want to display another week. you can: n Review lock wait events that occurred in the past and that were captured by the lock event monitor. To display more than one week. database or tablespace name) User Name of the SAP user who performed the action From System System from where the action was performed 2. 4. such as. lock time outs. the SQL statements that have been executed are displayed.12 Diagnostics Field Description Object Name of the modified object (for example. the following information is displayed: Column Description Event Type Type of lock event. In the Selection area. In the lower half of the screen.4 The DBA Cockpit 4. information about lock events is collected by the Lock Event data collector.12. select the corresponding action and choose Details. By default. Wait Time Max. but not found in the database Unknown objects in the ABAP Dictionary Objects that are found in the database. additional information about the type of inconsistency is provided.12 Diagnostics Column Description Max. which cannot be described at all or which cannot be completely described in the ABAP Dictionary for technical reasons.4 The DBA Cockpit 4. they are also displayed here. 90/116 PUBLIC 12/18/2012 .12. n If inconsistencies for these objects are detected. choose the Refresh pushbutton. In general. Optional indexes Mismatch between ABAP Dictionary and database regarding secondary indexes If the database structure has been changed since the last consistency check. lock-wait time of any of the involved agents Lock Objects Database objects involved in the lock conflict 4. but not defined in the ABAP Dictionary Inconsistent objects Results of the detailed comparison of the ABAP Dictionary and the database are displayed here Other checks Different checks are performed here: n It is checked whether the primary index of tables defined in the ABAP Dictionary was created uniquely on the database. You can find out whether tables or indexes are missing from either the database or the ABAP Dictionary by calling the DBA Cockpit and choosing Diagnostics Missing Tables and Indexes on the Database tab page of the DBA Cockpit. The results of the last consistency check are displayed in a tree structure that is grouped into the following sections: Section Description Objects missing from the database Objects that are defined in the ABAP Dictionary. n Objects in the SAP system tables are checked.3 Diagnostics: Missing Tables and Indexes Note This function is only available for local systems or for ABAP systems for which an additional RFC destination has been assigned. 4 Diagnostics: Error Log You can access information about the error log of the Sybase ASE database server by calling the DBA Cockpit and choosing Diagnostics Error Log on the Database tab page of the DBA Cockpit.12. installed licenses and versions.12 Diagnostics Recommendation To ensure consistency between the ABAP Dictionary and the database.4 The DBA Cockpit 4. a warning is displayed including a link to the Collector Configuration screen. the consistency check should be performed once a month or whenever the database structure has changed. If the DCF is not available or set up incorrectly.5 Diagnostics: ASE Status Choose Diagnostics ASE Status on the Database tab page of the DBA Cockpit to access information about the ASE database server status. you have to make sure that the data collection framework (DCF) is set up correctly.12. 4. see Data Collection Framework: Collector Configuration [page 66]. Note To monitor data on the Error Log screen. There you can perform the required steps. 4. For more information. 12/18/2012 PUBLIC 91/116 . This page is left blank for documents that are printed on both sides. . then use an external tool to perform a backup of all the database devices. you must: n ensure that the Adaptive Server can be recovered n ensure that databases can be restored from offline copies n ensure that a complete sequence of transaction logs has been archived at all times Ensure that the Adaptive Server can be recovered (UNIX) Create a file system backup for the file systems /sybase/<DBSID> (Unix) and <Drive>:\sybase\<DBSID> (Windows) at regular intervals (exclude the following database devices from the backup): The database does not have to be offline for this. You have to quiesce all databases that simultaneously reside on a device and you have to perform a simultaneous backup of all database devices. 12/18/2012 PUBLIC 93/116 . that are required to run your SAP system. n n n n sybsystem sapdiag sapdata_<n> saplog_<n> Ensure that databases can be restored from offline copies n Create copies of the following data at regular intervals. Alternatively. use the QUIESCE DATABASE command to block any update operation on a database. DUMP DATABASE can be run while databases are online and in use. DUMP images of the following databases: l <DBSID> database (SAP database) l master database l sybsystemprocs database (optional) l sybmgmtdb database l saptools database (optional) Use the command DUMP DATABASE to achieve this.1 Ensuring Recoverability for Sybase ASE You need to ensure that you are able to recover the Adaptive Server and all databases on the server.5 Backup and Recovery 5 Backup and Recovery 5. To guarantee recoverability. Do this for all the databases mentioned above. syssrvroles. Save the output to a file. To ensure a complete log sequence. Use the stored procedure sp_ddlgen to generate this statement (Syntax: sp_ddlgen ’database’. false full logging for all. These are optional. Save the output to a file you store offline. sysdatabases. Ensure that a complete sequence of transaction log archives is available at all times For your SAP database <DBSID> it is mandatory that you ensure that the archived log sequence remains unbroken. sysusages. inactive log entries will no longer be purged from the transaction log at checkpoints. true enforce dump tran sequence. but they can be used to check the loaded copy of the master database. set the following database options: n n n trunc log on chkpt. Keep copies of the dumped transaction log back to at least the last copy of your database (obtained using DUMP DATABASE or QUIESCE DATABASE. Caution After you have changed these options. However. it is recommended that you keep several database copies along with all required transaction log dumps. This is strongly recommended to ensure that the database has the same layout with respect to data and log segments whenever you recreate a database. Set these options using the stored procedure sp_dboption to change database options. sysremotelogins. (Syntax: sp_dboption [dbname. SAP Note 1588316 provides information on how database and log backups on the Adaptive Server can be automated. combined with an external backup). optname. 94/116 PUBLIC 12/18/2012 . sysservers.5 5. true You have to set these options after a successful DUMP DATABASE has been performed and before any change is made to the database. sysdevices. You can use the procedure sp_helpdevice to get this list.1 Backup and Recovery Ensuring Recoverability for Sybase ASE n Backup the DDL statements for the CREATE DATABASE statement including all later ALTER DATABASE statements. you have to get regular dumps of the transaction log. You must change to the master database to be able to change options for a database. DBSID ). In order to prevent the transaction log from filling up. {true | false}] ). n Create a copy of an up-to-date list of all of your database devices. sysloginroles. n Copy of the contents of the following system tables: syslogins. along with all the required dumps from the transaction log. n The device layout is known (you have saved an up-to-date copy of the output of sp_helpdevice).5 5. you have to reinstall ASE with the SAP installer . Pay particular attention to the following parameters: Parameter: Comment: sqlsrv. n The database layout is known (DDL commands for all databases are available). Recreate the file systems for the following directories: n n n n n DRIVE:\sybase\SID\sapdata_[1-n] DRIVE:\sybase\SID\saplog_[1-n] DRIVE:\sybase\SID\sybsystem DRIVE:\sybase\SID\sapdiag DRIVE:\sybase\SID\sybtemp Rebuild the Sybase Server If the file system of the SAP software installation (for example DRIVE:\sybase\<DBSID>) is available.main response file to recreate the Adaptive Server %SYBASE%\ASE-15_0\bsrv. you can use the original response files that were created by the Sybase installer to recreate the ASE server. n A current copy of the ASE server configuration file is available. It is not possible to reinstall the ASE software standalone using the ASE installer from the RDBMS installation medium provided by SAP.server_name Use <SAPSID> as server sqlsrv. sybmgmtdb and saptools databases are available. The following files are relevant for the restoration of the server: n n %SYBASE%\ASE-15_0\sqlsrv. If the file system of the Sybase software installation (that is. you have to install an empty SAP Netweaver system and then load your database backups into the Sybase ASE server. all the database devices and databases are damaged and have to be recreated. Assupmtions: n The file system DRIVE:\sybase\DBSID is available.res .response file for the backup server Review the contents of the file and ensure that it matches your installation. restore it from a file system backup. If you don’t have a file system backup.2 Backup and Recovery How to Restore a Sybase ASE Database Server (Windows) 5.res . DRIVE:\sybase\SID) is not available. since the necessary SAP OEM license can be installed only using the SAP installer.2 How to Restore a Sybase ASE Database Server (Windows) The instructions below provide an outline of what needs to be done to restore a Sybase ASE database server on Windows. n Current dumps of the master.for example. n A current dump of the DBSID database is available.server_page_size 16k is mandatory 12/18/2012 PUBLIC 95/116 . Example: %>ASE-15_0\bin\sybatch.sybsystemdb_db_device_physical_size: Size sqlsrv.<nnn>.2 Backup and Recovery How to Restore a Sybase ASE Database Server (Windows) Parameter: Comment: sqlsrv.).master_device_physical_name Path to master device sqlsrv..do_create_sybsystemdb_db_device Yes sqlsrv.characterset_install_list Install utf8 sqlsrv.tempdb_device_physical_name: Path to tempdb device sqlsrv. It will create a new master device and a new master database. A log file of the sybatch. Important: Review the contents of that log file.sort_order Binary sort order is mandatory sqlsrv. call the command sybatch.5 5.default_language Default language English (us_english) sqlsrv.exe command is written to %SYBASE%\ASE-15_0\init\logs\log <mmdd>. for example..res This command will rebuild a new server. and set the binary sort order.sybsystemdb_db_device_logical_name: Logical name sqlsrv.exe -r ASE-15_0\sqlsrv.do_create_sybsystemprocs_device Yes sqlsrv. 001.product:sqlsrv Product to be installed sqlsrv.master_device_size Master device size sqlsrv.exe as the ASE software owner syb<sid> to recreate the server. where <mmdd> is the month and day and <nnn> is a three-digit number.sybsystemdb_db_device_physical_name: Path to system device file sqlsrv. The error log file should contain an entry indicating that the default sort order is now ’binary’ (ID = 25) on top of default character set ’utf8’ (ID = 190).tempdb_device_size: Size Review the path and the size of the ASE devices that were created (master. After you have verified that the file matches your needs.default_characterset utf8 is mandatory sqlsrv. Ensure that the rebuild of the server has worked as expected. 96/116 PUBLIC 12/18/2012 .systemprocs.sybsystemprocs_device_logical_name Adaptive server device name sqlsrv. load the utf-8 character set.sybsystemprocs_device_size Size sqlsrv. Ensure that the sizes fit your current device sizes. Ensure that utf-8 has been installed as the default character set and that the binary sort order is set.language_install_list Install us_english sybinit.sybsystemprocs_device_physical_name Device for database sybsystemprocs sqlsrv. Recreate the Backup Server If required. Adaptive Server must be running in single user mode in order to load a master database. just re-create these as empty files in the file system. The SAP administrative login sapsa does not yet exist on the server. Example: load database master from c:\sybase\TNT\backups\master2011-08-04T220844.res Review the contents of the corresponding log file %SYBASE%\ASE-15_0\init\logs\log<mmdd>.bat. Edit the new file and add the startup option ’-m’ at the end of the file. Copy the file RUN_<SID>. Review the contents and then recreate the backup server. not as a service.exe -r ASE-15_0\bssrv.2 Backup and Recovery How to Restore a Sybase ASE Database Server (Windows) Note that since you are rebuilding the master database from scratch.5 5. you can recreate the backup server by calling the file bssrv.res with the sybatch. Do not close the DOS command shell where you started the server as long as the Adaptive Server is running! Load the Master Database In case you have not yet done so.bat to a file RUN_<SID>_SINGLE_USER_MODE. Ensure the physical device file(s) exist and are accessible for Adaptive Server. Recreate the Temporary Database(s) Temporary database(s) get recreated from scratch at startup.<nnn> Restart the Server in Single User Mode Change to the directory %SYBASE%\ASE-15_0\install. Use the login sa with empty password to logon to Adative Server. Important: Adaptive Server is now running as a user process. Start Adaptive Server by calling this batch file from a DOS command prompt.execommand. start the backup server.dmp go Adaptive Server shuts down automatically after master has been loaded successfully. The original master database has to get loaded with the LOAD DATABASE command. the default administrative login sa with an empty password is active. Recreate and Load the Job Scheduler Database ’sybmgmtdb’ You first have to drop the sybmgmtdb database from the catalog of the loaded master database and drop the non-existing sybmgmt database device sybmgmtdev Example: drop database sybmgmtdb 12/18/2012 PUBLIC 97/116 . If you lose the file(s) for the tempdb devices. Example: %>ASE-15_0\bin\sybatch. Log in to Adaptive Server with isql (or another SQL editor) and issue the LOAD DATABASE command. dmp If you have performed a dump of sybmgmtdb. you will have to recreate these manually. recreate the contents of sybmgmtdb with the scriptinstalljsdb and enable job scheduling again. @option="start_js" go After the recreation of sybmgmtdb. Call the DBA Cockpit and ensure that the required jobs are recreated properly.1 go exec sybmgmtdb.outfile Log in to ASE with isql as user sapsa and execute the commands: sp_configure ’enable job scheduler’. use the standard Windows service to start ASE this time. You have to drop the non-existing database from the master catalog.00M’. directio = ’true’ go create database sybmgmtdb on sybmgmtdev = ’72M’ for load go load database sybmgmtdb from c:\sybase\TNT\backups\sybmgmtdb2011-08-04T220847. Finally.sp_sjobcontrol @name=NULL. size=’75. load it with the LOAD DATABASE command. Recreate the saptools Database Reboot in multi-user mode.. 98/116 PUBLIC 12/18/2012 . then recreate the devices and the saptools database. If no dump of sybmgmtdb is available.2 Backup and Recovery How to Restore a Sybase ASE Database Server (Windows) go Then drop the device. physname=’D:\sybase\TNT\sybsystem\sybmgmtdb. sp_dropdevice sybmgmtdev go Recreate the device for sybmgmtdev and database sybmgmtdb Example: disk init name=’sybmgmtdev’. all previously defined jobs are gone.dat’.5 5. load the most recent dump of the saptools database. This includes: n Automatic Table Maintenance n Data Collection Framework n DBA Planning Calendar If you have defined your own jobs. Set the configuration parameter enable job scheduler to 1 and restart the job scheduler tasks with the command. Example: D:\> isql -STNT -Usapsa -P<PASSWORD> -i %SYBASE%\ASE-15_0\scripts\installjsdb -o jsdb. drop the corresponding device(s). followed by all dumps of the transaction log you took in the correct order.2 Backup and Recovery How to Restore a Sybase ASE Database Server (Windows) Example: drop database saptools go sp_dropdevice datasaptools_1 go sp_dropdevice logsaptools_1 go disk init name=’datasaptools_1’.00M’. First drop the non-existing <DBSID> database from the catalog and recreate it with the saved DDL statement for the database. physname=’D:\sybase\TNT\saplog_1\logTNT_1. physname=’D:\sybase\TNT\sapdata_1\dataTNT_1. size=’128000. Example: drop database TNT go sp_dropdevice dataTNT_1 go sp_dropdevice logTNT_1 go disk init name=’dataTNT_1’.dmp go Bring database saptools online with the online Example: database command. directio = ’true’ go disk init name=’logTNT_1’.dat’.5 5. Then load the latest dump of saptools.dat’.dat’. directio = ’true’ go disk init name=’logsaptools_1’. 12/18/2012 PUBLIC 99/116 .00M’. physname=’D:\sybase\TNT\sybdiag\datasaptools_1. physname=’D:\sybase\TNT\sybdiag\logsaptools_1. size=’200.dat’. this speeds up database creation. online database saptools go Load the <DBSID> database. load database saptools from c:\sybase\TNT\backups\saptools2011-08-04T220850. directio = ’true’ go CREATE DATABASE saptools ON datasaptools_1 = ’2048M’ LOG ON logsaptools_1 = ’200M’ FOR LOAD go Specifiy the FOR Example: LOAD option. size=’2048M’. Then load the most recent dump of the database. Example: load database TNT from ’c:\sybase\TNT\backups\TNT2011-08-04T220853. Mandatory DB options for SAP are ddl in tran.dmp’ go Do not bring the database online now. allow nulls by default. Logon as user sapsa with isql .’true’ 100/116 PUBLIC 12/18/2012 .’true’ go sp_dboption TNT. Bring the database online with the command online database after you loaded all available transaction dumps for the database. allow wide dol rows.5 5. ’allow wide dol rows’.’true’ go sp_dboption TNT. You need to load all previously taken transaction dumps to the database in the correct order.2 Backup and Recovery How to Restore a Sybase ASE Database Server (Windows) size=’2048. It is possible that further dumps need to be loaded.dmp’ go Repeat this step for each dump you took. Example: load transaction TNT from ’D:\sybase\TNT\log_archives\TNT_trans_2011-08-04T221019. this speeds up the creation of the database significantly.page compression These have to be set in any case. If you need to restore to a specific point in time. first load all the transaction log dumps. Now load the most recent dump of the <DBSID> database. ’ddl in tran’. Bring <DBSID> database online ASE does not bring a database online automatically after you loaded a dump. specify the until_time parameter of the load transaction command.00M’. Example: sp_dboption TNT. ’allow nulls by default’. online database TNT go Reset database options Important: Check and reset all database options as required before you start SAP. use the stored procedure sp_dboption to set the necessary options. Mandatory for a production system enforce dump tran sequence (see SAP Note 1585981 ) full logging for all. directio = ’true’ go CREATE DATABASE TNT ON dataTNT_1 = ’128000M’ LOG ON logTNT_1 = ’2048M’ for LOAD go Specify the load option. restore it from a file system backup.cfg. The instructions below provide an outline of what needs to be done in order to restore a Sybase ASE server. n Device layout is known (you saved an up-to-date copy of the output of sp_helpdevice).5 5. If the file system /sybase/<SID> is not available. n Current copy of ASE server configuration file is available. The Sybase ASE server runs on a UNIX or Linux operating system. Assumptions: n The file system /sybase/<SID> is available. If you don’t have a file system backup. If any changes to the database contents are made before you set enforce dump tran sequence. ’enforce dump tran sequence’. 12/18/2012 PUBLIC 101/116 . you need to reinstall an empty SAP Netweaver system using the SAP installer and then load your databases into the newly created ASE server.’true’ go sp_dboption TNT. all the database devices and databases are damaged and need to be recreated. 5. ’sybmgmtdb’ and ’saptools’ databases are available. You need to restore the database server. Copy the saved original copy of the ASE configuration file to the location of the ASE configuration file and reboot ASE. you have to get a full database dump before you can set the option. The default location of the ASE server configuration file is %SYBASE%\ASE-15_0\<SAPSID>. You are operating SAP with a Sybase ASE database server.3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) go sp_dboption TNT. It is not possible to reinstall the ASE server standalone using the ASE installer from the RDBMS installation medium provided by SAP. The ASE now has a default configuration for many configuration parameters. n Database layout is known (DDL commands for all databases are available).3 How to Restore a Sybase ASE Database Server (UNIX) Caution Check SAP Note 1618817 for the latest updates and newest information! You need to restore a Sybase ASE database instance on UNIX/Linux. n A current dump of the ’master’. since the SAP OEM license is installed only using SAPINST. ’true’ go !Attention: Set the database options immediately after the database has been brought online and before any user connects to the database. ’full logging for all’ . Review the saved copy of your configuration file and adapt the ASE configuration as needed. n A current dump of <DBSID> database is available along with all the required dumps from the transaction log. Then use the command srvbuildres to recreate the server.sybsystemdb_device_physical_name: # sqlsrv.3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) Recreate the filesystems Recreate the filesystems as required for the following directories: /sybase/<SID>/sapdata_[1‒n] /sybase/<SID>/saplog_[1‒n] /sybase/<SID>/sybsystem /sybase/<SID>/sapdiag /sybase/<SID/sybtemp Rebuild the ASE server We suggest that you use a response file to recreate the ASE server.master_database_size: # master datasbase size sqlsrv.tempdb_device_size: # sqlsrv.server_name: # set it to <SAPSID>.tempdb_device_physical_name: # sqlsrv.default_backup_server: # Ensure that the master device and master database sizes are large enough to incorporate the most recent dump of the master database you created before the system crash.sybsystemdb_database_size: # sqlsrv. the directory /sybase/<DBSID>) the original response used for server creation should still be available. Log in as the ASE software owner syb<sid> and call the command.sybsystemprocs_database_size: # sqlsrv. In the $SYBASE directory (that is. The SAP administrative login sapsa does not yet exist on the server. compare to interfaces file sqlsrv. Review the contents of that file.master_device_physical_name: # master device sqlsrv.res. same as <DBSID> sqlsrv.product: sqlsrv sqlsrv. Pay particular attention to the following parameters: sybinit.master_device_size: # master device size sqlsrv.sybsystemdb_device_size: # sqlsrv. 102/116 PUBLIC 12/18/2012 . it is the file $SYBASE/ASE-15_0/sqlserv.release_directory: # set to /sybase/<DBSID> sybinit.tempdb_database_size: # sqlsrv. Ensure that it matches your needs.sybsystemprocs_device_physical_name: # sqlsrv. the default administrative login sa with an empty password is active at this time. Example: srvbuildres -r ASE-15_0/sqlsrv.5 5.sybsystemprocs_device_size: # sqlsrv.network_port_list: #port of ASE .server_page_size: 16k # 16k is mandatory for SAP installations sqlsrv.res Note that since you are rebuilding the master database from scratch. dat \ -e/sybase/LEO/ASE-15_0/install/LEO. Restart ASE in single-user mode.This file was generated by Sybase Installer --# sybinit.cfg \ -M/sybase/LEO/ASE-15_0 \ -sLEO \ -m \ Start the ASE server with the command startserver.server_name: LEO sqlsrv. Copy the original RUN_<SERVER>file to a file RUN_<SERVER>_SINGLEUSERand add a startup parameter -m. Example #!/bin/sh # Name: RUN_LEO_SINGLEUSER # Starts ASE server LEO in single user mode # Master device path: /sybase/LEO/sybsystem/master. which was created during installation of the ASE server.log # Configuration file path: /sybase/LEO/ASE-15_0/LEO. it is important to load the utf-8 character set and configure binary sort order in a second step. Example startserver -f ./ASE-15_0/install/RUN_LEO_SINGELUSER To load utf-8 and configure binary sort order.dat # Error log path: /sybase/LEO/ASE-15_0/install/LEO.language_install_list: us_english 12/18/2012 PUBLIC 103/116 .res’.sa_password: sqlsrv.sa_login: sa sqlsrv. Its contents may look like this: # # --.cfg # Directory for shared memory files: /sybase/LEO/ASE-15_0 # Adaptive Server name: LEO # /sybase/LEO/ASE-15_0/bin/dataserver \ -d/sybase/LEO/sybsystem/master.release_directory: /sybase/LEO sqlsrv.3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) Configure utf8 and binary sort order After the ASE has been reinitialized. review the contents of the file $SYBASE/ASE-15_0/sqlsrv_lang.default_language: us_english sqlsrv.log \ -c/sybase/LEO/ASE-15_0/LEO. passing the newly created RUN_<SERVER>_SINGELUSER file as parameter. It is recommended that you create an adapted RUN_<SERVER> file to start the ASE in single-user mode.5 5. The ASE has to be started in single user mode in order to load a dump of the master database.characterset_install_list: utf8 sqlsrv. The ASE error log file should contain an entry indicating that ASE’s default sort order is now binary (ID = 25) on top of default character set ’utf8’ (ID = 190). Load the master database Now the original ’master’ database has to be loaded using the load database’command. Example sqllocres -SLEO -Usa -P -r ASE-15_0/sqlsrv_lang. It is sufficient to create the device(s) as an empty file in the correct location with correct permissions (sybsyb<sid>:sapsys 660) in the file system. Example load database master from ’/sybase/LEO/backups/master_2011-05-13. Recreate temporary databases Before you restart ASE.res Start the backup server.sort_order: binary Verify that the ASE server has started successfully in single-user mode.5 5. Example srvbuildres -r $SYBASE/ASE-15_0/bsrv.language_remove_list: sqlsrv. Then call the command sqllocres to set the utf8 and binary sort order using the file sqlsrv_lang.res. 104/116 PUBLIC 12/18/2012 . The backup server has to be started.characterset_remove_list: sqlsrv. call the RUN_<SERVER>_BS file with the startserver command. recreate the devices for the temporary database(s).res. Create and start the backup server Review the contents of the file $SYBASE/ASE-15_0/bsrv. Log on to the ASE server. Create the backup server by calling the file with ’srvbuildres’.res Verify that utf-8 has been installed as the default character set and the binary sort order is set.default_characterset: utf8 sqlsrv.dmp’ go ASE shuts down automatically afterwards.3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) sqlsrv. using isql as user sa (password is empty). too. Example drop database sybmgmtdb go Then drop the device. sp_dropdevice sybmgmtdev go Recreate the device for sybmgmtdb disk init name=’sybmgmtdev’.00M’. in multi user mode using the standard RNU_<SERVER> file. 12/18/2012 PUBLIC job scheduler to 1 105/116 .dat chmod 660 /sybase/LEO/sybtemp/tempdbdev. If you did not perform a dump of sybmgmtdb. size=’75.dat’./ASE-15_0/install/RUN_LEO Recreate and load the job scheduler database sybmgmtdb The reloaded master database has references to all the other system and user databases that existed prior to the restore. You need to remove and recreate these. you can recreate the contents of sybmgmtdb with the script installjsdb and enable job scheduling again. Example startserver -f . Example isql -SLEO -Usapsa -Ppassword -i ASE-15_0/scripts/installjsdb You have to enable job scheduler by setting the configuration parameter enable and starting the job scheduler tasks. physname=’/sybase/LEO/sybsystem/sybmgmtdb.5 5.dat Now restart ASE .3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) Example touch /sybase/LEO/sybtemp/tempdbdev. directio = ’true’ go create database sybmgmtdb on sybmgmtdev = ’72M’ go Load the dump of sybmgmtdb with the load database command and bring it online with the online database command afterwards. 3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) Example sp_configure ’enable job scheduler’. 1 go exec sybmgmtdb. Example online database saptools go Load the <DBSID> database First drop the non-existing database from the catalog. Recreate the devices and the database.5 5. you need to bring the saptools database online using the command online database. Then load the database. physname=’/sybase/LEO/sybdiag/logsaptools_1.dat’. Recreate saptools database Drop the non-existing saptools database from the catalog and its devices.dat’. Example drop database saptools go sp_dropdevice datasaptools_1 go sp_dropdevice logsaptools_1 go disk init name=’datasaptools_1’.00M’.131072 pages log on logsaptools_1 = ’200M’ -.00M’. @option="start_js" go You will have to recreate all your previously defined jobs if you used the installjsdb script to recreate sybmgmtdb. size=’200. 106/116 PUBLIC 12/18/2012 .. physname=’/sybase/LEO/sybdiag/datasaptools_1.sp_sjobcontrol @name=NULL. followed by all dumps of the transaction log you executed. directio = ’true’ go disk init name=’logsaptools_1’. size=’2048. directio = ’true’ go create database saptools on datasaptools_1 = ’2048M’ -. Then load the most recent dump of the database.12800 pages go After the dump has been loaded. Load transactions for the <DBSID>database After the dump has been loaded. since it speeds up the recreation of the database. Then load the latest dump available for the database.00M’. directio = ’true’ go create database LEO ON dataLEO_1 = ’128000M’ LOG ON logLEO_1 = ’2048M’ FOR LOAD go It is recommended that you use the for load’ option when recreating a large database. bring the database online. don’t bring the database online now. size=’128000. physname=’/sybase/LEO/saplog_1/logLEO_1. size=’2048.dmp’ go If you want to load transactions (that is. physname=’/sybase/LEO/sapdata_1/dataLEO_1.dat’. Example load database LEO from ’/sybase/LEO/backups/LEO_2011-05-13. perform a rollforward of transactions that took place after the most recent dump of the database.3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) Example drop database LEO1 go sp_dropdevice logLEO_1 go disk init name=’dataLEO_1’.00M’.dmp’ go Repeat this step for each dump you executed. Load the transaction dumps. the <DBSID> database is ready to load the dumps of the transaction log. After you have finished loading the transaction dumps.dat’. Example online database LEO go 12/18/2012 PUBLIC 107/116 . You have to load all dumps in the correct sequence in order to get the <DBSID> database back to the point in time before the crash. Specify the until_time option if you don’t want to roll forward to a specific point in time.5 5. Example load transaction LEO from ’/sybase/LEO/log_archives/LEO_trans_2011-05-14T00:00:03. directio = ’true’ go disk init name=’logLEO_1’. Review the configuration with respect to the saved copy of your configuration file. The default location of ASE’s configuration file is $SYBASE/ASE-15_0/<SAPSID>.cfg.5 5. 108/116 PUBLIC 12/18/2012 . Copy the saved configuration file to the ASE config file and restart ASE to make it active.3 Backup and Recovery How to Restore a Sybase ASE Database Server (UNIX) Reconfigure the ASE server The ASE configuration may not match your needs now. sap.1 The Main SAP Documentation Types The following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software. It lists the required installable units for each business or IT scenario.sap. This document contains general guidelines and suggestions.sap. n Target group: l Relevant for all target groups Current version: n l On SAP Help Portal at http://help. as well as many glossary entries in English and German. n Target group: l Consultants l System administrators l Project teams for implementations or upgrades n Current version: l On SAP Help Portal at http://help.com l In the SAP system in transaction STERM Glossary SAP Library is a collection of documentation for SAP software covering functions and processes. n Target group: l System administrators l Technology consultants l Solution consultants n Current version: l On SAP Service Marketplace at http://service. It contains SAP-specific vocabulary in over 30 languages. SAP applications have a security guide of their own. Cross-Phase Documentation SAPterm is SAP’s terminology database. A collective security guide is available for SAP NetWeaver. It provides scenario-specific descriptions of 12/18/2012 PUBLIC 109/116 .A Reference A Reference A.com (also available as documentation DVD) The security guide describes the settings for a medium security level and offers suggestions for raising security levels.com/securityguide Implementation The master guide is the starting point for implementing an SAP solution. execution. n Target group: l Technology consultants l Project teams for implementations n Current version: l On SAP Service Marketplace at http://service. is used. which refers to the relevant Customizing activities in the individual SAP systems. SAP Solution Manager. and precedes the application operations guides of SAP Business Suite. One of its main functions is the configuration of business scenarios.sap.sap.com/instguides The installation guide describes the technical implementation of an installable unit. the technical infrastructure guide and SAP Notes.com/instguides Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycle platform. It also provides references to other documents. business processes. n Target group: l Technology consultants l Project teams for implementations n Current version: l On SAP Service Marketplace at http://service. such as installation guides.1 The Main SAP Documentation Types preparation. as well as documentation. (In order to configure a whole system landscape from a process-oriented perspective. transactions. The Customizing activities and their documentation are structured from a functional perspective.A Reference A. and so on. The manual refers 110/116 PUBLIC 12/18/2012 . It does not describe any business-related configuration. It contains Customizing activities. and follow-up of an implementation. and implementable steps. n Target group: l Technology consultants l Solution consultants l Project teams for implementations Current version: n l In SAP Solution Manager The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system.) n Target group: l Solution consultants l Project teams for implementations or upgrades n Current version: l In the SAP menu of the SAP system under Tools Customizing IMG Production Operation The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver. taking into account the combinations of operating systems and databases. sap. master data maintenance. transports.sap.sap. execution. n Target group: l System administrators n Current version: l On SAP Service Marketplace at http://service.A Reference A. such as monitoring. n Target group: l Technology consultants l Project teams for upgrades n Current version: l On SAP Service Marketplace at http://service.com/instguides The application operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed.com/instguides The upgrade guide describes the technical upgrade of an installable unit. It does not describe any business-related configuration. and tests. It also refers to other documents. and follow-up of an upgrade. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG).sap. n Target group: l Technology consultants l Project teams for upgrades n Current version: l On SAP Service Marketplace at http://service.1 The Main SAP Documentation Types users to the tools and documentation that are needed to carry out various tasks. n Target group: l System administrators l Technology consultants l Solution consultants n Current version: l On SAP Service Marketplace at http://service. n Target group: 12/18/2012 PUBLIC 111/116 . such as upgrade guides and SAP Notes.com/instguides Upgrade The upgrade master guide is the starting point for upgrading the business scenarios and processes of an SAP solution. It provides scenario-specific descriptions of preparation.com/instguides Release notes are documents that contain short descriptions of new features in a particular release or changes to existing features since the previous release. backup/restore. taking into account the combinations of operating systems and databases. sap.1 The Main SAP Documentation Types l Consultants l Project teams for upgrades n Current version: l On SAP Service Marketplace at http://service.A Reference A.com/releasenotes l In the SAP menu of the SAP system under Help Release Notes (only ABAP developments) 112/116 PUBLIC 12/18/2012 . program names. These include report names.Typographic Conventions Example Description <Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system.sap. menu names. and key concepts of a programming language when they are surrounded by body text. database table names. and names of installation. and menu options. for example. messages n Source code or syntax quoted directly from a program n File and directory names and their paths.com Textual cross-references to an internet address /example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web 123456 Hyperlink to an SAP Note. for example. These include field labels. “Enter your <User Name>”. SAP Note 123456 Example n Words or characters quoted from the screen. names of variables and parameters. for example. SELECT and INCLUDE EXAMPLE Keys on the keyboard 12/18/2012 PUBLIC 113/116 . menu options Example Emphasized words or expressions Example Words or characters that you enter in the system exactly as they appear in the documentation http://www. for example. and database tools EXAMPLE Technical names of system objects. pushbutton labels. Example Example Arrows separating the parts of a navigation path. for example. screen titles. transaction codes. n Cross-references to other documentation or published works Example n Output on the screen following a user action. upgrade. Google Maps. All rights reserved. Gmail. The information contained herein may be changed without prior notice. iPhoto. HTML. IBM. VideoFrame. Google Store. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. DB2 Universal Database. pureScale. HACMP. Google Mobile Ads. Acrobat. System i5. ICA. POWER. and Smarter Planet are trademarks or registered trademarks of IBM Corporation. BlackBerry Torch. App Store. Power Systems. iPod. and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google Checkout. OS/2. RACF. Google App Engine. Google Data API. Windows. z/OS. StreamWork. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. DB2. Google Apps. POWER6. BlackBerry Pearl. System z. Google Updater. SAP HANA. Google Sync. Excel. and W3C are trademarks or registered trademarks of W3C®.sap. Wi-Fi is a registered trademark of Wi-Fi Alliance.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. PowerPoint. OS/390. OSF/1.com © Copyright 2012 SAP AG. iTunes. Duet. AIX. PostScript. XIV. GPFS. Google Mobile. BlackBerry PlayBook. BlackBerry Bold. Microsoft. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. Safari. IOS is a registered trademark of Cisco Systems Inc. DB2 Connect. zEnterprise. Massachusetts Institute of Technology. System x. Motorola is a registered trademark of Motorola Trademark Holdings LLC. System p. and Xcode are trademarks or registered trademarks of Apple Inc. Storwize. PowerHA. X/Open. Google Voice. System z10. INTERMEC is a registered trademark of Intermec Technologies Corporation. Citrix. ByDesign. Adobe. and Visual Studio are registered trademarks of Microsoft Corporation. XHTML. YouTube. BlackBerry Storm. Google Mail. Power Architecture. System Storage. BlackBerry. Intelligent Miner. Silverlight. World Wide Web Consortium. Apple. BlackBerry Curve. Retina. BladeCenter. PowerPC. Tivoli. Bluetooth is a registered trademark of Bluetooth SIG Inc. WinFrame. 114/116 PUBLIC 12/18/2012 . Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. System i. XML. and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. POWER6+. Dalvik and Android are trademarks or registered trademarks of Google Inc. WebSphere. iBooks. POWER7. Redbooks. SAP. R/3. and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Google Mobile Updater. Multi-Touch. System p5. UNIX. iPad. PowerVM. z10. Informix. Program Neighborhood. PartnerEdge. SAP BusinessObjects Explorer. BlackBerry Storm2. iPhone. Siri. MetaFrame. Linux is the registered trademark of Linus Torvalds in the United States and other countries. the Adobe logo. Oracle and Java are registered trademarks of Oracle and its affiliates. RETAIN. BBM. and Motif are registered trademarks of the Open Group. Objective-C. RIM. z/VM. Outlook. SAP NetWeaver. SQL Anywhere. and SAP Group shall not be liable for errors or omissions with respect to the materials.2 from Michael Kay (http://saxon. Nothing herein should be construed as constituting an additional warranty.sf.2) / XSL-FO: V5. if any.Business Objects and the Business Objects logo. Crossgate is an SAP company.sap. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase 365. National product specifications may vary. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. m@gic EDDY.1 Gamma and XSLT processor SAXON 6. B2B 360°. All other product and service names mentioned are the trademarks of their respective companies. Crystal Reports. as is any decompilation of these components. iAnywhere.5. Disclaimer Some components of this product are based on Java™. Crossgate. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. BusinessObjects.net/). Business Objects is an SAP company. This document was created using stylesheet 2007-12-10 (V7. and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. These materials are subject to change without notice. Xcelsius. Data contained in this document serves informational purposes only. Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.com/instguides 12/18/2012 PUBLIC 115/116 . These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only. Crystal Decisions. Sybase is an SAP company. Web Intelligence. without representation or warranty of any kind. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. Sybase and Adaptive Server. XSLT version 1. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.sap.com © Copyright 2012 SAP AG. . Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. All rights reserved. zu welchem Zweck und in welcher Form auch immer.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.