Understanding Post-installation Tasks

How You Further Customize Your Instance

After Ingres is installed, configured, and started, you may need to perform the following additional tasks:

• Change default values for some configuration parameters to suit your particular needs or enhance performance.

  The default configuration installed by the setup programs is suitable for moderate hardware (about 512 MB of memory) and a moderate number of users (about 32). You may need to change the size of the transaction log file or the number of concurrent users (connect_limit).

  To change parameter settings, use the Configuration-By-Forms utility (or its equivalent visual tool Configuration Manager, if available) or the ingsetenv command.

  Note: Some changes, such as to the logging system, should not be made while the DBMS Server is running. Changes made with Configuration-By-Forms while servers are running are not effective until you restart the servers.

• Set up virtual nodes, remote user authorizations, and connection data, as needed, for DBMS Server and client instances. Use the Net Management Utility (netutil) or Visual DBA, if available.

  If you installed Ingres Net for the first time and did not define the DBMS Server password on the server or client nodes, add authorization entries that enable clients to access databases on the DBMS Server node.

  If you are upgrading an existing instance or adding Ingres Net to your instance, your existing definitions remain in effect. For more information, see the Connectivity Guide.

• Add client capabilities to a networked DBMS Server by setting up the appropriate Ingres Net client parameters. For details, see the Connectivity Guide.
• (UNIX only) Set up and configure a raw log device in place of the default transaction log file.

How You Prepare Your Installation for General Use

After Ingres is installed, you must complete additional tasks so that users can access and use the new installation.

To prepare Ingres for general use, you must complete all or some of these tasks:

• Enable recovery of your master database.

  To help recover your master database (iidbdb) if it becomes corrupted, make sure that iidbdb has been checkpointed and journaling enabled (the default). For details, see the Database Administrator Guide.

• Add an automatic startup command.
• Authorize users to start and stop servers.

  If you want users other than the Ingres system administrator to be able to start and stop the Ingres servers, you must make changes to the config.dat file. For details, see the System Administrator Guide.

• (UNIX and Linux only) Allow access on systems using shadow passwords.
• Allow users to access tools and databases.
• Create databases. For details, see the chapter "Creating a Database."

  Note: You do not need to create the iidbdb master database because it is created during installation.

• (OpenVMS only) Maintain the installation history log file.

Note: Check the Readme file for any additional tasks necessary for your platform.

More information:

Post-Installation Tasks (UNIX)

Post-Installation Tasks (VMS)

How You Safely Uninstall Ingres

Removing Ingres is an irreversible event with pervasive effects. Any products or applications that share the removed DBMS Server are affected, as follows:

• Any future attempt to connect to this database will fail.
• If you re-install Ingres, you may not be able to reference the data files.

If you know you want to remove an Ingres instance, follow this process:

1. If you want to keep the data files for later use, you must run unloaddb against each database before removing Ingres. Doing so will allow you to reference the data files easily if you re-install Ingres later. For details on the unloaddb command, see the Database Administrator Guide and the Command Reference Guide.
2. If you do not want to keep the data files, you can run destroydb against each database before removing Ingres. The destroydb command locates and deletes all data files. For details on the destroydb command, see the Command Reference Guide.
3. Uninstall Ingres.

Uninstall Ingres for Linux Using the Installation Wizard

To uninstall Ingres for Linux, start the installation wizard and choose the option to modify an existing instance. The option "Remove all packages" removes only those files that are distributed with Ingres; it does not remove database and configuration files. To remove all files, check the "Remove all files" option.

uninstall_ingres Command—Uninstall Ingres for Linux

The uninstall_ingres command removes any or all instances of Ingres for Linux on a machine. This command invokes RPM. If this command is run without any parameters, it generates a list of standard (non-renamed) installed Ingres RPM packages and prompts for confirmation before removing them.

This command has the following format:

uninstall_ingres {[instance ID] | [-a (--all)]} [-y (--yes)] [-c (--clean)]

• instance ID

  Identifies the instance ID embedded in the renamed package names to be removed.

• -a

  Removes all Ingres RPM packages for all Ingres instances. This parameter cannot be used if specifying an instance ID.

• -y

  Answers yes to all prompts (that is, does not prompt).

• -c

  Removes the $II_SYSTEM/ingres directory after the uninstall operation is complete.

Uninstall Ingres for Windows

The Ingres uninstall program removes all binary files.

To uninstall Ingres

1. Click Start, Settings, Control Panel, Add or Remove Programs.

   The Add or Remove programs window appears.

2. Select the Ingres instance or component you want to remove.

   Note: If multiple instances installed, be sure to select the one you want to remove. Each instance is identified by a unique instance name.

   Note: Ingres .NET Data Provider and Ingres documentation, if installed, are separately installed products and must be individually selected for removal.

3. Click Add/Remove.

   The Ingres installation wizard is started.

4. Follow the installation wizard instructions to remove Ingres.

   Ingres binary files and any data files residing in II_SYSTEM are removed.