Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Performing administrative server tasks

Server tasks fall into two broad categories that are handled by different kinds of users. Tasks that involve managing the content of the database are handled by users with the appropriate permissions. Tasks that involve creating the database and configuring its servers are handled by the users with permissions to manage the database.

User maintenance tasks, including user access and permissions, cannot be performed using Longview Server Manager. These require the use of Longview Application Administrator.

For information on user and group maintenance, see the Longview Application Administrator Guide.

In this section, you can find information on these main topics:

Working with server status

This section outlines the means to determine and change the status of your server. Before you determine or change server status, you can analyze user data to determine how many users are connected to the server.

Determining server status

To determine the status of a server and its processes, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Click Actions and then click Status. The status of the server and its dependent processes is displayed in the Console pane.

    Text Description automatically generated

Changing server status

To change the status of a server, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. To change the server’s status, choose one of the following options:
    1. To restart a stopped server, select Actions > Start.
    2. To stop a running server, select Actions > Stop.
    3. To stop a running server immediately, select Actions > Stop Immediate.
    4. To reset error codes on a server, select Actions > Reset > Reset Server Warning.
    5. To reset the restatement error code, select Actions > Reset > Reset Restatement Warning.

Analyzing user data in Longview Server Manager

You can use Longview Server Manager to perform the following tasks related to user data analysis:

  • View a list of all users
  • View a list of currently connected users
  • View a list of user connection history

To analyze user data in Longview Server Manager:

  1. Open Longview Server Manager
  2. In the Server Explorer pane, select the server.
  3. Click View and then click User Connections. The User Connections pane comes into view.
  4. Choose one of the following options:
  5. To view a list of all users, click the Retrieve all users button. The list of all users appears in the User Connections pane

    Note: The Connected column indicates the current connection status of each user.

    1. To view the currently connected users, click the Retrieve currently connected users button. The list of currently connected users appears in the User Connections pane.
    2. To view the history of user connections for a certain number of days, type the desired number of days into the Days history field, and click the Retrieve user connection history button. The list of connected users for the desired number of days appears.

    Note: The Retrieve user connection history button is unavailable when the Days history field is blank. The Days history field is based on calendar days and always Includes results from the current day. For example, typing 0 in the Days history field retrieves users connected from 12:00 am on the current day up to the current time. Typing 1 in the Days history field retrieves all users connected from one day before the current day up to the current time.

  6. To sort the list of users, click the desired column heading to sort by that heading.
  7. When you are finished viewing user data, click Close in the User Connections pane.

Analyzing user data through User Reporting Views

Longview provides preconfigured User Reporting Views that you can query in Excel to view information for users, such as all users and groups in the system, along with their permissions, system activity, and information. You can use any method for querying database views; however, Longview recommends using Microsoft Excel in the manner described in this section.

To analyze user data through User Reporting Views, you must complete the following procedures:

  1. Add the relevant data source. For more information, see “Adding a Data Source”.
  2. Query the User Reporting Views in Microsoft Excel. For more information “Querying User Reporting Views”.

Adding a Data Source

Before you can view User Reporting views, you must add the required Data Source. Complete one of the following the procedures based on your database:

Adding a SQL Data Source

Before you can open User Reporting views in Microsoft Excel, you must add the related Data Source.

To add a SQL Data Source:

  1. Open Microsoft Excel on the Client machine.
  2. Click the Data tab.
  3. In the ribbon, click From Other Sources, and then click From Microsoft Query. The Choose Data Source dialog opens.

  4. Select <New Data Source> and click OK. The Create New Data Source dialog opens.

  5. Specify a name for the Data Source.
  6. Select the appropriate driver for the data source. For example, SQL Server Native Client 10.0.
  7. Click Connect. The SQL Server Login dialog opens.

  8. Complete the following fields:
    FieldDescription

    Server

    Specify the server on which the database is hosted.

    Login ID

    Specify the login ID for the View User, as specified during installation.

    Password

    Specify the password for the View User, as specified during installation.

  9. Click OK. The Create New Data Source dialog appears.
  10. Click OK. The Choose Data Source dialog appears with the new Data Source in the list.
  11. Do one of the following:
    1. If you want to query User Reporting Views immediately, Click OK, and continue with step 6 of Querying User Reporting Views.
    2. Click Cancel to close the Choose Data Source dialog and query User Reporting Views later.

Adding an Oracle Data Source

This procedure assumes you have installed and configured the relevant Oracle Client application.

Note: If you are using OS authentication, extra steps are required. Contact Longview Support Services.

To add an Oracle Data Source:

  1. Open Microsoft Excel on the Client machine.
  2. Click the Data tab.
  3. In the ribbon, click From Other Sources, and then click From Microsoft Query. The Choose Data Source dialog opens.

  4. Select <New Data Source> and click OK. The Create New Data Source dialog opens.

  5. Specify a name for the Data Source.
  6. Select the appropriate driver for the data source. For example, Oracle in OraClient11g_home1.
  7. Click Connect. The Oracle ODBC Driver Connect dialog opens.

  8. Complete the following fields:
    FieldDescription

    Service Name

    Specify the Oracle Instance name on which the database is hosted.

    User Name

    Specify the user ID for the View User, as specified during installation.

    Password

    Specify the password for the View User, as specified during installation.

  9. Click OK. The Create New Data Source dialog appears.
  10. Click OK. The Choose Data Source dialog appears with the new Data Source in the list.
  11. Do one of the following:
    1. If you want to query User Reporting Views immediately, Click OK, and continue with step 6 of Querying User Reporting Views.
    2. Click Cancel to close the Choose Data Source dialog and query User Reporting Views later.

Querying User Reporting Views

Once you have added the required Data Source, you can query User Reporting Views in Microsoft Excel.

For information on adding a Data Source, see “Adding a Data Source”.

