db2install.history. If the name already exists, then the DB2 installer renames it db2install.history.xxxx, where xxxx is
Each installation copy has a separate list of history files. If an installation copy is removed, the history files under this install path will be removed as well. This copying action is done near the end of the installation and if the program is stopped or aborted before completion, then the history file will not be created.
On Linux
DB2 Express memory limits and the DATABASE_MEMORY configuration parameter:
If you are installing DB2 Express Edition or DB2
Note: If you have more than one database on that server, the sum of all database memory usage cannot exceed 4GB.
You can use the Control Center or the UPDATE DATABASE CONFIGURATION command to make this change. For example, to set the DATABASE_MEMORY limit to 4GB, enter the following command:
DB2 UPDATE DATABASE CONFIGURATION using DATABASE_MEMORY 1000000 IMMEDIATE; CONNECT RESET;
Also, when using the Configuration Advisor to assist you in configuring the performance of your database, you need to set the Target Memory on the Server page to a percentage of your total system memory that will ensure you stay under the 4GB memory limit.
Related concepts:
v“DB2 Information Center installation options” in Quick Beginnings for DB2 Servers
v“DB2 database object naming rules” in Administration Guide: Implementation
Related tasks:
v“Notification and contact list setup and configuration” in Administration Guide: Implementation
v“Tools catalog database and DB2 administration server (DAS) scheduler setup and configuration” in Administration Guide: Implementation
v“Migrating a DB2 server (Linux and UNIX)” in Migration Guide
Related reference:
v“Centralized
v“UPDATE ADMIN CONFIGURATION command” in Command Reference
v“Multiple DB2 copies roadmap” in Administration Guide: Implementation
Chapter 2. Installation 21