Defines database settings by number, providing more options than SETDBSTATE.
SETDBSTATEITEM [optionNumber] ["appName"] ["dbName"] ["values"]
Note: It is most efficient to load the required database before you run the SETDBSTATE command, then stop and restart the database for the command to take effect.
Note: When changing sizes, valid size-entry units in ESSCMD are bytes (b), kilobytes (k), metabytes (m), gigabytes (g), or terabytes (t). Example: 8192b, 8k, 1m, ng, nt. If no size unit is given, the default unit is bytes (b).
optionNumber | An integer between 0 and 27, inclusive. This number corresponds to the options listed below. Enter 99 to be prompted for all options (in interactive mode). |
appName | Name of the application. Omit if the application is already selected using the SELECT command. |
dbName | Name of the database; required if appName is specified. |
values |
Acceptable value or values; these vary from
option to option.
0. Abort 1. Description
2. Allow Database to Start?
3. Start Database with Application?
4. Access Level
5. Data Cache Size
6. Aggregate Missing Values?
7. Two Pass Calc When [CALC ALL]?
8. Create Blocks on Equation?
9. Currency Database Name
10. Currency Conversion Type Member
11. Currency Conversion Type
12. Index Cache Size
13. Index Page Size
14. Data Compression on Disk?
15. Data Compression Type
16. Retrieval Buffer Size
17. Retrieval Sort Buffer Size
18. Isolation Level
Depending on which type of access you specify, ESSCMD prompts you for other parameters (or you can supply the values on the command line). If you choose 1 (committed access), ESSCMD prompts
for:
If you choose 2 (uncommitted access), ESSCMD
prompts for:
19. Pre Image Access?
20. Time Out
21. Number of blocks modified before internal commit
22. Number of rows to data load before internal commit
23. Add Disk Volume Definitions
ESSCMD prompts you for the following values, unless you supply them on the command line:
24. Modify Disk Volume Information
25. Delete Disk Volume Definition
For example, suppose you defined three volumes: first, C; then, E; then, D. Analytic Services considers D the third volume - definition number 3. Note: If you delete an application or database, Analytic Services does not remove the directory containing the application or database on a disk volume. The computer's operating system still shows the folder and file labels on the disk. However, you can reuse the same name of the application or database that you had removed on the disk volume. 26. Cache Memory Locking
27. Data File Cache Size
99. All Items
|
This command defines database settings by number, and provides more options than SETDBSTATE.
Enter:
SETDBSTATEITEM optionNumber ["application name"]
["database name"] ["values"]
optionNumber is a number between 0 and 99, corresponding to the itemized descriptions above. Values depend on the option you select. As with many other ESSCMD commands, if you issue only the SETDBSTATEITEM keyword in interactive mode, ESSCMD displays a list of all options. In interactive mode, you do not need to supply any values on the command line; ESSCMD prompts you for the required values.
Using the semicolon statement terminator (;) is optional in ESSCMD batch files. However, it is good practice to use the terminator with this command to signal the end of the parameter list. This is especially important if you omit some of the parameters and take their default values. If not all parameters are present, and the ; is omitted, ESSCMD looks for the remaining values in the next statement in the batch file, leading to unpredictable results.
The following example enables Committed access and Pre-image access, and specifies indefinite wait time:
SETDBSTATEITEM 18 "JTEMP" "JTEMPDB" "1" "Y" "1";
The following example allocates up to 4 GB on Volume E, sets a maximum file size of 1 GB, and specifies that data files should be stored only on E:
SETDBSTATEITEM 23 "SAMPLE" "BASIC" "1" "E" "4G" "2" "1G"
The following examples set the data cache value to 45000000 bytes. The difference between the first and second example is that the first example shows that the SELECT command was used to select the application and database. The second example illustrates that because the SELECT command was not used to select the application and database, the application and database must be specified in the SETDBSTATEITEM command line.
Example 1LOGIN "machinename" "admin" "password"; SELECT "Sample" "Basic"; SETDBSTATEITEM 5 45000000; LOGOUT; EXIT;Example 2
LOGIN "machinename" "admin" "password"; SETDBSTATEITEM 5 sample basic 45000000; LOGOUT; EXIT;
©2004 Hyperion Solutions Corporation. All Rights Reserved. http://www.hyperion.com |