Hello All,
I have a quick question regarding an issue that I ran into during the first environment refresh after our upgrade from v6.2.7 to v6.3.2. I used the environment refresh steps as described in Oracle Support Doc ID 1313815.1(Cloning OTM DB Schemas). I noticed that the 'GLOGDEV' account is no longer present in the V6.3 create_glog_users sql script, but that account still exists in my TEST and PROD Oracle RDBMS instance. I used datapump to export the necessary schemas from my TEST environment to refresh into DEV. The export went well, but I received a bunch of errors regarding attempts to grant privileges to the 'GLOGDEV' user, that no longer exists in the DEV environment(dropped all schemas, ran 6.3 version of create_glog_users). So, I just wanted to doublecheck: Is it OK for me to get rid of the 'GLOGDEV' db account from all my PTM Oracle RDBMS instances?
One other strange thing that I encountered with using the procedure in Oracle Support Doc ID 1313815.1: I wound up with a bunch of invalid synonyms that I had to fix with 'alter ...compile' scripts. That is very possibly some sort of error on my part, I will reply on that when I find the answer.
I have a quick question regarding an issue that I ran into during the first environment refresh after our upgrade from v6.2.7 to v6.3.2. I used the environment refresh steps as described in Oracle Support Doc ID 1313815.1(Cloning OTM DB Schemas). I noticed that the 'GLOGDEV' account is no longer present in the V6.3 create_glog_users sql script, but that account still exists in my TEST and PROD Oracle RDBMS instance. I used datapump to export the necessary schemas from my TEST environment to refresh into DEV. The export went well, but I received a bunch of errors regarding attempts to grant privileges to the 'GLOGDEV' user, that no longer exists in the DEV environment(dropped all schemas, ran 6.3 version of create_glog_users). So, I just wanted to doublecheck: Is it OK for me to get rid of the 'GLOGDEV' db account from all my PTM Oracle RDBMS instances?
One other strange thing that I encountered with using the procedure in Oracle Support Doc ID 1313815.1: I wound up with a bunch of invalid synonyms that I had to fix with 'alter ...compile' scripts. That is very possibly some sort of error on my part, I will reply on that when I find the answer.