If I wanted to degrade a database, I'd take it out
to a cheap pub, get it drunk, and let it make a fool
of itself on the dancefloor before taking it home for
some wild bedroom scenes...
Next morning, rest assured, the database will roll
over in your bed and exclaim:
I'll feel so degraded
Title: RE: Degrade a database??
I have no fresh ideas but how about keeping a file system backup of your oracle installation and 3 copies (in different locations of course) of a complete cold backup before the upgrade?
Or copy the existing database on a similar but separate machine, ready
:
Subject: Re: Degrade a database??
09/27/2002
Hello All,
We are in the process of upgrading a database from 8.0.6 to 8.1.7. The
upgrade is not a problem. We have been asked to come out with a fast
rollback strategy in case we have to fall back, say after a week, to the
8.0.6 database with no data loss. Any fresh ideas?
Thanks
Raj
--
1. Do not use any 8.1.7 specific features after the upgrade.
2. Take a cold backup while at 8.1.7
3. Run the downgrade script from $O_H/rdbms/admin directory (d0800060.sql).
4. Backup
5. Rollback your changes to all other scripts/files ($O_H, listener file
etc..etc..)
Best approach:
Create a
Title: RE: Degrade a database??
I can't think of any better way to back out of anything other than
a restore from disk or tape.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 26, 2002 2:48 PM
To: Multiple recipients of list ORACLE
and set COMPATIBLE = 8.0.6 to keep out new features.
Henry
-Original Message-
Kirti
Sent: Thursday, September 26, 2002 3:18 PM
To: Multiple recipients of list ORACLE-L
1. Do not use any 8.1.7 specific features after the upgrade.
2. Take a cold backup while at 8.1.7
3. Run the