My Oracle Support Banner

Complete Refresh Of Materialized View Hangs On Pipe Get (Doc ID 1193294.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2 to 12.1]
Information in this document applies to any platform.


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('MV_CUR_PSN_IDM','C',atomic_refresh=>false);
BEGIN dbms_mview.refresh('MV_CUR_PSN_IDM','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 to


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.