Wednesday, 12 February 2014

IBM Operational Decision Manager 8.5.1.0 - Problems with missing DB2 Buffer Pool

One about which I'd forgotten.

I saw this exception: -

Failed to execute SQL statement "CREATE TABLESPACE RESDWTS PAGESIZE 32K BUFFERPOOL BP32K".
DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=BP32K, DRIVER=3.65.97

when configuring the DB2 database for an IBM Operational Decision Manager (ODM) 8.5.1.0 Decision Server ( aka Rules Execution Server == RES ) environment.

ODM provides a nice GUI for configuration, and I got hit with this: -

 

I validated this on the DB2 server directly: -

$ db2 connect to resdb
$ db2 "CREATE TABLESPACE RESDWTS PAGESIZE 32K BUFFERPOOL BP32K"

DB21034E  The command was processed as an SQL statement because it was not a 
valid Command Line Processor command.  During SQL processing it returned:
SQL0204N  "BP32K" is an undefined name.  SQLSTATE=42704

Yes, you've guessed it - I'd forgotten to create the Buffer Pool BP32K.

This I did: -

$ db2 create bufferpool BP32K size 8000 pagesize 32 K

DB20000I  The SQL command completed successfully.

and re-ran the ODM wizard; this time it all ended happily :-)

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...