Doubt in materailized view

Hi,
version : Oracle 9.2
I have a master site. It contains 25 tables, which has a default column value.
Can i create updatable materialized view for those tables with default column value?
If yes, please tell me....
Thanks in Advance...

Two thoughts.
1. Why couldn't you?
2. Why didn't you just try and find out?
I hope you realize 9.2 will be fully desupported in just a matter of a few months. Wouldn't your efforts be better spent moving to 11.1.0.7 or above?

Similar Messages

Doubt about Tunning View Objects

Hi !. I have the following doubt about tunning View Objects:
If I have the following configuration on a VO:
All Rows
In Batches Of: 11
As Needed
Access Mode: Scrollable
Range Size: 10
Total Records On The Table: More than 100
What would happen is that while the initial render, the view cache is fetch with 11 rows from the table and the ui table shows 10. In subsequent scroll events, more queries again will be done but not when the user scrolls back. My doubt is this one: Why, while the initial render If I put a breakpoint in this overrided method executeQueryForCollection, the execution reachs there but in subsequent scroll events (forward) the execution doesn't reach there ?. I understand thast this should happen as the required rows are not yet in the cache. I would like to know a way to test this access mode and what method is executed in every roundtrip to the DB. Thankx !.

I don't think ADF needs to execute the query again - it just needs to fetch the next set of records.
So if the cursor is already open, no need to issue another query.
You can use the HTTP Analyzer to watch network traffic
Monitoring ADF Pages Round-Trips with the HTTP Analyzer
And you can use the logging features of ADF to see the queries being executed.
Declarative View Objects (VOs) for better ADF performance

Doubts related to views urgent help needed

Hi all ,
i am new to oracle technology and have a doubt related to VIEWS
i have a master table job_master and i have preapred a view of the master table as
job_master_view
The view i created as create view job_master_view as select * from job_master
Now my doubt is if i exevute a SELECT FOR UPDATE NOWAIT query on the view job_master_view then will corresponding row of the master table also be locked
I am trying to execute above query to avoid simultaneous access by multiple users
I the above approach correct ? and will the row of master table get locked ?
please let me know in case my query is not clear
Thanking in advance
Regards

My question is, how long you are going to hold lock on these table? If not, you can only use select for update with requried records using where cluase. I also suggest other application which updates this table to use same kind of statement, with NOWAIT caluse, when these applicationg trying to get a lock on these records and found already locked my other, it wont block or wait, just statement fails and can be re-tried again.
Bascially triggers are used for sort of action not for selecting data. What you can do is that develop a procedure and call it in the trigger and in the procedure you can easily use dbms_outout.put_line to display output on the sqlprompt.
Jaffar

Doubt in attribute view on joining the table .

Hello Team
                    Can some please help me in clearing the following doubts on joining tables .
i) Can we perform a self join in attribute view in HANA . like for ex :- joining a table to itself .
ii)Can we create an analytic view without creating an attribute view i.e creating an analytic view directly on tables .
iii)When aggregation happens in calculation view exactly what happens internally .
Please suggest me with the solution of these doubts .
Regards

Hi Prag,
As Rashmi has answered your question, i would like to add up to it few more important points.
1. Do not perform self join as it will return uncertain results. It is better to avoid self join.
You can create a copy of the same table and perform join which will be consistent.
2. In an analytic view, you will be adding table to data foundation, select the output fields.In the logical join node by default your data foundation will be present (this will contain the fields that you selected for output), you need not add any attribute view to this logical join node, leave it to default. In the semantics node select the attributes and measures. Perform validation and then activate. Your analytic view without attribute view is ready. You can check the data preview.
3. In a calculation view, the records gets grouped by all the attributes and then the measures are calculated based on this grouping by using the mentioned aggregation (sum/max/min).
Eg.
Customer ID 0Calmonth Amount (aggregation = max)
1001               01.2014     100
1001               01.2014     400
1002               01.2014     200
Output:
Customer ID 0Calmonth Amount (aggregation = max)
1001               01.2014     400
1002               01.2014     200
Hope this clarifies your doubts.
Thanks and Regards,
M.N.Adinarayanan

Difference between materailized view and a table

hey hiii
i want to know what is a difference between a materialized view and a table i.e suppose i create a table A and another table B on table A i have created a trigger which will upload all the changes made in A ie insert,update or delete so whether this will perform all the action that a materialized view can perform on A or is there any difference between them
thks

I'll add to Nicolas' answer that the MV maintenance does have access to mechsnisms other than row-by-row replication of the trigger-based type. Direct path inserts to the base table are very efficiently propagated to the MV, as are partition-based DDL operations. Also MV's come with optional query rewrite built in (you need 10g+ to query rewrite to a non-MV data set), and scheduled refresh so you can defer maintenance of the data set until later.
MV maintenance can be less efficient though -- you may know something about the data and the way that it changes that allows you to write more efficient meintenance than the MV code.

