Why does the Object Migration “Full Package” create mode not always return results?
The Object Migration (OM) tool’s “Full Package” create mode is not the ideal tool to be utilized by users. It was never fully documented, needs to be utilized in a very clean environment with limited data, and requires gigantic sums of memory — like 20GB+ of heap on the application server — in order to run. All data in the database is loaded into memory before the OM is created.
The Object Migration tool’s “Full Package” create mode will not work in most client environments because the makeup of the data and application definitions will cause either out of memory issues or infinite loop issues. Again, the system must be in a very, very, clean state with little to no instance data and the application definition needs to be in a nearly perfect state with no warnings. If there is instance data, it could cause the Object Migration process to go out of memory as it tries to write XML in memory for each and every record in the system. Also, it could fail if there are application definition (metadata) problems, such as forms that point to Business Object fields that do not exist, queries that reference queries that do not exist, looping hierarchies, and the like.
Even if none of these problems are present, it can takes days and days to create the package, while at the same time consuming large amounts of memory.
For these reasons, the Object Migration tool’s “Full Package” create mode has been removed from the Object Migration tool, starting with the 3.5 platform release. Details of this are found by searching for the string ‘Tri-173046’ in the TRIRIGA 10.5/3.5 Release Notes.