PK87641: WEBSPHERE PROCESS SERVER 7: CANNOT CREATE PROFILE WHEN CONFIGURING WITH DB2 V9 MICROSOFT WINDOWS SERVER 2003 PLATFORM

Fixes are available

APAR status

Closed as program error.

Error description

Failed to create the profile.

WASX7357I: By request, this scripting client is not connected
to any server process. Certain configuration and application
operations will be available in local mode.
WASX7015E: Exception running command: "$AdminTask
configEventServiceDB2DB {     -nodeName nlNode02
-serverName server1      -createDB true      -dbName EVENT
-jdbcClassPath {C:W70universalDriver_wbilib}
-dbHostName nl.cn.ibm.com     -dbPort 50000     -dbUser
administrator     -dbPassword *****}     -overrideDataSource
false      -outputScriptDir
{C:W70profilespatdbscriptsCEI_EVENT}} "; exception
information:
com.ibm.events.install.db.DBConfigException:
com.ibm.events.install.db.DBConfigException: CEIIN0721E
Creation of the event database on DB2 failed because of
errors. 'server' is not recognized as an internal or external
command, operable program or batch file.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 trying to configure the         *
*                  Common Event Infrastructure with supported  *
*                  databases via specific administration tasks.*
****************************************************************
* PROBLEM DESCRIPTION: The problem is encountered by the       *
*                      Common Event Infrastructure users       *
*                      who configure it with supported         *
*                      databases. The actual command for       *
*                      creating and configure the database     *
*                      repository is not run and therefore     *
*                      only the Common Event Infrastructure    *
*                      configuration at WebSphere              *
*                      Application Server level is run.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Common Event Infrastructure database configuration process
is broken by the fact that the run command for these scripts
was not issued properly and therefore this process is never
run. The database related scripts are generated according to
the received parameters and the WebSphere Application Server
configuration process is done but the command related to
repository databases configuration is never fired and
therefore not run.

Problem conclusion

The code that performs the initiation of the database creation
and configuration of the databases was corrected in order to
issue the command for the database scripts.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK87641
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-29
Closed date
2009-06-23
Last modified date
2009-06-23

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK87641: WEBSPHERE PROCESS SERVER 7: CANNOT CREATE PROFILE WHEN CONFIGURING WITH DB2 V9 MICROSOFT WINDOWS SERVER 2003 PLATFORM

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?