Wondering about anyone elses experience with Logical Standy Databases

Question

I setup a LSB database. It's been functioning fine for small changes made at the Primary database but periodically, I need to migrate tables and schemas from a test environment to the Primary database. Normally, I perform TRUNCATE table on all the tables affected and then import the data. One table is more than 2 million rows.
I performed the TRUNCATE operation and the import operation on the primary database two days ago but LSB is having fits trying to apply the inserts that is mined from the impdp process performed on the Primary db.
On the Primary database, the impdp operation importing 2 million rows generated about 10 archived redologs of 100M each. Those logs made it to the LSB database but on the LSB side, I've already blown through 64Gbytes of UNDO space while the SQL Apply only appears to have worked it's way into the second of the 10 transported redologs.
Should LSB be able to handle situations like this or am I using it for an incorrect type of application?
Any thoughts?
Thanks,
John S.

Answer 1

The 2 potential issues you may have are:
1) Potentially importing the wrong transport in to the wrong system. Since all systems dump their data files in the same directory all transports are available to be imported into each system...this just requires care.
2) Since all systems dump their data, cofiles, temp and logs files in the same directory, it can get huge quickly if you don't proactively clean it up. If too many files accumlate in the directories clean up and browsing the directories with be much, much harder...