OK, Finally after spending weeks of time to figure out what was going wrong with my import (IMPDP), it turns out to be a bug in 11gR2.
Was trying to import about 80G dumpfiles and impdp keeps failing on the last table with
Followed Metalink Doc: 1434643.1 (Data Pump (or other Oracle process) Reports ORA-01628: Max # Extents (32765) For Rollback Segment _SYSSMUx$) steps by shrinking and creating a new UNDO TS and etc., etc., but no use. That error kept poping up.
The thing is the table it was getting stuck is only about 9.5G with 93M records and UNDO still has about 30G left. It loads up 99% and then hangs with the wait event "wait for unread message on broadcast channel".
Note that this wait event is not just waiting on that continuously though. It only says waited a second or less than a second but never changes anything apart from that wait event.
Finally impdp will fail like 20-30 hours later with that above said error!!!!
Ok, enough blogging on this.
Reason for the error is, It's an Oracle Bug they recently identified and confirmed.
So, need to apply a patch "Patch 17306264: ORA-1628: MAX # EXTENTS (32765) REACHED FOR ROLLBACK SEGMENT - OFTEN ENCOUNTERE" and see how if the issue will be resolved or not.
Will know in couple of days.
Was trying to import about 80G dumpfiles and impdp keeps failing on the last table with
ORA-39171:
Job is experiencing a resumable wait.
ORA-01628:
max # extents (32765) reached for rollback segment _SYSSMU499_3908321086$
Followed Metalink Doc: 1434643.1 (Data Pump (or other Oracle process) Reports ORA-01628: Max # Extents (32765) For Rollback Segment _SYSSMUx$) steps by shrinking and creating a new UNDO TS and etc., etc., but no use. That error kept poping up.
The thing is the table it was getting stuck is only about 9.5G with 93M records and UNDO still has about 30G left. It loads up 99% and then hangs with the wait event "wait for unread message on broadcast channel".
Note that this wait event is not just waiting on that continuously though. It only says waited a second or less than a second but never changes anything apart from that wait event.
Finally impdp will fail like 20-30 hours later with that above said error!!!!
Ok, enough blogging on this.
Reason for the error is, It's an Oracle Bug they recently identified and confirmed.
So, need to apply a patch "Patch 17306264: ORA-1628: MAX # EXTENTS (32765) REACHED FOR ROLLBACK SEGMENT - OFTEN ENCOUNTERE" and see how if the issue will be resolved or not.
Will know in couple of days.
No comments:
Post a Comment