PL/SQL (MOSC)

MOSC Banner

PL/SQL used for ETL processing: what is best practice?

edited Aug 10, 2010 8:04AM in PL/SQL (MOSC) 3 comments
Hi All,

I am new to this forum; I hope I am posting in the right one.

To populate our data warehouse, we use PL/SQL stored procedures and the approach always is:

- pre processing: disable constraints and drop indexes, truncate table (in some cases),  alter table.. enable row movement, alter table.. shrink space.
- load: inserts/updates
- post processing: enable constraints and create indexes.

My question: some of the DDL invalidates our procedures, and in some instances even causes the dreadful ora-4068. Is there a way to avoid the invalidation/ora-4068? Does anyone have a best practice for doing this kind of ETL on Oracle?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center