Clearing tables in prototype

jay_newman

Member
All,
We are in a prototype environment and need to "refresh" the environment by
clearing all the transactional data. Does anyone have a list of tables that
should be cleared to accomplish this? We appreciate your help.

Jay Newman
[email protected]

OneWorld Xe Service pack 15.1 Oracle 8.1
 
You need to use the R98403 UBE. The R98403 uses information in the F9860 (Object Librarian) to decide which tables to create/copy when it runs.

***WARNING***
The R98403 can be extremely dangerous. If you choose to follow the instructions that follow, you will do so at your own risk. The instructions below make every reasonable attempt to guide you through what you need to do. You are ultimately responsible for making sense of the instructions and doing what makes sense in you enterprise. Read through the instructions first before actually doing any of the instructions. That being said...

Step 1.

Back up your enterprise server. The R98403 has the power to drop tables, erase data, and copy data. Backing up your data first is always advisable before running the R98403.

Step 2.

Goto Batch Versions (bv on the fast path). Copy the XJDE0024 version of the R98403 (the XJDE0024 has the closest data selection for what you want to do). Name your version PYREFRESH.

Edit the data selection to add the following line to the bottom:

And BC Copy Data With File (F9860) is equal to "N"

This will further limit the data selection to only those files that hold transactional data.

Next change the Processing options for your new version, PYREFRESH as follows: (note that when it says (blank) that means blank out the field, do not type "(blank)")

On the Environment Tab:

1. PY7333
2. (blank)
3. 2
4. (blank)
5. JD7333

On the Update Tab:
6. 0
7. A
8. (blank)
9. (blank)

Leave the remaining "Print" and "Licensing" tabs as they are.

Press OK to save your changes to PYREFRESH.

What the steps above have done is to setup the R98403 to clear out all business transaction tables in PY7333 in proof mode. That means that when you run the PYREFRESH, the UBE will print a report of what it is going to do without actually doing it (setting Option 6 = 0 does this "proof" mode).

If you feel comfortable at this point, run PYREFRESH. You should see the UBE run. Pages will be printed rapidly because the report is just listing what it will not (without doing it).

When the report is done, review the pdf file. Realize that because the report was run in proof mode, no table updates have occurred. Verify the target data source. It should point to PY business data for all transaction tables. Verify which tables the report printed as well.

If you feel that the proof mode report had the results that you expected and if you are ready to update PY7333, change the PO value of PYREFRESH to run in final mode (set Option 6 = 1).

Now if you are ready to run the UBE for real, run PYREFERSH. When the report runs, it will drop and re-add all the tables in its data selection.

If you feel uncomfortable running the R98403, get a consultant who has experience with it to set it up for you.

Good luck!
 
Back
Top