DB13 - Detailed Information (MaxDB)

MaxDB

DB13 - detailed information

DB13 - detailed information

This page provides detailed information about the actions which can be scheduled in DB13 and where this transaction gets the status

information of the jobs.

Which programs are used for the actions that can be scheduled?

Details about some of the actions

How to identify the jobs executing the scheduled actions in transaction SM37

Sources of Information

Further information

Which programs are used for the actions that can be scheduled?

The actions which can be scheduled in transaction DB13/DB13C are stored in the dictionary table SDBAC. In the different columns of

this table, you'll find the information, which actions can be scheduled and what they do - not only for MaxDB but for all available

database platforms.

� Column DBSYS:

The different database platforms are distinguished by column DBSYS.

As of SAP Basis release 6.10 different actions can be scheduled for different MaxDB instances (OLTP database, liveCache, database

not used for SAP system, ...).

� Column CTYPE:

EXT for an external program from the list in transaction SM49,

REP for an ABAP report

� Column CNAME:

Logical command from the list in transaction SM49 or

name of the ABAP report respectively

� Column PSTRING:

Additional parameters of the command from the list in transaction SM49 (only used, when CTYPE = EXT).

Some of the PSTRING content is substituted by e.g. instance information during execution of the scheduled action.

Note: util_execute verify out of SDBAC is substituted by db_execute check data for database versions >= 7.5 as of Basis release 6.10

SP46, 6.20 SP58, 6.40 SP16

back to top

Details about some of the actions

Added by Melanie Handreck , last edited by Melanie Handreck on May 04, 2007 (view change)

Labels: maxdb, support, db13

SAP Basis Release Column DBSYS

3.1I to 4.6D ADABAS D

6.10, 6.20 SAP DB; SAP DB/BAS; SAP DB/LVC; SAP DB/ANY

6.40 SDB; SDB/LVC; SDB/ANY

Page 1 of 5DB13 - detailed information - SAP Community Network Wiki

03/08/2010http://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=MaxDB&title=DB13+-+detail...

Reports (REP) RSADAUP1, RSADAUP2, RSADAUP3

� These reports are used to update the optimizer statistics.

Up to SAP Basis release 6.40 these reports can only be used for the basis database of the SAP System.

� Up to 4.6D: the reports write one line per action into table SDBAADAUPD and additionally a log file (one file per action) into

the work directory of the SAP system: <number>.updstat, e.g. 000001.updstat.

� 6.10 to 6.40: the reports write one line per action into tables SDBAH, DBAML and DBAOPTL and a log files (one file per

action) into the work directory of the SAP system: <timestamp>.osc, <timestamp>.och, <timestamp>.osr

Report (REP) RSADAUP4

� This report is only used in SAP basis releases 6.10 to 6.40.

� It is used for Update Statistics (all objects) for liveCache. This report uses generated ABAP code. No other update statistics

actions are available for liveCache in DB13C.

� The report writes one line per action into table SDBAH and additionally a log file (one file per action) into the work directory

of the SAP system: <con_name>#<timestamp>.osc

External Command (EXT) XPU (for verify (only tables))

� Used only up to SAP Basis release 6.40.

� XPU is called to execute the database structure check (only used for "verify only tables"). This is only possible, if there's an

application server on the database server.

� Inserts one line per action into table SDBAADAUPD and additionally writes one file per action into the work directory of the

SAP system (e.g. 000002.chtab.err).

External Command (EXT) DBMCLI (for verify)

� DBMCLI ist used for "Verify all objects" as of SAP Basis release 4.6C.

� The action is logged in file dbahist.prt and in the dbahist subdirectory of the rundirectory. Precondition for this logging:

DBMServer parameter DBADTL is set to 1 (you can check this with DBMCLI command dbm_configget and set it with DBMCLI

command dbm_configset). This parameter is set to 1 by the CCMS automatically, when it is not yet set.

External Command (EXT) DBMCLI (for other actions)

� The action is logged in file dbahist.prt and in the dbahist subdirectory of the rundirectory.

Precondition for this logging: DBMServer parameter DBADTL is set to 1 (you can check this with DBMCLI command

dbm_configget and set it with DBMCLI command dbm_configset). This parameter is set to 1 by the CCMS automatically,

when it is not yet set.

back to top

How to identify the jobs executing the scheduled actions in transaction SM37

� Execution type of the action: External Command (EXT in Column CTYPE of table SDBAC)

� e.g. dbmcli, xbackup, xpu

Report Action

RSADAUP1 Create new optimizer/space statistics

RSADAUP2 Check optimizer statistics (sets "TOBDO" flags in table DBSTATC)

RSADAUP3 Refresh optimizer/space statistics (on tables with "TOBDO" flag in DBSTATC)



� A job with the prefix DBA:<short_name_for_action> is scheduled (e.g. DBA:SAVEALLNCHK___@040000/6014). When

this job starts at the scheduled time, it executes report RSADAJOB, which calls the external command.

� The job log contains the output of the external command.

� Execution type of the action: Report (REP in Column CTYPE of table SDBAC)

� e.g. RSADAUP1/2/3/4, RSSDBCOLTS, RSSDBCOLCC

� First a job with the prefix DBA:<short_name_for_action> is scheduled (e.g. DBA:UPD_CHECK_____@020000/7007).

When this job starts at the scheduled time, it executes Report RSADAJOB, which creates a second job to start

immediately.

� This job with the prefix DBA!<short_name_for_action> (e.g. DBA!UPD_CHECK_____@020000/7007) is started

immediately after the first one. It executes the report given in column CNAME of table SDBAC.

� So before the scheduled time, there is only the job which starts with DBA: in transaction SM37. After the scheduled time

