erik.ykema_at_gmail.com schreef:
> During report runs users are active in the system (i.e. committing
> transactions through their client applications) and every fifteen
> minutes the MVs are refreshed by a scheduled process (which takes 7
> minutes, to be improved later).
> Several MSTR reports can be running concurrently.
>
> The challenge:
> run the report against a transactionally consistent set of data.
> "Isolation_level = serialized" or "transaction read only" would
> conceptually point in the right direction.
- Upgrade (your version of Oracle does matter here) to the
version that supports 'on commit refresh'.
- Run the reports against the real data (probably meaning
you'll need more iron)
--
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
Received on Sat Jun 03 2006 - 08:31:58 CDT
