Troubleshoot: Staging server

• 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
  
  
  

  where

  staging_server

  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.

 

Related Concepts

Staging server

 

Related Reference

Staging server limitations