there are two jobs: one starting with DBA: and one starting with DBA!. The second one is the one that performs the

action itself.

� The job log of the second job contains information about the DBA action.

Note: When an action is scheduled not for the basis database of the SAP system but e.g. for a liveCache or a remote MaxDB

instance (possible in transaction DB13 as of Basis 6.10 and in the DBACockpit as of Basis 7.00), the job name also contains the

DB13C/DBACockpit name of the instance concerned, e.g. DBA!COLLCLASSCO____LCA@105454/40

back to top

Sources of Information

SAP basis release 3.1I to 4.6D

� Action: Backups/Autosave Log/Verify all objects (3.1I to 4.6B and 4.6C SP < 51 and 4.6D SP < 42)

� The database kernel writes the action log into file dbm.knl and dbm.utl.

� Using DBMCLI command load_r3tab

� file dbm.knl is loaded into table CNHIST

� file dbm.utl is loaded into table CNREPRT

� load_r3tab is called

� when transaction DB13 is called or

� a refresh is performed in transaction in DB12 or

� when report RSADARFR is executed (note 650374).

� Transaction DB13 reads tables CNHIST and CNREPRT to get the return codes and logs of scheduled actions.

� Action: Backups/Autosave Log/Verify all objects (4.6C SP >= 51 and 4.6D SP >= 42)

� The database kernel writes the action log into file dbm.knl and dbm.utl.

� These files are directly read from the database server when the information is requested in transaction DB13.

� Action: Update Statistics

� Reports RSADAUP1/2/3 write

� one row per action into table SDBAADAUPD and

� long logs (one file per action) into the work directory of the SAP system (e.g. 000001.updstat)

� Transaction DB13 gets the return code of this action from table SDBAADAUPD.

� To display the long log the log file out of the SAP work directory is read (the number in column SAVID of table

SDBAADAUPD equals the number at the beginning of log file name (e.g. SAVID = 000001 -> file 000001.updstat))

� Action: Verify (only tables)

� XPU writes

� one row per action into table SDBAADAUPD and

� long logs (one file per action) into the work directory of the SAP system (e.g. 000002.chtab.err)

� Transaction DB13 gets the return code of this action from table SDBAADAUPD.

� To display the long log the log file out of the SAP work directory is read (the number in column SAVID of table

SDBAADAUPD equals the number at the beginning of log file name (e.g. SAVID = 000002 -> file 000002.chtab.err))

SAP basis release 6.10 to 6.40



Contact Us Site Index Marketing Opportunities Legal Terms Privacy Impressum

� When transaction DB13 is started, function module UPDATE_SDBAH_FOR_SYSID_SDB is executed. This

1. loads data of directory DBAHIST into table SDBAHSDB (backup actions, verify with dbmcli, ....)

2. loads update statistics entries of SDBAH into SDBAHSDB

3. loads update statistics and verify entries of SDBAADAUPD into SDBAHSDB

4. loads all entries of SDBAHSDB into SDBAH

5. deletes actions older than 1 year (older versions: 3 months) from SDBAH and SDBAHSDB

Steps 1. to 4. are actually performed by function module UPDATE_SDBAHSDB_SDB.

� Action: DBMServer commands (backups, autosave log, verify with dbmcli,...)

� DBMServer writes

� one entry per action into file dbahist.prt in directory dbahist and

� long logs (one file per action) into directory dbahist (e.g 20050101220000.sda)

� Precondition for this logging: DBMServer parameter DBADTL is set to 1 (you can check this with DBMCLI command

dbm_configget and set it with DBMCLI command dbm_configset). This parameter is set to 1 by the CCMS automatically,

when it is not yet set.

� Transaction DB13 gets the return code of this action from table SDBAH.

� To display the long log the log file out of the directory dbahist is read (using function module DBM_GETFILE which

works like DBMGETF). The log files of DBMServer actions are found using columns BEG and FUNCT of table SDBAH (e.g.

BEG = 200411110100, FUNCT = sdc -> File ID for DBM_GETFILE: DBADTL#200411110100.sdc)

� Action: Update Statistics for the basis database of the SAP System

� Reports RSADAUP1/2/3 write

� one entry per action into tables SDBAH, DBAML and DBAOPTL and

� long logs (one file per action) into the work directory of the SAP system (e.g. 20050101220000.osr)


� To display the long log the log file out of the SAP work directory is read. The log files are found with column BEG and

FUNCT in table SDBAH (e.g. BEG = 200411110100, FUNCT = osr -> file 200411110100.osr in the work directory of the

SAP system).

� Action: Update Statistics for a liveCache instance

� Report RSADAUP4 writes

� one entry per action into table SDBAH and

� long logs (one file per action) into the work directory of the SAP system (e.g. LCA#20050101220000.osc)


� To display the long log the log file out of the SAP work directory is read. The log files are found using the connection

name and columns BEG and FUNCT of table SDBAH (e.g. connection LCA, BEG=20050101220000, FUNCT=osc -> file in

the work directory of the SAP system: LCA#20050101220000.osc)

� Action: Verify (only tables) for the basis database of the SAP System

� XPU writes

� one line per action into table SDBAADAUPD and

� long logs (one file per action) into the work directory of the SAP system (e.g. 000002.chtab.err)


� To display the long log the log file out of the SAP work directory is read. The number in column SAVID of table

SDBAADAUPD equals the number at the beginning of the log file name (e.g. SAVID = 000002 -> file 000002.chtab.err in

the work directory of the SAP system).

back to top

Further information

Further information about directory dbahist can be found on page DBA History.

back to top



Powered by SAP NetWeaver



Documents

DB13 - Detailed Information (MaxDB)