RDB/VMS Relational Database Operator CHANGE_DATABASE — VMS RDB_4.0
Changes characteristics of the database root file and storage area files. When this statement executes, Rdb/VMS updates the characteristics named in the statement. All other characteristics remain the same. Example: RDO> CHANGE DATABASE FILENAME 'DISK2:[USER.TEST]PERSONNEL' cont> SNAPSHOT ALLOCATION IS 200.
Additional information available:
More
You need the Rdb/VMS ADMINISTRATOR privilege to use the CHANGE
DATABASE statement.
Use CHANGE DATABASE to:
o Define, change, and delete storage areas in multifile databases
o Enable or disable after-image journaling and change journal file
characteristics
o Enable or disable snapshot transactions and change snapshot file
characteristics
o Change a read/write storage area to read-only, or a read-only
storage area to read/write
o Change the number of recovery buffers
o Change physical parameters associated with the database
o Specify whether the database can be opened automatically or
manually
o Require the use of the data dictionary
Other users are not allowed to be attached to the database when you
issue the CHANGE DATABASE statement.
You cannot delete a storage area that is referred to in a storage
map.
Examples
Example 1
Use the CHANGE DATABASE statement to enable after-image
journaling:
CHANGE DATABASE PATHNAME 'PERSONNEL'
JOURNAL FILE IS 'DEPT3:PERSONNEL.AIJ'.
Example 2
You can also use CHANGE DATABASE to disable after-image journaling:
RDO> CHANGE DATABASE FILENAME 'PERSONNEL'
cont> NOJOURNAL.
Example 3
The database shutdown feature is designed to ensure that active users
on a single node or across a VAXcluster cannot access the database
while you perform administrative and maintenance tasks. For
instance, use this shutdown feature when you need the database in a
stable condition while performing backup and restore options, or when
you are tuning the database.
In the following example, a complete database shutdown is performed
for all users of a database residing on a common disk in a
VAXcluster. The CHANGE DATABASE ... OPEN IS MANUAL statement is
used to prevent new users from automatically opening that database
when the first DML statement is executed on the database.
$ RDO = "$RDO"
$ RDO CHANGE DATABASE FILENAME "$222$DUA17:[DBS]PERS" OPEN IS MANUAL.
$ REPLY/ALL "PERS.RDB database will be shut down in 15 minutes"
$ REPLY/ALL "Please complete any work with PERS before then"
$ WAIT 00:15:00.00
$ RMU/CLOSE/ABORT=FORCEX/CLUSTER $222$DUA17:[DBS]PERS
At this point, you are assured that no unprivileged users can invoke
this database and you can perform maintenance tasks (like tuning).
For example, you can add or delete indexes and compare the
performance results in a stable testing environment.
When you are ready to make the database available again across the
cluster, enter RDO and type:
RDO> CHANGE DATABASE FILE "$222$DUA17:[DBS]PERS"
cont> OPEN IS AUTOMATIC.
Example 4
The following example shuts down access to a clusterwide database and
then reopens the database for a specific node:
$ RDO = "$RDO"
$ RDO CHANGE DATABASE FILENAME "$222$DUA17:[DBS]PERS" OPEN IS MANUAL.
$ REPLY/ALL "PERS.RDB database will be shut down in 15 minutes"
$ REPLY/ALL "Please complete any work with PERS before then"
$ WAIT 00:15:00.00
$ RMU/CLOSE/ABORT=FORCEX/CLUSTER $222$DUA17:[DBS]PERS
$ !
$ SET HOST MADABT
.
.
.
$ ! On node MADABT now
$ RMU/OPEN $222$DUA17:[DBS]PERS
The RMU/OPEN command opens the PERS database on MADABT only. Users
logged into other nodes in the VAXcluster who normally have access to
the clusterwide database cannot access it until:
o The RMU/OPEN command is executed by a user with sufficient
privilege on his or her node.
o Or, the CHANGE DATABASE ... OPEN IS AUTOMATIC statement is
executed by a user with sufficient privilege from any node in the
VAXcluster.
Example 5
The following example shows how to disable snapshots on a database:
RDO> CHANGE DATABASE FILENAME 'PERSONNEL' SNAPSHOT IS DISABLED.
%RDMS-I-MODAREFLG, disabled snapshots
Example 6
The following example uses the CHANGE DATABASE statement to define a
new storage area for a multifile database:
RDO> CHANGE DATABASE FILENAME 'MF_PERSONNEL'
cont> DEFINE STORAGE AREA ARCHIVED_EMPS
cont> FILENAME DISK3:ARCHIVED_EMPS
cont> ALLOCATION IS 50 PAGES
cont> PAGE FORMAT IS MIXED
cont> SNAPSHOT_FILENAME IS DISK4:ARCHIVED_EMPS
cont> END ARCHIVED_EMPS STORAGE AREA.
Example 7
This example uses the DICTIONARY IS REQUIRED option to enforce use of
the data dictionary if metadata updates occur. Users must invoke the
database with the PATHNAME qualifier to perform any metadata changes.
Note that when you specify the DICTIONARY option, that is the only
option you can specify in a CHANGE DATABASE statement. To specify
other options, you must issue another CHANGE DATABASE statement.
RDO> CHANGE DATABASE FILENAME 'PERSONNEL'
cont> DICTIONARY IS REQUIRED.
Example 8
This example uses the READ_ONLY clause to change the ARCHIVED_EMPS
storage area to a read-only storage area.
RDO> CHANGE DATABASE FILENAME 'MF_PERSONNEL'
cont> CHANGE STORAGE AREA ARCHIVED_EMPS
cont> READ_ONLY.
Format
CHANGE DATABASE ─────────>───────────────────────────┐ ┌────────────────<────────────────<───────────────────┘ └┬─>──────────────────┬─┬─>
F
I
L
E
N
A
M
E ──> file-spec ─┬─┐ └─> db-handle ──> typebox (=) ─┘ └─>
P
A
T
H
N
A
M
E ──> path-name ─┘ │ ┌─────────────────────────────────────────────────────┘ └──┬──┬──> change-database-options1 ────────────────────┬──┬───> . │ ├──> change-database-options2 ────────────────────┤ │ │ ├──> change-journal-file-options ─────────────────┤ │ │ ├──> add-storage-area-clause ─────────────────────┤ │ │ ├──> change-storage-area-clause ──────────────────┤ │ │ └──>
D
E
L
E
T
E
S
T
O
R
A
G
E
A
R
E
A ──> storage-area-name ───┘ │ └───────────────────────────<────────────────────────────┘
Additional information available:
db-handlefile-specpath-namechange-database-options1change-database-options2
change-journal-file-optionsadd-storage-areachange-storage-area-clause
db-handle
A host language variable or name that you associate with the database. Use a database handle when you are accessing more than one database at a time.
file-spec
The name of the database file. Put the name in quotation marks.
path-name
The path name that refers to the data dictionary entity for the database. Put the name in quotation marks.
change-database-options1
change-database-options1 = ─┬─┬─────────────────────────>──────────────────────────────┬─┬─> │ ├──>
O
P
E
N typebox (I)typebox (S) ────────────┬──>
A
U
T
O
M
A
T
I
C ─┬──────────────┤ │ │ │ └──>
M
A
N
U
A
L ─────┘ │ │ │ ├──>
N
U
M
B
E
R typebox (O)F
V
A
X
C
L
U
S
T
E
R
N
O
D
E
S typebox (I)typebox (S) number-nodes ─────────┤ │ │ ├──>
N
U
M
B
E
R typebox (O)F
B
U
F
F
E
R
S typebox (I)typebox (S) ────> number-buffers ──────────┤ │ │ ├──>
N
U
M
B
E
R typebox (O)F
U
S
E
R
S typebox (I)typebox (S) ──────> number-users ────────────┤ │ │ ├──>
A
D
J
U
S
T
A
B
L
E
L
O
C
K
G
R
A
N
U
L
A
R
I
T
Y typebox (I)typebox (S) ─┬──>
E
N
A
B
L
E
D ───┬───┤ │ │ │ └──>
D
I
S
A
B
L
E
D ──┘ │ │ │ └──>
N
U
M
B
E
R typebox (O)F
R
E
C
O
V
E
R
Y
B
U
F
F
E
R
S typebox (I)typebox (S) ──> recovery buffers ─┘ │ └───────────────────────────<────────────────────────────────┘
Additional information available:
OPEN Optionsnumber-usersnumber-buffersnumber-nodes
recovery-buffers
OPEN Options
The OPEN options are OPEN IS AUTOMATIC and OPEN IS MANUAL. These options determine whether any user can open a previously unopened or a closed database by simply invoking it and executing a DML statement (OPEN IS AUTOMATIC, the default). When OPEN IS MANUAL is specified, only users with sufficient Rdb/VMS privilege (ADMINISTRATOR privilege) for the database can enter an explicit OPEN statement to open the database.
ADJUSTABLE_LOCK
Enables or disables adjustable locking granularity. The default is ENABLED.
number-users
The maximum number of users allowed to access the database at one time. The default is 50 users.
number-buffers
The number of buffers Rdb/VMS allocates per process using this database. Specify an unsigned integer between 2 and 32768. The default is 20 buffers.
number-nodes
Sets the upper limit on the maximum number of VAXcluster nodes from which users can access the shared database. The default is 16. The range is 1 node to 64 nodes.
recovery-buffers
The number of database buffers used during the automatic recovery process that is initiated after a system or process failure. Specify an unsigned integer between 2 and 32768. The default is 20 buffers.
change-database-options2
change-database-options2 = ─┬─┬──>──────────────────────>──────────────────────────────┬─┬─> │ ├──>
S
N
A
P
S
H
O
T typebox (I)typebox (S) ──┬─>
E
N
A
B
L
E
D ─┬───────>──────┬─┬───────┤ │ │ │ │ ├─>
I
M
M
E
D
I
A
T
E ─┤ │ │ │ │ │ │ └─>
D
E
F
E
R
R
E
D ──┘ │ │ │ │ │ └─>
D
I
S
A
B
L
E
D ────────>────────┘ │ │ │ ├──>
S
N
A
P
S
H
O
T
A
L
L
O
C
A
T
I
O
N typebox (I)typebox (S) ─> snp-pages ──> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ──────┤ │ │ ├┬─>
S
N
A
P
S
H
O
T
E
X
T
E
N
T typebox (I)typebox (S) ─┬──┬─> extent-pages ─> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ─┬─┤ │ │ │└─>
E
X
T
E
N
T
I
S ──────────┘ └─> (extension-options) ───┘ │ │ │ ├──>
R
E
A
D
O
N
L
Y ──────────────────────────────────────────┤ │ │ ├──>
R
E
A
D
W
R
I
T
E ─────────────────────────────────────────┤ │ │ └──>
D
I
C
T
I
O
N
A
R
Y typebox (I)typebox (S) ──────┬─>
R
E
Q
U
I
R
E
D ───────┬───────────┘ │ │ └─>
N
O
T
R
E
Q
U
I
R
E
D ───┘ │ └──────────────────<─────────────────────────────<───────────┘
Additional information available:
ENABLED-IMMEDIATEENABLED-DEFERREDDISABLEDREAD_ONLY
READ_WRITEDICTIONARY
snp-pagesextent-pagesextension-options
ENABLED-IMMEDIATE
Specifies that read/write transactions write copies of records to the snapshot file before those records are modified, regardless of whether a read-only transaction is active. The default is SNAPSHOT IS ENABLED IMMEDIATE. You enable snapshot writing to all snapshot files for all storage areas when you specify the SNAPSHOT IS ENABLED clause.
ENABLED-DEFERRED
Specifies that read/write transactions not write copies of records they modify to the snapshot file unless a read-only transaction is active. Read-only transactions that attempt to start after an active read/write transaction begins must wait for all active read/write users to complete their transactions. You enable snapshot writing to all snapshot files for all storage areas when you specify the SNAPSHOT IS ENABLED clause.
DISABLED
Disables snapshot transactions. If you use the SNAPSHOT IS DISABLED clause to disable snapshots on a multifile database, writing to all snapshot files for all storage areas is disabled.
snp-pages
The number of pages allocated for the snapshot file. The default is 100 pages.
extent-pages
The number of pages of each extent. The default is 100 pages.
extension-options
Specifies the MIN, MAX, and percent growth of each database file extent. Enclose the parameter list in parentheses. extension-options = ───> ( ───>
M
I
N
I
M
U
M typebox (O)F ──> min-pages ───> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S), ─┐ ┌────────────────────────────────────────┘ └──>
M
A
X
I
M
U
M typebox (O)F ──> max-pages ──> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S),─┐ ┌────────────────────────────────────────┘ └──>
P
E
R
C
E
N
T
G
R
O
W
T
H typebox (I)typebox (S) ───> growth ────> ) ───>
Additional information available:
min-pages
The minimum number of pages of each extent. The default is 99 pages.
max-pages
The maximum number of pages of each extent. The default is 9,999 pages.
growth
The percent growth of each extent. The default is 20 percent growth.
READ_ONLY
The READ_ONLY option is used to change a read/write RDB$SYSTEM storage area (and the Rdb/VMS system relations stored in the area) to read-only. You might choose the READ_ONLY option if your database is never or rarely updated. When the RDB$SYSTEM storage area is changed to read-only, locking conflicts occur less frequently, and the automatic updating of index and relation cardinality is inhibited. No write operation can be done in a read-only storage area except a cardinality update. See the RMU/ANALYZE/CARDINALITY help topic in the RMU help file for more information and restrictions on updating cardinalities. To change a storage area other than the RDB$SYSTEM storage area to read-only, or to change a database to read-only, use the READ_ONLY option of the change-storage-area-clause.
READ_WRITE
The READ_WRITE option is used to change a read-only RDB$SYSTEM storage area (and the Rdb/VMS system relations stored in the area) to read/write. Select the READ_WRITE option to change a read-only RDB$SYSTEM storage area to read/write. To change a storage area other than the RDB$SYSTEM storage area to read/write, or to change a database to read/write, use the READ_WRITE option of the change-storage-area-clause.
DICTIONARY
Determines whether the database must be invoked by path name for data definition changes to occur. If you specify the DICTIONARY IS REQUIRED option, the database must be invoked by path name to change metadata and the data dictionary will be maintained. If you specify the DICTIONARY IS NOT REQUIRED option, the database can be invoked by either file name or path name to change metadata. The default is DICTIONARY IS NOT REQUIRED. If you specify the DICTIONARY option, you cannot specify any other options in the same CHANGE DATABASE statement.
change-journal-file-options
change-journal-file-options = ─┬─┬─────────────────────────>────────────────────────────┬─┬─> │ ├─>
J
O
U
R
N
A
L
F
I
L
E
I
S ──> aij-journal-file-spec ─────────┤ │ │ ├─>
N
O
J
O
U
R
N
A
L ───────────────────>─────────────────────┤ │ │ ├─>
J
O
U
R
N
A
L
A
L
L
O
C
A
T
I
O
N typebox (I)typebox (S) ─> journal-blocks ─> typebox (B)typebox (L)typebox (O)typebox (C)typebox (K)typebox (S) ─┤ │ │ └─>
J
O
U
R
N
A
L
E
X
T
E
N
T typebox (I)typebox (S) ───> extent-blocks ──> typebox (B)typebox (L)typebox (O)typebox (C)typebox (K)typebox (S) ───┘ │ └───────────────────────────<──────────────────────────────┘
Additional information available:
aij-journal-file-specjournal-blocksextent-blocks
aij-journal-file-spec
The file specification for the after-image journal file. The journal file specification must be fully qualified and conform to VAX file naming conventions, except that the file specification must not include a DECnet node name. You can define a system logical name to refer to the journal file. If you do not include a file type in the journal file specification, Rdb/VMS assigns a default file type of AIJ.
journal-blocks
The number of blocks allocated to the after-image journal file. The default is 0 blocks.
extent-blocks
The size of each extent of the after-image journal file. The default is 512 blocks.
add-storage-area
Allows you to define a new storage area. add-storage-area-clause = ────>
D
E
F
I
N
E
S
T
O
R
A
G
E
A
R
E
A ───────> storage-area-name ───────────┐ ┌────────────────────────────────<──────────────────────────────┘ └────>
F
I
L
E
N
A
M
E ────> file-spec ───┬───────────────>───────────┬───┐ └──> storage-area-options ──┘ │ ┌──────────────────────────────────<───────────────────────────────┘ └──────────>
E
N
D ───┬─────────>───────────┬─> typebox (S)typebox (T)typebox (O)typebox (R)typebox (A)typebox (G)typebox (E) typebox (A)typebox (R)typebox (E)typebox (A) ────> └─>storage-area-name ─┘
Additional information available:
storage-area-namefile-specstorage-area-options
storage-area-name
The name of the storage area you want to create.
file-spec
The file specification for the storage area file. By default, this file has the default file type RDA.
storage-area-options
storage-area-options = ─┬┬───────────────────────────>─────────────────────────────────┬┬─> │├──>
A
L
L
O
C
A
T
I
O
N typebox (I)typebox (S) ───> number-pages ────>───────── typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ────┤│ │├──>
P
A
G
E
S
I
Z
E typebox (I)typebox (S) ────> page-blocks ─────>───────── typebox (B)typebox (L)typebox (O)typebox (C)typebox (K)typebox (S) ───┤│ │├──>
P
A
G
E
F
O
R
M
A
T typebox (I)typebox (S) ──┬────>
U
N
I
F
O
R
M ────┬────────────────────┤│ ││ └────>
M
I
X
E
D ──────┘ ││ │├──>
T
H
R
E
S
H
O
L
D
S typebox (A)typebox (R)typebox (E) ─> (─> val1─┬─────────────────────┬───> )─┤│ ││ └─> ,val2 ─┬────────┬─┘ ││ ││ └>,val3 ─┘ ││ │├──>
I
N
T
E
R
V
A
L typebox (I)typebox (S) ───────> number-data-pages ──────────────────┤│ │├──>
S
N
A
P
S
H
O
T
F
I
L
E
N
A
M
E
I
S ────> file-spec ────────────────────┤│ │├──>
S
N
A
P
S
H
O
T
A
L
L
O
C
A
T
I
O
N typebox (I)typebox (S) ───> snp-pages ───> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ────────┤│ │└┬─>
S
N
A
P
S
H
O
T
E
X
T
E
N
T typebox (I)typebox (S) ─┬──┬─> extent-pages ────> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ─┬───┘│ │ └─>
E
X
T
E
N
T typebox (I)typebox (S) ──────────┘ └─> extension-options ────────┘ │ └────────────────────────────<──────────────────────────────────┘
Additional information available:
number-pagespage-blocksnumber-data-pagesfile-specsnp-pages
extent-pagesextension-options
number-pages
The number of database pages allocated to the storage area initially. Rdb/VMS automatically extends the allocation to handle the loading of data and subsequent expansion. The default is 400 pages.
page-blocks
The size in blocks of each database page. Page size is allocated in 512-byte blocks. The default is two blocks (1024 bytes). If your largest record is larger than approximately 950 bytes, allocate more blocks per page to prevent records from being fragmented.
PAGE_FORMAT
Specifies whether a storage area contains UNIFORM or MIXED pages. You can use the PAGE FORMAT option with multifile databases only. In storage areas with uniform page format, all pages in a specific logical area contain records from the same relation. In storage areas with mixed page format, pages can hold records from different relations. The default is uniform.
THRESHOLDS
Specifies one, two, or three threshold values. The threshold values represent a fullness percentage on a data page and establish four possible ranges of guaranteed free space on the data pages. When a data page reaches the percentage defined by a given threshold value, the SPAM entry for the data page is updated to reflect the new fullness percentage and its remaining free space. The default thresholds are 70,85, and 95 percent. If you specify only one or two values, unspecified values default to 100 percent. You can specify the THRESHOLDS option only on a storage area for a multifile database. The storage area page format must be MIXED.
number-data-pages
Specifies the number of data pages between SPAM pages in the physical storage area file, and thus the maximum of data pages each SPAM page will manage. The default, and also the minimum interval, is 256 data pages. The first page of each storage area is a SPAM page. The interval you specify determines where subsequent SPAM pages are to be inserted, provided there are enough data pages in the storage file to require more SPAM pages. You can specify the INTERVAL option only on a storage area for a multifile database. The storage area page format must be MIXED.
file-spec
Provides a separate file specification for the snapshot file. Do not specify a file extension other than SNP to the file specification.
snp-pages
Specifies the number of pages allocated for the snapshot file. The
default is 100 pages. You can set the snapshot allocation to 0
pages. In the following cases, you may want to set the snapshot
allocation to 0 pages:
o If you have disabled snapshots. By setting the snapshot
allocation to 0, you may save space.
o If you have changed a read/write storage area to read-only. The
snapshot file is not used, and you can save space by setting the
snapshot allocation to 0 pages.
extent-pages
Specifies the number of pages of each extent. The default is 100 pages.
extension-options
Specifies the MIN, MAX, and percent growth of each database file extent. Enclose the parameter list in parentheses. extension-options = ───> ( ───>
M
I
N
I
M
U
M typebox (O)F ──> min-pages ───> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S), ─┐ ┌────────────────────────────────────────┘ └──>
M
A
X
I
M
U
M typebox (O)F ──> max-pages ──> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S),─┐ ┌────────────────────────────────────────┘ └──>
P
E
R
C
E
N
T
G
R
O
W
T
H typebox (I)typebox (S) ───> growth ────> ) ───> o min-pages Specifies the minimum number of pages of each extent. The default is 99 pages o max-pages Specifies the maximum number of pages of each extent. The default is 9,999 pages. o growth Specifies the percent growth of each extent. The default is 20 percent growth.
change-storage-area-clause
Allows you to modify the extent and snapshot allocation of a storage area. You cannot specify RDB$SYSTEM in the change-storage-area-clause. To change the EXTENT, SNAPSHOT ALLOCATION, or SNAPSHOT EXTENT for RDB$SYSTEM, specify these qualifiers as part of the change-database-options. When you specify these options as part of the change-database-options, they will be changed for RDB$SYSTEM but not for any other storage areas. change-storage-area-clause = ──────>
C
H
A
N
G
E
S
T
O
R
A
G
E
A
R
E
A ────────> storage-area-name ─────┐ ┌──────────────────────────────────<────────────────────────┘ └─┬─┬─┬─────────────────────────────>──────────────────────┬─┬─┬──> │ │ ├─>
R
E
A
D
W
R
I
T
E ──────────────────────────────────────┤ │ │ │ │ ├─>
E
X
T
E
N
T typebox (I)typebox (S) ─┬> extent-pages ──────── typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ─┬─────┤ │ │ │ │ │ └> extension-options ───────────┘ │ │ │ │ │ ├─>
S
N
A
P
S
H
O
T
A
L
L
O
C
A
T
I
O
N typebox (I)typebox (S) ──> snp-pages ───> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ─┤ │ │ │ │ └─>
S
N
A
P
S
H
O
T
E
X
T
E
N
T typebox (I)typebox (S) ─┬> extent-pages ──> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ─┬─┘ │ │ │ │ └> (extension-options) ────┘ │ │ │ └───────────────────────────────<────────────────────────┘ │ └─────>
R
E
A
D
O
N
L
Y ───────────────────────────────────────────┘
Additional information available:
snp-pagesextent-pagesextension-options
READ_WRITE
Used to change any read-only storage area (except the RDB$SYSTEM storage area) to a read/write storage area. To change a read-only RDB$SYSTEM storage area to read/write, you must use the READ_WRITE option of the change-database-options2 clause.
READ_ONLY
Used to change any read/write storage area (except the RDB$SYSTEM storage area) to a read-only storage area. To change a read/write RDB$SYSTEM storage area to read-only, you must use the READ_ONLY option of the change-database-options2 clause. You cannot change the parameters of a read-only storage area. You must first change the storage area to a read/write area, then change the parameters. Also, no write operation can be done in a read-only storage area except a cardinality update. See the RMU/ANALYZE/CARDINALITY help topic in the RMU help file for more information and restrictions on updating cardinalities.
snp-pages
Specifies the number of pages allocated for the snapshot file. The default is 100 pages.
extent-pages
Specifies the number of pages of each extent. The default is 100 pages.
extension-options
Specifies the MIN, MAX, and percent growth of each database file extent. Enclose the parameter list in parentheses. extension-options = ───> ( ───>
M
I
N
I
M
U
M typebox (O)F ──> min-pages ───> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S), ─┐ ┌────────────────────────────────────────┘ └──>
M
A
X
I
M
U
M typebox (O)F ──> max-pages ──> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S),─┐ ┌────────────────────────────────────────┘ └──>
P
E
R
C
E
N
T
G
R
O
W
T
H typebox (I)typebox (S) ───> growth ────> ) ───>
Additional information available:
min-pages
Specifies the minimum number of pages of each extent. The default is 99 pages.
max-pages
Specifies the maximum number of pages of each extent. The default is 9,999 pages.
growth
Specifies the percent growth of each extent. The default is 20 percent growth.
DELETE_STORAGE_AREA
Deletes the named storage area. You cannot delete the RDB$SYSTEM storage area. You cannot delete a storage area if a storage map refers to it, or if there is data in it.