Materialized View not getting refreshed

Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
PL/SQL Release 9.2.0.1.0 - Production
CORE 9.2.0.1.0 Production
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production
I am having a situation here..there a materialized view named mv_empdept,the base table of this MV is located on a remote database.Therefore the MV creation scripti contains a DB link.
Please find the script below.
Select Deptno,dept_name,empno,ename,DOB,Job
from [email protected];
The refresh mode of this MV is set as FAST,and the refresh cycle is scheduled through Oracle Job.
The job does get triggerd but from the log we found this error.
The error message is:ORA-12008: error in materialized view refresh path
ORA-01461: can bind a LONG value only for insert into a LONG column.
I even checked at the source Db and found that there is no mismatch as far datatype and datalength is concerned.
Strangely when i do a manual Complete refresh of the same MV the data does gets populated in mv_empdept snapshot.
Can anybody explain me the why the data is not getting populated in FAST refresh mode.
Your help is highly appreciated.
---Vineet

Read the following...
http://download.oracle.com/docs/cd/B10500_01/server.920/a96567/repmview.htm
and analyze the restrictions of Fast Refresh in your situation.

Similar Messages

Materialized view not fast refreshable

I need to calculate a moving total in a materialized view - that is, calculate subtotal for rows starting at current row up to the first row.
I am using a window function, as shown below.
The problem is, MVs using window functions are not fast refreshable, and I need this MV to be fast refreshable.
Is there any other way of getting the moving total without using a window function?
CREATE MATERIALIZED VIEW BIL_BI_OPDTL_MV_11_TST
--REFRESH FAST ON DEMAND
AS
SELECT
fact.txn_time_id txn_time_id
, fact.effective_time_id close_time_id
, prntmv.parent_group_id
, jgd.parent_group_id sales_group_id
, fact.lead_id
, fact.opp_open_status_flag
, fact.win_loss_indicator
, fact.forecast_rollup_flag
,fact.rev_flag1
, SUM(fact.rev_flag1) OVER (PARTITION BY
fact.effective_time_id , prntmv.parent_group_id
, fact.lead_id, fact.opp_open_status_flag, fact.win_loss_indicator, fact.forecast_rollup_flag
, to_number(to_char(opty_creation_date,'J'))
, to_number(to_char(opty_conversion_date,'J'))
ORDER BY fact.lead_id
ROWS UNBOUNDED PRECEDING) moving_total
, to_number(to_char(opty_creation_date,'J')) opty_creation_time_id
, to_number(to_char(opty_conversion_date,'J')) opty_conversion_time_id
,count(*) cnt
FROM bil.bil_bi_opty_ld_f_tst fact, bil_bi_rs_grp_mv rgmv, bil_bi_rs_grp_mv prntmv,
jtf.jtf_rs_groups_denorm jgd
WHERE rgmv.sales_group_id = fact.sales_group_id
and rgmv.salesrep_id = fact.salesrep_id
AND fact.sales_group_id = jgd.group_id
AND prntmv.sales_group_id = jgd.parent_group_id
AND prntmv.umarker in ('top_groups', 'groups')
AND jgd.active_flag='Y'
group by
fact.txn_time_id,
fact.effective_time_id
, prntmv.parent_group_id
, jgd.parent_group_id
, fact.lead_id
, fact.opp_open_status_flag
, fact.win_loss_indicator
, fact.forecast_rollup_flag
, fact.rev_flag1
, to_number(to_char(opty_creation_date,'J'))
, to_number(to_char(opty_conversion_date,'J'))

Please post your question at
General Database Discussions
for faster response

Materialized view not properly refreshing

