LB2.0-RC7: <renameTable> causes DB2-Error

Hi all,
we faced a problem when trying to update a DB2 (v9.7) database with a tag in the update script. We ran LB (v2.0-RC7) via Ant in a build target like

<updateDatabase
changeLogFile="${liquibase.changelog.create.meta}"
driver="${jdbc.db.driver}"
classpathref=“classpath”
url="${jdbc.db.url}"
username="${jdbc.db.user}"
password="${jdbc.db.pwd}"
defaultSchemaName="${jdbc.db.schema}"
promptOnNonLocalDatabase="${liquibase.prompt.non.local.db}"
contexts="${liquibase.customer}"

<changeLogProperty name="liquibase.schema" value="${jdbc.db.schema}" />

and  a tag in the update script like this

The LB generated SQL for the DB2 was

    RENAME db_schema.old_table_name TO db_schema.new_table_name

which caused a DB2 error with sqlcode: -108. The correct DB2 SQL should have been

    RENAME db_schema.old_table_name TO new_table_name

Running the same script with a Ant target nearly the same as before, but leaving out the defaultSchemaName attribute for the task works for the DB2. Unfortunately we need this defaultSchemaName attribute as we have to run the same scripts against a MS SQL database for which this attribute fixes a the [dbo] issue (topic “MSSQL2005: Controll tables allways in [dbo]-schema (using 2.0-RC7)”).

Is there anyone with an idea?
-Thanks in davance!!
Frank

Hi all,
a test against an Oracle 11g database leads to a similar error (ORA-14047) like that in DB2: The Oracle SQL LB generates was

  ALTER TABLE db_schema.old_table_name RENAME TO db_schema.new_table_name

but should have been

  ALTER TABLE db_schema.old_table_name RENAME TO new_table_name

Frank

I fixed up the SQL for the next release.  For now, you’d have to use the tag.  Thanks for reporting the problem

Nathan