To open User Reporting Views:

  1. In Microsoft Excel, click the Data tab.
  2. In the ribbon, click From Other Sources, and then click From Microsoft Query. The Choose Data Source dialog opens.
  3. Select the Data Source that you created for your Longview database and click OK. The SQL Server Login dialog opens.
  4. Complete the following fields:
    FieldDescription

    Server

    Specify the server on which the database is hosted.

    Login ID

    Specify the login ID for the View User, as specified during installation.

    Password

    Specify the password for the View User, as specified during installation.

  5. Click OK. The Query Wizard - Choose Columns dialog opens.

  6. Click Options. The Table Options dialog opens.

  7. Select Views and clear all other options.
  8. For Owner, select the View User, as specified during installation.
  9. Click OK. The Query Wizard - Choose Columns dialog comes into view, populated with the User Reporting Views.

  10. Select one of the following User Reporting Views, and click the arrow:

    View

    Description

    LV_CombinedUserGroupAccess

    Select this View to retrieve a list of combined user and group access for each user for all users in the system.

    Note: This View does not list the resolved access for each user.

    LV_GroupAccessForAllUsers

    Select this View to retrieve a list of Group Access for each user for all users in the system.

    LV_GroupAccessForGroups

    Select this View to retrieve a list of Group Access for each group for all user groups in the system.

    LV_GroupActivity

    Select this View to retrieve a list of login activity for each user group in the system.

    LV_GroupAuthorizations

    Select this View to retrieve a list of all groups in the system along with their related authorizations.

    LV_Groups

    Select this View to retrieve a list of user groups in the system.

    LV_GroupUserMembership

    Select this View to retrieve a list of all groups with their associated user membership.

    LV_RoleAccess

    Select this View to retrieve a list of role access for all roles in the system.

    LV_UserAccessForAllUsers

    Select this View to retrieve a list of user access for all users in the system.

    LV_UserActivity

    Select this View to retrieve a list of user login activity.

    LV_UserAttributes

    Select this View to retrieve a list of user attributes in the system, along with the value of the attribute for users for which the attribute is set.

    LV_UserAuthorizations

    Select this View to retrieve a list of all users in the system along with their authorizations.

    LV_UserGroupMembership

    Select this View to retrieve a list of all users in the system with their associated domain and assigned groups.

    LV_UserInfo

    Select this View to retrieve a list of all users and their information. For example, name, email, and phone numbers.

    LV_UserPasswordActivity

    Select this View to retrieve a log of user password activity.

    LV_Users

    Select this View to retrieve a list of all users in the system.

  11. Click Next. The Query Wizard - Filter Data dialog opens.
  12. Optionally, use the Filter options as required to filter the query data.

  13. Click Next. The Query Wizard - Sort Order dialog opens.
  14. Optionally, use the Sort options to sort the query data.

  15. Click Next. The Query Wizard - Finish dialog opens.

  16. Select Return Data to Microsoft Excel and click Finish. The Import Data dialog opens.

  17. Edit the settings as necessary and click OK.
  18. The selected View appears in Microsoft Excel.

  19. Repeat steps step 2 to step 17 for the required Views.

Working with server queues

You can use Longview Server Manager to:

  • view the status of data submission queues
  • recover data submission queues from batch tables.

Viewing the status of server queues

When a user submits data to the Longview database, the submission moves through the appropriate servers until it is complete. You can use Longview Server Manager to view the status of data submission queues. You can perform this task whether you are a System Administrator or the Database Owner (DBO).

To view the status of the server queues, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To view the status of all server queues, click Tools, point to Queue, and then click All.
    2. To view the status of the Math server queue, click Tools, point to Queue, and then click Math.
    3. To view the status of the Submission server queue, click Tools, point to Queue, and then click Submission.
    4. To view the status of the Writer server queue, click Tools, point to Queue, and then click Writer.
    5. To view the status of the Elimination server queue, choose click Tools, point to Queue, and then click Elimination.

The status of the server queue you chose appears in the Console pane.

Recovering the status of submission queues (resume processing)

When a user submits data to the Longview database, each submission is logged in batch tables. When an error occurs during a batch submission, you can use Longview Server Manager to check the batch tables for the status of the submission queues, and resume processing any outstanding submissions after the issues have been resolved. You can perform this task only if you are the Database Owner (DBO).

To recover the status of submission queues and resume processing, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To check the status of all queues and resume processing outstanding batches in all queues, click Tools, point to Recover, point to Queue, and then click All.
    2. To check the status of the Math queue and resume processing outstanding batches in the Math queue, click Tools, point to Recover, point to Queue, and then click Math.
    3. To check the status of the Submission queue and resume processing outstanding batches in the Submission queue, click Tools, point to Recover, point to Queue, and then click Submission.
    4. To check the status of the Writer queue and resume processing outstanding batches in the Writer queue, click Tools, point to Recover, point to Queue, and then click Writer.
    5. To check the status of the Elimination queue and resume processing outstanding batches in the Elimination queue, click Tools, point to Recover, point to Queue, and then click Elimination.

    A confirmation dialog opens.

  4. Click Yes. The recovered server queue you chose appears in the Console pane.

Recovering the status of submission queues (do not resume processing)

When a user submits data to the Longview database, each submission is logged in batch tables. When an error occurs during a batch submission, you can use Longview Server Manager to check the batch tables for the status of the submission queues. You can perform this task only if you are the Database Owner (DBO).

To recover the status of submission queues, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To check the status of all queues in the batch tables, click Tools, point to Recover, point to Status, and then click All.
    2. To check the status of the Math queue in the batch tables, click Tools, point to Recover, point to Status, and then click Math.
    3. To check the status of the Submission queue in the batch tables, click Tools, point to Recover, point to Status, and then click Submission.
    4. To check the status of the Writer queue in the batch tables, click Tools, point to Recover, point to Status, and then click Writer.
    5. To check the status of the Elimination queue in the batch tables, click Tools, point to Recover, point to Status, and then click Elimination.
  4. The recovered server queue you chose appears in the Console pane.

Clearing outstanding batch submissions

When a user submits data to the Longview database, each submission is logged in batch tables. When an error occurs during a batch submission, you can use Longview Server Manager to check the batch tables for the status of the submission queues, and then clear any outstanding batches. You can perform this task only if you are the Database Owner (DBO).

To clear outstanding batch submissions, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To check the status of all queues and clear outstanding batches in all queues, click Tools, point to Recover, point to Clear, and then click All.
    2. To check the status of the Math queue and clear outstanding batches in the Math queue, click Tools, point to Recover, point to Clear, and then click Math.
    3. To check the status of the Submission queue and clear outstanding batches in the Submission queue, click Tools, point to Recover, point to Clear, and then click Submission.
    4. To check the status of the Writer queue and clear outstanding batches in the Writer queue, click Tools, point to Recover, point to Clear, and then click Writer.
    5. To check the status of the Elimination queue and clear outstanding batches in the Elimination queue, click Tools, point to Recover, point to Clear, and then click Elimination.
  4. A confirmation dialog opens.
  5. Click Yes. The outstanding batches are cleared for the server queue you chose.

Exporting and importing server data

You can use Longview Server Manager to export and import the data in the database tables.

Note: The database table structure is not exported or imported.

You can use the export and import utilities to perform several tasks.

Task

Description

clean up leaf data

