Troubleshooting: Staging server

Issues you may encounter while using the stagingprop utility.

  • While using the stagingprop utility, you may receive the following message:
    SQLSTATE 54001: The statement is too long or too complex.

    Ensure that you have set the stmtheap size of your database as suggested in configuring the database. You should verify that you have enough memory to support the increase.

  • If the stagingcopy utility fails to complete processing, the database log may be too small. From a DB2 command window issue the commands:
    update database configuration for staging_server using logprimary 50 logfilsiz 1000 
    db2 terminate 
    db2stop db2start
    is the name of the staging server database.
    If the problem persists, try using a higher value for the logprimary or logfilsiz parameters.
  • AIX Ensure that the resource for DB2 user, such as db2inst1, has been configured properly. Entering the following command shows your resource limitation:
    ulimit -a
    Configure the data segment to 240MB and stack to 16MB. For additional information, refer to the DB2 Command Reference.
  • If stagingcopy fails while copying merchant tables, ensure that the MEMBER_ID is an organization or member group, not a user in the MEMBER table. Although not recommended, if the MEMBER_ID is a user, manually copy the referenced user's record from the source database to the target database in both the USER and MEMBER tables. For more information see Staging server limitations.
  • The stagingprop utility takes a long time during the consolidation step on a DB2 database. This problem is caused because the DB2 server does not use the primary key of the STAGLOG table.
    To correct this issue, connect to the staging database and run the following SQL:

    This command forces the DB2 database to use the primary key. Run this command only one time.

  • The stagingprop utility fails when attempting to resolve a circular key reuse for a unique key. The stagingprop utility handles circular value reuse only if each unique key in the table satisfies all of these conditions:
    • The unique key contains only one column.
    • The unique key column is not part of a foreign key.
    • The unique key has type number, character (char), or variable character (varchar).