Modify a Database Definition (dbdefModify)

The dbdefModify command modifies an existing database definition object in the model, defining characteristics of the database according to attribute settings in the specified file.

ttGridAdmin dbdefModify filepath

Options

The dbdefModify command has the option:

Option Description

filepath

Path and name of the file containing the database definition that will modify the database definition object.

The file name must be of the form dbname.dbdef, where dbname is the name of the database.

Examples

This example modifies database1, created in Create a Database Definition (dbdefCreate). The database definition file database1.dbdef was updated to change the PermSize and TempSize:

% cd /sw/tten/grid/dbdefs
% more database1.dbdef
DataStore=/disk/databases/database1
LogDir=/disk2/logs
DatabaseCharacterSet=AL32UTF8
ConnectionCharacterSet=AL32UTF8
PermSize=512
TempSize=256

Modify the database definition object:

% ttGridAdmin dbdefModify  /sw/tten/grid/dbdefs/database1.dbdef
Database Definition database1 modified.

Notes

  • Database definition files are in odbc.ini format, as shown in the example, with attribute=value on each line. See Create a Database Definition (dbdefCreate) for additional discussion.

  • Data store attributes, as listed in List of Connection Attributes (for example, DataStore, DatabaseCharacterSet, LogDir, and Durability), are frozen once a database is created. Trying to change them using dbdefModify will have no effect on the database.

  • If the database exists and is loaded, changes by the dbdefModify command to first connection attributes do not take effect until you unload (dbUnload) and load (dbLoad) the database.

  • This command does not modify the database itself, only the database definition object.

  • The connectable object that was automatically created when the database definition object was created is also modified appropriately.

  • When you apply the model after modifying a database definition, new versions of all necessary configuration files are written to each data instance, with the applicable entry modified according to the dbdef settings. (Never edit configuration files manually. They are overwritten each time the model is applied.)

  • The specified definition completely replaces the previous definition, deleting previous attribute settings for the database definition and connectable definition. Attributes that were set previously but are not set in the new definition will take their default settings.