Kbase P52764: Unable to change access to production environment by changin
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/11/2003 |
|
Status: Unverified
FACT(s) (Environment):
Oracle DataServer
SYMPTOM(s):
Unable to change access to production environment by changing the oracle user connected
Using the same Schema holder from development environment and trying to use the tables from production environment
Have 2 users in a unique Oracle database, one for development environment and the other for the production
CAUSE:
This is an expected behavior. The schema holder holds the name of the owner of the object internally into FOREIGN-OWNER field.
FIX:
You must have a separate schema holder for each environment.
Please advise that if you intend to change the FOREIGN-OWNER value to create a new schema holder for the other environment, you must delta.sql generator to apply your changes to both enviroment in a proper way to avoid data corruption.