Register Login
Python Photoshop SAP Java PHP Android C++ Hadoop Oracle Interview Questions Articles Other

DBA Cockpit for Oracle

Updated May 18, 2018

Overview of the new DBA Cockpit

 

The DBA Cockpit is used in place of different transactions that were used for monitoring and administration up to now. The DBA Cockpit include the following transactions:

DB13 DBA planning calendar
DB13C Central planning calendar
DB12 Backup logs
DB14 DBA operation logs
ST04 Database Performance Analysis: Oracle database overview
DB02 Database Performance: tables and indices

The transactions listed above continue to be available, but the transaction codes were renamed to <previous transaction code>OLD. This means that the transaction codes are now ST04OLD, DB02OLD, DB12OLD, DB13OLD, DB14OLD, and DB13COLD.

Transaction DBACOCKPIT is used to call the DBA Cockpit. The DBA Cockpit has a navigation area that is visible in all the functions of the DBA Cockpit. This area contains a menu tree with the following access points:

- Performance (corresponds to the old transaction ST04)
- Space       (corresponds to the old transaction DB02)
- Jobs        (corresponds to the old transactions DB13, DB12, DB14, DB13C)
- Diagnostics

The individual functions of the DBA Cockpit are located beneath these four access points. You can call a function by clicking it.

Prerequisites for using the DBA Cockpit:

The prerequisites described here are required for monitoring and administration of the local system i.e  the system on which the DBA Cockpit is running.

  • Some performance monitors within the DBA Cockpit require special database objects. These objects are created using an SQL script.
  • *The new planning calendar requires BR*Tools 700 patch level 24 or higher.
  • Some functions in the DBA Cockpit require the Oracle Active Workload Repository. This Oracle option must therefore be available for selection

Additional corrections for the DBA Cockpit with Basis 7.00 Support Package 12 which are only corrected in Support Package 13:

  • The correction from Note 1042725 (DB02 Refresh terminates in short dump) needs to be implemented.
  • The correction from Note 1046668 (DBA Cockpit->Database->Overview causes a dump) needs to be implemented.
  • You must import the transport that is attached to Note 1052909 (Transport_for_NW04s_SP12_only.zip). It corrects various small errors in the system administration and planning calendar.
  • Implement the corrections from Note 1076147 (Incorrect status display of backups in planning calendar).
  • Implement the corrections from Note 1084949 (DBACOCKPIT: Incorrect status display in Central Calendar).


Additional corrections for the DBA Cockpit with Basis 7.00 Support Package 12 and 13 which are only corrected in Support Package 14:

  • Implement the corrections from Note 1081265 (DBACOCKPIT: Backup logs are not displayed).
  • Implement the corrections from Note 1076507 (DBACOCKPIT SQL error ORA-942 during access to table DBAD).
  • Implement the corrections from Note 1076716 (DBACOCKPIT: RFC connection cannot be entered).
  • Implement the corrections from Note 1084146 (Planning calendar: Incorrect selection using list box).
  • Implement the corrections from Note 1088211 (DBACOCKPIT: Error when editing planned actions).
  • Implement the corrections from Note 1100026 (DBACOCKPIT: Short dump DYNP_TOO_MANY_RADIOBUTTONS_ON).

Additional corrections for the DBA Cockpit with Basis 7.00 Support Package 12, 13, and 14 that are only corrected in Support Package 15:

  • Implement the corrections from Note 1110280 (DBACOCKPIT: Incorrect number of redo logs that are not saved).
  • Implement the corrections from Note 1108971 (DBACOCKPIT: Overview is incorrect in Central Calendar).
  • Implement the corrections from Note 1112726 (DBACOCKPIT: Button 'All' in 'DBA Logs' does not display data). This error occurs with Support Package 13 and Support Package 14 but not with Support Package 12.
  • Implement the corrections from Note 1113261 (DBA Cockpit: Incorrect display of external jobs in DB13).
  • Implement the corrections from Note 1107729 (DBACOCKPIT: Action list in planning calendar is incorrect).
  • Implement the corrections from Note 1134253 (DBACOCKPIT: Display error in external BRCONNECT actions).

Additional corrections for DBA Cockpit with Basis 7.00 Support Package 12, 13, 14, and 15 that are corrected only in Support Package 16:

  •  Implement the corrections from Note 1142791 (Planning calendar: Incorrect status in the daily overview).
  •  Implement the corrections from Note 1139787 (Planning calendar: Option for profile in "Verify DB" missing).
  •  Implement the corrections from Note 1164574 (Planning calendar: db_error for action 'Cleanup').
  •  Implement the corrections from Note 1164986 (DBA Cockpit: Incorrect status of periodically scheduled jobs).

