Issues merging geodatabases

[OrrinFeril]

I'm having an issue merging records from eight existing geodatabases into a single geodatabase. When I merge the records, not all of the records make it into the target file geodatabase. I have found that I'm missing approximately 3000 records (~46,000 out of 49,000 records). The strange thing is, if I create a new record in the target file geodatabase (whether by create feature or by copying feature), it seems another record goes away. It's like I'm hitting a record limitation for the target file geodatabase, but this seems weird.

Any suggestions on settings to check or things to keep an eye out for?  I have attempted this multiple times with the same result. Thanks in advance. 

[VinceAngelo]

There are no effective limits on file geodatabase (two billion or four quintillion features).

It would help if you could document your exact steps, to the point of describing the feature counts in the eight tables, and specifying the exact geoprocessing command in the Analysis log.

- V

[OrrinFeril · Accepted solution]

I finally got back onto this issue. I went back in and to redo the merge and document the steps. In doing so, I notice a few warnings that I ignored. Some of the fields in the various geodatabases had different field lengths than the destination. The ones that had longer field lengths were able to be merged into the new geodatabase but the features that had data in the fields that exceeded the destination were dropped from the target geodatabase. I've addressed this issue now and all of the features are now in the destination. 

Thanks for looking into this issue!