Verify Database Dialog
The Verify Database dialog lets you set options for cleaning up a database and specifying an output log. Verifying a database can do the following:
• Delete unneeded disk files in a database directory
• Delete temporary and expired tables
• Remove all references to a specified table from the DBMS system catalogs
This dialog contains the following pages:
• General
• Options
• Output Log
These pages are described in the following sections.
For more information, see
Verify a Database.
General Page
This page lets you set the following options:
Effective User
Specifies the effective user name for the session. Valid only for a privileged user, DBA, or sessions that have the db_admin database privilege.
Note: This option does not assume the group of the effective user.
Mode
Specifies the mode in which the verification process executes. You can set the mode to one of the following:
report
Directs the verification to log its findings. Use this mode if you want the verification to only log, rather than actually delete, the tables or files that it finds.
run
Directs the verification to perform the specified operation and log all actions that it performs
runsilent
Tells the verification to perform the specified operations but turns off logging to the terminal. (Logging to the log file continues.)
Scope
Specifies at what level the verification is performed:
dbname
Directs the verification to operate on this database only
dba
Directs the verification to operate on all databases for which the currently logged in user is the DBA
installation
Directs the verification to operate on all operative databases in this installation. You must be a privileged user to use this option.
Operation
Specifies the operation to be performed during the verification. If report mode is specified, the files or tables found are not actually deleted, but only logged. The options for operation are:
accesscheck
Checks the database specified by the scope and returns a message that says whether the server can connect to the database and, if not, the reason. When using this option, you must also specify report mode.
You must be either a DBA or a privileged user to use this option. If you are a DBA and specify a scope of dba, you must be the DBA of all the listed databases. If you use a scope of dba, the verification checks all the databases for which you are the DBA. If you use a scope of installation, you must be a privileged user, and accesscheck checks all databases in the installation.
purge
Directs the verification to delete all disk files in the database directory that are no longer required. This operation is a combination of temp_purge and expired_purge.
temp_purge
Tells the verification to search for and delete all temporary tables from the database
expired_purge
Directs the verification to search for and delete all expired tables from the database.
Note: The expired_purge operation does not require exclusive access to the database, unlike other verification operations.
drop_table
Tells the verification to remove all references to a specified table from the DBMS system catalogs. If you specify this option, you must select a table in the next drop-down.
Table
Checks the specified table and reports any inconsistencies found, making recommendations to repair those inconsistencies. If you specify this option, you must select a table in the next drop-down.
The table operation cannot be used on core system catalogs. Secondary indexes can be checked but cannot be repaired. A table lock is taken during table verification operations, but a database lock is not taken. Use this option only when you are using report mode.
This operation also verifies referential integrity between the internal pointers for long data types stored in base table records and the extension table records they point to. Any inconsistencies are reported.
Caution! Using this option when you are in any run mode is not supported unless you are receiving assistance from Actian Support and are advised to do so; it can have severe, unexpected results.
xtable
Functions like the table option; however, xtable uses a stricter patch algorithm, which guarantees data integrity—with the risk that some valid data may be discarded. Use this option only when you are using report mode.
Caution! Using this option when you are in any run mode is not supported unless you are receiving assistance from Actian Support and are advised to do so; it can have severe, unexpected results.
dbms_catalogs
Checks the DBMS catalogs and reports any inconsistencies found, making recommendations to repair those inconsistencies. Use this option only when you are using report mode.
force_consistent
Permits entry into a database that is inconsistent. This does not fix the problem with the database; it merely allows you to force the database to act as if it were in a consistent state. This can be very dangerous if used against a production database. Hidden data damage may render one or more tables in the database unrecoverable at some time in the future. Use this option only when you are using report mode.
Caution! Using this option when you are in any run mode is not supported unless you are receiving assistance from Actian Support and are advised to do so; it can have severe, unexpected results.
refresh_ldbs
Directs the verification to ensure that a distributed database correctly reflects the release level of all remote databases that contain objects registered to the distributed database. We recommend that you run this operation on a distributed database after you run upgradedb (see Ingres Command Reference Guide) on any of the remote databases accessed by the distributed database. For more information about using this parameter, see the Ingres Star User Guide.
The distributed databases are specified by the Scope parameter. For the refresh_ldbs option only, the verification skips all non-distributed databases and processes only distributed databases. (In all other cases, the verification processes only non-distributed databases.)
Table
Specifies a table for the verification operation when the Operation is set to drop_table, table, or xtable.
Verbose Mode, Print Information as the Verify Proceeds
Provides additional dialog messages when performing the verification operation. This applies only to table operations.
Options Page
This page lets you set the following options:
Turn off logging to iivdb.log
Turns off logging to the log file. Logging to the terminal continues.
Alternative output log file
Specifies an alternate log file (to that specified in the II_CONFIG location) to which the verification operation is to log activity. When using this option, do not turn off logging with the previous option.
Output Log Page
The Output Log page displays the output of the verification process based on the options you have selected on the other dialog pages.