Database Settings
The component allows you to define your preferences for the databases. The table in the right-hand part of the Administration Console displays in the left column the options and in the right one drop-down lists or entry fields for the settings. In the lower part of the table you find brief descriptions of the options (which are displayed when clicking them).
The settings that can be applied only to individual databases, are printed in blue in the table below.
| Option | Description |
|---|---|
| Save all parameters in the DB.INI file | All parameters for the administration of databases are saved in the DB.INI file. |
| Allow multiple connections | Enable multiple connections from one client computer. |
| Default access permissions to data * | Data permissions are set in the OLAP Server using the TABACC, DAC and MDAC cubes. This setting determines is how the server interprets an empty cell. |
| Visible Server | Select YES to display the console window, even if the server was started by the Communication
Manager.
Note: If the Console Window of the Infor BI OLAP Server is displayed and the active Windows user is logged off, the Infor10 OLAP Server is
shut down.
Caution: It is highly recommended to run OLAP Server not as "Visible Server" but as service
in a productive environment. Due to the closing behavior newer MS Windows operating
systems starting with Windows Vista kill the server process after ca. 5 seconds when
the "Close Window" event is detected. Therefore it cannot be assured that all cubes
are saved correctly.
|
| Default startup mode for new databases * | Defines the startup mode of new databases. |
| Startup mode (individual setting) | Defines the startup mode for the current database. |
| Check cubes * | Specifies at which event the cube integrity is checked. This check compares the cube
in memory to the cube on disk. If inconsistencies are found, they will be repaired
automatically.
|
| User who is allowed to connect to a database during the start of the Event Agent | Name of user who may connect to the database during the reservation mode when the Event Agent is started. |
| Case sensitivity for attribute values |
YES: Attribute value tests are case sensitive (default value until 5.2.0) NO: Attribute value tests are not case sensitive Applies only to searching in the dimension browser and in attribute driven subsets. |
| Use scientific format for the cube export |
Using the scientific format for the cube export allows the usage of exponents. YES: Scientific notation is used for the cube export (default format in Infor10 OLAP Server 10.0 and older). Using this notation the values have an exponent part, 9.99E-10 for example. NO: Decimal notation is used for the cube export. In this case all numbers smaller than 1E+100 are exported in decimal notation, numbers >= 1E+100 are exported in scientific notation. In both cases values smaller than 1E-10 are exported as 0. |
| Maximum calculation time | Maximum calculation time for a data call that is restricted by a pending write request. |
| Calculated values cache * | Cache for calculated values (rules calculated and consolidated values). ’0’ disables the cache, any value greater than 0 enables it. |
| Listen Port TCP | TCP port by which the server can be addressed via network. If no value is specified, the server selects automatically a free port. The specification of a TCP port makes sense, if you want to release just that port on a firewall. |
| Listen Port HTTP | Port on which the OLAP Server listens for HTTP XMLA requests. |
| Listen Port HTTPS | Port on which the OLAP Server listens for HTTPS XMLA requests. |
| HTTP/S session timeout * | Period of inactivity after which a HTTP/S user session ends automatically. |
| Repository Registration * | Name of the registration to be used in Repository. |
| Project name * | Name of the project to be used in Repository.
Note: ONE OLAP database retrieves the permissions and roles exactly from ONE OLAP Permission
Management in the Repository. The opposite way is impossible, it is not the OLAP Permission
Management transferring the data to the OLAP database.
|
| OLAP Permission Management | Alias for this database model in the OLAP Permission Management of the Repository. |
| Number of processors | Set this parameter for a slightly enhanced performance. Even with default settings OLAP is working fine on a multiprocessor computer. |
| Processor affinity mask | With this mask you instruct the operating system to run the OLAP Server on certain processors only. For additional information refer to the documentation of the WIN API 32 command SetProcessorAffinityMask which can be found in the documentation of the operating system. |
| Multicore calculation (for single user) * |
Divide a request into a number of tasks, depending on the number of available CPU cores. This setting can be applied at runtime. To apply the runtime settings, click the corrresponding server/database and select the Apply Runtime Settings command. |
| Undo files directory | Directory for storing undo files created during splashing. |
| Maximum number of cells for one splashing operation (equal allocation and absolute distribution only) | Maximum number of basic cells to be filled with one splashing operation. The limit is only valid for equal allocation and absolute distribution, all other splashing modes (weighted, external weighted, external weighted basic) are unlimited. |
| Allow rules during splashing |
NO: The algorithm does not allow rule calculations in cells changed by the algorithm or in the external source cell. YES: The algorithm does not check for cells calculated by rules. Due to this the calculated value can differ from the one entered by the user. |
| Size of the calculation block * |
Maximum number of cells for internal rule calculation during an export. Use scientific notation to avoid problems with the decimal separator (for example 1E6 instead of 1000000). This setting can be applied at runtime. To apply the runtime settings, click the corrresponding server/database and select the Apply Runtime Settings command. |
| Size of the calculation block for export * | Maximum number of cells for internal rule calculation during an export. Use scientific notation to avoid problems with the decimal separator (for example 1E6 instead of 1000000). |
| Calculation Slots | Number of slots that are used for a calculation. Each calculated slice and each rule cell reference needs one slot. This number limits the amount of simultaneously calculated requests and the recursion depth. Currently 1 slot represents 10kB of memory. |
| Automatic cube loading | Specifies which cubes are loaded immediately after starting the server: None, All, Listed |
| List of automatically loaded cubes (only for individual database setting) | List of the cubes which are loaded automatically. |
| Format of unique names | Defines the format of the unique element.
|
| Remove copies in OLAP subsets | Select YES to use only the first occurrence of an OLAP element during the conversion of OLAP subsets to Named Sets. |
| Allow reference to inaccessible members | If Yes, MDX statements can contain references to inaccessible members. |
| Connection string * | Connection string to the source dabatase (see Administrator Manual for details).
This setting can be applied at runtime. To apply the runtime settings, click the corrresponding server/database and select the Apply Runtime Settings command. |
*: This settings can be applied at runtime. To apply the runtime settings, click the corresponding server/database and select the Apply Runtime Settings command.
If you change the settings by modifying the ALEA.INI or DB.INI files, or by using a separate window within the MMC, the resulting changes are visible only if you first click another component and then click the changed component again.