# Running Liquibase against database after changing logical file path

**URL:** <https://forum.liquibase.org/t/running-liquibase-against-database-after-changing-logical-file-path/2293>\
**Category:** General Discussion\
**Created:** [June 19, 2013, 4:11pm UTC](https://forum.liquibase.org/t/running-liquibase-against-database-after-changing-logical-file-path/2293 "2013-06-19T16:11:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guest](https://avatars.discourse-cdn.com/v4/letter/g/8dc957/32.png) [@Guest](https://forum.liquibase.org/u/Guest)\
**Post date:** [June 19, 2013, 4:11pm UTC](https://forum.liquibase.org/t/running-liquibase-against-database-after-changing-logical-file-path/2293/1 "2013-06-19T16:11:00Z")

</div>

Hi,

I have a scenario where I want to change the logical file path in the xml&nbsp;files . But these changelogs have already been run against the database . So if I change the logical path , how can i avoid these files from getting executed on the database again ?

For ex . I have a xml called abc.xml , i changed the logical file path like below

I updated the filename column in databasechangelog table with from&nbsp;new/abc.xml to old/abc.xml . But now when i try to run the liquibase , it showing the changelog from these files as well . What is the best way to avoid ?

Thanks,

Raharida