You can use the export and import utilities to clean up:

  • data corresponding to deleted symbols
  • data corresponding to symbol indexes out of the valid range
  • non-static parent data
  • data with a value of 0.0
  • data with empty character strings

reorganize symbol indexes

You can collapse deleted symbol gaps, and then reorganize existing symbol lists, collapse out deleted symbols, and reindex all existing data to use the new index coordinates.

perform data transfers across platforms

The import and export utilities provide flexible data transfers by creating Longview-related binary files independent of the Longview database and server platform.

Note: When you export or import server data, the export or import files, respectively, are saved to a folder as specified by the RECALC_FILES server configuration parameter. For more information, see the Longview Installation Guide.

Exporting data from database tables

You can use Longview Server Manager to export the data in database tables. (However, you do not export the structure of the tables.) The export utility extracts data from the appropriate database tables, creating multiple binary files that can be stored or subsequently imported. (It does not export data from any tables whose name starts with klx_ic.)

To export data from database tables, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Click Tools and then click Export. The Export dialog opens.

    Graphical user interface, text, application, Word Description automatically generated

  4. Select from the following options:
    OptionDescription
    Export Name

    Enter the name that the export will be saved as.

    The export name cannot:

    • be more than 64 characters long.
    • cannot contain characters \ / * ? “ < > | % $ or spaces.

    Export all database information

    To export all system, system data, and leaf data tables. This includes metadata, journal entry, batch, locking, symbol statistics, shared files, models, and intercompany tables data.

    Use this option to:

    • reorganize the Longview database structure and optimize performance
    • export system tables and leaf data for the purpose of leaf-level repartitioning
    • copy the database to another Longview instance
    • create an exact backup of your database

    Export all database information except the leaf data

    To export data from main system tables in the Longview database, including metadata tables such as the dimension and symbol tables. In addition, journal entry, batch, locking, symbol statistics, shared files, models, and intercompany tables data is exported.

    Data from the leaf data tables is not exported.

    Use this option to copy the symbols and hierarchy of a database to another database, along with the additional tables.

    Export system information only

    To export data from only the main system tables in the Longview database, including metadata tables such as the dimension and symbol tables.

    Data from journal entry, batch, locking, symbol statistics, shared files, models, intercompany, and leaf data tables is not exported.

    Use this option to:

    • copy the symbols and hierarchy of a database to another database
    • reorganize the Longview database structure and optimize performance when no data exists

    Do not clean up deleted symbols and data

    To export data from the database in its raw state without removing, re-sequencing, or reorganizing deleted symbols.

    Use this option to create an exact snapshot of a database at a particular moment in time.

    Restrict to data affected by deleted symbols

    To export data from tables that would be affected by symbol re-indexing only.

    Use this option to reduce the number of tables to export and import. However, it is not suitable if you are using the Export utility to create a backup.

    Note: You can only select one of “Do not clean up deleted symbols and data ” or “Restrict to data affected by deleted symbols”. If you do not select either option, data is exported from the database and its indexes are reordered.

  5. Click OK. Data from the tables you selected is exported to Longview-related binary files that you can either store or import back into the Longview database.
  6. A dialog opens. To view the export log file, click OK. The log file opens. For more information, see “Working with log files”.

Importing data into database tables

You can use Longview Server Manager to import data into Longview database tables. You can perform this task only if you are the Database Owner (DBO). The Import utility reads binary files created by the Export utility, and restores the appropriate database tables. Importing data can save time when duplicating a data-base structure from one server to another, particularly when setting up a new server.

To import data into database tables, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Click Tools and then click Import. The Import dialog opens.

    Graphical user interface, application, Word Description automatically generated

  4. Select the following:
    OptionResult
    Export NameSelect the name of the export file to import.

    Force the servers to stop if users are connected

    This causes the servers to stop and any users to be disconnected.

    Perform a restatement after import is completed

    Once the binary files are imported, this option forces the system to run an immediate restatement.

    View import logs after import

    Selecting this option causes the log file to display automatically after the import process is complete. For more information, see “Working with log files”.

  5. Click OK. The binary files are imported, and the database tables are updated accordingly. Depending on the options you selected, a log file may be displayed, and a restatement may occur if the import process was successful.

Managing exports

You can use Longview Server Manager to manage your exports. Longview Server Manager allows you to see all your exports, as well as the version they were exported from and the date they were created.

From the list of exports, you can open the export log file associated with the export, delete the export or import.

  1. Open Longview Server Manager.
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane.
  3. The existing Exports are displayed in the content window.

Deleting export files

You can use Longview Server Manager to delete exports from your system.

To delete an export, follow these steps.

  1. Open Longview Server Manager
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane. The existing exports are displayed in the content window.
  3. Select the export you want to delete and click the Delete icon in the toolbar. A confirmation dialog opens.

    Note: The delete only deletes the export files. The export log file will remain.

  4. Click Yes to delete the export.

Viewing an export log file

You can use Longview Server Manager to view the export log associated with an export.

To view the export log file, follow these steps.

  1. Open Longview Server Manager
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane. The existing exports are displayed in the content window.
  3. Right-click the export you want to view the export log file and select View Log.

The log file opens in Microsoft WordPad. From here, you can read or save the file to local or network drives.

Importing an export

You can use Longview Server Manager to import a specific export from the view export list.

For more information on exporting and importing server data, see Exporting and importing server data.

To import the export, follow these steps.

  1. Open Longview Server Manager
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane. The existing exports are displayed in the content window.
  3. Right-click the export you want to import and select Import….

    Note: Note The export selected must match the version of the Longview data servers to be able to be imported.

  4. The Import dialog will open with the Export Name populated with the export that was selected.
  5. Select the option you want to use for this import and click OK.

Working with log files

You can use Longview Server Manager to analyze various types of data and activity in your system.

Longview Data Server Log tracking can help identify specific activities performed by individual System Administrators. For example, symbol maintenance, user maintenance, and server model maintenance activities are listed in the Longview Data Server Log (lv_dataserver.log).

Longview Server Manager also makes available other log files, such as restatement, import (impsys.log and impdata.log), and export (export.log) logs. These logs record the status of the restatement, import, or export, and if any errors occurred during the process. In addition it also displays any restatement error log files that were generated as a result of a failed restatement (restate_recalc_errors_<timestamp>.log) and archived lv_dataserver.log files.

Opening log files

You can use Longview Server Manager to view log files that contain information about various activities in your system.

To open log files in Longview Server Manager, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files are displayed in the content window.

  3. Double-click the appropriate log file. The log file opens in Microsoft WordPad. From here, you can read or save the file to local or network drives.

