This guide includes the individual steps that are required to set up an DB2 database for AE usage.
Important: Automic recommends carefully reading the relevant notes about optimizing the AE database's performance before you start setting up the database. See:Configuration & Performance of the Database, the Automic Compatibility Checker for details on supported versions and platforms and the general information in Supported Platforms.
Do not limit resource consumption. Transactions that repeatedly abort because of limitations that are specified in the database can impede processing in your AE system. Inconsistent database contents can be a result thereof and cause subsequent errors or endless loops.
Note that your database will become inconsistent when you modify database contents.
Size required for the initial installationnull of an AE database |
|
---|---|
Test systems: |
1 GB |
Production systems: |
|
Small systems |
5 - 20 GB |
Medium systems |
20 - 50 GB |
Large system |
more than 50 GB |
Procedure
General Requirements:
A temporary system tablespace of 32k must be available.
The following scripting example creates a new database with a specific coding:
create db uc4
automatic storage yes
on ...
using codeset <code set> territory <short form of country> ;
The following is a scripting example for the US:
create db uc4 automatic storage yes on ... using codeset iso-8859-1 territory us ;
DB2 for UNIX or Windows
SQLDRIVERCONNECT=ODBCVAR=NNJNIORD,DSN=DB2CLI;UID=uc4;PWD=--1018A94DA12E7FA991
The following parameters have to be set in order to improve performance for DB2 on UNIX/Windows:
These parameters can be called using the command "get dbm cfg" which requires no authorizations:
db2set db2codepage=819
LoginAnmeldedaten für Zielsysteme. Auch ein eigener Objekttyp in der Automation Engine. with DB2 Admin:
db2
catalog tcpip node <servername> remote <servername> server 50000
catalog database <db-name> as <alias-name> at node <servername>
quit