DROP HISTORY CONFIGURATION

Use the DROP HISTORY CONFIGURATION command to drop a history configuration.

After you drop a history configuration, any existing but unloaded history files in the staging or loading area for that configuration will not be loaded. When the loading process attempts to load those files, it will not be able to find the associated history-logging configuration, and will move the files to the error directory ($NZ_DATA/hist/error).

Syntax

Syntax for dropping a history configuration:

DROP HISTORY CONFIGURATION <config_name>

Input

The DROP HISTORY CONFIGURATION command has the following input:

Table 1. DROP HISTORY CONFIGURATION input
Input	Description
<`config_name`>	The name of the history configuration to be dropped. You cannot drop the currently active configuration.

Outputs

The DROP HISTORY CONFIGURATION command has the following outputs:

Table 2. DROP HISTORY CONFIGURATION outputs
Output	Description
`DROP HISTORY CONFIGURATION`	Message is returned if the command is successful.
`ERROR: permission denied`	You must have Manage Security permission to drop a configuration.
`ERROR: <config-name> not found.`	The specified configuration name cannot be found.

Privileges

To drop a history configuration, you must satisfy at least one of the following criteria:

You must be the admin user.
You must be the owner of the history configuration.
Your account must have Manage Security and Drop permissions.

Usage

The following sample command drops the history configuration with the name basic_hist:

MYDB.SCH1(USER)=> DROP HISTORY CONFIGURATION basic_hist;