Skip to main content


Define Caché databases.


[Databases]    Name=a,b,c,d,e, f


Each entry has up to six comma-separated arguments that define a database. The only argument that is required is the first, the directory specification. If the other arguments are not specified, then the default is used. From left to right:

  • Full directory specification for database file. Required.

  • Remote system name (empty for local system). If the system is remote (non-empty name), subsequent fields are ignored. Default is the local system.

  • Must mount at startup. 0 – Database is not mounted at startup (default). 1 – Database must be mounted at startup, or startup fails.

  • Cluster mount mode – 0 – Private mount (default), 1 – cluster mount (valid only for clustered systems.)

  • Mount at startup – 0 – Database is mounted when first accessed (default), 1 database attempts to be mounted at startup. If it fails, startup continues. Valid only for cluster databases; ignored for non-cluster databases. (To mount non-cluster databases at startup, use the third value, the Must mount at startup flag. Or mount the database explicitly in the ^%ZSTART routine using the SYS.DatabaseOpens in a new tab class.

  • Stream Location. Directory where the streams associated with this database go. The default is blank — "" (which InterSystems recommends.) This default location is in the subdirectory stream, underneath the database directory. For example, for a database located in c:\abc, the default stream location is c:\abc\stream.

By default even if they are not specified, the CACHESYS, CACHELIB, CACHETEMP, and CACHEAUDIT databases must be local to the system, private mounted, and mount required at startup.


In the [Databases] section, each line is a database with arguments Name=a,b,c,d,e,f. Here is an example from Windows:

; Database is on system SALESERVER
; Database is local and mount required
CLUSTER=dka300:[cluster],,,1      ; Database is cluster mounted

Example of remote databases without mirroring:


Example of remote databases with mirroring. Note in this mirrored example the two remote databases, both mirrored and non-mirrored, are formatted differently than they would be in a non-mirrored environment.

PRDAUDIT=:mirror:PRDMIRROR:PRDAUDIT,PRD - Mirrored remote database
PRDDCIFC=:ds:PRDDCIFC,PRD - Non-mirrored remote database
PRDERR=\cache\mgr\prderr\,,1 - Local database 
Range of Values

As described above.

Management Portal

On the page System Administration > Configuration > System Configuration > Local Databases, to add a new entry, select Create New Database. To edit an existing entry, select Edit in that entry's row.

FeedbackOpens in a new tab