Production is in 10.2A
Future production will be 11.3
Problem: Need to refresh TEST (11.3) env from PROD (10.2A).
Question: Is there a way to avoid doing a prodel of the test 11.3 DB so that I can retain the physical structure on disk? I want to trick OE 10.2A to permit a prorest of the 10.2A backup on top of the 11.3 structure. After that I can run a conv1011. All of this is just to save the time of re-creating 150 Gb of physical files on disk.
* Paul Koufalis
* Progresswiz Consulting
* Email: firstname.lastname@example.org
* Phone: 514 247 2023
* Fax : 514 439 6782
* Progress, MFG/PRO, UNIX, Windows, EDI
$DLC/(versionyouwant)utils/procopy empty sports
Douglas R. Vanek
Senior Systems Engineer
(717) 269-8470 Mobile
(781) 280-4900 Pre-Sales Support
That won't work because the existing test DB is 11.3. I cannot use 102b_dbutil to restore a 10.2B empty on top of an 11.3 DB. But you've got the right idea: that's what I want to do.
I'm not sure if I understood properly what you want (and don't want) to do, but since the database's physical structure is defined in the .st file, you can retain the existing structure by saving a copy of the .st file, deleting the old database and restoring the backup using the saved .st file. It might be a good idea to do "prostrct list" first to refresh the .st file.
What he wants to do is to NOT have to delete and re-create the extents, but I can't think of a way to make this work. The DB version is tagged in the master block... try deleting just the .DB file and using the v10 prostrct builddb to replace it? <-- This is so far beyond "not supported" that I hesitate to mention it. :)
Ha! Great idea Doug! I thought that would work but no.
$ rm dev-tst.db
$ which prostrct
$ prostrct builddb dev-tst
** Database has the wrong version number. (db: 4269, pro: 4246). (44)
Any other such unsupported ideas? Mike Furgal suggested a bunch of dd/hex edit stuff to hack the version but that's waaay too much of a pain to bother with.
I suspect that you are going to eventually come to the conclusion that any alternative will either take as long as building the extents or will be so much of a pain that it isn't worth it. The one suggestion that I think buys you something is to use separate directories and build the void database in advance so that you don't have to spend that time in the actual transition.
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
I have already come to that conclusion. Now it's just about intellectual curiosity.
Isn't the DB master block in the schema area rather than the control area?
So, did you got a way to restore 10.2A database backup on 11.3 database ?
Please let know if you had any luck.
kunal.watkar No I did not. I suspect I could have hacked some master block somewhere and fooled the DB to allow it but that would not have exactly been a supported configuration!