JR47158: FIRST COMPONENT IN NAME <DBNAME> NOT FOUND.

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• Migration will do some cluster level detection in target env
  during
  startup of every server/cluster, it will traverse datasource of
  every
  component via JNDI lookup, like BPC, ProcessServer,PerformaneDW.
  But every datasource has its specific scope, like
  PerformanceDW(jdbc/PDWDB) was created only in Support cluster so
  that
  some error like "First
  component in name PDWDB not found." would be thrown when
  attempting to
  look up jdbc/PDWDB during AppTarget cluster startup.
  

Local fix

• This kind of error message has no impact to any function,
  customer can ignore it.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM 7.5.1.x                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Errors in log during server start:      *
  *                      "First component in name PDWDB not      *
  *                      found"                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Migration will do some cluster level detection in target env
  during startup of every server/cluster,
  it will traverse datasource of every component via JNDI
  lookup, like BPC, ProcessServer,PerformaneDW.
  But every datasource has its specific scope, like
  PerformanceDW(jdbc/PDWDB) was created only in Support cluster
  so that some error like "First component in name PDWDB not
  found."
  would be thrown when attempting to look up jdbc/PDWDB during
  AppTarget cluster startup.
  

Problem conclusion

• The error thrown has no functional impact. The fix provided
  logs the situation and continues starting up.
  
  Install/Dependency information is available in the readme.txt
  on FixCentral. When the user goes to the download files page
  in FixCentral, the readme will be available with the fix
  package as a separate download.
  

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

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP