Oracle install question

To all,

When OneWorld is installed, the tables are made part of the Public schema. This is bad, in our view, as anyone with an oracle ID can go in and delete/add/change data via SQL anytime they want. We would like to lock this down and remove the tables from the Public schema. Is there any reason we shouldn't just remove the tables from the public schema. Is there a document anywhere that can give us some guidance on this???

Thank you,

I seem to remember a document on the KG in the past but I have done a quick search and cannot find it.

As long as the "system" Oracle ID's used by OneWorld have the appropriate rights you can remove access from public. I have done this many times.

The approach in a nutshell is:

1. Explicitly grant rights to the OneWorld System User Id's
2. Revoke all rights from public

The KG document "How to Secure Oracle Objects", doc id oti-00-0115, covers these steps.