Recently i come across a strange situation with BODS content migration using ATL File. Currently we are in BODS 4.0 SP3 and BO BI 4.0 with Oracle 11g Database.
We had a new development in BODS Development environment, tested, working fine. To migrate this to QAS, we exported the content of DEV into ATL file, moved to QAS and then imported into QAS repository. Then for testing, we executed the ETL job with migrated content in QAS, the changes which we imported are not applied, the job was executed with old version objects. But the new changes which we migrated are seeing in the designer. Later we closed the designer, reopened then executed the job, this time it worked fine with new version objects which we imported. This is not happening every time, sometime it behaves like this.
Here, my intention is to know the below points:
1. When we import an ATL file in designer, after completion of import, the import process will automatically updates the Repository tables and performs commit or explicitly need to perform refresh / commit by closing and reopening the designer? (This is not need in 3.x)
2. Is there any metadata table in BODS repository to check when a particular object in the repository got created or updated or when the was last modified information?
3. Is this a bug or need to follow any specific steps while importing the ATL file in 4.x?
Looking for your valuable inputs...