How to prevent common Ingres related problems in a CA Directory deployment?

Document ID : KB000055489
Last Modified Date : 14/02/2018
Show Technical Document Details

When installation problems or operational problems with the Ingres database are experienced, please use the following checklist.

The first 4 items apply to Windows platforms only.

  1. [Windows Only!] Do not install as a user beginning with a digit (0-9)

    Ingres does not support usernames or database names beginning with a digit .

  2. [Windows Only!] Do not have an Administrator user (RID=500) beginning with a digit (0-9)

    Ingres adds the RID=500 user as an Ingres Administrator user, and this user must not begin with a digit.

  3. [Windows Only!] Do not remove or rename the user which installed Ingres

    The installing user most likely has also created the databases.

    Because a database can be owned by only a single user, removing this user will leave the database in a so called orphaned state.

    We recommend to designate a single, non-transient username to the task of Ingres administration.

  4. [Windows Only!] Do not have a file called C:\Program

    If Ingres was installed to "Program Files", then when it looks for files in "C:\Program Files\..." and finds a file called "C:\Program instead, this can cause an error. The same applies to any other drive letter where Ingres is installed to a Program Files directory.

  5. Do not delete the primary Transaction Log II_SYSTEM\ingres\log\INGRES_LOG.l01

    Ingres pre-allocates disk space to the transaction log, normally 256MB, but it the size can vary up to 2GB.

    This may look like a large unnecessary file, but the transaction log file is actually a vital part of the Ingres system.

    Ingres can not operate without it.

  6. Do not patch the database to make it consistent without identifying the cause of inconsistency

    It is important to identify why a database has become inconsistent before attempting to fix it.

    There may be a variety of reasons for database inconsistency.

    If the inconsistency was caused by a recovery (REDO) error, then the only recovery option is to restore from backup.

    Forcing the database consistent will not fix the data, and will lead to problems when the bad data is accessed.

  7. Do not manually edit the configuration file II_SYSTEM\ingres\files\config.dat

    Use CBF or the iisetres command to adjust Ingres parameters.

    Manually editing the config.dat is not recommended for various reasons; the most important ones are:

    1. there is no audit trail written to config.log;

    2. any dependent parameters are also not adjusted;

    3. non-ASCII escape characters can be left behind by clumsy fingers, and these are impossible to detect when Ingres won't start.

  8. Do not leave a connection open while removing or upgrading Ingres

    During an upgrade, Ingres attempts to shut down.

    If a connection is left open, then the shutdown will fail and the servers will restart.

    This causes major problems with the post-installation process.

  9. Do not change the hostname of the machine after installing Ingres

    Ingres adds the hostname of the machine to its configuration during installation.

    It is possible to edit the configuration to deal with a planned change of the hostname, it is recommended to contact contact CA Support for guidance.

  10. Do not ignore database maintenance

    Ensure to regularly maintain the database(s).

    Monitor for tables that have a potential to grow larger than 2GB in size, and extending in to multiple locations.

    Scheule a regular periodic FULL tune of the database(s) to avoid latency and maintain optimum performance.