Upgrade the $ORACLE_HOME from 220.127.116.11 to 18.104.22.168, don't downgrade the database.
Why would anyone choose to go back to the bug-ridden cesspool of 22.214.171.124?
On 4/12/17 09:24, angelo wrote:
yep, I could imagine.. the right thing would be have Oracle updated, but... they didn´t the homework..
So, I will negotiate with my users if I can make a expdp/impdp instead to avoid these issues... just for restoring a few schemas and tables, from a production to a devel machine
On 12 April 2017 at 12:01, Andrew Kerber <andrew.kerber@xxxxxxxxx <mailto:andrew.kerber@xxxxxxxxx>> wrote:
yes, all kinds of problems. At the very least, you will need to
open the database resetlogs upgrade and run catupgrade after the
On Wed, Apr 12, 2017 at 9:57 AM, angelo <angelolistas@xxxxxxxxx
Is there any big issue about restoring an oracle 126.96.36.199
backup to 188.8.131.52 server ?
I will do it on this afternoon attending a request
-- Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'