Doubt Regarding Materialized View

Hello,
I am working on Oracle 10g.
We have multiple materialized Views which we Refresh in every 15 mins. My question is that can we get data from these MV's for a particular date....??

When i am Executing a query ..which was mentioned in the earlier post...m getting a particular error.
My Query
select * from db_rational_status_reaffirm_mv as of timestamp sysdate-1
Error m Getting
ORA-01555: snapshot too old : rollback segment number 4 with name "_SYSSMU4$" too small
Any Solution ..?

Doubt on Materialized view

Hi all,
I want to create materialized view, which will refresh the materialized view whenever, there is COMMIT on base table. The following
statement is correct for this requirement.
CREATE MATERIALIZED VIEW my_MV
BUILD IMMEDIATE
REFRESH COMPLETE
ON COMMIT
AS SELECT * FROM EMP@REMOTEDB;
and my question here is , is START WITH and NEXT values are required to fullfill my requirement.
Thanks,
Pal

Hi,
If U need view to referesh to when base table is committed, then no need of start with and next.
START WITH CLAUSE --- > Specify a datetime expression for the first automatic refresh time
NEXT Clause --->
Specify a datetime expression for calculating the interval between automatic refreshes.
Both the START WITH and NEXT values must evaluate to a time in the future. If you omit the START WITH value, then the database determines the first automatic refresh time by evaluating the NEXT expression with respect to the creation time of the materialized view. If you specify a START WITH value but omit the NEXT value, then the database refreshes the materialized view only once. If you omit both the START WITH and NEXT values, or if you omit the create_mv_refresh entirely, then the database does not automatically refresh the materialized view.
Regards,
Simma,,,

Doubt in Create View Syntax

