This content has been marked as final. Show 5 replies
Not sure what your acronym is supposed to stand for, but regardless, you would need to export all the items, more than just the schema's from one database into the other. Then you would also have to copy any keys related to the encryption.
I would assume that if you installed your UAT instance completely as a vanilla install, you would not have to point your jdbc information to another location when you import into it.
It's not a simple process, and in all honesty, you should follow your build process that you used to go from Dev, to QA, to Prod, and do the same thing to build any other environment, and not just try a quick and easy copy one instance to another, because with the complexity of these products now, it isn't a quick process. But your build process should be documented, and repeatable.
I have 11g R1 and I have done the same thing except that I have kept the schema name and password same.
So, for me it was less work, I just have to update the database host and db instance name. Rest of the parameters remain same. So, I followed the same doc for R1 and it worked for me.
I have been troubled by xldatabasekey in the past, so that's why I asked dba to keep the schema name and password as same.