What your note tries to say is that you are "stuck" in the delete phase of
the load.
This has nothing to do with "relational integrity"!
It means that you have indexes that are unique (at least one) and that the
delete phase of the load has identifie duplicate keys. Since the load and
build phase are done, it is deleting the rows from the table, writing error
messages to the message file and "logging" (I didn't want to use capitals)
the deletes.
maybe your source table where the cursor is running has a lot of duplicates
for the target index !!! But if you are "stuck" in the delete phase, that's
what it is doing.
HTH, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"technocrat" <su************@gmail.com> a écrit dans le message de news:
11**********************@i39g2000cwa.googlegroups. com...
I am trying to load from a cursor which selects 124 million
records...but while loading it completes the build phase and it stuck
..I think...at the delete phase(which in turn looks like doing the
relational Integrity thing) according my DBA at around 4%...Is there a
way to speed this up and try to get it done sooner...This has been
running for almost 2 hrs now and seems no near to completion...
Any suggestions are welcome...
