Re: Build duplicate databases
Posted in 2003
Topics: Backup & Restore, Storage & Space Management, Migration, Import/Export & Data Conversion
----- Original Message -----
From: Carol Dennis <c.dennis@nib.com.au>
At: 12/ 9 23:52
> Is it possible to build 2 databases exactly the same on the one server but
give
> them different names and restore them with ONBAR
Yes to building identical databases with different names on one server. No to
restoring with onbar. IDS archive/restore utilities do not operate at the
database level and even if they did would not restore one database to a
different name. Use dbexport/dbimport, the HPLoader (onpload), or my
dbexport/dbimport replacement package myexport (available from the IIUG
Software
Repository) which can be run using Jonathan Leffler's sqlcmd package for the
unload/reload or using onpload. Myexport includes a feature to remap the
dbspaces into which tables/fragments/indexes are loaded if they are not all
loaded into the database's root.
Art S. Kagel
Yes, you can do it with onbar.
Someone from IBM told me the trick for Unix.
Use only relative pathnames for the chunks.
Even for the ROOTDBS in onconfig.
From the current directory you can use files (awfull) as chunk or symbolic
links to disk partitions.
When you start the engine with oninit, informix looks for the primary chunk
in current directory.
The same way it does with onbar backup and onbar restore.
so for the restore you have to be in another directory, with the same
symbolic link names pointing to other partitions.
You have to change the servername, the servernum and the services in
/etc/services and sqlhosts
BTW : This was our method to test HDR on exactly the same machine.
Yves
-----Original Message-----
From: nobody@ace.iiug.org [mailto:nobody@ace.iiug.org]
Sent: 10 December 2003 16:15
To: ids@iiug.org
Subject: Re: Build duplicate databases [2334]
----- Original Message -----
From: Carol Dennis <c.dennis@nib.com.au>
At: 12/ 9 23:52
> Is it possible to build 2 databases exactly the same on the one server but
give
> them different names and restore them with ONBAR
Yes to building identical databases with different names on one server. No
to
restoring with onbar. IDS archive/restore utilities do not operate at the
database level and even if they did would not restore one database to a
different name. Use dbexport/dbimport, the HPLoader (onpload), or my
dbexport/dbimport replacement package myexport (available from the IIUG
Software
Repository) which can be run using Jonathan Leffler's sqlcmd package for
the
unload/reload or using onpload. Myexport includes a feature to remap the
dbspaces into which tables/fragments/indexes are loaded if they are not all
loaded into the database's root.
Art S. Kagel
------_=_NextPart_001_01C3C2D8.CD27FBE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: Build duplicate databases [2334] </TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Yes, you can do it with onbar.</FONT>
<BR><FONT SIZE=3D2>Someone from IBM told me the trick for Unix.</FONT>
<BR><FONT SIZE=3D2>Use only relative pathnames for the chunks.</FONT>
<BR><FONT SIZE=3D2>Even for the ROOTDBS in onconfig.</FONT>
<BR><FONT SIZE=3D2>From the current directory you can use files =
(awfull) as chunk or symbolic links to disk partitions.</FONT>
<BR><FONT SIZE=3D2>When you start the engine with oninit, informix =
looks for the primary chunk in current directory.</FONT>
<BR><FONT SIZE=3D2>The same way it does with onbar backup and =
onbar restore.</FONT>
<BR><FONT SIZE=3D2>so for the restore you have to be in another =
directory, with the same symbolic link names pointing to other =
partitions.</FONT>
<BR><FONT SIZE=3D2>You have to change the servername, the servernum and =
the services in /etc/services and sqlhosts</FONT>
</P>
<P><FONT SIZE=3D2>BTW : This was our method to test HDR on exactly the =
same machine.</FONT>
</P>
<P><FONT SIZE=3D2>Yves</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: nobody@ace.iiug.org [<A =
HREF=3D"mailto:nobody@ace.iiug.org">mailto:nobody@ace.iiug.org</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: 10 December 2003 16:15</FONT>
<BR><FONT SIZE=3D2>To: ids@iiug.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Build duplicate databases [2334] =
</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>----- Original Message -----</FONT>
<BR><FONT SIZE=3D2>From: Carol Dennis =
<c.dennis@nib.com.au></FONT>
<BR><FONT SIZE=3D2>At: 12/ 9 23:52</FONT>
</P>
<P><FONT SIZE=3D2>> Is it possible to build 2 databases exactly the =
same on the one server but</FONT>
<BR><FONT SIZE=3D2>give</FONT>
<BR><FONT SIZE=3D2>> them different names and restore them with =
ONBAR</FONT>
<BR><FONT SIZE=3D2>Yes to building identical databases with different =
names on one server. No to</FONT>
<BR><FONT SIZE=3D2>restoring with onbar. IDS archive/restore =
utilities do not operate at the</FONT>
<BR><FONT SIZE=3D2>database level and even if they did would not =
restore one database to a</FONT>
<BR><FONT SIZE=3D2>different name. Use dbexport/dbimport, the =
HPLoader (onpload), or my</FONT>
<BR><FONT SIZE=3D2>dbexport/dbimport replacement package myexport =
(available from the IIUG Software</FONT>
<BR><FONT SIZE=3D2> Repository) which can be run using Jonathan =
Leffler's sqlcmd package for the</FONT>
<BR><FONT SIZE=3D2>unload/reload or using onpload. Myexport =
includes a feature to remap the</FONT>
<BR><FONT SIZE=3D2>dbspaces into which tables/fragments/indexes are =
loaded if they are not all</FONT>
<BR><FONT SIZE=3D2>loaded into the database's root.</FONT>
</P>
<P><FONT SIZE=3D2>Art S. Kagel</FONT>
</P>
<BR>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C3C2D8.CD27FBE0--
We've been using relative paths for years. It can be done, but you
obviously have to first rebuild your source instance to use relative path.
You can then use onbar or ontape to restore an "entire instance" on the
same server. However, keep in mind what Art said. This is at the instance
level, not the database. If you have multiple databases in the instance,
you can't pick and choose.
The other option is informix 9.4. You can restore instances with the file
rename option on the same server. This is the equivalent of a redirected
restore in DB2.
Barry Leb
Senior DBA - Informix/DB2
John H. Harland
bjleb@harland.net
770.593.5050 x6137
"Support
Inf...." To: ids@iiug.org
<supinformix@dof cc:
i.fgov.be> Subject: RE: Build duplicate databases [2353]
Sent by:
forum.subscriber
@iiug.org
12/15/2003 03:07
AM
Yes, you can do it with onbar.
Someone from IBM told me the trick for Unix.
Use only relative pathnames for the chunks.
Even for the ROOTDBS in onconfig.
From the current directory you can use files (awfull) as chunk or symbolic
links to disk partitions.
When you start the engine with oninit, informix looks for the primary chunk
in current directory.
The same way it does with onbar backup and onbar restore.
so for the restore you have to be in another directory, with the same
symbolic link names pointing to other partitions.
You have to change the servername, the servernum and the services in
/etc/services and sqlhosts
BTW : This was our method to test HDR on exactly the same machine.
Yves
-----Original Message-----
From: nobody@ace.iiug.org [mailto:nobody@ace.iiug.org]
Sent: 10 December 2003 16:15
To: ids@iiug.org
Subject: Re: Build duplicate databases [2334]
----- Original Message -----
From: Carol Dennis <c.dennis@nib.com.au>
At: 12/ 9 23:52
> Is it possible to build 2 databases exactly the same on the one server
but
give
> them different names and restore them with ONBAR
Yes to building identical databases with different names on one server. No
to
restoring with onbar. IDS archive/restore utilities do not operate at the
database level and even if they did would not restore one database to a
different name. Use dbexport/dbimport, the HPLoader (onpload), or my
dbexport/dbimport replacement package myexport (available from the IIUG
Software
Repository) which can be run using Jonathan Leffler's sqlcmd package for
the
unload/reload or using onpload. Myexport includes a feature to remap the
dbspaces into which tables/fragments/indexes are loaded if they are not all
loaded into the database's root.
Art S. Kagel
------_=_NextPart_001_01C3C2D8.CD27FBE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: Build duplicate databases [2334] </TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Yes, you can do it with onbar.</FONT>
<BR><FONT SIZE=3D2>Someone from IBM told me the trick for Unix.</FONT>
<BR><FONT SIZE=3D2>Use only relative pathnames for the chunks.</FONT>
<BR><FONT SIZE=3D2>Even for the ROOTDBS in onconfig.</FONT>
<BR><FONT SIZE=3D2>From the current directory you can use files =
(awfull) as chunk or symbolic links to disk partitions.</FONT>
<BR><FONT SIZE=3D2>When you start the engine with oninit, informix =
looks for the primary chunk in current directory.</FONT>
<BR><FONT SIZE=3D2>The same way it does with onbar backup and =
onbar restore.</FONT>
<BR><FONT SIZE=3D2>so for the restore you have to be in another =
directory, with the same symbolic link names pointing to other =
partitions.</FONT>
<BR><FONT SIZE=3D2>You have to change the servername, the servernum and =
the services in /etc/services and sqlhosts</FONT>
</P>
<P><FONT SIZE=3D2>BTW : This was our method to test HDR on exactly the =
same machine.</FONT>
</P>
<P><FONT SIZE=3D2>Yves</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: nobody@ace.iiug.org [<A =
HREF=3D"mailto:nobody@ace.iiug.org">mailto:nobody@ace.iiug.org</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: 10 December 2003 16:15</FONT>
<BR><FONT SIZE=3D2>To: ids@iiug.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Build duplicate databases [2334] =
</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>----- Original Message -----</FONT>
<BR><FONT SIZE=3D2>From: Carol Dennis =
<c.dennis@nib.com.au></FONT>
<BR><FONT SIZE=3D2>At: 12/ 9 23:52</FONT>
</P>
<P><FONT SIZE=3D2>> Is it possible to build 2 databases exactly the =
same on the one server but</FONT>
<BR><FONT SIZE=3D2>give</FONT>
<BR><FONT SIZE=3D2>> them different names and restore them with =
ONBAR</FONT>
<BR><FONT SIZE=3D2>Yes to building identical databases with different =
names on one server. No to</FONT>
<BR><FONT SIZE=3D2>restoring with onbar. IDS archive/restore =
utilities do not operate at the</FONT>
<BR><FONT SIZE=3D2>database level and even if they did would not =
restore one database to a</FONT>
<BR><FONT SIZE=3D2>different name. Use dbexport/dbimport, the =
HPLoader (onpload), or my</FONT>
<BR><FONT SIZE=3D2>dbexport/dbimport replacement package myexport =
(available from the IIUG Software</FONT>
<BR><FONT SIZE=3D2> Repository) which can be run using Jonathan =
Leffler's sqlcmd package for the</FONT>
<BR><FONT SIZE=3D2>unload/reload or using onpload. Myexport =
includes a feature to remap the</FONT>
<BR><FONT SIZE=3D2>dbspaces into which tables/fragments/indexes are =
loaded if they are not all</FONT>
<BR><FONT SIZE=3D2>loaded into the database's root.</FONT>
</P>
<P><FONT SIZE=3D2>Art S. Kagel</FONT>
</P>
<BR>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C3C2D8.CD27FBE0--
This message and any attachments have been scanned by Symantec Anti-Virus
prior to leaving the originator's network.
Related threads
- Conversion to differeent characters sets
- Problem in changing locale via dbexport/dbimport
- RE: openlink error "Unable to load locale categories"