Hi Jeff,
You need to byte-swap data as part of the migration process. For example,
what's stored as (hex) 004E on the Solaris machine (unless it uses Intel chips)
is stored as (hex) 4E00 on the Intel-chipped Linux machine. UniVerse, as
someone else noted has a utility called fnuxi (also
You need to byte-swap data as part of the migration process. For
example, what's stored as (hex) 004E on the Solaris machine (unless it
uses Intel chips) is stored as (hex) 4E00 on the Intel-chipped Linux
machine. UniVerse, as someone else noted has a utility called fnuxi
(also known as
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Butera
Sent: Friday, November 20, 2009 7:23 PM
To: Ray Wurlod
Cc: U2 Users List
Subject: Re: [U2] Migrating OS
You need to byte-swap data as part of the migration
...@listserver.u2ug.org] On Behalf Of Jeff Butera
Sent: Friday, November 20, 2009 7:23 PM
To: Ray Wurlod
Cc: U2 Users List
Subject: Re: [U2] Migrating OS
You need to byte-swap data as part of the migration process. For
example, what's stored as (hex) 004E on the Solaris machine (unless
it
uses
-boun...@listserver.u2ug.org] On Behalf Of Jeffrey Butera
[jbut...@hampshire.edu]
Sent: Friday, November 20, 2009 6:02 PM
To: Don
Cc: U2 Users List
Subject: Re: [U2] Migrating OS
Thanks Don - I did already run all three and still encountered issues.
Sent from my iPhone
Jeff Butera
jbut
Wally wrote:
1) you haven't actually detailed the problems you encountered
2) you do need to move the files in a 'binary' mode
3) As you pointed out, Datatel has migrated many customers from Solaris to
Linux. Perhaps you should re-direct your queries to your support provider
(Datatel) - and
So I've never had the pleasure of moving Unidata from one OS to another,
but now do. We'll be moving from unidata 7.1.8 on Solaris 9 to Unidata
7.2.x on RedHat Enterprise.
At this point I'm just playing but would like advice on preferred ways
to migrate tables from Solaris to RedHat. I tried
[snip]
high byte order vs low byte order.
[snip]
It has been a really long time and my memory isn't what it was but, you may
want to look at putting something like zip onto the machines and compiling
(if your version doesn't have it already). Then just zip up your data and
move it to the new
Jeff:
I don't believe UniData has any save/restore capability, so that
method won't work. :-(
Because of this, I think there is pretty good documentation in
Administering UniData on Windows Platforms. You can also look at the
UniAdmin manual, as these functions are discussed there.
, 2009 8:29 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Migrating OS
So I've never had the pleasure of moving Unidata from one OS to another,
but now do. We'll be moving from unidata 7.1.8 on Solaris 9 to Unidata
7.2.x on RedHat Enterprise.
At this point I'm just playing but would like advice
Are you sure the technique you used to move your files kept them intact?
tarred them on Solaris
Used scp to transfer to new host
untarred on linux
Of course the database on the source system would need to be paused or
down - to be sure the files are in good state before moving them.
This
I haven't been following this thread but it occurs to me to point out that
Linux machine is probably running Intel chips with a different byte order to
that used on the Solaris machine. If that point's already been made then
please ignore this observation.
On Thu, 19 Nov 2009, Ray Wurlod wrote:
I haven't been following this thread but it occurs to me to point out that
Linux machine is probably running Intel chips with a different byte order to
that used on the Solaris machine. If that point's already been made then
please ignore this
I have moved a couple of installs of UniVerse from AIX and Windows to RH
Linux. I have found that the easiest was to do this is to use UniAdmin to
do an account save on the old system and then use UniAdmin on the new
system to restore the account. I usually do the backup to a file and ftp
the
14 matches
Mail list logo
