DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0601N The name of the object to be created is identical to the existing name "LOG_CONF_BP" of type "BUFFERPOOL". SQLSTATE=42710

How to remove pre-existed "LOG_CONF_BP" of type "BUFFERPOOL" in db2 database? Is there any other way to define logging for my stored procedures?

  • Hi, I am the designer and developper of that tool. If you have any problem, please let me know at: github.com/angoca/log4db2/issues I already created a ticket in order to continue the installation in case the bufferpools or tablespaces already exist. If you have any other question do not hesitate to contact me.
    – AngocA
    Commented May 25, 2015 at 17:07

1 Answer 1


LOG_CONF_BP is a bufferpool. That is a chunk of memory dedicated to doing something (usually servicing one or more tablespaces, which is where tables reside). So what is happening is your stored procedure is trying to create an object that already exists.

So what is going to need to change is the stored procedure. I would ask if your stored procedure needs that exact bufferpool or not. If yes, then change the stored procedure to check for the existence of LOG_CONF_BP (you can check against syscat.bufferpools for that). If it doesn't exist, create it, otherwise don't.

Otherwise, even if you drop the LOG_CONF_BP, so your stored procedure succeeds, it will just fail again the next time you run it anyway....

  • It was helpful to track my problem...:-)
    – vipin
    Commented May 21, 2015 at 10:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.