Hi All,
I want to know the logic behind the following create view statement. Primarily I want to know about the significance of "with" statement in the following command.
CREATE OR REPLACE FORCE VIEW ODS_DEV.RPT_BU_GEN_REV_V_2
(HRCHY_ID, FRE_ID, S_BU_ID, BU_ID, EFF_FROM_DT,
EFF_TO_DT, ACTIVE_FLG, HRCHY_NM_LONG, HRCHY_LVL_NB, S_LVL1,
LVL1, NM_LONG_1, LOB_CD_1, LVL_NB_1, LVL_NM_1,
S_LVL2, LVL2, NM_LONG_2, LOB_CD_2, LVL_NB_2,
LVL_NM_2, S_LVL3, LVL3, NM_LONG_3, LOB_CD_3,
LVL_NB_3, LVL_NM_3, S_LVL4, LVL4, NM_LONG_4,
LOB_CD_4, LVL_NB_4, LVL_NM_4, S_LVL5, LVL5,
NM_LONG_5, LOB_CD_5, LVL_NB_5, LVL_NM_5, S_LVL6,
LVL6, NM_LONG_6, LOB_CD_6, LVL_NB_6, LVL_NM_6,
S_LVL7, LVL7, NM_LONG_7, LOB_CD_7, LVL_NB_7,
LVL_NM_7, S_LVL8, LVL8, NM_LONG_8, LOB_CD_8,
LVL_NB_8, LVL_NM_8, S_LVL9, LVL9, NM_LONG_9,
LOB_CD_9, LVL_NB_9, LVL_NM_9, S_LVL10, LVL10,
NM_LONG_10, LOB_CD_10, LVL_NB_10, LVL_NM_10, S_LVL11,
LVL11, NM_LONG_11, LOB_CD_11, LVL_NB_11, LVL_NM_11,
S_LVL12, LVL12, NM_LONG_12, LOB_CD_12, LVL_NB_12,
LVL_NM_12, S_LVL13, LVL13, NM_LONG_13, LOB_CD_13,
LVL_NB_13, LVL_NM_13, S_LVL14, LVL14, NM_LONG_14,
LOB_CD_14, LVL_NB_14, LVL_NM_14, S_LVL15, LVL15,
NM_LONG_15, LOB_CD_15, LVL_NB_15, LVL_NM_15, S_LVL16,
LVL16, NM_LONG_16, LOB_CD_16, LVL_NB_16, LVL_NM_16,
S_LVL17, LVL17, NM_LONG_17, LOB_CD_17, LVL_NB_17,
LVL_NM_17, S_LVL18, LVL18, NM_LONG_18, LOB_CD_18,
LVL_NB_18, LVL_NM_18, S_LVL19, LVL19, NM_LONG_19,
LOB_CD_19, LVL_NB_19, LVL_NM_19, S_LVL20, LVL20,
NM_LONG_20, LOB_CD_20, LVL_NB_20, LVL_NM_20, S_LVL21,
LVL21, NM_LONG_21, LOB_CD_21, LVL_NB_21, LVL_NM_21,
S_LVL22, LVL22, NM_LONG_22, LOB_CD_22, LVL_NB_22,
LVL_NM_22, S_LVL23, LVL23, NM_LONG_23, LOB_CD_23,
LVL_NB_23, LVL_NM_23, S_LVL24, LVL24, NM_LONG_24,
LOB_CD_24, LVL_NB_24, LVL_NM_24, S_LVL25, LVL25,
NM_LONG_25, LOB_CD_25, LVL_NB_25, LVL_NM_25, S_LVL26,
LVL26, NM_LONG_26, LOB_CD_26, LVL_NB_26, LVL_NM_26,
S_LVL27, LVL27, NM_LONG_27, LOB_CD_27, LVL_NB_27,
LVL_NM_27, S_LVL28, LVL28, NM_LONG_28, LOB_CD_28,
LVL_NB_28, LVL_NM_28, S_LVL29, LVL29, NM_LONG_29,
LOB_CD_29, LVL_NB_29, LVL_NM_29, S_LVL30, LVL30,
NM_LONG_30, LOB_CD_30, LVL_NB_30, LVL_NM_30)
AS
WITH parse1 AS
(SELECT hrchy_id, fre_id, bu_node_id s_node_id, eff_from_dt, eff_to_dt, active_flg, hrchy_nm_long,
     substr(path, instr(path, '/', 1, 1) +1, instr(path, '/', 1, 2) - instr(path, '/', 1, 1) -1) gen_prnt1,
     substr(path, instr(path, '/', 1, 2) +1, instr(path, '/', 1, 3) - instr(path, '/', 1, 2) -1) gen_prnt2,
     substr(path, instr(path, '/', 1, 3) +1, instr(path, '/', 1, 4) - instr(path, '/', 1, 3) -1) gen_prnt3,
     substr(path, instr(path, '/', 1, 4) +1, instr(path, '/', 1, 5) - instr(path, '/', 1, 4) -1) gen_prnt4,
     substr(path, instr(path, '/', 1, 5) +1, instr(path, '/', 1, 6) - instr(path, '/', 1, 5) -1) gen_prnt5,
     substr(path, instr(path, '/', 1, 6) +1, instr(path, '/', 1, 7) - instr(path, '/', 1, 6) -1) gen_prnt6,
     substr(path, instr(path, '/', 1, 7) +1, instr(path, '/', 1, 8) - instr(path, '/', 1, 7) -1) gen_prnt7,
     substr(path, instr(path, '/', 1, 8) +1, instr(path, '/', 1, 9) - instr(path, '/', 1, 8) -1) gen_prnt8,
     substr(path, instr(path, '/', 1, 9) +1, instr(path, '/', 1, 10) - instr(path, '/', 1, 9) -1) gen_prnt9,
     substr(path, instr(path, '/', 1, 10) +1, instr(path, '/', 1, 11) - instr(path, '/', 1, 10) -1) gen_prnt10,
     substr(path, instr(path, '/', 1, 11) +1, instr(path, '/', 1, 12) - instr(path, '/', 1, 11) -1) gen_prnt11,
     substr(path, instr(path, '/', 1, 12) +1, instr(path, '/', 1, 13) - instr(path, '/', 1, 12) -1) gen_prnt12,
     substr(path, instr(path, '/', 1, 13) +1, instr(path, '/', 1, 14) - instr(path, '/', 1, 13) -1) gen_prnt13,
     substr(path, instr(path, '/', 1, 14) +1, instr(path, '/', 1, 15) - instr(path, '/', 1, 14) -1) gen_prnt14,
     substr(path, instr(path, '/', 1, 15) +1, instr(path, '/', 1, 16) - instr(path, '/', 1, 15) -1) gen_prnt15,
     substr(path, instr(path, '/', 1, 16) +1, instr(path, '/', 1, 17) - instr(path, '/', 1, 16) -1) gen_prnt16,
     substr(path, instr(path, '/', 1, 17) +1, instr(path, '/', 1, 18) - instr(path, '/', 1, 17) -1) gen_prnt17,
     substr(path, instr(path, '/', 1, 18) +1, instr(path, '/', 1, 19) - instr(path, '/', 1, 18) -1) gen_prnt18,
     substr(path, instr(path, '/', 1, 19) +1, instr(path, '/', 1, 20) - instr(path, '/', 1, 19) -1) gen_prnt19,
     substr(path, instr(path, '/', 1, 20) +1, instr(path, '/', 1, 21) - instr(path, '/', 1, 20) -1) gen_prnt20,
     substr(path, instr(path, '/', 1, 21) +1, instr(path, '/', 1, 22) - instr(path, '/', 1, 21) -1) gen_prnt21,
     substr(path, instr(path, '/', 1, 22) +1, instr(path, '/', 1, 23) - instr(path, '/', 1, 22) -1) gen_prnt22,
     substr(path, instr(path, '/', 1, 23) +1, instr(path, '/', 1, 24) - instr(path, '/', 1, 23) -1) gen_prnt23,
     substr(path, instr(path, '/', 1, 24) +1, instr(path, '/', 1, 25) - instr(path, '/', 1, 24) -1) gen_prnt24,
     substr(path, instr(path, '/', 1, 25) +1, instr(path, '/', 1, 26) - instr(path, '/', 1, 25) -1) gen_prnt25,
     substr(path, instr(path, '/', 1, 26) +1, instr(path, '/', 1, 27) - instr(path, '/', 1, 26) -1) gen_prnt26,
     substr(path, instr(path, '/', 1, 27) +1, instr(path, '/', 1, 28) - instr(path, '/', 1, 27) -1) gen_prnt27,
     substr(path, instr(path, '/', 1, 28) +1, instr(path, '/', 1, 29) - instr(path, '/', 1, 28) -1) gen_prnt28,
     substr(path, instr(path, '/', 1, 29) +1, instr(path, '/', 1, 30) - instr(path, '/', 1, 29) -1) gen_prnt29,
     substr(path, instr(path, '/', 1, 30) +1, instr(path, '/', 1, 31) - instr(path, '/', 1, 30) -1) gen_prnt30,
hrchy_lvl_nb
FROM rpt_bu_gen_rev_v),
parse2 AS
(SELECT a.hrchy_id, a.fre_id, a.s_node_id s_bu_id, LTRIM(a.s_node_id,'S') bu_id, a.eff_from_dt, a.eff_to_dt,
a.active_flg, a.hrchy_nm_long,
a.hrchy_lvl_nb, a.gen_prnt1 s_lvl1,
LTRIM (a.gen_prnt1, 'S') lvl1, a.gen_prnt2 s_lvl2,
LTRIM (a.gen_prnt2, 'S') lvl2, a.gen_prnt3 s_lvl3,
LTRIM (a.gen_prnt3, 'S') lvl3, a.gen_prnt4 s_lvl4,
LTRIM (a.gen_prnt4, 'S') lvl4, a.gen_prnt5 s_lvl5,
LTRIM (a.gen_prnt5, 'S') lvl5, a.gen_prnt6 s_lvl6,
LTRIM (a.gen_prnt6, 'S') lvl6, a.gen_prnt7 s_lvl7,
LTRIM (a.gen_prnt7, 'S') lvl7, a.gen_prnt8 s_lvl8,
LTRIM (a.gen_prnt8, 'S') lvl8, a.gen_prnt9 s_lvl9,
LTRIM (a.gen_prnt9, 'S') lvl9, a.gen_prnt10 s_lvl0,
LTRIM (a.gen_prnt10, 'S') lvl10, a.gen_prnt11 s_lvl11,
LTRIM (a.gen_prnt11, 'S') lvl11, a.gen_prnt12 s_lvl12,
LTRIM (a.gen_prnt12, 'S') lvl12, a.gen_prnt13 s_lvl13,
LTRIM (a.gen_prnt13, 'S') lvl13, a.gen_prnt14 s_lvl14,
LTRIM (a.gen_prnt14, 'S') lvl14, a.gen_prnt15 s_lvl15,
LTRIM (a.gen_prnt15, 'S') lvl15, a.gen_prnt16 s_lvl16,
LTRIM (a.gen_prnt16, 'S') lvl16, a.gen_prnt17 s_lvl17,
LTRIM (a.gen_prnt17, 'S') lvl17, a.gen_prnt18 s_lvl18,
LTRIM (a.gen_prnt18, 'S') lvl18, a.gen_prnt19 s_lvl19,
LTRIM (a.gen_prnt19, 'S') lvl19, a.gen_prnt20 s_lvl20,
LTRIM (a.gen_prnt20, 'S') lvl20, a.gen_prnt21 s_lvl21,
LTRIM (a.gen_prnt21, 'S') lvl21, a.gen_prnt22 s_lvl22,
LTRIM (a.gen_prnt22, 'S') lvl22, a.gen_prnt23 s_lvl23,
LTRIM (a.gen_prnt23, 'S') lvl23, a.gen_prnt24 s_lvl24,
LTRIM (a.gen_prnt24, 'S') lvl24, a.gen_prnt25 s_lvl25,
LTRIM (a.gen_prnt25, 'S') lvl25, a.gen_prnt26 s_lvl26,
LTRIM (a.gen_prnt26, 'S') lvl26, a.gen_prnt27 s_lvl27,
LTRIM (a.gen_prnt27, 'S') lvl27, a.gen_prnt28 s_lvl28,
LTRIM (a.gen_prnt28, 'S') lvl28, a.gen_prnt29 s_lvl29,
LTRIM (a.gen_prnt29, 'S') lvl29, a.gen_prnt30 s_lvl30,
LTRIM (a.gen_prnt30, 'S') lvl30
FROM parse1 a)
SELECT b.hrchy_id, b.fre_id, b.s_bu_id, b.bu_id, b.eff_from_dt, b.eff_to_dt, b.active_flg, b.hrchy_nm_long, b.hrchy_lvl_nb,
CAST(b.s_lvl1 AS VARCHAR2(13)) s_lvl1,
CAST(b.lvl1 AS VARCHAR2(13)) lvl1,
(CASE WHEN b.lvl1 is not null then (select x.nm_long from bu x where x.fre_id=b.fre_id and x.bu_id=b.lvl1)END) nm_long_1,
(CASE WHEN b.lvl2 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl2)END) lob_cd_1,
'' lvl_nb_1,
'' lvl_nm_1,
CAST(b.s_lvl2 AS VARCHAR2(13)) s_lvl2,
CAST(b.lvl2 AS VARCHAR2(13)) lvl2,
(CASE WHEN b.lvl2 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl2)END) nm_long_2,
(CASE WHEN b.lvl2 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl2)END) lob_cd_2,
'' lvl_nb_2,
'' lvl_nm_2,
CAST(b.s_lvl3 AS VARCHAR2(13)) s_lvl3,
CAST(b.lvl3 AS VARCHAR2(13)) lvl,
(CASE WHEN b.lvl3 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl3)END) nm_long_3,
(CASE WHEN b.lvl3 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl3)END) lob_cd_3,
'' lvl_nb_3,
'' lvl_nm_3,
CAST(b.s_lvl4 AS VARCHAR2(13)) s_lvl4,
CAST(b.lvl4 AS VARCHAR2(13)) lvl4,
(CASE WHEN b.lvl4 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl4)END) nm_long_4,
(CASE WHEN b.lvl4 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl4)END) lob_cd_4,
'' lvl_nb_4,
'' lvl_nm_4,
CAST(b.s_lvl5 AS VARCHAR2(13)) s_lvl5,
CAST(b.lvl5 AS VARCHAR2(13)) lvl5,
(CASE WHEN b.lvl5 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl5)END) nm_long_5,
(CASE WHEN b.lvl5 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl5)END) lob_cd_5,
'' lvl_nb_5,
'' lvl_nm_5,
CAST(b.s_lvl6 AS VARCHAR2(13)) s_lvl6,
CAST(b.lvl6 AS VARCHAR2(13)) lvl6,
(CASE WHEN b.lvl6 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl6)END) nm_long_6,
(CASE WHEN b.lvl6 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl6)END) lob_cd_6,
'' lvl_nb_6,
'' lvl_nm_6,
CAST(b.s_lvl7 AS VARCHAR2(13)) s_lvl7,
CAST(b.lvl7 AS VARCHAR2(13)) lvl7,
(CASE WHEN b.lvl7 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl7)END) nm_long_7,
(CASE WHEN b.lvl7 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl7)END) lob_cd_7,
'' lvl_nb_7,
'' lvl_nm_7,
CAST(b.s_lvl8 AS VARCHAR2(13)) s_lvl8,
CAST(b.lvl8 AS VARCHAR2(13)) lvl8,
(CASE WHEN b.lvl8 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl8)END) nm_long_8,
(CASE WHEN b.lvl8 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl8)END) lob_cd_8,
'' lvl_nb_8,
'' lvl_nm_8,
CAST(b.s_lvl9 AS VARCHAR2(13)) s_lvl9,
CAST(b.lvl9 AS VARCHAR2(13)) lvl9,
(CASE WHEN b.lvl9 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl9)END) nm_long_9,
(CASE WHEN b.lvl9 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl9)END) lob_cd_9,
'' lvl_nb_9,
'' lvl_nm_9,
CAST(b.s_lvl0 AS VARCHAR2(13)) s_lvl10,
CAST(b.lvl10 AS VARCHAR2(13)) lvl10,
(CASE WHEN b.lvl10 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl10)END) nm_long_10,
(CASE WHEN b.lvl10 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl10)END) lob_cd_10,
'' lvl_nb_10,
'' lvl_nm_10,
CAST(b.s_lvl11 AS VARCHAR2(13)) s_lvl11,
CAST(b.lvl11 AS VARCHAR2(13)) lvl11,
(CASE WHEN b.lvl11 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl11)END) nm_long_11,
(CASE WHEN b.lvl11 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl11)END) lob_cd_11,
'' lvl_nb_11,
'' lvl_nm_11,
CAST(b.s_lvl12 AS VARCHAR2(13)) s_lvl12,
CAST(b.lvl12 AS VARCHAR2(13)) lvl12,
(CASE WHEN b.lvl12 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl12)END) nm_long_12,
(CASE WHEN b.lvl12 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl12)END) lob_cd_12,
'' lvl_nb_12,
'' lvl_nm_12,
CAST(b.s_lvl13 AS VARCHAR2(13)) s_lvl13,
CAST(b.lvl13 AS VARCHAR2(13)) lvl13,
(CASE WHEN b.lvl13 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl13)END) nm_long_13,
(CASE WHEN b.lvl13 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl13)END) lob_cd_13,
'' lvl_nb_13,
'' lvl_nm_13,
CAST(b.s_lvl14 AS VARCHAR2(13)) s_lvl14,
CAST(b.lvl14 AS VARCHAR2(13)) lvl14,
(CASE WHEN b.lvl14 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl14)END) nm_long_14,
(CASE WHEN b.lvl14 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl14)END) lob_cd_14,
'' lvl_nb_14,
'' lvl_nm_14,
CAST(b.s_lvl15 AS VARCHAR2(13)) s_lvl15,
CAST(b.lvl15 AS VARCHAR2(13)) lvl15,
(CASE WHEN b.lvl15 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl15)END) nm_long_15,
(CASE WHEN b.lvl15 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl15)END) lob_cd_15,
'' lvl_nb_15,
'' lvl_nm_15,
CAST(b.s_lvl16 AS VARCHAR2(13)) s_lvl16,
CAST(b.lvl16 AS VARCHAR2(13)) lvl16,
(CASE WHEN b.lvl16 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl16)END) nm_long_16,
(CASE WHEN b.lvl16 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl16)END) lob_cd_16,
'' lvl_nb_16,
'' lvl_nm_16,
CAST(b.s_lvl17 AS VARCHAR2(13)) s_lvl17,
CAST(b.lvl17 AS VARCHAR2(13)) lvl17,
(CASE WHEN b.lvl17 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl17)END) nm_long_17,
(CASE WHEN b.lvl17 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl17)END) lob_cd_17,
'' lvl_nb_17,
'' lvl_nm_17,
CAST(b.s_lvl18 AS VARCHAR2(13)) s_lvl18,
CAST(b.lvl18 AS VARCHAR2(13)) lvl18,
(CASE WHEN b.lvl18 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl8)END) nm_long_18,
(CASE WHEN b.lvl18 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl18)END) lob_cd_18,
'' lvl_nb_18,
'' lvl_nm_18,
CAST(b.s_lvl19 AS VARCHAR2(13)) s_lvl19,
CAST(b.lvl19 AS VARCHAR2(13)) lvl19,
(CASE WHEN b.lvl19 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl19)END) nm_long_19,
(CASE WHEN b.lvl19 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl19)END) lob_cd_19,
'' lvl_nb_19,
'' lvl_nm_19,
CAST(b.s_lvl20 AS VARCHAR2(13)) s_lvl20,
CAST(b.lvl20 AS VARCHAR2(13)) lvl20,
(CASE WHEN b.lvl20 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl20)END) nm_long_20,
(CASE WHEN b.lvl20 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl20)END) lob_cd_20,
'' lvl_nb_20,
'' lvl_nm_20,
CAST(b.s_lvl21 AS VARCHAR2(13)) s_lvl21,
CAST(b.lvl21 AS VARCHAR2(13)) lvl21,
(CASE WHEN b.lvl21 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl21)END) nm_long_21,
(CASE WHEN b.lvl21 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl21)END) lob_cd_21,
'' lvl_nb_21,
'' lvl_nm_21,
CAST(b.s_lvl22 AS VARCHAR2(13)) s_lvl22,
CAST(b.lvl22 AS VARCHAR2(13)) lvl22,
(CASE WHEN b.lvl22 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl22)END) nm_long_22,
(CASE WHEN b.lvl22 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl22)END) lob_cd_22,
'' lvl_nb_22,
'' lvl_nm_22,
CAST(b.s_lvl23 AS VARCHAR2(13)) s_lvl23,
CAST(b.lvl23 AS VARCHAR2(13)) lvl23,
(CASE WHEN b.lvl23 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl23)END) nm_long_23,
(CASE WHEN b.lvl23 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl23)END) lob_cd_23,
'' lvl_nb_23,
'' lvl_nm_23,
CAST(b.s_lvl24 AS VARCHAR2(13)) s_lvl24,
CAST(b.lvl24 AS VARCHAR2(13)) lvl24,
(CASE WHEN b.lvl24 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl24)END) nm_long_24,
(CASE WHEN b.lvl24 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl24)END) lob_cd_24,
'' lvl_nb_24,
'' lvl_nm_24,
CAST(b.s_lvl25 AS VARCHAR2(13)) s_lvl25,
CAST(b.lvl25 AS VARCHAR2(13)) lvl25,
(CASE WHEN b.lvl25 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl25)END) nm_long_25,
(CASE WHEN b.lvl25 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl25)END) lob_cd_25,
'' lvl_nb_25,
'' lvl_nm_25,
CAST(b.s_lvl26 AS VARCHAR2(13)) s_lvl26,
CAST(b.lvl26 AS VARCHAR2(13)) lvl26,
(CASE WHEN b.lvl26 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl26)END) nm_long_26,
(CASE WHEN b.lvl26 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl26)END) lob_cd_26,
'' lvl_nb_26,
'' lvl_nm_26,
CAST(b.s_lvl27 AS VARCHAR2(13)) s_lvl27,
CAST(b.lvl27 AS VARCHAR2(13)) lvl27,
(CASE WHEN b.lvl27 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl27)END) nm_long_27,
(CASE WHEN b.lvl27 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl27)END) lob_cd_27,
'' lvl_nb_27,
'' lvl_nm_27,
CAST(b.s_lvl28 AS VARCHAR2(13)) s_lvl28,
CAST(b.lvl28 AS VARCHAR2(13)) lvl28,
(CASE WHEN b.lvl28 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl28)END) nm_long_28,
(CASE WHEN b.lvl28 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl28)END) lob_cd_28,
'' lvl_nb_28,
'' lvl_nm_28,
CAST(b.s_lvl29 AS VARCHAR2(13)) s_lvl29,
CAST(b.lvl29 AS VARCHAR2(13)) lvl29,
(CASE WHEN b.lvl29 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl29)END) nm_long_29,
(CASE WHEN b.lvl29 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl29)END) lob_cd_29,
'' lvl_nb_29,
'' lvl_nm_29,
CAST(b.s_lvl30 AS VARCHAR2(13)) s_lvl30,
CAST(b.lvl30 AS VARCHAR2(13)) lvl30,
(CASE WHEN b.lvl30 is not null then (select x.nm_long from bu_node x where x.bu_node_id=b.lvl30)END) nm_long_30,
(CASE WHEN b.lvl30 is not null then (select x.lob_cd from bu_node x where x.bu_node_id=b.lvl30)END) lob_cd_30,
'' lvl_nb_30,
'' lvl_nm_30
FROM parse2 b;
Thanks & Regards,
Subbu S

create or replace view tv as
with t as
(select 1 id, to_date('01/02/1994','MM/DD/YYYY') dte
from dual
union
select 2 id, to_date('02/02/2000','MM/DD/YYYY') dte
from dual
union
select 3 id, to_date('01/05/1988','MM/DD/YYYY') dte
from dual
union
select 4 id, to_date('06/05/2006','MM/DD/YYYY') dte
from dual)
select * from t where dte > (select dte from t where id = 4);
-- eliminate the necessity of writing the same query more than once.
WITH Clause will add readability of code.
If the scenario is such that you need to write the same query inline multiple times, you can name it using WITH clause and then use it.
In some cases it improves the performance as well. Some times it creates global temp table for the query specified in WITH clause. It can improve performance drastically, if the query is complex.
The life time of the temp table is only till that query executes.....

Doubt on Maintainence view

Hi,
I want to create one maintainence view where in when i go for table contents it should ask for one field name and after entering the field name it should display all related field contents.
My requirement is that i should get one popup asking field name.Can anyone help me in this regard?
Thnx in adv
Regards,
pavvi.

Hi,
You could create a dialog program for the above requirement.
Thanks
Nidhi

Different sequence of Materail Views

Hi All,
While creating a material maser for a particular material type i need the Views in different sequence
For Example BASIC DATA 1,ACCOUNTING VIEW ,PURCHASING VIEW ,MRP2,MRP1 ,BASIC DATA 2 in this sort of manner its not possible through OMS2 ,
please suggest me
Regards
Srinivasan

Hi,
As per the SAP Standard there are some standard views which is applicable to Material types are available as per the Material types in OMS2.
If you need to modify views there 2 options
In OMT3R you need to modify the Standard sequence 01 and can include the other views which is avaiable.
then in OMT3B you can modify the main data screen & sub screens.
then in OMS2 you will get the additional views to include in your Material type.
Otherwise you can take a help of ABAP consultant to include the addtional views through the modification in the Program and can achieve it.
rgds
gsc

A quicker way to create a materialized view?

Hi,
I'm new to replication and have been reading doco on it. Basically I want to set up read-only materialized views in oracle 11g.
So on the replicated database I created a db link that points to the master db.
Then I created a materialized view that does "select * from table@dblink" and that is forced refresh every 10 minutes.
Problem is that the table on the master db is large and the network link is slow, so the "create materialized view" statement would take a long time to complete.
So I think to speed up the process I would export/import the table from master to replicated db, then make this imported table a materialized view somehow.
Is this possible, and if so, how?
Thanks.
Long

If you are able to use other means (exp-imp, expdp/impdp, unload-sqlldr, externalfile etc) to copy the data faster (as a normal table in the target database), you can then use the "ON PREBUILT TABLE" clause in the CREATE MATERAILIZED VIEW statement.
See
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6002.htm#i2063793
Alternatively, you must first verify if the CREATE is slow only because of SQL Query performance on the source, rather than because of network bandwidth/latency. If query execution needs to be tuned, that would be a cleaner solution, because the Refresh can then be automatically handled by Oracle.
Remember that you can use Materialized View Log(s) on the source tables to enable FAST Refresh's as well.

