Hide Forgot
Date of First Response: 2009-05-25 05:05:38 project_key: SOA If one use the schema tool for the first time, it works. When db is changed and the schema tool is used again, the schema tool is not aware of the db change it uses old one (db.properties file). The fix is below (on the /tools/schema/build.xml): 110,111c110,111 < <move file="@{file}" tofile="@{file}.orig"/> < <move file="@{file}.orig" tofile="@{file}"> --- > <move file="@{file}" tofile="@{file}.rf-orig"/> > <move file="@{file}.rf-orig" tofile="@{file}"> 124,125c124,125 < <move file="@{file}" tofile="@{file}.orig"/> < <move file="@{file}.orig" tofile="@{file}"> --- > <move file="@{file}" tofile="@{file}.rfex-orig"/> > <move file="@{file}.rfex-orig" tofile="@{file}">
Link: Added: This issue is related to SOA-1223
Fixed with revision 3075 (4.2.0 branch) of: build-tools/resource/schema/eap/build.xml build-tools/resource/schema/esb/build.xml Commit message: JIRA SOA-1325 Use a different name for the reconfigure target temporary file (from pmacik). Work around ant's copy/move behaviour by checking for the existance of the db.properties file.
Release Note added: The database schema tool can now be used more than once to change your database configuration.
Verified in CR4