To display the log files by type switch to the details view by selecting Details in the View Menu.

Analyzing log files

Some log files (the Longview Data Server Log, for example) contain time stamp information that can be represented in a graphic array to provide a better sense of what processes ran at what time relative to one another. Server processes are listed in a graph on the vertical axis and plotted against time on the horizontal axis. Activity is indicated through the display of dots for intermittent activity and lines for continuous activity.

To view a graphic analysis of a log file, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files display in the content window.

    Graphical user interface, application, Word, Teams Description automatically generated

  3. Right-click the appropriate log file and select Analyze. A dialog opens displaying the server activity recorded by the log file.

    Note: The Analyze option may not be available for all log files.

  4. When you are finished reviewing the graph, click Close.

Archiving a log file

It is possible to archive the Longview Data Server Log, effectively preserving a snapshot of the file as it exists now for future reference.

To archive the Longview Data Server Log, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files are displayed in the content window.

  3. Right-click the lv_dataserver.log file and select Archive. The Archive Monitor File dialog opens.

  4. Specify a name for the archive file.
  5. Click Save. The archived version of the lv_dataserver.log file appears in the array of log files.

Deleting a log file

To remove a log file from the array, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files are displayed in the content window.

  3. Select the log file you want to delete and click the Delete icon in the toolbar. A confirmation dialog opens.

    Note: You cannot delete the Longview Data Server Log (lv_dataserver.log). However, you can delete an archived version of the lv_dataserver.log file.

  4. Click Yes to delete the log file.

Caching data in memory

You can create a memory cache configuration file to optimize the performance of your system. When you implement this feature, the system optimizes queries and submissions in the following ways:

  • Queries resolve from memory.
  • Submissions update the data loaded in memory and write through to the database.

The memory cache configuration file is specific to the Data Server and is a list containing database data tables and allocated memory blocks of specified sizes. The specified memory blocks are allocated into shared memory when the Data Server starts.

Note: You must select the Use Memory Cache configuration parameter to cache data in memory. For more information, see “Use Memory Cache”.

By caching the specified data in shared memory, all services across your Longview product that perform queries and submissions can interact with the data quickly. This means you can perform faster queries; however, the following should be considered before you set up the memory cache configuration file:

  • Initial server startup time increases while the servers generate the shared memory block files.
  • Additional memory is required.
  • The maximum size of specified data tables is predetermined.

Due to these considerations, Longview recommends caching data in memory only after implementing the following performance strategies:

  • Determining the source of possible performance loss is based on server-side queries and not submissions or restatements.
  • Creating a strong virtual parent strategy. For more information, see the Longview Application Administrator Guide.
  • Partitioning. For more information, see the Longview Application Administrator Guide.

If you are unsure whether to implement this feature, contact Longview Support.

Understanding the memory cache configuration file

The memory cache configuration file contains, per line, a comma-delimited list of database data table name, memory block size, and number of blocks. The memory cache configuration file must reside in the Data Server working directory and in the same folder as the lvsrvr.cfg file.

For example, in C:\Longview\DataServers\Longview.

Once you have created and saved the memory cache configuration file, you do not need to modify or maintain the file unless you decide to add or remove tables or increase the number or size of memory blocks.

When the Data Server starts, the system creates one file for every memory block specified in the memory cache configuration file. These files are stored in the location specified by the Memory Cache Files Location configuration parameter.

If you do not specify a location for the Memory Cache Files Location configuration parameter, the files are stored in the Memory Cache folder in the Data Server working directory at the same level as the lvsrvr.cfg and the memory cache configuration file.

For more information, see “Memory Cache Files Location”.

The block files are created with the naming convention

LVIM_<LID>_<TableName>_<block#>. For example, LVIM_LVCPM_KLX_ACN_P000_CELLS_1. These files are used as part of the shared memory caching process.

Caution: Do not modify the block files.

If you modify the memory cache configuration file, the system makes the following changes when the server starts:

If...

The system...

you change the block size of an already-specified block.

regenerates the block file with the appropriate block size.

you change the number of blocks for a specified table.

deletes the previously existing block files and then regenerates the appropriate number of block files.

you add a table.

adds the corresponding block file.

you remove a table.

removes the corresponding block file.

the Data Server shuts down due to unexpected external factors such as a power outage.

regenerates all block files using the data written to the database.

Memory cache configuration file syntax

TableName,BlockSize,Number

where:

  • TableName is the name of the database data table to put into the shared memory. You can include each database data table only once. For a list of database data tables, see “Data tables” in the Longview Installation Guide.
  • BlockSize is the size of the memory block for the specified data table, in bytes, and can be a number between 1024000 and 2147483648.
  • Number is the number of blocks for each data table. This allows you to use more than two gigabytes of memory for a single data table. For example, to specify three blocks for one data table, type 3. You cannot include more than 32767 blocks per data table.

Example

KLX_ULN_P000_CELLS,1024000000,1

KLX_ULS_P000_CELLS,1024000000,1

KLX_ULN_P001_CELLS,1024000000,1

KLX_ULN_P002_CELLS,2000000000,2

Creating the memory cache configuration file

You can create the memory cache configuration file using your preferred text editor. The memory cache configuration file must reside in the Data Server working directory and in the same folder as the lvsrvr.cfg file.

For example, in C:\Longview\DataServers\Longview.

Caution: You must allocate sufficient space for the memory cache before you create the memory cache configuration file. Failure to allocate space sufficiently may cause the system to run out of space during the submission of new data. If the system runs out of space during a submission, the data may be committed to the database but will not be visible to users until you increase the memory cache size and stop and restart the server.

To create the memory cache configuration file:

  1. In the Data Server working directory (for example: C:\Longview\DataServers\Longview) create a file named MemoryCacheSizes.txt.
  2. On each line, specify TableName,BlockSize,Number, separating parameters with commas. where:
    • TableName is the name of the database data table to put into the shared memory. You can include each database data table only once. For a list of database data tables, see “Data tables” in the Longview Installation Guide.
    • BlockSize is the size of the memory block for the specified data table, in bytes, and can be a number between 1024000 and 2147483648.
    • Number is the number of blocks for each data table. This allows you to use more than two gigabytes of memory for a single data table. For example, to specify three blocks for one data table, type 3. You cannot include more than 32767 blocks per data table.
  3. Save and close the file.
  4. Stop, and then restart, your Longview server.
Published:

Performing administrative server tasks

Server tasks fall into two broad categories that are handled by different kinds of users. Tasks that involve managing the content of the database are handled by users with the appropriate permissions. Tasks that involve creating the database and configuring its servers are handled by the users with permissions to manage the database.

