PK58701: CREATING DATABASES AND USERS FOR DB2 IN THE INFORMATION CENTER LEADS CUSTOMER'S TO CREATE DATABASES THAT CAUSE WCM PERFORMANCE

APAR status

• Closed as documentation error.

Error description

• The Portal Information Center section
  " Creating databases and users for DB2 " contains an example
   that is resulting in huge performance issues for customer's
   using WCM.
  http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?to
  pic=/com.ibm.wp.ent.doc/wpf/setup_db2.html
  ..
  states and then shows the following:
  ..
      * By default, all databases collate using the UCA400_NO
        collation of DB2. As this collation may not be suitable
        for certain needs, you may decide to change this collation
        in the 'CREATE DB' command below. Please refer to the DB2
        InfoCenter for more information on this topic.
  .
  db2 "CREATE DB dbname using codeset UTF-8 territory us
  COLLATE USING UCA400_NO PAGESIZE 8192"
  .
  While there is a warning I would suggest placing a * or adding
  UCA400_NO or (IDENTITY for JCR DB) in the example to help avoid
  a very frustrating situation for customer's
  ..
  .
  KEYWords:
    WCM JCR Performance delete library module import export
    transaction timeout deadlock DB2 collate
  

Local fix

• Create a new JCR DB that uses IDENTITYthen transfer the JCR DB
  per technote  1267813.
  

Problem summary

• The documentation has been clicked
  

Problem conclusion

• Documentation is updated
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels