Answer Posted / amit

Definitely yes.....While creating a Data Warehouse
application,we need fact tables to be created from various
dimension tables and the fact table load type is always
INSERT not INSERT/UPDATE.Just think of a real world example
where the need is to populate all the daily transactional
data to a Data Warehouse for analytical purpose such as
creating reports and all.Suppose the DW is loaded two times
a day.In the first load,whatever the data present in the
Transactional Database is loaded into the DW.Before the
second load there might be some sort of updation made to
some of the records,so those records need to be inserted
into the DW again in the second load.If there would be
primary key in the fact table(i,e;DW),it will raise an error
(unique constraint violated.....).So,fact tables should not
contain any primary key.

Assuming today is Monday, how would you use the DBMS_JOB package to schedule the execution of a given procedure owned by SCOTT to start Wednesday at 9AM and to run subsequently every other day at 2AM.

1911

---

What is the cache hit ratio, what impact does it have on performance of an Oracle database and what is involved in tuning it?

2083

---

What is an Oracle Instance?

1081

---

How to use "in" parameter properly?

1014

---

What is Redo Log Buffer in Oracle?

1145

---

What is meant by raw datatype?

1017

---

What is a trace file and how is it created in oracle?

993

---

What is oracle in java?

922

---

How do you increase the OS limitation for open files (LINUX and/or Solaris)?

1887

---

Is the After report trigger fired if the report execution fails ?

2881

---

How to load excel data sheet to oracle database

979

---

What is a proxy object?

1018

---

How to create a new table in oracle?

1084

---

What is hot backup and logical backup?

1010

---

How to start instance with a minimal initialization parameter file?

1000

---