|
|
|
The extenddb command extends databases to new or existing locations.
The extenddb command has the following format:
extenddb –llocation [-uuser] [dbname…|-nodb] [-aarea_dir]
[-Udata,ckp,jnl,dmp,work|awork] [-rraw_pct] [-drop] [-alter]
Identifies the name of the new or existing location.
Specifies the effective user for the session, as described in Standard Flags and Parameters.
Specifies the list of databases to be extended. If no databases are to be extended, use the –nodb flag. This flag allows for the creation of a location without extending databases to it.
Also specifies the vnode, if required, as described in Standard Flags and Parameters.
Specifies the directory (area_dir) that the new location will point to. This option creates the full directory path below the ingres root location. Use this option when creating a new location only. Do not use it when extending a database to an existing location.
Note: On VMS, this option does not create the area.
Specifies the usage for the new location. Valid usages include data (database), ckp (checkpoint), jnl (journal), dmp (dump), work (work), and (awork) auxiliary work.
Specifies, for Raw locations, the percentage of the Raw Area to be allocated to this location. Use this option when creating a new location only. Do not use it when extending a database to an existing location.
Drops the specified location.
Modifies a location's usage to add data, ckp, jnl, dmp, or work areas.
|
|
|
This command extends the stockdb database to use the directory /disk1/loc1 as new data and work areas:
extenddb –lextraloc1 stockdb –a/disk1/loc1 –Udata,work
This command creates a location without extending databases to it:
extenddb –lextraloc2 –a/disk2/loc2 –Uckp,jnl –nodb
This command extends the employeedb database to an existing location:
extenddb –lextraloc3 –Udata employeedb