dban_start 
Use this command to call the Database Analyzer program in Database Manager. You can also specify options for Database Analyzer.
While executing this command, Database Manager implicitly transfers the data of the database system administrator to the Database Analyzer program.
In case Database Analyzer is already active, only its status is displayed.
Prerequisites
You have the DBInfoRead server permission.
Structure
dban_start [<option_list>]
<option_list> : = <option> | <option> <option> ...
Option |
Description |
|---|---|
-c <level> |
Displays debugging information You can specify a value between 1 (low) and 4 (high). |
-d <database_name> |
Database name |
-delete <date> |
Deletes all analysis data and log files of Database Analyzer up to and including <date> Enter <date> in the format YYYYMMDD. |
-f <configfile> |
Name of the configuration file If you do not specify a configuration file, Database Analyzer uses the dbanalyzer<version>.cfg file in the <installation_path>\env directory. You can display the installation path using the dbm_getpath DBM command: dbmcli dbm_getpath InstallationPath For more information, see Database Manager CLI, dbm_getpath. |
-i |
Deletes any existing log files for the current day |
-keep <days> |
Database Analyzer automatically deletes all Database Analyzer files and directories that are older than <days>. |
-n <database_computer> |
Name of the computer on which the database is running If you specify the computer name, you must also use the –o option to specify the directory for the log files. |
-noenv |
Suppresses logging and output of the environment variables from the configuration file |
-nologo |
Suppresses the logo |
-o <outputdir> |
Directory for the log files If you start Database Analyzer on the computer on which the database is installed, you do not need to specify –o. If you do not specify -o, Database Analyzer uses the analyzer subdirectory in the run directory of the database. More information: Database Administration, Log Files |
-state |
Displays information about the running Database Analyzer |
-stop |
Stops Database Analyzer |
-t <interval>[,<number>] |
Time interval <number> between two analyses (in seconds) and the chosen number <interval> of analyses The system default for <interval> is 900 seconds. If you specify a value for <number>, Database Analyzer stops after this number of analyses. |
-trace <treshold> |
If the system needs longer than <threshold> milliseconds to calculate a Database Analyzer object (SQL statement, parameter, array, or monitor), it is logged in the <outputdir>/<date>/DBAN.trc trace file. |
-u <database_user>,<database_user_password> |
Name and password of the database user |
-V |
Displays the version of Database Analyzer |
-? |
Displays the Database Analyzer help |
Result
The output of the Database Analyzer program is displayed.
Example
Call Database Manager CLI, log on as the operator OLEG with the password MONDAY, connect to the database DEMODB, and call Database Analyzer.
Simultaneously change the time interval between two analyses to 300 seconds and limit the number of analyses to 4:
>dbmcli -u OLEG,MONDAY -d DEMODB dban_start –t 300,4
OK
0,OK: everything works fine
0,"C:\Program Files\sdb\programs\bin\dbanalyzer" -d DEMODB -u *,* -state
MaxDB Database Analyzer, The Performance Analysis Tool, Version 7.7.06.01
Copyright 2000-2008 by SAP AG
Using log directory: C:\Documents and Settings\All Users\Application Data\sdb\data\wrk\DEMODB\analyzer
INFO 13: Database Analyzer active in directory "C:\Documents and Settings\All Users\Application Data\sdb\data\wrk\DEMODB\analyzer".
Database = DEMODB
Node =
Rundirectory = C:\Documents and Settings\All Users\Application Data\sdb\data\wrk\DEMODB
Configfile = C:\Program Files\sdb\programs\env\dbanalyzer77.cfg
Protocoldirectory = C:\Documents and Settings\All Users\Application Data\sdb\data\wrk\DEMODB\analyzer
Interval = 300
Reconnect = false
ProcessID = 4180
SessionID = 404
Driver = MaxDB
Started = 2008–09–30 13:13:50
More Information
Database Analyzer documentation