Additional corrections for DBA Cockpit with Basis 7.00 Support Package 12, 13, 14, 15 and 16 that are corrected only in Support Package 17:

  •  Implement the corrections from Note 1166977 (DBACOCKPIT: Display error for backups with redo log).

Further corrections that you may have to implement in remote systems (ABAP) that are connected to the DBA Cockpit:

  • Implement the corrections from Note 1088975 (Short dump COMPUTE_INT_ZERODEVIDE in DB13).
  • Implement the corrections from Note 1077188 (DBACOCKPIT: RFC for remote systems cannot be configured).
  • Implement the correction from Note 1093883 (ORACLE: Function module DB6_PLAN_ADD_BATCH failed) in remote systems with Basis Release 640 if you want to use the planning calendar in the DBA Cockpit for these systems.


New planning calendar

(Transaction DB13 or Jobs -> DBA Planning Calendar in the DBA Cockpit menu tree)

The planning calendar previously used was replaced with the new calendar to meet legal requirements regarding the accessibility of screen programs.

The previously used planning calendar is still available in transaction DB13OLD. Completed actions are visible in both the old and new planning calendars. Actions that were scheduled in the old planning calendar also appear as scheduled in the new calendar. The reverse also applies: Actions that you have scheduled in the new planning calendar are also visible in the old calendar. However, there is one exception:

Periodically scheduled actions in the new planning calendar with a repetition period other than weekly (for example, hourly or daily) are not displayed in the old planning calendar.

This can lead to problems if the old and new planning calendar are used in parallel. We therefore advise against using both planning calendars at the same time.

Even if the old calendar is still usable, it now has the status "deprecated". For this reason, we recommend that you switch to the new calendar in the medium term, provided that you do not need to use it right away.

For more information about the new planning calendar, especially about the configuration and administration of external databases, see Note 1025707 and the documentation.

New central planning calendar

(Transaction DB13C or Jobs -> Central Calendar in the DBA Cockpit menu tree)

The new central planning calendar differs from the old planning calendar by having a different configuration for systems that are to be monitored. The old planning calendar is still available under transaction DB13COLD. The new central planning calendar uses the system configuration of the DBA Cockpit to add or remove systems.

To migrate the systems of the old central planning calendar to the new planning calendar, choose Administration -> Migration DB13C Configuration in the new central planning calendar.

New transaction DB02 (Space)
(Transaction DB02 -> Space in the DBA Cockpit menu tree)

Refer to Note 868063 and also to Note 1002840 if required.

Administration and monitoring of external databases

A feature of the DBA Cockpit is that you can monitor and administer external databases. This applies to both ABAP and non-ABAP systems.

Oracle databases and all other database systems supported by SAP can be connected as external databases. If you want to connect non-Oracle databases, the relevant database client software and the SAP database shared library must be installed.
(In this note, we assume that the system on which the DBA Cockpit is running is an Oracle database system. If this is not the case, but you intend to connect external Oracle databases, you must first install the Oracle database client software and the corresponding SAP database shared library.)

External Oracle databases are only supported as of Version 9.2.

If you need to connect external Unicode databases, the system on which the DBA Cockpit is running must be a Unicode system.

The connection of external databases requires a working secondary database connection; that is, there must be an entry in the DBCON table. When you add an external database in the system configuration of the DBA Cockpit, you can create a DBCON entry directly. The database user who is to be entered for the database connection must be the relevant schema owner, in other words, SAPR3, SAP<SID>, SAPSR3 or SAP<SID>DB. For dual-stack systems (that is, ABAP and Java stack in one database) or even for MCOD systems, you must select the database user who is defined as "TABLE_OWNER" in DBA_SYNONYMS for the tables 'SDBAH' and 'SDBAD' in the synonyms 'SAP_SDBAH' and 'SAP_SDBAD. If the explain is to be possible for each schema of the MCOD system or of the dual-stack system, the user must also have read authorization for the database
in the other schemas.

Before you connect an external Oracle database, the following requirements must be met:

    1. The script from Note 706927 must be executed on the external Oracle database.

    2. For the planning calendar (DB13) and the related transactions DB12 and DB14, you also need to configure either an RFC ABAP connection (only allowed for external ABAP systems) or a connection through SAP gateway or a remote shell. For more information, see Note 1025707.

    3. In addition, at least BR*Tools 700 patch level 24 (Oracle client 10) or BR*Tools 640 patch level 42 (Oracle client 9) must be installed on the external system.

    4. You should ensure the system time does not differentiate between the remote system and the system, on which the DBA cockpit runs. The deviation must not be longer that 60 seconds under any circumstance.


 

 

Recommended Posts:
×