User maintenance tasks, including user access and permissions, cannot be performed using Longview Server Manager. These require the use of Longview Application Administrator.

For information on user and group maintenance, see the Longview Application Administrator Guide.

In this section, you can find information on these main topics:

Working with server status

This section outlines the means to determine and change the status of your server. Before you determine or change server status, you can analyze user data to determine how many users are connected to the server.

Determining server status

To determine the status of a server and its processes, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Click Actions and then click Status. The status of the server and its dependent processes is displayed in the Console pane.

    Text Description automatically generated

Changing server status

To change the status of a server, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. To change the server’s status, choose one of the following options:
    1. To restart a stopped server, select Actions > Start.
    2. To stop a running server, select Actions > Stop.
    3. To stop a running server immediately, select Actions > Stop Immediate.
    4. To reset error codes on a server, select Actions > Reset > Reset Server Warning.
    5. To reset the restatement error code, select Actions > Reset > Reset Restatement Warning.

Analyzing user data in Longview Server Manager

You can use Longview Server Manager to perform the following tasks related to user data analysis:

  • View a list of all users
  • View a list of currently connected users
  • View a list of user connection history

To analyze user data in Longview Server Manager:

  1. Open Longview Server Manager
  2. In the Server Explorer pane, select the server.
  3. Click View and then click User Connections. The User Connections pane comes into view.
  4. Choose one of the following options:
  5. To view a list of all users, click the Retrieve all users button. The list of all users appears in the User Connections pane

    Note: The Connected column indicates the current connection status of each user.

    1. To view the currently connected users, click the Retrieve currently connected users button. The list of currently connected users appears in the User Connections pane.
    2. To view the history of user connections for a certain number of days, type the desired number of days into the Days history field, and click the Retrieve user connection history button. The list of connected users for the desired number of days appears.

    Note: The Retrieve user connection history button is unavailable when the Days history field is blank. The Days history field is based on calendar days and always Includes results from the current day. For example, typing 0 in the Days history field retrieves users connected from 12:00 am on the current day up to the current time. Typing 1 in the Days history field retrieves all users connected from one day before the current day up to the current time.

  6. To sort the list of users, click the desired column heading to sort by that heading.
  7. When you are finished viewing user data, click Close in the User Connections pane.

Analyzing user data through User Reporting Views

Longview provides preconfigured User Reporting Views that you can query in Excel to view information for users, such as all users and groups in the system, along with their permissions, system activity, and information. You can use any method for querying database views; however, Longview recommends using Microsoft Excel in the manner described in this section.

To analyze user data through User Reporting Views, you must complete the following procedures:

  1. Add the relevant data source. For more information, see “Adding a Data Source”.
  2. Query the User Reporting Views in Microsoft Excel. For more information “Querying User Reporting Views”.

Adding a Data Source

Before you can view User Reporting views, you must add the required Data Source. Complete one of the following the procedures based on your database:

Adding a SQL Data Source

Before you can open User Reporting views in Microsoft Excel, you must add the related Data Source.

To add a SQL Data Source:

  1. Open Microsoft Excel on the Client machine.
  2. Click the Data tab.
  3. In the ribbon, click From Other Sources, and then click From Microsoft Query. The Choose Data Source dialog opens.

  4. Select <New Data Source> and click OK. The Create New Data Source dialog opens.

  5. Specify a name for the Data Source.
  6. Select the appropriate driver for the data source. For example, SQL Server Native Client 10.0.
  7. Click Connect. The SQL Server Login dialog opens.

  8. Complete the following fields:
    FieldDescription

    Server

    Specify the server on which the database is hosted.

    Login ID

    Specify the login ID for the View User, as specified during installation.

    Password

    Specify the password for the View User, as specified during installation.

  9. Click OK. The Create New Data Source dialog appears.
  10. Click OK. The Choose Data Source dialog appears with the new Data Source in the list.
  11. Do one of the following:
    1. If you want to query User Reporting Views immediately, Click OK, and continue with step 6 of Querying User Reporting Views.
    2. Click Cancel to close the Choose Data Source dialog and query User Reporting Views later.

Adding an Oracle Data Source

This procedure assumes you have installed and configured the relevant Oracle Client application.

Note: If you are using OS authentication, extra steps are required. Contact Longview Support Services.

To add an Oracle Data Source:

  1. Open Microsoft Excel on the Client machine.
  2. Click the Data tab.
  3. In the ribbon, click From Other Sources, and then click From Microsoft Query. The Choose Data Source dialog opens.

  4. Select <New Data Source> and click OK. The Create New Data Source dialog opens.

  5. Specify a name for the Data Source.
  6. Select the appropriate driver for the data source. For example, Oracle in OraClient11g_home1.
  7. Click Connect. The Oracle ODBC Driver Connect dialog opens.

  8. Complete the following fields:
    FieldDescription

    Service Name

    Specify the Oracle Instance name on which the database is hosted.

    User Name

    Specify the user ID for the View User, as specified during installation.

    Password

    Specify the password for the View User, as specified during installation.

  9. Click OK. The Create New Data Source dialog appears.
  10. Click OK. The Choose Data Source dialog appears with the new Data Source in the list.
  11. Do one of the following:
    1. If you want to query User Reporting Views immediately, Click OK, and continue with step 6 of Querying User Reporting Views.
    2. Click Cancel to close the Choose Data Source dialog and query User Reporting Views later.

Querying User Reporting Views

Once you have added the required Data Source, you can query User Reporting Views in Microsoft Excel.

For information on adding a Data Source, see “Adding a Data Source”.

