AWS BluAge L3 Workshop : bac.war causing issues in loading KSDS files to postgres

Per this step in the workshop - https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/data-migration/datasets/vsam-ksds , we have to launch the Tomcat server with bac and gapwalk-application applications to load postgres/carddemo-bluesam database with the data from KSDS files available at C:/Work/Resources/vsam-ksds. The bac-client (may be due to some caching issue) might be loading incorrect data into the database. When I try to load one file, the previous file contents creep into the tables.

Can you please provide a resolution to this solution ASAP as it is blocking the L3 Workshop flow?

Image: BluAge-L3-Workshop-Image-4-2-0 gapwalk version: 4.2.0

The only table with correct data is USERSEC, and it looks like whenever I load the other tables, the same USERSEC data is picked from Cache and inserted into all the other tables.

Here are the screenshots I am trying to load AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS to bluesam db and here is what happens (please note that I deleted the contents and I am trying to reload again) - This time it loaded 25 records, last time it loaded 2 records. It varies everytime I try