Environment:
WPS 6.2.0WAS 6.1.0.21
Win XP SP3
DB2v9.7
Problem(Abstract)
A second deployment environment cannot be generated through the Network Deployment wizard in the administrative console or command line scripting.Cause
The error occurs because one of the deployment environment components (CEI) requires its own database. If the database is already being used by another CEI component in a previously generated deployment environment, the second deployment environment will not be generated.
Diagnosing the problem
This following error is displayed in the log and shown in the administrative console:
CWLDB9014E: The configuration of component WBI_CEI failed. Reason java.lang.Exception: java.lang.Exception: com.ibm.db2.jcc.b.SqlException:
DB2 SQL error: SQLCODE: -601, SQLSTATE: 42710, SQLERRMC: EVENT_BP_4K_DATA;BUFFERPOOL.
CWLDB9016E: The generation for deployment environment drs_esb2 failed.
Reason: CWLDB9014E: The configuration of component WBI_CEI failed. Reason java.lang.Exception: java.lang.Exception: com.ibm.db2.jcc.b.SqlException:
DB2 SQL error: SQLCODE: -601, SQLSTATE: 42710, SQLERRMC: EVENT_BP_4K_DATA;BUFFERPOOL.. If in doubt, discard the changes and do not save the failed configuration to the master repository.
CWLDB9014E: The configuration of component WBI_CEI failed. Reason java.lang.Exception: java.lang.Exception: com.ibm.db2.jcc.b.SqlException:
DB2 SQL error: SQLCODE: -601, SQLSTATE: 42710, SQLERRMC: EVENT_BP_4K_DATA;BUFFERPOOL.
CWLDB9016E: The generation for deployment environment drs_esb2 failed.
Reason: CWLDB9014E: The configuration of component WBI_CEI failed. Reason java.lang.Exception: java.lang.Exception: com.ibm.db2.jcc.b.SqlException:
DB2 SQL error: SQLCODE: -601, SQLSTATE: 42710, SQLERRMC: EVENT_BP_4K_DATA;BUFFERPOOL.. If in doubt, discard the changes and do not save the failed configuration to the master repository.
Tried Doing..
We'd tried to re-install the whole DB2 database on the system.But even after the DB2 was reinstalled the same issue persisted.The issue was not with the deployment generation it was with the database.Now here is what happened in our particular case.Once a successful deployment is generated the database schema's and tables are created as per the scripts.On windows platform they are reflected on the local file system C:\DB2\...If you(mostly in development environment ) decide to altogether remove the(successfully generated) deployment environment and delete the corresponding DB2 tables in the database,Apart from 'dropping' the tables also manually delete the DB2 folder in the file system(eg C:\DB2\..).This will make sure that the database is in the 'consistent' state.
No comments:
Post a Comment