onload error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Susana Barea - 27 May 2005 20:36 GMT

Hello list, i need help

I need migrate a database from IDS 7.31 ON SCO OPENSERVER 5.0.5 in a PROLIANT 1850 R to a IDS 7.31 on SCO OpenServer 5.0.5 in a IBM x-series 225.

The Proliant have a DAT 40 DDS 4 and the IBM have a DAT 72 DD5.

On the Proliant i execute onunload -b 1024 -s 12582912 -t /dev/rct0 database
On the IBM i execute onload -b 1024 -s 12582912 -t /dev/rct0 -d dbdat datase and recive : "Error reading from tape device Erro No. = 0"

I verify de data on the tape with dd an i see all ok.
When i do a tar cv8 xx on the Proliant and tar xv8 xx on the IBM, it extrat the data fine, then i think that is not problem with the format of DAT (DD4 vs DDS 5).

I can do ontape and tar in the IBM.

I´ll apreciate any idea.

I need use onunload becose the dbexport produce a file grather than 2 gb and the SCO no support this; and dbexport to tape demand 5 tapes.

Thanks

Susana

sending to informix-list

Reply to this Message

Obnoxio The Clown - 27 May 2005 21:30 GMT

Susana Barea said:

> Hello list, i need help
>
[quoted text clipped - 3 lines]
>
> The Proliant have a DAT 40 DDS 4 and the IBM have a DAT 72 DD5.

Why not stick the two boxes on the same network and simply use SQL to
migrate the data?

> On the Proliant i execute onunload -b 1024 -s 12582912 -t /dev/rct0
> database
[quoted text clipped - 18 lines]
>
> sending to informix-list

Signature

Bye now,
Obnoxio

"C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule"
- Coluche

A smile is a gift that is free to the giver and precious to the recipient.
But giving someone the finger is free too, and I find it more personal and
sincere.
sending to informix-list

Reply to this Message

Neil Truby - 27 May 2005 22:33 GMT

> Hello list, i need help
>
[quoted text clipped - 20 lines]
> I need use onunload becose the dbexport produce a file grather than 2 gb
> and the SCO no support this; and dbexport to tape demand 5 tapes.

Are you sure the tape is re-wound before you do the onload?
Can you try with a smaller blocksize?
If you dd if=/dev/rct0 and pipe the result through stings, then more, does
it look sensible?

Have you enough space on the x-series to dd the tape contents out to raw
disk and try from there (obviously you could just try the first few hunndred
megabytes first).

It seems strange in the extreme that the dbexports spans five tapes. An
export will always be smaller than a binary unload, because it doesn't
contain the indexes etc.

For the table(s) whose output is greater than 2 Gigabytes you could use HPL
to bypass the limitation.

Reply to this Message