Manage cube properties

Cube properties provide information about cubes that are used in different processes. Some of these properties cannot be edited directly, they are updated by the system.

To view and manage cube properties, click Properties icon on the cube view toolbar.

Note:

Cube properties are stored in the }CubeProperties control cube. In some cases, this control cube may not be present on a Planning Analytics database. To create one, an administrator can run the following code in the Metadata section of a TurboIntegrator process:

CubeCreate( '}CubeProperties', '}Cubes','}CubeProperties' );

Element	Description
REPSTATUS	If a cube is replicated on the database, the value of RepStatus is `Copied`, otherwise this property value is empty. For more information, see Replicating Cubes.
SYNCVIEWS	For replicated cubes, this property indicates whether views are synchronized when the associated cube is synchronized.
SYNCRULE	For replicated cubes, this property indicates whether rules are synchronized when the associated cube is synchronized.
DEMANDLOAD	Indicates that a cube is automatically loaded when the database starts or is loaded 'on demand' only when a cube value is requested. By default, all cubes are loaded into memory when a database starts. While this allows fast access to data, it can consume significant resources. If your database contains infrequently accessed cubes, you can conserve resources by setting those cubes to load only when a client attempts to access the cube data. When a cube is loaded on demand, the value of the DemandLoad property is YES, otherwise the property value is NO.
TIME_DIMENSION	If a time dimension is defined for a cube, this property stores the name of the dimension.
MEASURES_DIMENSION	If a measures dimension has been defined for a given cube, this property stores the name of the dimension.
LOCK	When a cube is locked, this property stores the name of the client that has locked the cube.
VMT	For each cube, this property defines the time threshold, in seconds, beyond which the algorithm that stores Stargate views is triggered. If the time required to calculate a cube view surpasses the specified threshold, IBM® Planning Analytics attempts to store a Stargate view. If not enough memory is available to store the Stargate view, Planning Analytics purges the oldest Stargate view that is not currently in use, and continues to purge views in this manner until sufficient memory is made available. If no VMM value is specified the default value is 5 seconds. The valid range is 1 - 259,200 seconds.
VMM	For each cube, this property determines the amount of RAM reserved on the server for the storage of Stargate views. The more memory made available for Stargate views, the better the performance is. You must, however, make sure sufficient memory is available for the TM1 server to load all cubes. The value of VMM is expressed in kilobytes. If no VMM value is specified the default value is 128 kilobytes. The valid range for VMM is 0 - 2,147,483,647 KB. The actual upper limit of VMM is determined by the amount of RAM available on your system.
REPSCRNAME	For replicated cubes, this property stores the name of the source cube.
REPLICATION	For replicated cubes, this property stores the name of the replication connection with which the replicated cube is associated.
LOGGING	Indicates that logging is enabled for a cube. When cube logging is enabled, the value of this property is YES, otherwise the value is NO.
VIRTUALCUBE	Stores the name of the virtual cube. A virtual cube has no data loaded in it, but references data in other cubes by using rules.
SAPCLIENTID	Used when connecting to SAP. The client number that corresponds to the UI version on the SAP server to which you are connected.
SAPCLIENTLANG	Used when connecting to SAP. The language setting for the SAP system.
PROVIDERSTRING
SAPVARIABLESCLAUSE
SLICERMEMBERS
DATARESERVATIONMODE	Data Reservation (DR) is a server-related feature in TM1 that allows you to configure exclusive write-access to regions of a cube for individual users. By default, Data Reservation is not enabled. An administrator must enable and configure the feature before you can use the related TurboIntegrator and API functions to manage Data Reservations. You can enter the following values in English only. These keyword values are not translated: OFF Turns off the Data Reservation feature for the specific cube. The default value is OFF. REQUIRED This mode disables write access for all users for the entire cube and requires you to explicitly assign Data Reservations for any user that needs to write to this cube. For example, a user must have a Data Reservation on a cell if they want to write to that cell. REQUIREDSHARED This mode is a variation of the REQUIRED mode that allows Data Reservations for different users to overlap. All other aspects of this mode behave the same as REQUIRED mode. REQUIREDSHARED mode was implemented to accommodate overlapping requests that use multi-node edit capability in IBM Cognos TM1 Applications. This mode is the default assigned DR mode on all cubes represented by Cube Views or Manual Dependencies in TM1 Applications. In REQUIRED mode, the TM1 database restricts write access to a slice by allowing only a single user to have a reservation for a node at any one time. In REQUIREDSHARED mode the application must enforce this restriction if necessary. ALLOWED Maintains write access, based on security, for all users across the entire cube, but allows you to selectively restrict write access to an area of the cube by assigning Data Reservations to individual users. For example, ALLOWED mode sets aside a section of a cube for a specific user while keeping write access available for all other users to the rest of the cube.
ALLOWPERSISTENTHOLDS	Specifies whether cells continue to be excluded from data spreading after the user logs out and logs in again.
CALCULATIONTHRESHOLD	Sets the threshold for the calculation cache in terms of number of calculation steps. Setting the cube property overrides the global value CalculationThresholdForStorage that is defined in the tm1s.cfg file.
RULE_STATS	This property determines whether performance statistics are collected for the rules that are associated with the cube. To enable statistic collection, set the Rule_Stats property to YES. To disable statistic collection, set the property to NO, the default value). Rule_Stats is a dynamic property, meaning that it does not require a server restart to take effect. However, it can take up to 60 seconds for a dynamic property change to be applied on the TM1 server.
MAINTAIN_DETAILED_ FEEDER_MEMORY_STATS	A value of 'YES' for the ( cubeName, propertyName ) tuple turns on the detailed feeder memory used calculation. Note: The detailed feeder memory used calculation is intended to be used during pre-production as an aid to help design the cube. When this step is complete, the property value should be switched to 'NO', so that the much faster feeder memory used calculation is used during production.