Creating statistics is very useful. Reorganize your tables and indexes if major modifications were made, otherwise do so from time to time.
The AE database is a Relational Database ManagementManagement ist der Funktionsbereich des Service Orchestrator, in dem die Verwaltung von Service Level Agreements (SLAs) durchgeführt wird. In diesem Bereich werden SLA-Definitionen erstellt, bearbeitet und gelöscht. Außerdem dient dieser Bereich auch der Verwaltung Ihrer Geschäftseinheiten. System (RDMS) that administers all scheduling data from a central point.
It contains objects, statistical data, job reports etc. In order to keep a well-performing AE database, Automic strongly recommends maintaining it regularly.
Specific database-configuration advices are provided in the following documents:
Note that data records should also be reorganized. This is easily done using the supplied utilities.
Description
Different areas are available for the tables:
|
Area |
Table name |
|---|---|
|
CODE, HACL, HOST, IY, JBA, JFA, JPA, JPOP, JPOV, JPP, JPPA, JPPC, JPPCV, JPPF, JPPO, JPPV, JPVA, MAND, OACL, OBLOB, OCA, OCV, ODOC, OEA, OET, OFA, OFC, OFS, OGA, OH, OHA, OHAA, OHAF, OHG, OHGF, OIA, OKA, OKB, OKC, OKD, OEO, OKG, OKZ, OLC, ONA, OOA, OOI, OPPF, OPSA, OPSE, OPSEA, OPU, OPUD, OPUDA, OQA, OQT, ORA, ORACL, ORADR, ORB, ORCON, ORET, ORLNK, ORSYS, OSA, OSLF, OSLOA, OSLOB, OT, OTA, OTI, OTZC, OUA, OVB, OVC, OVD, OVP, OV, OVT, OVW, OVX, OX, OY, OYD, OYR, OYW, UACL, USG, USR, USRG, USRP |
|
|
ECA, ECV, EEC, EEDB, EET, EFC, EH, EJ, EJPCV, EJPFV, EJPOP, EJPOV, EJPP, EJPPA, EJPPC, EJPPF, EJPPO, EJPPV, EJPVA, EOI, EPD, EPDC, EPPF, EPUD, EPUDA, EQT, ERB, ERET, ESTP, ETI, EV, EVP, EY |
|
|
ABLOB, ACA, ACLNT, ACMT, ACTEX, ACV, AFC, AH, AHG, AHGH, AJPCV, AJPFV, AJPOP, AJPOV, AJPP, AJPPA, AJPPF, AJPPO, AJPPC, AJPPV, AJPVA, APD, APDC, APPF, ARB, AUSR, AV, AWS, LAH, LASLM, LLOG, RH, RT, XAO, XRO |
|
|
FE, FH, FJPP, FJPPA, FJPPC, FJPPF |
|
|
MELD |
|
|
IPH, ISTMT, ITL, MQLS, MQMEM, MQSRV, MQ1CP001, MQ1CP0.N, MQ1WP, MQ2DWP, MQ2JWP, MQ2OWP, MQ2PWP, MQ2QWP, MQ2RWP, MQ2WP |
|
|
FIFO, IDS, INI, UC_ACLB, UC_ACLK, UC_ACLT, UC_AKTX, UC_ATYP, UC_CAR, UC_CHCK, UC_DBSYN, UC_HTYP, UC_INDEX, UC_JOBQ, UC_JOBQE, UC_JOBQT, UC_LIC, UC_MTYP, UC_OREF, UC_OTTYP, UC_OTYP, UC_OVFMT, UC_OVGB, UC_OVTYP, UC_PLATF, UC_REST, UC_RTYP, UC_SGRP, UC_STYP, UC_SVAL, UC_SVALF, UC_SVALM, UC_SVALU, UC_SVALV, UC_SYS, UC_TABLE, UC_VERSI, UC_XERR, UC_ZDU, UC_ZUTYP, VERSION, XREQ |
|
|
BH, BT, DIVDB, UC_TEMP, UC_TEMP1, UC_TEMP2, UC_TEMP3 |
|
|
non-used tables |
APA, PC, UC_JBA_REST, UC_SYNTX |
The IMAGE:\DB\_STRUCTURE\ACCESS folder of the delivery directory contains the database UC2003.mdb. It includes the AE database's structure and a description of the individual tables and columns.
The AE database's structural description is also available in the form of HTML files (IMAGE:\DB\_STRUCTURE\HTML).
The size of this table depends on the number of objects that have been created. Usually, it grows slowly. If the Version Management is used or Transport Cases are loaded and clients are copied, these tables grow rapidly. Use the provided utilities for deleting object versions, Recycle Bin contents or clients that are no longer used.
Creating statistics is very useful. Reorganize your tables and indexes if major modifications were made, otherwise do so from time to time.
The tables of this area contain information about the activities taking place in the AE system. Therefore, its size depends on the tasks that are shown in the Activity Window. Automic recommends specifying "Deactivate automatically" in order to keep control over table growth and avoid possible adverse effects on performance.
It is not possible to work with dynamic statistics because table entries change constantly. Automic recommends creating one-time statistics instead. Tables and indices must only be reorganized when there have been atypically large table movements. Usually, they do not have to be reorganized.
This area comprises the largest part of the AE database because it keeps growing slowly but surely. Its content depends on the ongoing activities and the corresponding reports. The "RT" table is the largest one. Significant changes in volume occur when clients are copied or deleted. Use the supplied utilities in order to archive and remove data.
Automic recommends creating statistics whenever data records have been reorganized. Tables and indices should also be reorganized on a regular basis.
Forecasts comprise a small area of the AE database because mostly not many forecasts are available.
Statistics must only be created once.
The table MELD is relatively large. It includes AE system messages and keeps growing constantly. Use the supplied utilities in order to reduce data amounts.
Automic recommends creating statistics whenever you have had data records reorganized. Reorganize tables and indices regularly.
Because processing is handled on a highly dynamic basis, the corresponding tables are mostly empty.
Creating statistics automatically is not useful. Automic recommends creating statistics once on a manual basis. Tables and indices must only be reorganized after unusually large table movements but not regularly. Example: The work processes block because of a database problem. The communication processes run as usual and write in the corresponding tables. These tables are not processed.
These tables are almost static; data amounts do not really change.
Statistics must only be created once. Tables do not have to be reorganized.
This area is mostly empty because the tables are only filled when data has been searched and the contents are deleted subsequently.
Do not create access statistics. Tables and indices must only be reorganized if there have been large table movements. No regular reorganization is necessary.
Statistics should be created when notable data records are available. Usually, this is done with several different data constellations. Check the effects of statistics in order to find out which ones are optimal for your AE database.
See also: