Jump to: navigation, search


The arsdb command performs database-specific tasks for Content Manager OnDemand Servers. This includes Installation related tasks, Maintenance, Upgrades, and Special tasks like importing and exporting database tables. Check the Usage section for sample online help, and a description of each feature. Examples shows some common tasks completed with arsdb.


arsdb is used during the installation process to create the database, plus OnDemand's internal tables for metadata, and indexes inside those tables.

  arsdb -I ARCHIVE -ctrv

After the installation is complete, you must build the System Log, System Load, and System Migration Application Groups separately using the arssyscr command.

Common errors during this command are: ARS0147E and ARS4067E.


The IBM Content Manager OnDemand database needs routine maintenance to ensure performance and reliability. Depending on the volume and age of your system, you may want to run these options more or less frequently. While performing IBM CMOD database maintenance, it's possible to receive ARS0013E and ARS0014I messages, which alert you to errors or warnings from the database engine from CMOD. Investigate the error messages from the database with your local Database Administrator, or visit the Troubleshooting Content Manager OnDemand page.

  arsdb -I ARCHIVE -msv 

Regular backups are a wise part of any maintenance window. For online backups, use:

  arsdb -I ARCHIVE -zv 

And for offline backups, use:

  arsdb -I ARCHIVE -yv 

Special Note about Database Backups

arsdb is a great way to do very simple online or offline backups, regardless of your underlying database engine. Some companies prefer to do their database backups through a different method. For example, DB2 provides for incremental and differential backups, in addition to online or offline backups. There are also options for enabling database backup compression, or backing up directly to tape via a facility like Tivoli Storage Manager. You will want to work with your DBAs to ensure your backups are recoverable and complete, regardless of which method you choose.


In Content Manager OnDemand v7.1 and v7.1.1, upgrades to OnDemand that required database changes required you to export, drop, create, then import your CMOD metadata tables:

  arsdb -I ARCHIVE -xlvf
  arsdb -I ARCHIVE -dev
  arsdb -I ARCHIVE -trv
  arsdb -I ARCHIVE -ilvf

In CMOD 7.1.2.x, 8.x and 9.x, IBM has added the -u option to arsdb, allowing you to update the definitions inside the OnDemand database.

  arsdb -I ARCHIVE -uv 


This is the online help for arsdb included with CMOD v10.1.0.2:

$ arsdb 
ARS4010I Usage: arsdb [options] [table(s)]
	-c (DB2/MSSQL) Create the OnDemand database
	-d Drop the OnDemand system tables
	-e Drop the OnDemand system indexes
	-f Ignore DB Failures
	-F Do not prompt
	-g (DB2/MSSQL) Start the OnDemand database
	-h (DB2/MSSQL) Stop the OnDemand database
	-i Import data to the OnDemand system tables
	-I <od_inst> OnDemand instance name
	-k (DB2) Activate the OnDemand database
	-m (DB2/MSSQL) Run Maintenance for the OnDemand system tables
	-o <filename> Output file name
	-O OnDemand Distribution Facility (ODF)
	-r Create indexes for the OnDemand system tables
	-s Run statistics on the OnDemand system tables
	-t Create the OnDemand system tables
	-u Update the OnDemand system tables
	-v Verbose
	-x Export data from the OnDemand system tables
	-y <device> (DB2) Backup the OnDemand database offline to the device
	            (MSSQL) Complete OnDemand database backup to the device
	-Y <device> (DB2) Backup the OnDemand database tablespace(s) offline to the device
	-X (DB2 only) If -Y or -Z, don't backup tablespace USERSPACE1
	-z <device> (DB2) Backup the OnDemand database online to the device
	            (MSSQL) Differential OnDemand database backup to the device
	-Z <device> (DB2) Backup the OnDemand database tablespace(s) online to the device