Last updated on FEBRUARY 22, 2014
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
Information in this document applies to any platform.
Words 'materialized view' and mview are used interchangeably in this document.
After installing 184.108.40.206.7 PSU (<Patch 16619892>), fast refresh of certain materialized views errors out. All these refreshes worked without error prior to the application of the 220.127.116.11.7 PSU.
If the fast refresh has been initiated while no change needs to be applied to the mview (e.g. corresponding mview log(s) is (are) empty), then the refresh completes, but the following error is logged in the alert log:
ORA-01741: illegal zero-length identifier
In such a case the tefresh code generates the following internal SQL where the indentifier in the WITH clause is empty string, hence the ORA-01741:
PARSE ERROR #46964325355104:len=1663 dep=2 uid=0 oct=3 lid=0 tim=1374763343678838 err=1741 WITH "" AS ( SELECT /*+ RESULT_CACHE(LIFETIME=SESSION) */ "MAS$"."RID$" ...
The above can be seen in SQL (10046) trace, or dumping an errorstack on 1741.
Otherwise, the fast refresh may error out with ORA-600 error like the following during parsing the mview definition query:
ORA-00600 [kkzgajdl_dltgen-0], 
ORA-00600 [kghstack_free1], [kkzgjctx:cta]
ORA-00600 [expecting modified table]
Note, you may also see the above errors while commit is done on the master table of an on commit materialized view, as the commit triggers fast refresh of the mview.
18.104.22.168.7 PSU (<Patch 16619892>) has been applied.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms