The customer had a strange issue recently - lots of custom SQL statements were missing when they imported a good ATL file into a brand new repository. This hasn't happened before. And they are sure that the DI repository versions are the same between the one it was exported and imported. I did some troubleshooting for them and found out:
1) The custom SQLs are intact when I opened the ATL file in a text editor. And the ATL file can be imported without any issue into other repositories.
2) Most custom SQLs are missing but not all. Some are imported OK.
3) When I opened the SQL tranform for those with missing SQLs, the textbox area for the SQL statement was blank. This caused errors in validating the job.
4) Sometimes the issue was resolved when the developer re-initialized the repository and imported the ATL again. But sometimes this strategy doesn't work - the SQL statements are still missing after the repository has been re-initialized a couple of times.
The DI version is 11.5.3 on HPUX with repository version 11.5.1.5. The repository database is either Oracle 9i or 10g.
Thanks,
Larry