Configuring a database for staging

Before using the Stage Copy, Stage Propagate, or the Database Cleanup utility:

  1. DB2 If you are using a DB2 database, configure the staging database and the production database by issuing the following commands in a db2 command window:

    • db2 update db config fordb_nameusing LOGPRIMARY 80

    • db2 update db config fordb_nameusing LOGBUFSZ 512

    • db2 update db config fordb_nameusing DBHEAP 2048

    • db2 update db config fordb_nameusing APPLHEAPSZ 2048

    • db2 update db config fordb_nameusing PCKCACHESZ 8200

    where db_name is the name of your database.

    Note:

    • The default STMTHEAP size is 60000.

    • The default LOCKLIST is 2400.

    • The default STAT_HEAP_SZ is 2048.

    • The default APP_CTL_HEAP_SZ is 4096.

  2. WindowsAIXSun Solaris Operating EnvironmentLinuxDB2 Increase the buffer pool size for improved performance. Determine the optimum buffer pool size based on your DB2 database size and available memory. Run the following commands in a DB2 command window to change the default buffer pool size:

    • db2 connect todb_name

    • db2 alter bufferpool IBMDEFAULTBP size n

    • db2 terminate

    where n is the optimum buffer pool size.

  3. i5/OS Log on as a user profile with secofr authority and cssid with a value other than 65535.

  4. If you have set up your staging server on a machine other than your production server, the remote database must be configured. If you plan to run staging utilities from the staging server, you need to configure your production database as the remote database in your staging server. If you plan to run staging utilities from the production server, you need to configure the staging database as the remote database in your production server.

    DB2 For a DB2 database, refer to the DB2 Administration Guide.

    Oracle For an Oracle database, refer to the product's documentation.

Feedback