|
Any user that is able to create tables in another schema will likely have too much privileges for the environment you're describing. Your standard is
admirable, but it seems almost too restrictive to get the work done.
The only other potential solution for your problem (which has several
restrictions of its own) is to use a logical standby database on one of the
hosts. This may or may not work for you depending on your requirements. The
logical standby database can be "fed" from archived redo logs. So, instead of
doing an export on your primary and copying that file to the secondary server,
copy the archived redo logs. Once they are restored to the secondary system,
they can be applied to update the secondary server.
|
