Hi prabharhar,
This is why Liquibase uses the two tables. One to prevent duplicate invocations, the other to track already applied changeLogs (so they are not applied twice). What you can do is to rename the tables and even put them in another schema/catalog but I don't think it's possible to skip them entirely (or keep the info only in the filesystem).
If your DBA does not accept that your only way to go may be preparing a test database (that allows the liquibase tables) and give the DBA a cleaned up version of the liquibase generated sql (the command would then be updateSQL instead of update).
Hope this helps.
Daniel