To open User Reporting Views:

  1. In Microsoft Excel, click the Data tab.
  2. In the ribbon, click From Other Sources, and then click From Microsoft Query. The Choose Data Source dialog opens.
  3. Select the Data Source that you created for your Longview database and click OK. The SQL Server Login dialog opens.
  4. Complete the following fields:
    FieldDescription

    Server

    Specify the server on which the database is hosted.

    Login ID

    Specify the login ID for the View User, as specified during installation.

    Password

    Specify the password for the View User, as specified during installation.

  5. Click OK. The Query Wizard - Choose Columns dialog opens.

  6. Click Options. The Table Options dialog opens.

  7. Select Views and clear all other options.
  8. For Owner, select the View User, as specified during installation.
  9. Click OK. The Query Wizard - Choose Columns dialog comes into view, populated with the User Reporting Views.

  10. Select one of the following User Reporting Views, and click the arrow:

    View

    Description

    LV_CombinedUserGroupAccess

    Select this View to retrieve a list of combined user and group access for each user for all users in the system.

    Note: This View does not list the resolved access for each user.

    LV_GroupAccessForAllUsers

    Select this View to retrieve a list of Group Access for each user for all users in the system.

    LV_GroupAccessForGroups

    Select this View to retrieve a list of Group Access for each group for all user groups in the system.

    LV_GroupActivity

    Select this View to retrieve a list of login activity for each user group in the system.

    LV_GroupAuthorizations

    Select this View to retrieve a list of all groups in the system along with their related authorizations.

    LV_Groups

    Select this View to retrieve a list of user groups in the system.

    LV_GroupUserMembership

    Select this View to retrieve a list of all groups with their associated user membership.

    LV_RoleAccess

    Select this View to retrieve a list of role access for all roles in the system.

    LV_UserAccessForAllUsers

    Select this View to retrieve a list of user access for all users in the system.

    LV_UserActivity

    Select this View to retrieve a list of user login activity.

    LV_UserAttributes

    Select this View to retrieve a list of user attributes in the system, along with the value of the attribute for users for which the attribute is set.

    LV_UserAuthorizations

    Select this View to retrieve a list of all users in the system along with their authorizations.

    LV_UserGroupMembership

    Select this View to retrieve a list of all users in the system with their associated domain and assigned groups.

    LV_UserInfo

    Select this View to retrieve a list of all users and their information. For example, name, email, and phone numbers.

    LV_UserPasswordActivity

    Select this View to retrieve a log of user password activity.

    LV_Users

    Select this View to retrieve a list of all users in the system.

  11. Click Next. The Query Wizard - Filter Data dialog opens.
  12. Optionally, use the Filter options as required to filter the query data.

  13. Click Next. The Query Wizard - Sort Order dialog opens.
  14. Optionally, use the Sort options to sort the query data.

  15. Click Next. The Query Wizard - Finish dialog opens.

  16. Select Return Data to Microsoft Excel and click Finish. The Import Data dialog opens.

  17. Edit the settings as necessary and click OK.
  18. The selected View appears in Microsoft Excel.

  19. Repeat steps step 2 to step 17 for the required Views.

Working with server queues

You can use Longview Server Manager to:

  • view the status of data submission queues
  • recover data submission queues from batch tables.

Viewing the status of server queues

When a user submits data to the Longview database, the submission moves through the appropriate servers until it is complete. You can use Longview Server Manager to view the status of data submission queues. You can perform this task whether you are a System Administrator or the Database Owner (DBO).

To view the status of the server queues, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To view the status of all server queues, click Tools, point to Queue, and then click All.
    2. To view the status of the Math server queue, click Tools, point to Queue, and then click Math.
    3. To view the status of the Submission server queue, click Tools, point to Queue, and then click Submission.
    4. To view the status of the Writer server queue, click Tools, point to Queue, and then click Writer.
    5. To view the status of the Elimination server queue, choose click Tools, point to Queue, and then click Elimination.

The status of the server queue you chose appears in the Console pane.

Recovering the status of submission queues (resume processing)

When a user submits data to the Longview database, each submission is logged in batch tables. When an error occurs during a batch submission, you can use Longview Server Manager to check the batch tables for the status of the submission queues, and resume processing any outstanding submissions after the issues have been resolved. You can perform this task only if you are the Database Owner (DBO).

To recover the status of submission queues and resume processing, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To check the status of all queues and resume processing outstanding batches in all queues, click Tools, point to Recover, point to Queue, and then click All.
    2. To check the status of the Math queue and resume processing outstanding batches in the Math queue, click Tools, point to Recover, point to Queue, and then click Math.
    3. To check the status of the Submission queue and resume processing outstanding batches in the Submission queue, click Tools, point to Recover, point to Queue, and then click Submission.
    4. To check the status of the Writer queue and resume processing outstanding batches in the Writer queue, click Tools, point to Recover, point to Queue, and then click Writer.
    5. To check the status of the Elimination queue and resume processing outstanding batches in the Elimination queue, click Tools, point to Recover, point to Queue, and then click Elimination.

    A confirmation dialog opens.

  4. Click Yes. The recovered server queue you chose appears in the Console pane.

Recovering the status of submission queues (do not resume processing)

When a user submits data to the Longview database, each submission is logged in batch tables. When an error occurs during a batch submission, you can use Longview Server Manager to check the batch tables for the status of the submission queues. You can perform this task only if you are the Database Owner (DBO).

To recover the status of submission queues, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To check the status of all queues in the batch tables, click Tools, point to Recover, point to Status, and then click All.
    2. To check the status of the Math queue in the batch tables, click Tools, point to Recover, point to Status, and then click Math.
    3. To check the status of the Submission queue in the batch tables, click Tools, point to Recover, point to Status, and then click Submission.
    4. To check the status of the Writer queue in the batch tables, click Tools, point to Recover, point to Status, and then click Writer.
    5. To check the status of the Elimination queue in the batch tables, click Tools, point to Recover, point to Status, and then click Elimination.
  4. The recovered server queue you chose appears in the Console pane.

Clearing outstanding batch submissions

When a user submits data to the Longview database, each submission is logged in batch tables. When an error occurs during a batch submission, you can use Longview Server Manager to check the batch tables for the status of the submission queues, and then clear any outstanding batches. You can perform this task only if you are the Database Owner (DBO).

To clear outstanding batch submissions, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Choose one of the following options:
    1. To check the status of all queues and clear outstanding batches in all queues, click Tools, point to Recover, point to Clear, and then click All.
    2. To check the status of the Math queue and clear outstanding batches in the Math queue, click Tools, point to Recover, point to Clear, and then click Math.
    3. To check the status of the Submission queue and clear outstanding batches in the Submission queue, click Tools, point to Recover, point to Clear, and then click Submission.
    4. To check the status of the Writer queue and clear outstanding batches in the Writer queue, click Tools, point to Recover, point to Clear, and then click Writer.
    5. To check the status of the Elimination queue and clear outstanding batches in the Elimination queue, click Tools, point to Recover, point to Clear, and then click Elimination.
  4. A confirmation dialog opens.
  5. Click Yes. The outstanding batches are cleared for the server queue you chose.

Exporting and importing server data

You can use Longview Server Manager to export and import the data in the database tables.

Note: The database table structure is not exported or imported.

You can use the export and import utilities to perform several tasks.

Task

Description

clean up leaf data

You can use the export and import utilities to clean up:

  • data corresponding to deleted symbols
  • data corresponding to symbol indexes out of the valid range
  • non-static parent data
  • data with a value of 0.0
  • data with empty character strings