User defined function in materialized view over db link

I am working in Oracle 10g. Trying to create a materialized view to populate a reporting warehouse from a transactaional database (also oracle 10g).
In SQL plus I can access a function in a package on the remote database but when I try to use the "working" sql statement in a materialized view I get an invalid identifier error.
Basically my select statement is ...
select
ColA,
ColB,
PackageName.Function@db_link(parameters)
from
SourceTable@db_link .....
The select statement works but when I use it within a create materialized view statement I get ora-00904: PackageName.Function: invalid identifier.
Any help is appreciated.
Tx,

What about the error message doesn't make sense?
The identifier is valid when used in the SQL statement outside of the Create Materailized view. It is my understanding that "most any" valid SQL statement should be usable in an MV.
Put the function in the local schema?
I tried that. If the function does not have any input parameters it works. But if it has input parameters the create view statement complains about ORA-00997: illegal use of LONG datatype.
I made a real simple function Pkg.ASTRING - no input parameters just returns the string 'ABC' -- that worked.
Then I added an input parameter Pkg.ASTRING (TheInString VARCHAR2) that returns the same 'ABC' string.
When I include it in the create MV statement Pkg.ASTRING('XYZ') I get the illegal use of LONG datatype.
What LONG datatype?

UPDATING the query in materialized view

Hi,
i have a little doubt in Materialized view. i created a materialized view and log with the following query,
create table test_mv (a number ,b number )
alter table test_mv add constraint t_pk primary key ( a );
insert into test_mv values (1,2);
insert into test_mv values(2,2);
insert into test_mv values(3,2);
insert into test_mv values(4,2);
insert into test_mv values(5,2);
commit;
CREATE MATERIALIZED VIEW LOG ON test_mv
WITH SEQUENCE, ROWID
*(a,b)*
INCLUDING NEW VALUES;
CREATE MATERIALIZED VIEW product_sales_mv
ENABLE QUERY REWRITE
AS SELECT b from test_mv;
Now i want to update the query in the MV as 'Select a from test_mv' . for that i tried with
*'ALTER MATERIALIZED VIEW product_sales_mv AS SELECT a from test_mv;'*
But it throwing error,
Error starting at line 5 in command:
alter MATERIALIZED VIEW product_sales_mv AS SELECT b from test_mv
Error report:
SQL Error: ORA-00933: SQL command not properly ended
+00933. 00000 - "SQL command not properly ended"+
*Cause:+
*Action:+
i guess i am doing wrong. kindly help me here. i want to update it without drop and recreate.
thanks,
Jeevanand.Ke

Hi Jeeva,
No. you cannot add or drop columns to the materialized view using the ALTER Statement.
To Change the Structure of the view , drop and re-create the materialized view.
To Alter a materialized view log, You can use the ALTER MATERIALIZED VIEW LOG. By this,
You can add new columns to a materialized view log.
ALTER MATERIALIZED VIEW LOG ON sggi_mrps.emp ADD(deptno);Thanks,
Shankar
Edited by: Shankar Viji on Aug 24, 2012 2:11 AM

Logical Standby Database - Doubts

Hi everyone,
I have a doubt about this view: dba_logstdby_unsupported;
This view shows up me 400 tables, so i understand that an operation DML on these tables won't be replicated in the other node?, or only the fields allowed will be replicated in the news record? or new record on these tables will be replicated if these records have NULL value in the fields doesn't allow.
Thank you very much if someone can help me with this doubts.
Regards

This is what the documentation says:
If the primary database contains unsupported tables, SQL Apply automatically excludes these tables when applying redo data to the logical standby database.Source: Unsupported Tables

Error on Materialized view

Hi,
I am trying to create a materialized view based on a view on remote site.
CREATE MATERIALIZED VIEW MV_ABC_ABX
USING INDEX TABLESPACE GPDAT
REFRESH fast ON commit with rowid
ENABLE QUERY REWRITE
AS select * from ABC_ABX@KIH_GHL
so i am getting error, ORA - 12054 - Cannot set On Commit refresh attribute for the Materialized view.
When i'm trying to create the same with On Demand or REFRESH FORCE START WITH SYSDATE NEXT SYSDATE + 30 , the MV is getting created.
Note - MV_ABC_ABX is in my current schema say ABC
ABC_ABX is in remote schema XYZ.
I got the CREATE ANY MATERIALIZED VIEW,ON COMMIT REFRESH,QUERY REWRITE privileges on the remote schema XYZ.
I have created Materailized view log based on the view ABC_ABX.
Thanks
Please Guide me.

Yes you can. Here is an AskTom link from way back in 2006 where he answered this exact question and shows an example of that.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1167235330355
See his reply labeled 'Followup September 28, 2006 - 3am Central time zone:
'

Doubt in materailized view

Similar Messages

Maybe you are looking for