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

Maintenance

Use this command to enable or disable the ability to perform any database maintenance activity by any other user in Longview.

When you are ready to make Database Maintenance changes to the Data Server repository, enable the Maintenance mode. While it is enabled, users can still connect and perform read-only queries. They can also perform locks, journal entry posting, and data submissions. These activities are suspended (not stopped) for the duration it takes the servers to commit and refresh user and symbol changes.

The time required for the servers to commit and refresh can be several seconds to several minutes. The length of time depends on several factors:

  • symbol and hierarchy sizes
  • use of other features, such as NDD or data translation
  • status of the Math queue. When user or symbol changes are committed, the submission queue is suspended and a suspend request is sent to the Math queue. All pending math jobs in the queue prior to this request must complete before the Math Server can be suspended and refreshed. When large math jobs are pending, long wait times may occur.

Selecting Maintenance or Exclusive

Do not confuse the Maintenance command with the Exclusive command:

Value

Description

Maintenance

  • allows users to connect and perform read-only queries
  • allows users to perform locks, journal entry posting, and submissions
  • may result in long wait times for maintenance activities, if many users are working in the application at the same time

Exclusive

  • used in conjunction with Maintenance
  • does not prevent users from connecting or performing read-only queries
  • prevents users from performing locks, journal entry posting, and submissions
  • can be invoked only if no pending submissions are taking place

Although you can use Maintenance alone to perform user and symbol maintenance when users are actively connected, querying, and submitting, in certain situations, you should use Exclusive in conjunction with Maintenance.

  • If you make changes to symbols while submissions are in queue, and those symbols are implicated within active submissions, invalid parent symbol totals may occur. In particular, be careful with the following types of symbol changes:
    • symbol weights
    • parent switching
    • virtual status
    • symbol deletion
    • symbol change from a parent symbol to a child symbol
    • symbol change from a child symbol to a parent symbol
  • If you are concerned that parent totals may calculate incorrectly, use Exclusive in conjunction with Maintenance, and then perform a full enterprise restatement.
  • If you change a user’s access from write to read-only while that user has an active submission, the submission may not proceed completely. In this situation, use Exclusive in conjunction with Maintenance.
Copy

Syntax

MAINTENANCE StatusType                                    

where:

  • StatusType can be one of the following:

    Value

    Description

    		 

    ON

    To allow the use of maintenance commands.

    OFF

    To stop the use of maintenance commands and refresh the servers.

Copy

Syntax example

MAINTENANCE ON 
...
MAINTENANCE OFF                                    

See also

For more information on restatements, see the Longview Application Administrator Guide.
Published:

Maintenance

Use this command to enable or disable the ability to perform any database maintenance activity by any other user in Longview.

When you are ready to make Database Maintenance changes to the Data Server repository, enable the Maintenance mode. While it is enabled, users can still connect and perform read-only queries. They can also perform locks, journal entry posting, and data submissions. These activities are suspended (not stopped) for the duration it takes the servers to commit and refresh user and symbol changes.

The time required for the servers to commit and refresh can be several seconds to several minutes. The length of time depends on several factors:

  • symbol and hierarchy sizes
  • use of other features, such as NDD or data translation
  • status of the Math queue. When user or symbol changes are committed, the submission queue is suspended and a suspend request is sent to the Math queue. All pending math jobs in the queue prior to this request must complete before the Math Server can be suspended and refreshed. When large math jobs are pending, long wait times may occur.

Selecting Maintenance or Exclusive

Do not confuse the Maintenance command with the Exclusive command:

Value

Description

Maintenance

  • allows users to connect and perform read-only queries
  • allows users to perform locks, journal entry posting, and submissions
  • may result in long wait times for maintenance activities, if many users are working in the application at the same time

Exclusive

  • used in conjunction with Maintenance
  • does not prevent users from connecting or performing read-only queries
  • prevents users from performing locks, journal entry posting, and submissions
  • can be invoked only if no pending submissions are taking place

Although you can use Maintenance alone to perform user and symbol maintenance when users are actively connected, querying, and submitting, in certain situations, you should use Exclusive in conjunction with Maintenance.

  • If you make changes to symbols while submissions are in queue, and those symbols are implicated within active submissions, invalid parent symbol totals may occur. In particular, be careful with the following types of symbol changes:
    • symbol weights
    • parent switching
    • virtual status
    • symbol deletion
    • symbol change from a parent symbol to a child symbol
    • symbol change from a child symbol to a parent symbol
  • If you are concerned that parent totals may calculate incorrectly, use Exclusive in conjunction with Maintenance, and then perform a full enterprise restatement.
  • If you change a user’s access from write to read-only while that user has an active submission, the submission may not proceed completely. In this situation, use Exclusive in conjunction with Maintenance.
Copy

Syntax

MAINTENANCE StatusType                                    

where:

  • StatusType can be one of the following:

    Value

    Description

    		 

    ON

    To allow the use of maintenance commands.

    OFF

    To stop the use of maintenance commands and refresh the servers.

Copy

Syntax example

MAINTENANCE ON 
...
MAINTENANCE OFF                                    

See also

For more information on restatements, see the Longview Application Administrator Guide.
For an optimal Community experience, Please view on Desktop