# DB2 Aliases and LiquiBase

**URL:** <https://forum.liquibase.org/t/db2-aliases-and-liquibase/2189>\
**Category:** General Discussion\
**Created:** [January 25, 2013, 2:30am UTC](https://forum.liquibase.org/t/db2-aliases-and-liquibase/2189 "2013-01-25T02:30:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ecalvert](https://avatars.discourse-cdn.com/v4/letter/e/e19adc/32.png) [@ecalvert](https://forum.liquibase.org/u/ecalvert)\
**Post date:** [January 25, 2013, 2:30am UTC](https://forum.liquibase.org/t/db2-aliases-and-liquibase/2189/1 "2013-01-25T02:30:00Z")

</div>

While using LiquiBase to generateChangeLog for a large DB2 database, I noticed that one particular schema took way longer than the others (we have about 60 schemas). &nbsp;The one that took longer makes heavy use of aliases to point to tables in other schemas. &nbsp;However, LiquiBase extracts these aliases as full tables - meaning that in the generated XML file, it puts createTable entries in for each alias. &nbsp;While this would technically produce a correct schema, the objects that were aliases will be empty.

Anybody have any ideas how to work around this?

I would have hoped for a entry or similar.