Skip to Content
Former Member
Nov 12, 2007 at 03:23 PM

How to handle out-of-memory problems during repository load?


Hi all,

During load tests, we've loaded a lot of test data into a repository. The load itself worked, but as we unloaded the repository and loaded it again, we got an "out of memory" exception.

Now, as the test data wasn't valuable, we were able to just delete the repository. But what would be the options for valuable data?

Sure, a productive system should have enough memory installed. But imagine a defective client application that doesn't stop loading records into the MDM system.

I currently see two options - which are both not optimal in my opinion:

1. Transfer the repository to a system with more memory.

2. Access the database directly and extract the non-bogus data.

Are there further possibilities?

Best regards,