Hi,
As materialized view is not refreshing properly. we compare the sum of hashcode materialized view with the sum of hash code of the base view or table the materialized view is defined. If it's found equal then materialized view got refreshed succesfully else not.
But in below example the column value is interchanged in between the row eventhough hashcode is same.
Is there any other way to find the materialized view got refreshed successfully or not.
SQL> create table temp as select object_name, subobject_name from user_objects where rownum<3;
Table created
SQL> select * from temp;
OBJECT_NAME SUBOBJECT_NAME
ATP_BN_I_1
ATP_START_END_DATE_I_2
SQL> create materialized view mv1 as select * from temp;
Materialized view created
SQL> select * from mv1;
OBJECT_NAME SUBOBJECT_NAME
ATP_BN_I_1
ATP_START_END_DATE_I_2
SQL> select sum(nvl(ora_hash("OBJECT_NAME"||"SUBOBJECT_NAME"),0)) from temp;
SUM(NVL(ORA_HASH("OBJECT_NAME"
4852176374
SQL> select sum(nvl(ora_hash("OBJECT_NAME"||"SUBOBJECT_NAME"),0)) from MV1;
SUM(NVL(ORA_HASH("OBJECT_NAME"
4852176374
SQL> UPDATE TEMP SET OBJECT_NAME=SUBOBJECT_NAME,SUBOBJECT_NAME=OBJECT_NAME;
2 rows updated
SQL> COMMIT;
Commit complete
SQL> select * from mv1;
OBJECT_NAME SUBOBJECT_NAME
ATP_BN_I_1
ATP_START_END_DATE_I_2
SQL> select * from temp;
OBJECT_NAME SUBOBJECT_NAME
ATP_BN_I_1
ATP_START_END_DATE_I_2
SQL> select sum(nvl(ora_hash("OBJECT_NAME"||"SUBOBJECT_NAME"),0)) from MV1;
SUM(NVL(ORA_HASH("OBJECT_NAME"
4852176374
SQL> select sum(nvl(ora_hash("object_name"||"subobject_name"),0)) from temp;
select sum(nvl(ora_hash("object_name"||"subobject_name"),0)) from temp
ORA-00904: "subobject_name": invalid identifier
SQL> select sum(nvl(ora_hash("OBJECT_NAME"||"SUBOBJECT_NAME"),0)) from temp;
SUM(NVL(ORA_HASH("OBJECT_NAME"
4852176374
Any help really appreciated.
Thanks in advance.

unique wrote:
Is there any other way to find the materialized view got refreshed successfully or not.You can look at the last_refresh_date and staleness columns of all_mviews: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/statviews_1105.htm#REFRN20139
Or maybe use the all_mview_refresh_times view: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/statviews_1104.htm#sthref1068
Regards,
Rob.

Materialised view not getting refreshed.

Hi All
I have created a Materialised view which looks at the master tables in another database... using a DB link. I use to have the refresh force option in the materialised view.. I recieve no error messages when I create DB link, create Mview and I can refresh the Mview manually.. but the auto refresh is not happening... for some reason.. Database version is 10.2.0.1 Standard Edition on Solaris 10 OS.
Below are the scripts I have used to create DB link and MView... Please do let me know if I am missing any detail.. in particular.. what could be the issue/miss here thats avoiding the auto refresh of MView.
Thank you in advance.
Sarat.
DB LINK :
create public database link FBS_DB_LINK.REGRESS.RDBMS.DEV.US.ORACLE.COM connect to FBSUSER20 identified by <pwd> using 'FBSTEST'
Materialized View :
CREATE MATERIALIZED VIEW TWPERFUSER.CASE_DETAILS
                PCTFREE 10 PCTUSED 0 INITRANS 2 MAXTRANS 255
                STORAGE(
                                INITIAL 64 K
                                MINEXTENTS 1
                                MAXEXTENTS UNLIMITED
                                PCTINCREASE 0
                                BUFFER_POOL DEFAULT
TABLESPACE USERS
LOGGING
NOCACHE
NOPARALLEL
USING INDEX     PCTFREE 10 INITRANS 1 MAXTRANS 255
                STORAGE(
                                BUFFER_POOL DEFAULT
REFRESH FORCE
                WITH ROWID
USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE AS
select frc.reg_case_id,fp.provider_id,fptm.name,fp.provider_name,flam.authority_name,fp.creation_date,fp.multicentre_flag,
                                                fp.commercial_for_profit_flag,fp.three_month_programmes_flag,frcsm.long_form,frcsm.short_form
                                from
                                                fbs_provider@FBS_DB_LINK fp,
                                                fbs_provider_type_mst@FBS_DB_LINK fptm,
                                                fbs_reg_case@FBS_DB_LINK frc,
                                                fbs_reg_case_status_mst@FBS_DB_LINK frcsm,
                                                fbs_address@FBS_DB_LINK fa,
                                                fbs_local_authority_mst@FBS_DB_LINK flam
                                where
                                                      frc.provider_id = fp.provider_id
                                       and    fp.provider_type_id = fptm.provider_type_id
                                       and    fp.address_id = fa.address_id
                                       and    fa.local_authority_id = flam.local_authority_id

Hi,
REFRESH FORCE
As per my knowledge
REFRESH COMPLETE NEXT <date>
else check for the job status
select job, what, last_date, last_sec, this_date, this_sec, next_date, next_sec, failures, broken from user_jobs ;
Thanks
Pavan Kumar N

Cube Materialized View not getting created

Hi
I have a cube which has 8 dimensions. Only one of the dimensions has a level based hierarchy and the rest are value based.
I have not created levels for value based hierarchies.
So the materialized view compataility screen tells me that I need to have levels in these value based hierarchies so that I can create a materialized view.
How can I get around or solve this issue ?

If you are querying the base tables, then creating a materialized view (cube or table based) and relying on query rewrite will usually make things faster. In this case you would need to include a GROUP BY in your SQL queries, and I don't know how you would do that with value hierarchies.
If, instead, you are querying the generated cube views, then creating a cube materialized view will make absolutely no difference to query times. This is the recommended approach, and is the best way to integate with clients such as OBIEE and Simba.

Materialized views not updating

I'm having trouble with getting a materialized view with fast refresh to update. I'm working between two schemas and have the global query rewrite privilege for both users. I've run the catrep.sql script to make sure it had been run and find that it has a lot of packages that don't compile, which I guess is expected as I'm not using Advanced Replication. I think the problem is that I can't get the dbms_snapshot package to compile so can't even update the view manually. Is there another script I need to run to make the materialized views work? Some other privilege or variable?
I've granted permissions on tables, views, materialized views, triggers, and snapshots to both users.
The log does get entries but never sends them to the views.
I have a base table and a log on the table in schema 1.
I have a materialized view in schema 2:
create materialized view log on schema1.document
tablespace app_mview
with primary key
( list columns needed);
create materialized view schema2.doc_mv
pctfree 0
tablespace app_mview
storage (initial 128k next 128k pctincrease 0)
refresh fast
start with sysdate
next sysdate + 1/1440
as select * from schema1.document
Does anyone know where my problem might be?
thanks for any help

I have temporary parameters, not in itit.ora but echoing the job_queue_processes is 10, job_queue_interval is 60.
a sho err returns no errors.
earlier I did not get anything new in dba_errors when trying to compile. Since I've rerun the catrep.sql I'm getting pls-00201 - identifier must be declared for a lot of dbms_snap, sys.dbms_alert, dbms_reputil2 etc. (package, package body, and trigger types) That is why I think there must be another script that should be run that I don't know about.
I can't do a full refresh because the dbms_snapshot package will not compile. I believe it's possible that both full and fast will work once I get the dbms_snapshot package working.
thanks for your help
pat

Urgent - MV not getting refreshed

I created a MV as under.
CREATE MATERIALIZED VIEW schema.abc_mv
TABLESPACE "aaa"
REFRESH FAST ON DEMAND START WITH sysdate+0 NEXT SYSDATE+5/1440
AS SELECT *
FROM abc@dblink;
Its not getting refreshed. Yesterday one record was inserted in the abc table but the MV was not refreshed. I tried refreshing the MV manually by running the below script but its still not working. PLEASE HELPPPP!
BEGIN
DBMS_MVIEW.REFRESH('abc_mv');
END;

For urgent issues please log with metalink

Report is not getting refreshed after changing prompts once again?

HI,
I am running some webi and deski reports using webi sdk also i'm handling the prompts of
report.
Problem is that if i ran the parametrized webi or deski report then my application shows the prompt page
then i fill all the prompt for the report it shows the data for selected prompt values.
But if i once again changed prompt values it shows data of previously selected prompt values not for
the currently changed prompt values. means reports not getting refreshed.
sometimes its work correctly.
What will be problem?
How can i resolve this issues?
Please help me
Thanks in advance
Harshad

The workflow is:
1. Refresh
2. Set Prompts
3. Get View.
then repeat.
Are you refreshing before setting prompts?
Sincerely,
Ted Ueda

Oracle BI Publisher Report from OEM12c data is not getting refreshed...

Hello,
We've integrated BI Publisher with EM12c. I've developed a report which checks a given database extents information (initial, next, maxextents) at tablespace level. The dataset is chosen as EM repository. The report runs absolutely fine until new data is added to a database. For eg, I created a new tablespace. The new tablespace related info is not getting refreshed despite the fact that I've refreshed the data source and checked that the tablespace exists in the database.
Can anyone pls help.
Thanks,
Dhananjay

Dhananjay,
Has the data in the EM repository view been refreshed? The report retrieves data via the published repository views. If the view does not display the latest information, then you will have to wait till the relevant config or monitoring collections are complete.

CRM Header data not getting refreshed in BADI when clicked in New order

We have used a ORDERADM_H BADI, header badi to populate some custom field values.
Step 1) While creating sales order in CRM(CRMD_ORDER), we are giving inputs such as sold to party , material etc.
Step 2) Before actually saving the order, we found that we dont need this order to be created and again click on create new button in the transaction. In order header BADI, order data for the previous order is not getting refreshed. The previous GUID is still there and function module CRM_ORDER_READ still retrieves the old order values which was cancelled in the previous step. It is causing lot of issues and finally giving dump.
basically the previous GUID is not getting refreshed. Please suggest

Pls send the code that you have in the Badi. Did you actually compare the GUIDs manually ? Instead of CRM_ORDER_READ have you tried using CRM_ORDER_READ_OW ?

Order by in MATERIALIZED VIEW not work successfully with first column (ID)

Dears,
I am trying to create a Materialized View as below:
CREATE MATERIALIZED VIEW HR.MV_EMP
PCTFREE 10
MAXTRANS 255
TABLESPACE users
STORAGE (
INITIAL 65536
MINEXTENTS 1
MAXEXTENTS 2147483645
BUILD IMMEDIATE
REFRESH ON DEMAND
AS
SELECT *
FROM employees
where rownum < 5000 order by employee_id desc ;But while querying the MATERIALIZED VIEW, it did not work successfully as the data did not appear in the accurate order.
I tried to create the same MATERIALIZED VIEW but order by another column (Column Date), it worked successfully and the data appeared in the accurate order.
It means that MATERIALIZED VIEW not work successfully with the first column (id).
Can you please help me in this ?
Thanks & regards,,

A few pointers :
1. As has been pointed out, the ROWNUM has been incorrectly placed. ROWNUM values are assigned as rows are fetched from the source before the ORDER BY. You need to ORDER BY first (in a SubQuery) and then ROWNUM afterwards (outside the SubQuery).
2. I wonder why you want only the last 5000 EMPLOYEE_IDs. What if Employee_ID 1 is still an active employee (he is the founder, first employee and CEO ?). There could be very many "low" EMPLOYEE_IDs that are still active.
3. Logically I would expect some filter other than the ROWNUM ... ORDER BY to be used to select candidate rows. Then, an ORDER BY in the CREATE query would be unnecessary.
4. When querying the Materialized View you must explicitly ORDER BY (irrespective of whether you did or did not do an ORDER BY in the CREATE ...)
5. How do you expect to refresh the MV ? Will it always be a COMPLETE Refresh ? Remember that your "5000 employees" filter would likely exclude older employees at the next refresh. If you use some other filter, it should be consistent across all refreshs.
Hemant K Chitale

Query against materialized view awful after refresh of Mview

We have a materialized view defined to refresh complete daily at 5am. YOu can run queries against the MV alone or joining it to other tables. Results come back in 2 or 3 seconds. Once the MView refreshes at 5am - those same queries now take 15 minutes or even more sometimes to complete. WHY IS THIS HAPPENING?? Help anyone?

okay this is better... sorry...
this is the GOOD EXPLAIN PLAN:
PLAN_TABLE_OUTPUT
| Id | Operation                         | Name             | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT                  |                   |     1 |   127 | 1665 |
|   1 | SORT AGGREGATE                   |                   |     1 |   127 |       |
|   2 |   NESTED LOOPS                    |                   |     1 |   127 | 1665 |
|   3 |    NESTED LOOPS                   |                   |     1 |   113 | 1664 |
|   4 |     NESTED LOOPS                  |                   |     1 |    99 | 1663 |
|   5 |      NESTED LOOPS                 |                   |     1 |    88 | 1662 |
|* 6 |       HASH JOIN ANTI              |                   |     1 |    70 | 1661 |
|* 7 |        TABLE ACCESS BY INDEX ROWID| CONTACT           | 3815 |   201K| 1534 |
|   8 |         AND-EQUAL                 |                   |       |       |       |
|* 9 |          INDEX RANGE SCAN         | IDX_CNT__C_STATE |       |       |       |
|* 10 |          INDEX RANGE SCAN         | IDX_CNT__STATUS   |       |       |       |
| 11 |        INDEX FAST FULL SCAN       | PK_RPP            | 69277 | 1082K|   120 |
|* 12 |       TABLE ACCESS BY INDEX ROWID | REP_PROFILE       |     1 |    18 |     1 |
|* 13 |        INDEX UNIQUE SCAN          | PK_C19            |     1 |       |       |
|* 14 |      INDEX UNIQUE SCAN            | PK_B01            |     1 |    11 |       |
|* 15 |     INDEX UNIQUE SCAN             | PK_B02            |     1 |    14 |       |
|* 16 |    INDEX UNIQUE SCAN              | PK_RCN            |     1 |    14 |       |
Predicate Information (identified by operation id):
   6 - access("B"."CONTACT_ID"="RPP"."PARTNERSHIP_ID")
   7 - filter("B"."C_STATE"='GA' AND "B"."C_LAST"<>'Name Unknown' AND
              "B"."STATUS"='Confirmed')
   9 - access("B"."C_STATE"='GA')
10 - access("B"."STATUS"='Confirmed')
12 - filter("C19"."TERR1"='46')
13 - access("B"."CONTACT_ID"="C19"."CONTACT_ID")
14 - access("B"."FIRM_ID"="B01"."FIRM_ID")
15 - access("B"."OFFICE_ID"="B02"."OFFICE_ID")
16 - access("B"."CONTACT_ID"="RCN"."CONTACT_ID")
Note: cpu costing is off
38 rows selected.

Enabling materialized view for fast refresh method

In AWM when i select refresh method as FAST and enable the materialized view, am getting the below error:
"Refresh method fast requires materialized view logs and a previously run complete refresh of the cube mv". i need this Fast refresh of a cube materialized view, so that it performs an incremental refresh and re-aggregation of only changed rows in the source table.
can anyone help me on this??

If you want the cube to hold data even after it has been deleted from the relational table, then you should disable the MV on the cube.
Synchronization with the source table is determined by the default "cube script".
<li>CLEAR, LOAD, SOLVE : This will synchronize your cube with the source table. It is a requirement for MVs.
<li>LOAD, SOLVE: This will allow your cube to contain data even after it has been removed from the source table. It sounds like you want this.
Cube builds can be "incremental" in one of two ways.
(1) You can have an "incremental LOAD" if the source table contains only the changed rows or if you use MV "FAST" or "PCT" refresh. Since you can't use MVs, you would need a source table with only the changed rows.
(2) You will have an "incremental SOLVE" (a.k.a. "incremental aggregation") if there is no "CLEAR VALUES" or "CLEAR AGGREGATES" step and various other conditions hold.
To force a "complete LOAD" with an "incremental SOLVE" you should have all rows in your source table and run the following build script.
LOAD, SOLVE You could also run "CLEAR LEAVES, LOAD, SOLVE" to synchronize the cube with the table.
To force an "incremental LOAD" with a "complete SOLVE" you make the source table contains only the changed rows and the run the following:
CLEAR AGGREGATES, LOAD, SOLVEor
LOAD, CLEAR AGGREGATES, SOLVEFinally, if you want both LOAD and SOLVE to be incremental you make the source table contains only the changed rows and the run the following:
LOAD, SOLVE

Material type not getting displayed in the cube........

Hi,
In my infocube material type for one of the material is not getting displayed.
When I check in the content of the cube for this material all the fileds are getting displayed except material type.
However it is present in the material master data from which it is put into the update rules to populate in the cube.
Its getting displayed for some other materials , so we cant say that mapping is wrong or problem with update rules.
Can some body let me know what could be the reason.
Thanks,
Jeetu

Hi Jeetu,
can you check in your cube if you have for one material, entries with AND entries without the MATL_TYPE? If this is the case then you were loading transactional data before having the corresponding material master data.
You should adapt your scenario:
- first do not use the standard attribute derivation during your URules: performance is very bad.
- implement a start routine filling an internal table with your material and MATL_TYPE for all entries of material in your datapackage.
- implement an update routine on the MATL_TYPE with a READ on this internal table an raise an ABORT = 4 if the MATL_TYPE is initial or the material in not found.
Now to fix your situation you'll have to reload your cube or alternatively just reload your missing MATL_TYPE MATERIAL from your cube itself and selective delete those which are empty.
hope this helps...
Olivier.

Data is not Getting refresh in Dashboard

Hi I have implemented Xcelsius on the top of SAP BI System.
I have the following architecture -
SAP BI Cube --> BO XI 3.1 Universe Based on Cube --> QWaaS on the Universe --> Xcelsius Dashboard on the QWaas.
When i created a dashboard and run it , it worked fine and showed me data , which is lying in Cube.
But When the Data get updated in Cube and i again refresh the Dashboard , It still showing me the old data , the Data is not getting refresh in Dashboard .
what could be the possible casue ?
Is QWaas always fetch the dat at run time ?
Thanks

QaaWS web service call needs to be invoked to get the data updates from the datasource. Xcelsius provides several options to command how frequently web services connections are calle/refreshed ('refresh on load', 'refresh every X seconds' or trigger cells...).
You should also keep in mind, that, since QaaWS hits datasource each time web service is called, this can bring some performance issues (web service calls WebI server to run corresponding query, which performs a refresh). In order to mitigate this, since XI 3.0, QaaWS features a cache mechanism, that is used to store data results from each query refresh (corresponding to a web service call), in order to serve it again with better efficiency, in case same request is performed during a specific time interval (which typically corresponds to dashboard interactions).
Cache sessions are sorted according to the user names and prompt values used, cache is emptied after a defauilt duration without any interaction (request from the same session).
Cache timeout duration is set for each QaaWS query, and can be tuned from QaaWS Designer when modifying/creating the query : go to Advanced... button on first step of query edition wizard, cache lifetime corresponds to timeout value (in seconds) displayed on Advanced parameter panel (default value being set to 60 seconds).
Cache lifetime may also be an explanation why you do not see data refreshed (if you are with QaaWS XI 3.0 or later).
Hope that helps,
David.

Materialized View not getting refreshed

Similar Messages

Maybe you are looking for