Posted: Wed Apr 14, 2004 5:27 am Post subject: Unexpected error while deplying
Acolyte
Joined: 18 Jan 2004 Posts: 52
We are getting the following error when we deploy a particluar flow-
Has anyone faced this earlier. Any pointers welcome...
BIP1205E: Unexpected exception accessing configuration repository; exception text: '[IBM][CLI Driver][DB2/6000] SQL0302N The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use. SQLSTATE=22001 '.
While attempting a database operation on the configuration repository, a SQL exception was caught by the Configuration Manager. The database operation did not complete successfully. If this message was issued by the Configuration Manager, then it will continue if it is safe to do so. The exception text is: [IBM][CLI Driver][DB2/6000] SQL0302N The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use. SQLSTATE=22001 .
For more information on this error refer to the relevant documentation for the database manager you are using for the configuration repository (for example, for DB2 refer to the DB2 SQL Reference manual
Joined: 16 May 2001 Posts: 200 Location: Green Bay Packer Country
For Message Broker v5 this error is the result of a bug. You should only get this on versions before CSD#3 when you created your Config Mgr at that level (pre-CSD#3). IBM response is the following (after installing CSD#3):
Solution: Defect 34698 has been reaised for this issue - Due to changes in the way the Configuration Manager stores deployed message flow in the database, deploying message flows greater than 2MBytes will cause a BIP1205 error. There are two ways to solve this problem. You can either delete and recreate the tables or run the migration script "mqsimigrateconfigxmldata.cmd". This will increase capacity to 10MBytes. To run the script:
1) Stop the Configuration Manager
2) Open a DB2 Command window (type "db2cmd" from a windows command window)
3) Run the script providing the Configuration Manager Database name, Database user/pwd
C:> mqsimigrateconfigxmldata domain1 db2admin db2
4) Restart the Configuration Manager
This would fix the tables effected. Will need to use ID and password of schema owner on your tables or you will get errors. This is most likely your service ID anyway (i.e. mqsi). _________________ Thanks!!!
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum