0

The scenario is as follows:
We have a data warehouse type application that relies on the Oracle job scheduler and a Chain. This chain is responsible for generating materialized views (caches) that are to be queried against based on data that exists in the primary tables. For the sake of discussion the materialized views are :
select * from Cats,
select * from Dogs,
select * from Humans

During this cache creation process there are arbitrary tasks that are constantly populating the Cats, Dogs, and Humans tables. My question is:

Given the above scenario is it possible for the creation of the materialized views (a read statement) to block during the insertion of new records from an abritrary program (these are bound by a transaction). I believe that there should be zero conflict, but I want to bring this question to more experienced DBAs.

Improve this question

1 Answer 1

Reset to default
2

No, the reading of your cats, dogs and humans tables wont block other processes that are inserting in them.

Improve this answer
2
  • That is what I thought, because reads should never be blocked. Some of my peers seem to disagree.
    – Woot4Moo
    Commented Nov 9, 2012 at 16:46
  • 1
    @Woot4Moo: docs.oracle.com/cd/E14072_01/server.112/e10713/… - "a reader never blocks a writer [...] a writer never blocks a reader"
    – Mat
    Commented Nov 9, 2012 at 16:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.