Discussion:
Materialized view refresh fails - m_row$$ column
Arun Chugh
2018-09-03 17:35:49 UTC
Permalink
All,

We have materialized view having m_row$$ column earlier in prod, but after
db refresh to lower env. the db link stopped working, which is fine, so
we re-created db link in non prod with different name, hence need to re
create the mview as well

while recreating mview at target database build immediate using index with
rowid option and refresh fast on demand option it is not allowing the
m_row$$ column in mview, as the column not exist in source base table
whereas the same is present in mview log table at source side. Even though
it is refreshing the mview without that m_row$$ column.

Now after somedays, it is giving below error, any idea why it is behaving
like this. Please suggest.

Ora-12018 and ora -00904 m_row$$ invalid identifier

Regards,
Arun
Mladen Gogala
2018-09-03 22:08:58 UTC
Permalink
You should trap the 904 error to find out what identifier is the problem.
Now after somedays, it is giving below error, any idea why it is
behaving like this.  Please suggest.
Ora-12018 and ora -00904 m_row$$ invalid identifier
Regards,
Arun
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217

--
http://www.freelists.org/webpage/oracle-l
Tony
2018-09-03 23:46:50 UTC
Permalink
Surely you are not attempting to build a materialised view on a materialised view log?

Cheers
Tony
Post by Mladen Gogala
You should trap the 904 error to find out what identifier is the problem.
Now after somedays, it is giving below error, any idea why it is
behaving like this.  Please suggest.
Ora-12018 and ora -00904 m_row$$ invalid identifier
Regards,
Arun
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
--
http://www.freelists.org/webpage/oracle-l
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Arun Chugh
2018-09-04 01:48:46 UTC
Permalink
Yes I am using source base table to create the mview. Not the mview log

Regards,
Arun
Post by Tony
Surely you are not attempting to build a materialised view on a materialised view log?
Cheers
Tony
On 4 September 2018 8:08:58 am AEST, Mladen Gogala <
Post by Mladen Gogala
You should trap the 904 error to find out what identifier is the problem.
Now after somedays, it is giving below error, any idea why it is
behaving like this. Please suggest.
Ora-12018 and ora -00904 m_row$$ invalid identifier
Regards,
Arun
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Arun Chugh
2018-09-04 01:47:28 UTC
Permalink
The problem is with m_row$$ identifier as it is not thr in the base table
but present in the mview log, so that the reason it is giving invalid
identifier

Regards,
Arun
Post by Mladen Gogala
You should trap the 904 error to find out what identifier is the problem.
Now after somedays, it is giving below error, any idea why it is
behaving like this. Please suggest.
Ora-12018 and ora -00904 m_row$$ invalid identifier
Regards,
Arun
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
--
http://www.freelists.org/webpage/oracle-l
Loading...