Large metadata Import, tomcat dying silently

[Gassim (AL-Gassim Sharaf Addin)]

Hi @Eric_Boyd_Ramirez,

Welcome to the community!

If it’s a performance issue then maybe some configuration settings need to be changed/updated. May you share more info about the infrastructure and software environment that you are using. Java heap space size, RAM, …etc?

However, it might also be because the metadata import needs more preparation and configuration. Please consider these instructions in a post by @Markus:

@Markus

When importing a metadata file that contains a new program into an instance where the program does not already exist, the program and all its dependencies must be included in the metadata file you are importing.

I would start by making a program dependency export in one of the instances, this produces such a file:

This metadata file should contain most of the data needed by the program. Your org unit structure might be different in the instance where you import the file, and if so, the program will not be connected to any org units after import. You must also set up sharing for the program after import to allow users to see it.

Markus

---

Also I would try a different approach! Since you are making an exact copy of the metadata then how about cloning the instance and then using import to delete all the data from the new instance? It will be clean as new, I think!