Exadata - Oracle DB Materialized view getting Invalid
Issue #:
Materialized view getting Invalid after running everyday midnight and application team thinks it is because of Goldengate DDL enabled and it is causing problem.
Analysis #1:
Please can you share DDL statements for procedure, view and table of materialized view before and after midnight (before or after materialized getting invalid).
Goldengate configuration files (ggerror log file also) from source and target.
AWR and ADDM report from DB during materialized view getting invalid.
If tonight materialized get invalid, then recompile materialized view and provide error (simply run alter materialized view compile statement) and also take invalid objects list before and after materialized view getting invalid.
Analysis #2:
Please send the remaining items as soon as possible. As your manager mentioned, the more days this is not resolve, the more noise we will be hearing from business.
Kindly provide us the remaining items:
(2) All DDLs of the dependent objects of the materialized view from PROD and OGG databases.
(3) Golden Gate synchronization logs of the days on which the incidents happened.
(4) Golden Gate configuration files.
(5) AWR from OGG PROD database.
core DBA Team:
I have checked the MVIEW was in invalid state today also, I compiled it and now it is in VALID state.
Question to core DBA Team:
Did you compiled with normal command or used any procedure given my app team and then compiled materialized view?
Did you captured DDL’s statements before compiling INVALID materialized view from source and target DB’s?
core DBA Team:
I have Compiled normally...Alter materialized view NAME compile; No procedure was executed.
Yes! I have given you the DDL's before invalid state. Now am fetching the DDL's after validation.
Will update you once i got all DDL's
Question to core DBA Team:
I need DDL’s before compiling MVIEW (when it is invalid state). So that we can compare which procedure or table DDL changing.
Did you captured invalid objects before and after invalid MVIEW.
core DBA Team:
There were no invalid objects like before...only MVIEW was invalid state after the scheduler job was getting executed @12AM.
The base Tables and Materialized view table were in VALID state only though MVIEW was invalid state. SO, there is no issue with regards data and sync.
Question to core DBA Team:
Can you provide AWR and ADDM report from 11pm to 12am and 12am to 1am.
Can you share DDL’s from Source DB also.
select owner, object_name, object_type, created,last_ddl_time,timestamp,status from dba_objects where object_name in (‘’);
Solution:
As discussed in call,
- Materialized view is creating @ 10:30pm on 27th Feb. and schedular job for MVIEW is running after 11:30PM.
- There is no information recorded in DB level, from where and who is triggered this creating materialized view.
- Materialized view also shows expensive statement in DB level at 10:30pm to 12:30am
Action Items for Tomorrow:
1. Disable schedular job MVIEW (only for tonight)
2. 12:30am get status of MVIEW (valid or invalid state)
3. 7:00 am get status of MVIEW (valid or invalid state)
4. Manually run the schedular job MVIEW
5. Monitor job
Schedule another call tomorrow morning. We can close it by tomorrow.
To client:
We were trying to resolve the Golden gate issue for app report, and we had a detailed discussion with one of the Golden gate SME.
He has suggested few things to figure out the root cause (refer the action points highlighted in yellow in the above mail trail from Venu).
We would like your approval on disabling the batch job “NAME”. The impact of disabling would be just the data won’t get refreshed and we will manually refresh the data in the morning 9.00 AM.
Finally:
The Mview refresh was done successfully. Here we came accross new thing, after refresh also the MVIEW is still in VALID state.
Solution:
After Observed load in AWR report during that time, we tested with different time when less LOAD ( less activity ) on DB level and MVIEW ran successfully. So we scheduled that time permanently.
Comments
Post a Comment