reorganize symbol indexes

You can collapse deleted symbol gaps, and then reorganize existing symbol lists, collapse out deleted symbols, and reindex all existing data to use the new index coordinates.

perform data transfers across platforms

The import and export utilities provide flexible data transfers by creating Longview-related binary files independent of the Longview database and server platform.

Note: When you export or import server data, the export or import files, respectively, are saved to a folder as specified by the RECALC_FILES server configuration parameter. For more information, see the Longview Installation Guide.

Exporting data from database tables

You can use Longview Server Manager to export the data in database tables. (However, you do not export the structure of the tables.) The export utility extracts data from the appropriate database tables, creating multiple binary files that can be stored or subsequently imported. (It does not export data from any tables whose name starts with klx_ic.)

To export data from database tables, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Click Tools and then click Export. The Export dialog opens.

    Graphical user interface, text, application, Word Description automatically generated

  4. Select from the following options:
    OptionDescription
    Export Name

    Enter the name that the export will be saved as.

    The export name cannot:

    • be more than 64 characters long.
    • cannot contain characters \ / * ? “ < > | % $ or spaces.

    Export all database information

    To export all system, system data, and leaf data tables. This includes metadata, journal entry, batch, locking, symbol statistics, shared files, models, and intercompany tables data.

    Use this option to:

    • reorganize the Longview database structure and optimize performance
    • export system tables and leaf data for the purpose of leaf-level repartitioning
    • copy the database to another Longview instance
    • create an exact backup of your database

    Export all database information except the leaf data

    To export data from main system tables in the Longview database, including metadata tables such as the dimension and symbol tables. In addition, journal entry, batch, locking, symbol statistics, shared files, models, and intercompany tables data is exported.

    Data from the leaf data tables is not exported.

    Use this option to copy the symbols and hierarchy of a database to another database, along with the additional tables.

    Export system information only

    To export data from only the main system tables in the Longview database, including metadata tables such as the dimension and symbol tables.

    Data from journal entry, batch, locking, symbol statistics, shared files, models, intercompany, and leaf data tables is not exported.

    Use this option to:

    • copy the symbols and hierarchy of a database to another database
    • reorganize the Longview database structure and optimize performance when no data exists

    Do not clean up deleted symbols and data

    To export data from the database in its raw state without removing, re-sequencing, or reorganizing deleted symbols.

    Use this option to create an exact snapshot of a database at a particular moment in time.

    Restrict to data affected by deleted symbols

    To export data from tables that would be affected by symbol re-indexing only.

    Use this option to reduce the number of tables to export and import. However, it is not suitable if you are using the Export utility to create a backup.

    Note: You can only select one of “Do not clean up deleted symbols and data ” or “Restrict to data affected by deleted symbols”. If you do not select either option, data is exported from the database and its indexes are reordered.

  5. Click OK. Data from the tables you selected is exported to Longview-related binary files that you can either store or import back into the Longview database.
  6. A dialog opens. To view the export log file, click OK. The log file opens. For more information, see “Working with log files”.

Importing data into database tables

You can use Longview Server Manager to import data into Longview database tables. You can perform this task only if you are the Database Owner (DBO). The Import utility reads binary files created by the Export utility, and restores the appropriate database tables. Importing data can save time when duplicating a data-base structure from one server to another, particularly when setting up a new server.

To import data into database tables, follow these steps.

  1. Open Longview Server Manager.
  2. In the Server Explorer pane, select the server.
  3. Click Tools and then click Import. The Import dialog opens.

    Graphical user interface, application, Word Description automatically generated

  4. Select the following:
    OptionResult
    Export NameSelect the name of the export file to import.

    Force the servers to stop if users are connected

    This causes the servers to stop and any users to be disconnected.

    Perform a restatement after import is completed

    Once the binary files are imported, this option forces the system to run an immediate restatement.

    View import logs after import

    Selecting this option causes the log file to display automatically after the import process is complete. For more information, see “Working with log files”.

  5. Click OK. The binary files are imported, and the database tables are updated accordingly. Depending on the options you selected, a log file may be displayed, and a restatement may occur if the import process was successful.

Managing exports

You can use Longview Server Manager to manage your exports. Longview Server Manager allows you to see all your exports, as well as the version they were exported from and the date they were created.

From the list of exports, you can open the export log file associated with the export, delete the export or import.

  1. Open Longview Server Manager.
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane.
  3. The existing Exports are displayed in the content window.

Deleting export files

You can use Longview Server Manager to delete exports from your system.

To delete an export, follow these steps.

  1. Open Longview Server Manager
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane. The existing exports are displayed in the content window.
  3. Select the export you want to delete and click the Delete icon in the toolbar. A confirmation dialog opens.

    Note: The delete only deletes the export files. The export log file will remain.

  4. Click Yes to delete the export.

Viewing an export log file

You can use Longview Server Manager to view the export log associated with an export.

To view the export log file, follow these steps.

  1. Open Longview Server Manager
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane. The existing exports are displayed in the content window.
  3. Right-click the export you want to view the export log file and select View Log.

The log file opens in Microsoft WordPad. From here, you can read or save the file to local or network drives.

Importing an export

You can use Longview Server Manager to import a specific export from the view export list.

For more information on exporting and importing server data, see Exporting and importing server data.

To import the export, follow these steps.

  1. Open Longview Server Manager
  2. Click the Exports icon grouped under the Data Server icon in the Server Explorer pane. The existing exports are displayed in the content window.
  3. Right-click the export you want to import and select Import….

    Note: Note The export selected must match the version of the Longview data servers to be able to be imported.

  4. The Import dialog will open with the Export Name populated with the export that was selected.
  5. Select the option you want to use for this import and click OK.

Working with log files

You can use Longview Server Manager to analyze various types of data and activity in your system.

Longview Data Server Log tracking can help identify specific activities performed by individual System Administrators. For example, symbol maintenance, user maintenance, and server model maintenance activities are listed in the Longview Data Server Log (lv_dataserver.log).

Longview Server Manager also makes available other log files, such as restatement, import (impsys.log and impdata.log), and export (export.log) logs. These logs record the status of the restatement, import, or export, and if any errors occurred during the process. In addition it also displays any restatement error log files that were generated as a result of a failed restatement (restate_recalc_errors_<timestamp>.log) and archived lv_dataserver.log files.

Opening log files

You can use Longview Server Manager to view log files that contain information about various activities in your system.

To open log files in Longview Server Manager, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files are displayed in the content window.

  3. Double-click the appropriate log file. The log file opens in Microsoft WordPad. From here, you can read or save the file to local or network drives.

