informix upgrade to V10
Posted in 2006
Denny asked how to move a 7.31 instance on AIX 4.3 to IDS 10 on AIX 5.3, proposing an mksysb OS migration plus in-place upgrade. Respondents advised treating the new box as a fresh build and moving data via unload/load or dbexport/dbimport, which also lets you edit db.sql to reorganize tables, indexes and fragmentation. Denny then hit dbexport tape-size limits (the -s value is capped around 2,097,151 KB in v7, forcing tape changes on a 50 GB export). Art Kagel suggested -s 0 (unlimited, detect EOT), but noted v7's dbexport lacks it and you'd need to run the v10 dbexport against the old instance; Denny confirmed -s 0 fails on v7. No confirmed final outcome is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Installation, Setup & Upgrades, Migration, Import/Export & Data Conversion, Platform-Specific Issues
Hi all, We have one machine A is running Informix (V7.31) on Aix 4.3. We are planning to migrate to machine B which will run Informix (V10) on Aix 5.3. I am looking for advice to how to get it done. I was thinking to do mksysb migration, which can use mksysb tape(V4.3) with AIX V5.3 installation CD to do a OS migration. Then restore Informix (V7.31) on machine B. Then we can upgrade to Informix V10. I am not sure whether the V7.31 will be supported on AIX V5.3. Still looking at the documents. Any suggestion is very welcome. Thanks, Denny ******************************************* The information contained in this e-mail message may contain privileged and confidential information. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you have received this message in error, please notify the sender by return e-mail, delete this message and destroy any copies. Internet e- mail is not guaranteed to be secure or error-free. Messages could be intercepted, corrupted, lost, arrive late or contain viruses. The sender will not be liable for these risks. ******************************************* Ce message electronique pourrait contenir des informations privilegiees et confidentielles. Si vous n'en etes pas le recipiendaire prevu, nous vous signalons qu'il est strictement interdit d'examiner, de diffuser, de distribuer et de reproduire le present message. Si vous l'avez recu par erreur, veuillez prevenir l'expediteur par courriel, puis effacer ce message et en detruire toute copie. Le courrier electronique n'est pas garanti securitaire ni exempt d'erreurs. Les messages pourraient etre interceptes, corrompus, egares, retardes ou contamines par des virus. L'exp'editeur n'est pas responsable de ces risques .
On 19/12/06, Guo, Denny <DGuo@livingstonintl.com> wrote: > > Hi all, > > We have one machine A is running Informix (V7.31) on Aix 4.3. > We are planning to migrate to machine B which will run Informix (V10) on > Aix 5.3. > I am looking for advice to how to get it done. > I was thinking to do mksysb migration, which can use mksysb tape(V4.3) > with AIX V5.3 installation CD to do a OS migration. Then restore > Informix (V7.31) on machine B. Then we can upgrade to Informix V10. > I am not sure whether the V7.31 will be supported on AIX V5.3. Still > looking at the documents. > Any suggestion is very welcome. > > Thanks, > Denny > <SNIPPED> Denny What you are suggesting would work, but you would not gain best benefit of migration by being able to reorg and tidy the database and implementing some of the new features of v10 immediately. If you can it would be better to 'bite the bullet' and treat the new machine as a new build and then populate the data using dbunload/dbload (if tables are not too large, or to tape if you have compatible drices) or separate unload/load scripts using pipes. Keith
Denny,
We used dbexport/dbimport and got the job done perfectly!
Especially, you can modify the db.sql file to reorganize your table, index,
fragmentation...
amazing!
Good luck,
Frank
On 12/19/06, Guo, Denny <DGuo@livingstonintl.com> wrote:
>
>
> Hi all,
>
> We have one machine A is running Informix (V7.31) on Aix 4.3.
> We are planning to migrate to machine B which will run Informix (V10) on
> Aix 5.3.
> I am looking for advice to how to get it done.
> I was thinking to do mksysb migration, which can use mksysb tape(V4.3)
> with AIX V5.3 installation CD to do a OS migration. Then restore
> Informix (V7.31) on machine B. Then we can upgrade to Informix V10.
> I am not sure whether the V7.31 will be supported on AIX V5.3. Still
> looking at the documents.
> Any suggestion is very welcome.
>
> Thanks,
> Denny
>
> *******************************************
> The information contained in this e-mail message may
> contain privileged and confidential information.
> If you are not the intended recipient, you are
> hereby notified that any review, dissemination,
> distribution or duplication of this communication
> is strictly prohibited. If you have received this
> message in error, please notify the sender by return
> e-mail, delete this message and destroy any copies.
> Internet e- mail is not guaranteed to be secure or
> error-free. Messages could be intercepted, corrupted,
> lost, arrive late or contain viruses.
> The sender will not be liable for
> these risks.
>
> *******************************************
> Ce message electronique pourrait contenir des
> informations privilegiees et confidentielles. Si vous
> n'en etes pas le recipiendaire prevu, nous vous
> signalons qu'il est strictement interdit d'examiner,
> de diffuser, de distribuer et de reproduire le
> present message. Si vous l'avez recu par erreur,
> veuillez prevenir l'expediteur par courriel, puis
> effacer ce message et en detruire toute copie.
> Le courrier electronique n'est pas garanti
> securitaire ni exempt d'erreurs. Les messages
> pourraient etre interceptes, corrompus, egares,
> retardes ou contamines par des virus.
> L'exp'editeur n'est pas
> responsable de ces risques .
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can
write to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
Thanks Art,
I am not using the commas in real case.
Just try made it easy to compare.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
ART KAGEL, BLOOMBERG/ 731 LEXIN
Sent: Friday, January 12, 2007 11:39 AM
To: ids@iiug.org
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
Only a limit for export to disk, and only in versions prior to 9.40, however,
you are correct anyway, you cannot specify 100000000, you have to use zero (0)
to mean UNLIMITED and dbexport will detect the EOT signal. So, REALLY the line
should be:
dbexport -c -ss -b 1024 -s 0 -f db.sql ip_0p
Good catch Kern.
Art S. Kagel
----- Original Message -----
From: Kern Doe <ids@iiug.org>
At: 1/12 12:01:38
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
OOO, but also I should point out that the IDS 7.xx dbexport does not support
-s 0 so Denny, you'll have to bring up an IDS 10 instance, and use the v10.00
dbexport.
Art
----- Original Message -----
From: Kern Doe <ids@iiug.org>
At: 1/12 12:01:38
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Version 7 does not have the -s 0 option.
I try already, it would not work.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
ART KAGEL, BLOOMBERG/ 731 LEXIN
Sent: Friday, January 12, 2007 12:08 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8190]
Only a limit for export to disk, and only in versions prior to 9.40,
however,
you are correct anyway, you cannot specify 100000000, you have to use
zero (0)
to mean UNLIMITED and dbexport will detect the EOT signal. So, REALLY
the line
should be:
dbexport -c -ss -b 1024 -s 0 -f db.sql ip_0p
Good catch Kern.
Art S. Kagel
----- Original Message -----
From: Kern Doe <ids@iiug.org>
At: 1/12 12:01:38
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
If you are on Unix write a script that back ups to disk and then copy those
files to tape. It's a trivial exercise
Cheers
Paul
Paul Watson
Tel: +44 1414161772
Mob: +44 7818003457
Web: www.oninit.com
Failure is not as frightening as regret.
Attend IDUG 2007 San Jose, North America
May 6-10, 2007
Visit http://www.iiug.org/conf for more information.
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of Guo, Denny
> Sent: 12 January 2007 11:08
> To: ids@iiug.org
> Subject: RE: informix upgrade to V10 [8188]
>
>
> Yes. I think The limitation is 2GB.
> Say for a 50G database, do you need 25 tapes? How to solve
> such problem?
> I am trying to not change the tape (100G capability), the
> dbexport can write to the same tape.
> The question is will it write from beginning? Will old data
> been erased?
>
> Thanks,
> Denny
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of Kern Doe
> Sent: Friday, January 12, 2007 11:52 AM
> To: ids@iiug.org
> Subject: Re: informix upgrade to V10 [8187]
>
> I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
> kilobytes.) -- you can't specify size 100000000 (yes/no?)
>
> ----- Original Message ----
> From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
> To: ids@iiug.org
> Sent: Friday, January 12, 2007 11:39:15 AM
> Subject: RE: informix upgrade to V10 [8186]
>
> Remove the commas from the -s argument. It should be:
>
> dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p>
> Art S. Kagel
> ----- Original Message -----
> From: Denny Guo <ids@iiug.org>
> At: 1/12 11:41:58
>
> Hi All,
>
> I am doing the dbexport now. But have some issues.
> The current version of informxi we are running is V7.31.
>
> The tape we are using have 100G capability.
> Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f
> db.sql ip_0p"
> would work. It complains about the block size must less than
> or equal to
>
> tape side.
> I have to change to tape size to "1,000,000,000". However it
> stops at some point ask to mount another tape? The databse we
> try to export only 50G.
>
> According to the manual, there are some restrictions for
> version 7. See below statement.
> "-s tapesize Specifies, in kilobytes, the amount of data that
> you canstore on the tape. ** Restrictions: The tape size is limited to
> 2,097,151 kilobytes. The limit is required because of the way
> dbexport and dbimport track their positions into the tape."
>
> Any ideas?
>
> Thanks,
> Denny
>
> *******************************************
> The information contained in this e-mail message may contain
> privileged and confidential information.
> If you are not the intended recipient, you are hereby
> notified that any review, dissemination, distribution or
> duplication of this communication is strictly prohibited. If
> you have received this message in error, please notify the
> sender by return e-mail, delete this message and destroy any copies.
> Internet e- mail is not guaranteed to be secure or
> error-free. Messages could be intercepted, corrupted, lost,
> arrive late or contain viruses.
> The sender will not be liable for
> these risks.
>
> *******************************************
> Ce message electronique pourrait contenir des informations
> privilegiees et confidentielles. Si vous n'en etes pas le
> recipiendaire prevu, nous vous signalons qu'il est
> strictement interdit d'examiner, de diffuser, de distribuer
> et de reproduire le present message. Si vous l'avez recu par
> erreur, veuillez prevenir l'expediteur par courriel, puis
> effacer ce message et en detruire toute copie.
> Le courrier electronique n'est pas garanti securitaire ni
> exempt d'erreurs. Les messages pourraient etre interceptes,
> corrompus, egares, retardes ou contamines par des virus.
> L'exp'editeur n'est pas
> responsable de ces risques .
>
> **************************************************************
> **********
> *******
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> **************************************************************
> **********
> *******
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> **************************************************************
> **********
> *******
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> *******************************************
> The information contained in this e-mail message may contain
> privileged and confidential information.
> If you are not the intended recipient, you are hereby
> notified that any review, dissemination, distribution or
> duplication of this communication is strictly prohibited. If
> you have received this message in error, please notify the
> sender by return e-mail, delete this message and destroy any copies.
> Internet e- mail is not guaranteed to be secure or
> error-free. Messages could be intercepted, corrupted, lost,
> arrive late or contain viruses.
> The sender will not be liable for
> these risks.
>
> *******************************************
> Ce message electronique pourrait contenir des informations
> privilegiees et confidentielles. Si vous n'en etes pas le
> recipiendaire prevu, nous vous signalons qu'il est
> strictement interdit d'examiner, de diffuser, de distribuer
> et de reproduire le present message. Si vous l'avez recu par
> erreur, veuillez prevenir l'expediteur par courriel, puis
> effacer ce message et en detruire toute copie.
> Le courrier electronique n'est pas garanti securitaire ni
> exempt d'erreurs. Les messages pourraient etre interceptes,
> corrompus, egares, retardes ou contamines par des virus.
> L'exp'editeur n'est pas
> responsable de ces risques .
>
>
> **************************************************************
> *****************
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
Thanks Paul,
The reason is we do not have enough disk space.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Paul Watson
Sent: Friday, January 12, 2007 12:24 PM
To: ids@iiug.org
Subject: RE: informix upgrade to V10 [8193]
If you are on Unix write a script that back ups to disk and then copy
those
files to tape. It's a trivial exercise
Cheers
Paul
Paul Watson
Tel: +44 1414161772
Mob: +44 7818003457
Web: www.oninit.com
Failure is not as frightening as regret.
Attend IDUG 2007 San Jose, North America
May 6-10, 2007
Visit http://www.iiug.org/conf for more information.
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of Guo, Denny
> Sent: 12 January 2007 11:08
> To: ids@iiug.org
> Subject: RE: informix upgrade to V10 [8188]
>
>
> Yes. I think The limitation is 2GB.
> Say for a 50G database, do you need 25 tapes? How to solve
> such problem?
> I am trying to not change the tape (100G capability), the
> dbexport can write to the same tape.
> The question is will it write from beginning? Will old data
> been erased?
>
> Thanks,
> Denny
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of Kern Doe
> Sent: Friday, January 12, 2007 11:52 AM
> To: ids@iiug.org
> Subject: Re: informix upgrade to V10 [8187]
>
> I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
> kilobytes.) -- you can't specify size 100000000 (yes/no?)
>
> ----- Original Message ----
> From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
> To: ids@iiug.org
> Sent: Friday, January 12, 2007 11:39:15 AM
> Subject: RE: informix upgrade to V10 [8186]
>
> Remove the commas from the -s argument. It should be:
>
> dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p>
> Art S. Kagel
> ----- Original Message -----
> From: Denny Guo <ids@iiug.org>
> At: 1/12 11:41:58
>
> Hi All,
>
> I am doing the dbexport now. But have some issues.
> The current version of informxi we are running is V7.31.
>
> The tape we are using have 100G capability.
> Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f
> db.sql ip_0p"
> would work. It complains about the block size must less than
> or equal to
>
> tape side.
> I have to change to tape size to "1,000,000,000". However it
> stops at some point ask to mount another tape? The databse we
> try to export only 50G.
>
> According to the manual, there are some restrictions for
> version 7. See below statement.
> "-s tapesize Specifies, in kilobytes, the amount of data that
> you canstore on the tape. ** Restrictions: The tape size is limited to
> 2,097,151 kilobytes. The limit is required because of the way
> dbexport and dbimport track their positions into the tape."
>
> Any ideas?
>
> Thanks,
> Denny
>
> *******************************************
> The information contained in this e-mail message may contain
> privileged and confidential information.
> If you are not the intended recipient, you are hereby
> notified that any review, dissemination, distribution or
> duplication of this communication is strictly prohibited. If
> you have received this message in error, please notify the
> sender by return e-mail, delete this message and destroy any copies.
> Internet e- mail is not guaranteed to be secure or
> error-free. Messages could be intercepted, corrupted, lost,
> arrive late or contain viruses.
> The sender will not be liable for
> these risks.
>
> *******************************************
> Ce message electronique pourrait contenir des informations
> privilegiees et confidentielles. Si vous n'en etes pas le
> recipiendaire prevu, nous vous signalons qu'il est
> strictement interdit d'examiner, de diffuser, de distribuer
> et de reproduire le present message. Si vous l'avez recu par
> erreur, veuillez prevenir l'expediteur par courriel, puis
> effacer ce message et en detruire toute copie.
> Le courrier electronique n'est pas garanti securitaire ni
> exempt d'erreurs. Les messages pourraient etre interceptes,
> corrompus, egares, retardes ou contamines par des virus.
> L'exp'editeur n'est pas
> responsable de ces risques .
>
> **************************************************************
> **********
> *******
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> **************************************************************
> **********
> *******
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> **************************************************************
> **********
> *******
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> *******************************************
> The information contained in this e-mail message may contain
> privileged and confidential information.
> If you are not the intended recipient, you are hereby
> notified that any review, dissemination, distribution or
> duplication of this communication is strictly prohibited. If
> you have received this message in error, please notify the
> sender by return e-mail, delete this message and destroy any copies.
> Internet e- mail is not guaranteed to be secure or
> error-free. Messages could be intercepted, corrupted, lost,
> arrive late or contain viruses.
> The sender will not be liable for
> these risks.
>
> *******************************************
> Ce message electronique pourrait contenir des informations
> privilegiees et confidentielles. Si vous n'en etes pas le
> recipiendaire prevu, nous vous signalons qu'il est
> strictement interdit d'examiner, de diffuser, de distribuer
> et de reproduire le present message. Si vous l'avez recu par
> erreur, veuillez prevenir l'expediteur par courriel, puis
> effacer ce message et en detruire toute copie.
> Le courrier electronique n'est pas garanti securitaire ni
> exempt d'erreurs. Les messages pourraient etre interceptes,
> corrompus, egares, retardes ou contamines par des virus.
> L'exp'editeur n'est pas
> responsable de ces risques .
>
>
> **************************************************************
> *****************
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-
OK then back out each disk file to a no-rewind tape device
Cheers
Paul
Paul Watson
Tel: +44 1414161772
Mob: +44 7818003457
Web: www.oninit.com
Failure is not as frightening as regret.
Attend IDUG 2007 San Jose, North America
May 6-10, 2007
Visit http://www.iiug.org/conf for more information.
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of Guo, Denny
> Sent: 12 January 2007 11:30
> To: ids@iiug.org
> Subject: RE: informix upgrade to V10 [8194]
>
>
> Thanks Paul,
>
> The reason is we do not have enough disk space.
>
> Denny
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of Paul Watson
> Sent: Friday, January 12, 2007 12:24 PM
> To: ids@iiug.org
> Subject: RE: informix upgrade to V10 [8193]
>
> If you are on Unix write a script that back ups to disk and
> then copy those files to tape. It's a trivial exercise
>
> Cheers
> Paul
>
> Paul Watson
> Tel: +44 1414161772
> Mob: +44 7818003457
> Web: www.oninit.com
>
> Failure is not as frightening as regret.
>
> Attend IDUG 2007 San Jose, North America May 6-10, 2007 Visit
> http://www.iiug.org/conf for more information.
>
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of
> > Guo, Denny
> > Sent: 12 January 2007 11:08
> > To: ids@iiug.org
> > Subject: RE: informix upgrade to V10 [8188]
> >
> >
> > Yes. I think The limitation is 2GB.
> > Say for a 50G database, do you need 25 tapes? How to solve such
> > problem?
> > I am trying to not change the tape (100G capability), the
> dbexport can
> > write to the same tape.
> > The question is will it write from beginning? Will old data been
> > erased?
> >
> > Thanks,
> > Denny
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On
> Behalf Of
> > Kern Doe
> > Sent: Friday, January 12, 2007 11:52 AM
> > To: ids@iiug.org
> > Subject: Re: informix upgrade to V10 [8187]
> >
> > I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
> > kilobytes.) -- you can't specify size 100000000 (yes/no?)
> >
> > ----- Original Message ----
> > From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
> > To: ids@iiug.org
> > Sent: Friday, January 12, 2007 11:39:15 AM
> > Subject: RE: informix upgrade to V10 [8186]
> >
> > Remove the commas from the -s argument. It should be:
> >
> > dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p> >
> > Art S. Kagel
> > ----- Original Message -----
> > From: Denny Guo <ids@iiug.org>
> > At: 1/12 11:41:58
> >
> > Hi All,
> >
> > I am doing the dbexport now. But have some issues.
> > The current version of informxi we are running is V7.31.
> >
> > The tape we are using have 100G capability.
> > Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql
> > ip_0p"
> > would work. It complains about the block size must less
> than or equal
> > to
> >
> > tape side.
> > I have to change to tape size to "1,000,000,000". However
> it stops at
> > some point ask to mount another tape? The databse we try to export
> > only 50G.
> >
> > According to the manual, there are some restrictions for version 7.
> > See below statement.
> > "-s tapesize Specifies, in kilobytes, the amount of data that you
> > canstore on the tape. ** Restrictions: The tape size is limited to
>
> > 2,097,151 kilobytes. The limit is required because of the
> way dbexport
> > and dbimport track their positions into the tape."
> >
> > Any ideas?
> >
> > Thanks,
> > Denny
> >
> > *******************************************
> > The information contained in this e-mail message may contain
> > privileged and confidential information.
> > If you are not the intended recipient, you are hereby notified that
> > any review, dissemination, distribution or duplication of this
> > communication is strictly prohibited. If you have received this
> > message in error, please notify the sender by return e-mail, delete
> > this message and destroy any copies.
> > Internet e- mail is not guaranteed to be secure or error-free.
> > Messages could be intercepted, corrupted, lost, arrive late
> or contain
> > viruses.
> > The sender will not be liable for
> > these risks.
> >
> > *******************************************
> > Ce message electronique pourrait contenir des informations
> > privilegiees et confidentielles. Si vous n'en etes pas le
> > recipiendaire prevu, nous vous signalons qu'il est strictement
> > interdit d'examiner, de diffuser, de distribuer et de reproduire le
> > present message. Si vous l'avez recu par erreur, veuillez prevenir
> > l'expediteur par courriel, puis effacer ce message et en detruire
> > toute copie.
> > Le courrier electronique n'est pas garanti securitaire ni exempt
> > d'erreurs. Les messages pourraient etre interceptes, corrompus,
> > egares, retardes ou contamines par des virus.
> > L'exp'editeur n'est pas
> > responsable de ces risques .
> >
> > **************************************************************
> > **********
> > *******
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> > **************************************************************
> > **********
> > *******
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> > **************************************************************
> > **********
> > *******
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> > *******************************************
> > The information contained in this e-mail message may contain
> > privileged and confidential information.
> > If you are not the intended recipient, you are hereby notified that
> > any review, dissemination, distribution or duplication of this
> > communication is strictly prohibited. If you have received this
> > message in error, please notify the sender by return e-mail, delete
> > this message and destroy any copies.
> > Internet e- mail is not guaranteed to be secure or error-free.
> > Messages could be intercepted, corrupted, lost, arrive late
> or contain
> > viruses.
> > The sender will not be liable for
> > these risks.
> >
> > *******************************************
> > Ce message electronique pourrait contenir des informations
> > privilegiees et confidentielles. Si vous n'en etes pas le
> > recipiendaire prevu, nous vous signalons qu'il est strictement
> > interdit d'examiner, de diffuser, de distribuer et de reproduire le
> > present message. Si vous l'avez recu par erreur, veuillez prevenir
> > l'expediteur par courriel, puis effacer ce message et en detruire
> > toute copie.
> > Le courrier electronique n'est pas garanti securitaire ni exempt
> > d'erreurs. Les messages pourraient etre interceptes, corrompus,
> > egares, retardes ou contamines par des virus.
Based on what you want to do (no tape changing) and with IDS version 7 you're
running with, dbexport won't serve you well -- again because of the dbexport's
2G limitation. This is what you can try and I've done it before, for example:
1) using "unload" statement to unload tables to a tape, specify "no rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer;
unload to /dev/rmt/tl0n select * from order;
unload to /dev/rmt/tl0n select * from state;
unload to /dev/rmt/tl0n select * from inventory;
unload to /dev/rmt/tl0n select * from address;
2) the reload is tricky, you will to rewind the whole tape, then start with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address;
load from /dev/rmt/tl0n insert into inventory;
load from /dev/rmt/tl0n insert into state;
load from /dev/rmt/tl0n insert into order;
load from /dev/rmt/tl0n insert into customer;
This will help you to overcome the 2GB limitation, say, your customer table is
greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of your
database -- in some cases, you must load one table before another -- so you
must understand your database structure, that's the whole new subject besides
this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can
write to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I understand that dbexport and dbimport with v5 and v7 have problems with a
2-GB limit.
Does unload and load have the same limitation?
Take care.
Clifton
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kern
Doe
Sent: Friday, January 12, 2007 12:19 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8197]
Based on what you want to do (no tape changing) and with IDS version 7
you're
running with, dbexport won't serve you well -- again because of the
dbexport's
2G limitation. This is what you can try and I've done it before, for
example:
1) using "unload" statement to unload tables to a tape, specify "no rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer;
unload to /dev/rmt/tl0n select * from order;
unload to /dev/rmt/tl0n select * from state;
unload to /dev/rmt/tl0n select * from inventory;
unload to /dev/rmt/tl0n select * from address;
2) the reload is tricky, you will to rewind the whole tape, then start with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address;
load from /dev/rmt/tl0n insert into inventory;
load from /dev/rmt/tl0n insert into state;
load from /dev/rmt/tl0n insert into order;
load from /dev/rmt/tl0n insert into customer;
This will help you to overcome the 2GB limitation, say, your customer table
is
greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of your
database -- in some cases, you must load one table before another -- so you
must understand your database structure, that's the whole new subject
besides
this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can
write to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************
Thanks Kern.
I will think about it.
Have nice weekend.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 1:19 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8197]
Based on what you want to do (no tape changing) and with IDS version 7
you're
running with, dbexport won't serve you well -- again because of the
dbexport's
2G limitation. This is what you can try and I've done it before, for
example:
1) using "unload" statement to unload tables to a tape, specify "no
rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer;
unload to /dev/rmt/tl0n select * from order;
unload to /dev/rmt/tl0n select * from state;
unload to /dev/rmt/tl0n select * from inventory;
unload to /dev/rmt/tl0n select * from address;
2) the reload is tricky, you will to rewind the whole tape, then start
with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address;
load from /dev/rmt/tl0n insert into inventory;
load from /dev/rmt/tl0n insert into state;
load from /dev/rmt/tl0n insert into order;
load from /dev/rmt/tl0n insert into customer;
This will help you to overcome the 2GB limitation, say, your customer
table is
greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of your
database -- in some cases, you must load one table before another -- so
you
must understand your database structure, that's the whole new subject
besides
this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can
write to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "R
Denny-
Assuming the you're running a Unix variant, have you considered
loading Linux on a PC with a 50GB + hard drive in it? You could then
NFS mount the PC's drive and dbexport to it. As long as none of your
tables is bigger than 2GB unloaded, you should be in good shape... You
could then tar (or whatever your favorite Unix backup util is) the
mounted directory to your tape.
--EEM
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Guo, Denny
Sent: Friday, January 12, 2007 12:40 PM
To: ids@iiug.org
Subject: RE: informix upgrade to V10 [8199]
Thanks Kern.
I will think about it.
Have nice weekend.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 1:19 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8197]
Based on what you want to do (no tape changing) and with IDS version 7
you're
running with, dbexport won't serve you well -- again because of the
dbexport's
2G limitation. This is what you can try and I've done it before, for
example:
1) using "unload" statement to unload tables to a tape, specify "no
rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer;
unload to /dev/rmt/tl0n select * from order;
unload to /dev/rmt/tl0n select * from state;
unload to /dev/rmt/tl0n select * from inventory;
unload to /dev/rmt/tl0n select * from address;
2) the reload is tricky, you will to rewind the whole tape, then start
with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address;
load from /dev/rmt/tl0n insert into inventory;
load from /dev/rmt/tl0n insert into state;
load from /dev/rmt/tl0n insert into order;
load from /dev/rmt/tl0n insert into customer;
This will help you to overcome the 2GB limitation, say, your customer
table is
greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of your
database -- in some cases, you must load one table before another -- so
you
must understand your database structure, that's the whole new subject
besides
this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can
write to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas
Not to unload/load and to either filesystem or tape, as far as my experiment
went.
----- Original Message ----
From: Clifton Bean <cbean@ctm.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 1:39:23 PM
Subject: RE: informix upgrade to V10 [8198]
I understand that dbexport and dbimport with v5 and v7 have problems with a
2-GB limit.
Does unload and load have the same limitation?
Take care.
Clifton
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kern
Doe
Sent: Friday, January 12, 2007 12:19 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8197]
Based on what you want to do (no tape changing) and with IDS version 7
you're
running with, dbexport won't serve you well -- again because of the
dbexport's
2G limitation. This is what you can try and I've done it before, for
example:
1) using "unload" statement to unload tables to a tape, specify "no rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer;
unload to /dev/rmt/tl0n select * from order;
unload to /dev/rmt/tl0n select * from state;
unload to /dev/rmt/tl0n select * from inventory;
unload to /dev/rmt/tl0n select * from address;
2) the reload is tricky, you will to rewind the whole tape, then start with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address;
load from /dev/rmt/tl0n insert into inventory;
load from /dev/rmt/tl0n insert into state;
load from /dev/rmt/tl0n insert into order;
load from /dev/rmt/tl0n insert into customer;
This will help you to overcome the 2GB limitation, say, your customer table
is
greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of your
database -- in some cases, you must load one table before another -- so you
must understand your database structure, that's the whole new subject
besides
this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can
write to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'e
My understanding is that with v7 the only 2GB limit you have is on chunk
size. Output file size (exports, level0,1,2's and unloads) are an OS
limit. Which you can probably getting around by enabling large file
support (at least on the AIX platform).
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 1:14 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8202]
Not to unload/load and to either filesystem or tape, as far as my
experiment
went.
----- Original Message ----
From: Clifton Bean <cbean@ctm.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 1:39:23 PM
Subject: RE: informix upgrade to V10 [8198]
I understand that dbexport and dbimport with v5 and v7 have problems
with a
2-GB limit.
Does unload and load have the same limitation?
Take care.
Clifton
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern
Doe
Sent: Friday, January 12, 2007 12:19 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8197]
Based on what you want to do (no tape changing) and with IDS version 7
you're
running with, dbexport won't serve you well -- again because of the
dbexport's
2G limitation. This is what you can try and I've done it before, for
example:
1) using "unload" statement to unload tables to a tape, specify "no
rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer;
unload to /dev/rmt/tl0n select * from order;
unload to /dev/rmt/tl0n select * from state;
unload to /dev/rmt/tl0n select * from inventory;
unload to /dev/rmt/tl0n select * from address;
2) the reload is tricky, you will to rewind the whole tape, then start
with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address;
load from /dev/rmt/tl0n insert into inventory;
load from /dev/rmt/tl0n insert into state;
load from /dev/rmt/tl0n insert into order;
load from /dev/rmt/tl0n insert into customer;
This will help you to overcome the 2GB limitation, say, your customer
table
is
greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of your
database -- in some cases, you must load one table before another -- so
you
must understand your database structure, that's the whole new subject
besides
this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can
write to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Kern Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at
some point ask to mount another tape? The databse we try to export only
50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you
canstore on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport
and dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des
informations privilegiees et confidentielles. Si vous
n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner,
de diffuser, de distribuer et de reproduire le
present message. Si vous l'avez recu par erreur,
veuillez prevenir l'expediteur par courriel, puis
effacer ce message et en detruire toute copie.
Le courrier electronique n'est pas garanti
securitaire ni exempt d'erreurs. Les messages
pourraient etre interceptes, corrompus, egares,
retardes ou contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may
contain privileged and confidential information.
If you are not the intended recipient, you are
hereby notified that any review, dissemination,
distribution or duplication of this communication
is strictly prohibited. If you have received this
message in error, please notify the sender by return
e-mail, delete this message and destroy any copies.
Internet e- mail is not guaranteed to be secure or
error-free. Messages could be intercepted, corrupted,
lost, arrive late or contain virus
Denny,
This should be the easiest way, in order to go around tape problems.
A dbexport to an NFS mount should be no problem, you can also import from
the same external volume.
In this case you do not even need a tape.
If you have a table > 2GB (as export file !), you should use unload to ...
in 2-3 steps and then concat the data.
Truncate the table to one row and do the rest by dbexport. In the export
script, you can see the filename and replace it by the unloaded one.
Marcus
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Everett Mills
Sent: Friday, January 12, 2007 8:13 PM
To: ids@iiug.org
Subject: RE: informix upgrade to V10 [8201]
Denny-
Assuming the you're running a Unix variant, have you considered loading
Linux on a PC with a 50GB + hard drive in it? You could then NFS mount the
PC's drive and dbexport to it. As long as none of your tables is bigger than
2GB unloaded, you should be in good shape... You could then tar (or whatever
your favorite Unix backup util is) the mounted directory to your tape.
--EEM
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Guo,
Denny
Sent: Friday, January 12, 2007 12:40 PM
To: ids@iiug.org
Subject: RE: informix upgrade to V10 [8199]
Thanks Kern.
I will think about it.
Have nice weekend.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kern
Doe
Sent: Friday, January 12, 2007 1:19 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8197]
Based on what you want to do (no tape changing) and with IDS version 7
you're running with, dbexport won't serve you well -- again because of the
dbexport's 2G limitation. This is what you can try and I've done it before,
for
example:
1) using "unload" statement to unload tables to a tape, specify "no rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer; unload to /dev/rmt/tl0n
select * from order; unload to /dev/rmt/tl0n select * from state; unload to/dev/rmt/tl0n select * from inventory; unload to /dev/rmt/tl0n select * from
address;
2) the reload is tricky, you will to rewind the whole tape, then start with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address; load from /dev/rmt/tl0n insert
into inventory; load from /dev/rmt/tl0n insert into state; load from/dev/rmt/tl0n insert into order; load from /dev/rmt/tl0n insert into
customer;
This will help you to overcome the 2GB limitation, say, your customer table
is greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of your
database -- in some cases, you must load one table before another -- so you
must understand your database structure, that's the whole new subject
besides this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such problem?
I am trying to not change the tape (100G capability), the dbexport can write
to the same tape.
The question is will it write from beginning? Will old data been erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kern
Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql ip_0p"
would work. It complains about the block size must less than or equal to
tape side.
I have to change to tape size to "1,000,000,000". However it stops at some
point ask to mount another tape? The databse we try to export only 50G.
According to the manual, there are some restrictions for version 7. See
below statement.
"-s tapesize Specifies, in kilobytes, the amount of data that you canstore
on the tape. ** Restrictions: The tape size is limited to
2,097,151 kilobytes. The limit is required because of the way dbexport and
dbimport track their positions into the tape."
Any ideas?
Thanks,
Denny
*******************************************
The information contained in this e-mail message may contain privileged and
confidential information.
If you are not the intended recipient, you are hereby notified that any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you have received this message in error, please
notify the sender by return e-mail, delete this message and destroy any
copies.
Internet e- mail is not guaranteed to be secure or error-free. Messages
could be intercepted, corrupted, lost, arrive late or contain viruses.
The sender will not be liable for
these risks.
*******************************************
Ce message electronique pourrait contenir des informations privilegiees et
confidentielles. Si vous n'en etes pas le recipiendaire prevu, nous vous
signalons qu'il est strictement interdit d'examiner, de diffuser, de
distribuer et de reproduire le present message. Si vous l'avez recu par
erreur, veuillez prevenir l'expediteur par courriel, puis effacer ce message
et en detruire toute copie.
Le courrier electronique n'est pas garanti securitaire ni exempt d'erreurs.
Les messages pourraient etre interceptes, corrompus, egares, retardes ou
contamines par des virus.
L'exp'editeur n'est pas
responsable de ces risques .
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
*******************************************
The information contained in this e-mail message may contain privileged and
confidential information.
If
On 13/01/07, Marcus Haarmann <marcus.haarmann@midoco.de> wrote:
>
> Denny,
>
> This should be the easiest way, in order to go around tape problems.
> A dbexport to an NFS mount should be no problem, you can also import from
> the same external volume.
> In this case you do not even need a tape.
> If you have a table > 2GB (as export file !), you should use unload to ...
> in 2-3 steps and then concat the data.
> Truncate the table to one row and do the rest by dbexport. In the export
> script, you can see the filename and replace it by the unloaded one.
>
> Marcus
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Everett Mills
> Sent: Friday, January 12, 2007 8:13 PM
> To: ids@iiug.org
> Subject: RE: informix upgrade to V10 [8201]
>
> Denny-
>
> Assuming the you're running a Unix variant, have you considered loading
> Linux on a PC with a 50GB + hard drive in it? You could then NFS mount the
> PC's drive and dbexport to it. As long as none of your tables is bigger than
> 2GB unloaded, you should be in good shape... You could then tar (or whatever
> your favorite Unix backup util is) the mounted directory to your tape.
>
> --EEM
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Guo,
> Denny
> Sent: Friday, January 12, 2007 12:40 PM
> To: ids@iiug.org
> Subject: RE: informix upgrade to V10 [8199]
>
> Thanks Kern.
> I will think about it.
>
> Have nice weekend.
>
> Denny
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kern
> Doe
> Sent: Friday, January 12, 2007 1:19 PM
> To: ids@iiug.org
> Subject: Re: informix upgrade to V10 [8197]
>
> Based on what you want to do (no tape changing) and with IDS version 7
> you're running with, dbexport won't serve you well -- again because of the
> dbexport's 2G limitation. This is what you can try and I've done it before,
> for
> example:
>
> 1) using "unload" statement to unload tables to a tape, specify "no rewind"
> --> n
> for example,
> unload to /dev/rmt/tl0n select * from customer; unload to /dev/rmt/tl0n
> select * from order; unload to /dev/rmt/tl0n select * from state; unload to> /dev/rmt/tl0n select * from inventory; unload to /dev/rmt/tl0n select * from
> address;
>
> 2) the reload is tricky, you will to rewind the whole tape, then start with
> the last table, still with "no rewind":
> for example,
> load from /dev/rmt/tl0n insert into address; load from /dev/rmt/tl0n insert
> into inventory; load from /dev/rmt/tl0n insert into state; load from> /dev/rmt/tl0n insert into order; load from /dev/rmt/tl0n insert into
> customer;
>
> This will help you to overcome the 2GB limitation, say, your customer table
> is greater than 2GB, it won't matter any more.
>
> 3) the last tricky part is, and it depends on the logical design of your
>
> database -- in some cases, you must load one table before another -- so you
> must understand your database structure, that's the whole new subject
> besides this dbexport issue.
>
> Good luck.
<SNIPPED>
If both instances are on the same network you could try making them
visible to each other (TCP/IP connection, entries in hosts and
sqlhosts and .rhosts files). This would enable you so run ' INSERT
INTO local:db.table SELECT * FROM remote:db.table '. If the tables are
rather large (individually) then use a named pipe on the new machine
and run 2 seesions:
1. ' UNLOAD TO named_pipe SELECT * FROM remote:db.table '
2. DBLOAD from anmed pipe into target table.
Use dbschema to generate your tables and amend to place where you
require with sensible init and next.
I used this mechanism to transfer 300Gb in Nov 2005 with no issues.
Keith
Thanks for all the reply.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Penza Kenneth at MITTS
Sent: Saturday, January 13, 2007 10:55 AM
To: ids@iiug.org
Subject: RE: - RE: informix upgrade to V10 [8204] - Bay.... [8205]
Denny,
I suggest that you use HPL and unload to NFS and use HPL to load
the data from NFS. This will allow you to overcome the problem of 2G
tables, by assigning multiple devices for a particular table/s. For
example if a table is 15G create 8 or 9/10 devices for that table.
Note that HPL will use all the files at once, but there is not
guarntee that the files will all be of the same size so better an
extra one if you are not sure.
During loading use express mode for tables that do not
byte/text/blob/clob as it is a lot faster (bypass SQL layer), and for
tables that have byte/text/blob/clob columns use deluxe mode which as
slower as it requires transaction logging. Another advantage over
dbexport/dbimport is that the process is restartable of each table
without messing around.
HPL is not as straight forward as dbexport/dbimport but from my
experience with the product it justifies its complexity. I had issues
with byte/text columns and HPL in 7.30 but when I upgraded to 7.31.UD7
it worked seamlessly.
Another option can be to migrate smaller that using load/unload
commands and use HPL for the bigger tables.
Regards
Kenneth
-----Original Message-----
From: ids-bounces@iiug.org on behalf of Marcus Haarmann
Sent: Sat 1/13/2007 11:13 AM
To: ids@iiug.org
Subject: [SPAM] - RE: informix upgrade to V10 [8204] - Bayesian Filter
detected spam
Denny,
This should be the easiest way, in order to go around tape problems.
A dbexport to an NFS mount should be no problem, you can also import
from
the same external volume.
In this case you do not even need a tape.
If you have a table > 2GB (as export file !), you should use unload to
....
in 2-3 steps and then concat the data.
Truncate the table to one row and do the rest by dbexport. In the
export
script, you can see the filename and replace it by the unloaded one.
Marcus
-----Original Message-----
From: ids-bounces@iiug.org [[1]mailto:ids-bounces@iiug.org] On Behalf
Of
Everett Mills
Sent: Friday, January 12, 2007 8:13 PM
To: ids@iiug.org
Subject: RE: informix upgrade to V10 [8201]
Denny-
Assuming the you're running a Unix variant, have you considered
loading
Linux on a PC with a 50GB + hard drive in it? You could then NFS mount
the
PC's drive and dbexport to it. As long as none of your tables is
bigger than
2GB unloaded, you should be in good shape... You could then tar (or
whatever
your favorite Unix backup util is) the mounted directory to your tape.
--EEM
-----Original Message-----
From: ids-bounces@iiug.org [[2]mailto:ids-bounces@iiug.org] On Behalf
Of Guo,
Denny
Sent: Friday, January 12, 2007 12:40 PM
To: ids@iiug.org
Subject: RE: informix upgrade to V10 [8199]
Thanks Kern.
I will think about it.
Have nice weekend.
Denny
-----Original Message-----
From: ids-bounces@iiug.org [[3]mailto:ids-bounces@iiug.org] On Behalf
Of Kern
Doe
Sent: Friday, January 12, 2007 1:19 PM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8197]
Based on what you want to do (no tape changing) and with IDS version 7
you're running with, dbexport won't serve you well -- again because of
the
dbexport's 2G limitation. This is what you can try and I've done it
before,
for
example:
1) using "unload" statement to unload tables to a tape, specify "no
rewind"
--> n
for example,
unload to /dev/rmt/tl0n select * from customer; unload to
/dev/rmt/tl0n
select * from order; unload to /dev/rmt/tl0n select * from state;
unload to
/dev/rmt/tl0n select * from inventory; unload to /dev/rmt/tl0n select
* from
address;
2) the reload is tricky, you will to rewind the whole tape, then start
with
the last table, still with "no rewind":
for example,
load from /dev/rmt/tl0n insert into address; load from /dev/rmt/tl0n
insert
into inventory; load from /dev/rmt/tl0n insert into state; load from
/dev/rmt/tl0n insert into order; load from /dev/rmt/tl0n insert into
customer;
This will help you to overcome the 2GB limitation, say, your customer
table
is greater than 2GB, it won't matter any more.
3) the last tricky part is, and it depends on the logical design of
your
database -- in some cases, you must load one table before another --
so you
must understand your database structure, that's the whole new subject
besides this dbexport issue.
Good luck.
----- Original Message ----
From: "Guo, Denny" <DGuo@livingstonintl.com>
To: ids@iiug.org
Sent: Friday, January 12, 2007 12:07:43 PM
Subject: RE: informix upgrade to V10 [8188]
Yes. I think The limitation is 2GB.
Say for a 50G database, do you need 25 tapes? How to solve such
problem?
I am trying to not change the tape (100G capability), the dbexport can
write
to the same tape.
The question is will it write from beginning? Will old data been
erased?
Thanks,
Denny
-----Original Message-----
From: ids-bounces@iiug.org [[4]mailto:ids-bounces@iiug.org] On Behalf
Of Kern
Doe
Sent: Friday, January 12, 2007 11:52 AM
To: ids@iiug.org
Subject: Re: informix upgrade to V10 [8187]
I thought the limitation for IDS 7 is at 2GB for dbexport (2,097,151
kilobytes.) -- you can't specify size 100000000 (yes/no?)
----- Original Message ----
From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
To: ids@iiug.org
Sent: Friday, January 12, 2007 11:39:15 AM
Subject: RE: informix upgrade to V10 [8186]
Remove the commas from the -s argument. It should be:
dbexport -c -ss -b 1024 -s 100000000 -f db.sql ip_0p
Art S. Kagel
----- Original Message -----
From: Denny Guo <ids@iiug.org>
At: 1/12 11:41:58
Hi All,
I am doing the dbexport now. But have some issues.
The current version of informxi we are running is V7.31.
The tape we are using have 100G capability.
Issue command " dbexport -c -ss -b 1024 -s 100,000,000 -f db.sql
ip_0p"
would work. It complains about the block size must less than or equal
to
tape side.
I have to change to tape size to @@DQ@