PK70986: "DBCONFIGURECR.SH" DOES NOT ALLOW PREDEFINED Z/OS DB2 DATABASE

Fixes are available

APAR status

Closed as program error.

Error description

The predefined z/OS DB2 database allocated by a z/OS DB2
administrator for special disk use cannot be filled
with the appropriate tablespace and schemas from a Linux
system with WebSphere Process Server 6.1.2 installed.
The already existing z/OS DB2 database causes an error and the
shell script "dbConfigureCr.sh" deletes the database.
The next run of "dbConfigureCr.sh" allocates a new z/OS DB2
database using default setting and the special disk setting
on z/OS are lost.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All WebSphere Application Server users who  *
*                  intend to install or configure Common       *
*                  Event Infrastructure (CEI) to a use DB2     *
*                  for z/OS database as the event repository   *
*                  and have already allocated the DB2 database.*
****************************************************************
* PROBLEM DESCRIPTION: The predefined z/OS DB2 database        *
*                      allocated by a z/OS DB2 administrator   *
*                      for special disk use cannot be filled   *
*                      with the appropriate tablespaces,       *
*                      schemas and the rest of the database    *
*                      objects. The already existing z/OS DB2  *
*                      database causes an error and the        *
*                      database creation shell script          *
*                      deletes the database.                   *
*                      The next run of database creation       *
*                      shell script allocates a new z/OS DB2   *
*                      database using default setting and      *
*                      the special disk settings on z/OS are   *
*                      lost.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The database creation shell script does treat the overall
database objects process creation as a whole simulating a
transaction.  In other words if an error is raised during DB2
configuration process the already executed statements are
rolled back leading to database deletion. In the case of
the already existing database scenario when the script tries to
create the database it finds it and therefore an error is
being raised saying that the name of the object to be created
is identical to the existing name. Since an error has been
raised the whole configuration process is rolled back ending
with deletion of the database.

Problem conclusion

The database creation shell script was modified in order to
tolerate the scenario of a database that already exits. That is
the creation of the database stands and if the returning
message returned SQL code does signal that a database with the
same name is already created, the execution continues since
it is not considered a fatal error anymore. Instead, the
situation is assumed to be part of the already existing
database scenario.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.21 and 7.0.0.1.  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
PK70986
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-08-22
Closed date
2008-10-07
Last modified date
2008-10-07

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK70986: "DBCONFIGURECR.SH" DOES NOT ALLOW PREDEFINED Z/OS DB2 DATABASE

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?