• Increase font size
  • Default font size
  • Decrease font size

DB Sanity Command Line Arguments

Command Line Invocation

    dbsanity [options] <environment_name>



Short Option
Long Option
-i <check folder>
read the sanity check definitions from the specified folder (Default: ./test)
-o <report folder>
write the test reports to the specified folder (Default: ./result)
-c --clear
clear the report folder before generating the report (Default: don't clear)
creates a report which contains only failed checks
-a <version>
--appversion <version>
only perform checks that relate to the specified version
buffer database meta data
open a browser window with the report when checks are finished
-s <skin>
--skin <arg>
use skin (default: online, optional: offline)
-l <locale>
render the report using the specified locale (2 letter iso code)
-L <number>
--limit <number>
limits the number of reported defects per check to the specified value
limits the number of listed defect data rows per check to the specified value 
-t <table list>
--tables <table list>
perform checks only for the comma-separated list of tables
-T <tag list>
--tag <tag list>
perform only checks which have one or more of the specified tags
quiet mode
verbose mode
prints out DB Sanity's version number
keep the temoporary files (for developers)
print this help
makes DB Sanity compress the report in a ZIP file


Process Exit Code

When calling DB Sanity from another process, e.g. using a script file, you can now evaluate execution success from its process exit code: 0 stands for complete success, -1 signals that checks failed or resulted in an error.


Recommended further reading: Versioning DB Sanity Checks.