To display the log files by type switch to the details view by selecting Details in the View Menu.

Analyzing log files

Some log files (the Longview Data Server Log, for example) contain time stamp information that can be represented in a graphic array to provide a better sense of what processes ran at what time relative to one another. Server processes are listed in a graph on the vertical axis and plotted against time on the horizontal axis. Activity is indicated through the display of dots for intermittent activity and lines for continuous activity.

To view a graphic analysis of a log file, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files display in the content window.

    Graphical user interface, application, Word, Teams Description automatically generated

  3. Right-click the appropriate log file and select Analyze. A dialog opens displaying the server activity recorded by the log file.

    Note: The Analyze option may not be available for all log files.

  4. When you are finished reviewing the graph, click Close.

Archiving a log file

It is possible to archive the Longview Data Server Log, effectively preserving a snapshot of the file as it exists now for future reference.

To archive the Longview Data Server Log, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files are displayed in the content window.

  3. Right-click the lv_dataserver.log file and select Archive. The Archive Monitor File dialog opens.

  4. Specify a name for the archive file.
  5. Click Save. The archived version of the lv_dataserver.log file appears in the array of log files.

Deleting a log file

To remove a log file from the array, follow these steps.

  1. Open Longview Server Manager.
  2. Click the Log Files icon grouped under the Data Server icon in the Server Explorer pane. The existing log files are displayed in the content window.

  3. Select the log file you want to delete and click the Delete icon in the toolbar. A confirmation dialog opens.

    Note: You cannot delete the Longview Data Server Log (lv_dataserver.log). However, you can delete an archived version of the lv_dataserver.log file.

  4. Click Yes to delete the log file.

Caching data in memory

You can create a memory cache configuration file to optimize the performance of your system. When you implement this feature, the system optimizes queries and submissions in the following ways:

  • Queries resolve from memory.
  • Submissions update the data loaded in memory and write through to the database.

The memory cache configuration file is specific to the Data Server and is a list containing database data tables and allocated memory blocks of specified sizes. The specified memory blocks are allocated into shared memory when the Data Server starts.

Note: You must select the Use Memory Cache configuration parameter to cache data in memory. For more information, see “Use Memory Cache”.

By caching the specified data in shared memory, all services across your Longview product that perform queries and submissions can interact with the data quickly. This means you can perform faster queries; however, the following should be considered before you set up the memory cache configuration file:

  • Initial server startup time increases while the servers generate the shared memory block files.
  • Additional memory is required.
  • The maximum size of specified data tables is predetermined.

Due to these considerations, Longview recommends caching data in memory only after implementing the following performance strategies:

  • Determining the source of possible performance loss is based on server-side queries and not submissions or restatements.
  • Creating a strong virtual parent strategy. For more information, see the Longview Application Administrator Guide.
  • Partitioning. For more information, see the Longview Application Administrator Guide.

If you are unsure whether to implement this feature, contact Longview Support.

Understanding the memory cache configuration file

The memory cache configuration file contains, per line, a comma-delimited list of database data table name, memory block size, and number of blocks. The memory cache configuration file must reside in the Data Server working directory and in the same folder as the lvsrvr.cfg file.

For example, in C:\Longview\DataServers\Longview.

Once you have created and saved the memory cache configuration file, you do not need to modify or maintain the file unless you decide to add or remove tables or increase the number or size of memory blocks.

When the Data Server starts, the system creates one file for every memory block specified in the memory cache configuration file. These files are stored in the location specified by the Memory Cache Files Location configuration parameter.

If you do not specify a location for the Memory Cache Files Location configuration parameter, the files are stored in the Memory Cache folder in the Data Server working directory at the same level as the lvsrvr.cfg and the memory cache configuration file.

For more information, see “Memory Cache Files Location”.

The block files are created with the naming convention

LVIM_<LID>_<TableName>_<block#>. For example, LVIM_LVCPM_KLX_ACN_P000_CELLS_1. These files are used as part of the shared memory caching process.

Caution: Do not modify the block files.

If you modify the memory cache configuration file, the system makes the following changes when the server starts:

If...

The system...

you change the block size of an already-specified block.

regenerates the block file with the appropriate block size.

you change the number of blocks for a specified table.

deletes the previously existing block files and then regenerates the appropriate number of block files.

you add a table.

adds the corresponding block file.

you remove a table.

removes the corresponding block file.

the Data Server shuts down due to unexpected external factors such as a power outage.

regenerates all block files using the data written to the database.

Memory cache configuration file syntax

TableName,BlockSize,Number

where:

  • TableName is the name of the database data table to put into the shared memory. You can include each database data table only once. For a list of database data tables, see “Data tables” in the Longview Installation Guide.
  • BlockSize is the size of the memory block for the specified data table, in bytes, and can be a number between 1024000 and 2147483648.
  • Number is the number of blocks for each data table. This allows you to use more than two gigabytes of memory for a single data table. For example, to specify three blocks for one data table, type 3. You cannot include more than 32767 blocks per data table.

Example

KLX_ULN_P000_CELLS,1024000000,1

KLX_ULS_P000_CELLS,1024000000,1

KLX_ULN_P001_CELLS,1024000000,1

KLX_ULN_P002_CELLS,2000000000,2

Creating the memory cache configuration file

You can create the memory cache configuration file using your preferred text editor. The memory cache configuration file must reside in the Data Server working directory and in the same folder as the lvsrvr.cfg file.

For example, in C:\Longview\DataServers\Longview.

Caution: You must allocate sufficient space for the memory cache before you create the memory cache configuration file. Failure to allocate space sufficiently may cause the system to run out of space during the submission of new data. If the system runs out of space during a submission, the data may be committed to the database but will not be visible to users until you increase the memory cache size and stop and restart the server.

To create the memory cache configuration file:

  1. In the Data Server working directory (for example: C:\Longview\DataServers\Longview) create a file named MemoryCacheSizes.txt.
  2. On each line, specify TableName,BlockSize,Number, separating parameters with commas. where:
    • TableName is the name of the database data table to put into the shared memory. You can include each database data table only once. For a list of database data tables, see “Data tables” in the Longview Installation Guide.
    • BlockSize is the size of the memory block for the specified data table, in bytes, and can be a number between 1024000 and 2147483648.
    • Number is the number of blocks for each data table. This allows you to use more than two gigabytes of memory for a single data table. For example, to specify three blocks for one data table, type 3. You cannot include more than 32767 blocks per data table.
  3. Save and close the file.
  4. Stop, and then restart, your Longview server.
For an optimal Community experience, Please view on Desktop