Complete Refresh Of Materialized View Hangs On Pipe Get
(Doc ID 1193294.1)
Last updated on AUGUST 17, 2020
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 18.104.22.168 [Release 10.2 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
When a complete refresh of materialized view having indexes defined against it hangs.
And after investigation it has been determined that this is on a "pipe get".
It is also noted that when the refresh is stopped it fails with
ORA-30438: unable to access named pipe 'IDX_RB$PIPE_32: operation timed out'.
The following wait times were also seen to highlight this issue:
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 120285 0.05 7.05
db file scattered read 13 0.00 0.01
direct path write 2 0.00 0.00
pipe get 229 4.88 1099.31
SQL> exec dbms_mview.refresh('<MATERIALIZED VIEW NAME>','C',atomic_refresh=>false);
BEGIN dbms_mview.refresh('<MATERIALIZED VIEW NAME>','C',atomic_refresh=>false); END;
ERROR at line 1:
ORA-20001: Job failed:
ORA-30438: unable to access named pipe 'IDX_RB$JIPIPE_123_3_PARAM'
Database was upgraded from 10.2.0.3 to 10.2.0.4
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document