Chat now with support
Chat with Support

One Identity Management Console for Unix 2.5.2 - Administration Guide

One Identity Privileged Access Suite for Unix Introducing One Identity Management Console for Unix Installing Management Console for Unix Preparing Unix hosts Working with host systems Managing local groups Managing local users Active Directory integration Authentication Services integration Privilege Manager integration Reporting Setting preferences Security Troubleshooting tips
Auto profiling issues Active Directory Issues Auditing and compliance Cannot create a service connection point Check Authentication Services agent status commands not available CSV or PDF reports do not open Database port number is already in use Elevation is not working Hosts do not display Import file lists fakepath Information does not display in the console License information in report is not accurate Out of memory error Post install configuration fails on Unix or Mac Privilege Manager feature issues Profile task never completes questusr account was deleted Readiness check failed Recovering from a failed upgrade Reports are slow Reset the supervisor password Running on a Windows 2008 R2 domain controller Service account login fails Setting custom configuration settings Single Sign-on (SSO) issues JVM memory tuning suggestions Start/stop/restart Management Console for Unix service Toolbar buttons are not enabled UID or GID conflicts
System maintenance Command line utilities Web services Database maintenance

Database location and files

Database location

Management Console for Unix database files are located in the following locations:

  • On Unix/Linux: /var/opt/quest/mcu/db
  • On Windows: %SystemDrive%:\ProgramData\Quest Software\Management Console for Unix\db
Database files

The data for each database consists of multiple files located in the same directory. All the database files start with the same name as defined by the value in the jdbc.url key. For Management Console for Unix, the database consists of the following files by default:

Table 23: Database files
File Description
console.lck This file is used to determine if the database is in use. If console.lck exists, the server is currently running. This file is deleted once the database is properly shutdown. DO NOT BACKUP THIS FILE.
console.log This file contains the extra SQL statements that have modified the console database since the last checkpoint (something like the 'Redo-log' or 'Transaction-log', but just text.) For a normal shutdown this file is deleted once the database has completely shutdown. This file contains general settings about the database including the entry 'modified'. If [modified=yes], the database is either running or was not closed correctly (because the close algorithm sets 'modified' to 'no' at the end).
console.script This file contains the SQL statements that make up the database up to the last checkpoint.

Database backup procedure

It is best to perform a backup when the HSQLDB is not running. use normal backup methods, such as archiving the files in a compressed bundle.

To backup a database

  1. Shutdown the HSQLDB server. See Start/stop/restart Management Console for Unix service for details about starting and starting the Management Console for Unix Service.
  2. Copy the following files to a backup location: and console.script.
  3. Once the HSQLDB server is stopped, replace the files in the database directory with the ones you previously backed up. See Database location and files.
  4. Once you have replaced the files, start the HSQLDB server.

Note: If a backup immediately follows a checkpoint, then the console.log file can also be excluded, reducing the significant files to and console.script.

You can backup the files while the HSQLDB server is running, but make sure that a shutdown or checkpoint is NOT performed during the backup. If you perform a backup while the server is running, you will need to backup the console.log file, as well. This file will be deleted once the server is shutdown.

Database states

Use the following information to determine if the database was shutdown successfully.

State after shutting down the HSQLDB server:

  • The console.script file contains the information in the database, excluding data for text tables.
  • The file contains the entry [modified=no].
  • There is no console.log file.

Aborted database state (may happen by sudden power outage, Ctrl+C in Windows)

  • The file still contains the entry [modified=yes].
  • The console.script file contains a snapshot of the database at the last checkpoint and is OK.
  • The console.log file contains all the information to restore all the changes since the snapshot. As a result of abnormal termination, this file may be partially corrupt.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating