ontape question
We have a production database (IDS 7.3 UC7) running on an AIX (4.3) box
that we would like to 'recreate' on another AIX box for QA purposes. We
thought ontape might be the right tool for the job.
The QA box is used for other tasks. Therefore, I would prefer not to
used 'raw' partitioning on it. Now, to the meat of my question.
Can we use ontape to restore an instance from a box using 'raw'
partitions to one using 'cooked', as long as all the dbspace sizing is
the same and the same ONCONFIG file is used?
I searched this list for ontape + chunk and found quite a few 'nuggets'.
Per Art Kagel:
"Actually you do not need the oninit -i at all. Just have the same
disks (or links) available where each is AT LEAST as large as the
corresponding file on the source system, create the ONCONFIG file and
restore. Voila! Instant database. In the ONCONFIG file only the disk
parameters (ie ROOTFILE, PHYSFILE,...) need to be the same as the
source. Shared memory parameters may differ including the servername
and server number."
However, I did not see anything addressing 'raw' versus 'cooked'.
TIA,
Steve Weaver
In a world without walls or fences, who needs windows and gates?
Sent via Deja.com http://www.deja.com/
Before you buy.
sweav_er@my-deja.com wrote:
> We have a production database (IDS 7.3 UC7) running on an AIX (4.3) box
> that we would like to 'recreate' on another AIX box for QA purposes. We
> thought ontape might be the right tool for the job.
>
> The QA box is used for other tasks. Therefore, I would prefer not to
> used 'raw' partitioning on it. Now, to the meat of my question.
>
> Can we use ontape to restore an instance from a box using 'raw'
> partitions to one using 'cooked', as long as all the dbspace sizing is
> the same and the same ONCONFIG file is used?
>
> I searched this list for ontape + chunk and found quite a few 'nuggets'.
>
> Per Art Kagel:
>
> "Actually you do not need the oninit -i at all. Just have the same
> disks (or links) available where each is AT LEAST as large as the
> corresponding file on the source system, create the ONCONFIG file and
> restore. Voila! Instant database. In the ONCONFIG file only the disk
> parameters (ie ROOTFILE, PHYSFILE,...) need to be the same as the
> source. Shared memory parameters may differ including the servername
> and server number."
>
> However, I did not see anything addressing 'raw' versus 'cooked'.
>
> TIA,
> Steve Weaver
>
> In a world without walls or fences, who needs windows and gates?
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
You can do. But the sizes and names (= paths) of the dbspaces must be the
same. That's easy if you have used symbolic links on your original system.
If you did not use links, it may cause confusion if you use something like
/dev/rrootdbs to address a file system file.
Regards
--
Helmut Leininger
Bull AG / Vienna
Open Systems Support
Email: h.leininger@bull.at
helmut.leininger@bull.net
This opinion is mine and not necessarily that of my employer.
No guarantees whatsoever.
sweav_er@my-deja.com wrote:
> We have a production database (IDS 7.3 UC7) running on an AIX (4.3) box
> that we would like to 'recreate' on another AIX box for QA purposes. We
> thought ontape might be the right tool for the job.
> [...]
> Can we use ontape to restore an instance from a box using 'raw'
> partitions to one using 'cooked', as long as all the dbspace sizing is
> the same and the same ONCONFIG file is used?
You should be ok, as long as the ROOTPATH in $ONCONFIG and all the other
paths to the dbspaces/chunks are identical. Here it pays off if you heed
the old advice to NEVER use physical pathnames for this purpose and use
links instead. Then you can let your link point to whatever device or file
you want.
Regards, Richard
--
+--------------------------+------------------------------------------+
| Dr. Richard Spitz | INTERNET: spitz@ana.med.uni-muenchen.de |
| EDV-Gruppe Anaesthesie | Tel : +49-89-7095-6110 |
| Klinikum Grosshadern | FAX : +49-89-7095-6420 |
| 81366 Munich, Germany | GSM : +49-172-8933578 |
+--------------------------+------------------------------------------+