Switching from SCO to Linux
Posted in 1999
Topics: Error Codes & Troubleshooting, Connectivity: ODBC / JDBC / .NET, Server Administration, Platform-Specific Issues
Hi All,
I'm trying to switch our Informix 7.24 standard Engine database from SCO
Openserver to Linux. I got the informix system up and running in about
20 minutes on the linux machine, built the sample database and was able
to use it (locally and remotely via ODBC), everything was dandy. But
when I tried to use our old database from the SCO system (I made a cpio
file of the entire ./sales.dbs/ directory, then copied that to the linux
system and extracted it) I got the following error in dbaccess while
trying to select the database
329: Database not found or no system permission.
117: ISAM error: isam file format change detected.
As far as I can tell all the permissions and ownerships are identical on
both systems...
(usernames and groups match, the user-id and group-id numbers do vary
from the SCO system since I cannot recreate the entire userbase from SCO
to Linux)
Hardware wise both systems are virtually identical (Pentium II's).
Am I doing something fundamentally wrong here, is there a better way of
copying databases between systems?
Many thanks in advance,
Sven Eric, The Netherlands
P.S. please also reply directly to my e-mail address since my news-feed
is thready (no pun intended) at best.
In article <3766AC06.C7FFD103@xs4all.nl>,
Sven Eric <sveneric@xs4all.nl> wrote:
>I'm trying to switch our Informix 7.24 standard Engine database from SCO
>Openserver to Linux. I got the informix system up and running in about
>20 minutes on the linux machine, built the sample database and was able
>to use it (locally and remotely via ODBC), everything was dandy. But
>when I tried to use our old database from the SCO system (I made a cpio
>file of the entire ./sales.dbs/ directory, then copied that to the linux
>system and extracted it) I got the following error in dbaccess while
>trying to select the database
>
>329: Database not found or no system permission.
>117: ISAM error: isam file format change detected.>
>...
>
>Am I doing something fundamentally wrong here, is there a better way of
>copying databases between systems?
>
>Many thanks in advance,
>Sven Eric, The Netherlands
>
>P.S. please also reply directly to my e-mail address since my news-feed
>is thready (no pun intended) at best.
The Linux SE port uses a different locking protocol from the SCO
port. The proper way to do this would have been to use unload and
load, or dbexport/dbimport.
You might get away with running bcheck against *every* table in the
affected databases (*including* the system catalog tables) with the
-s option to reconstruct the index nodes, but I've never tried that
in your situation. The safer method is to unload to and reload
from flat files. (Check the manual appendix for bcheck syntax;
I don't think REPAIR TABLE has an equivalent to the -s option).
--
Alan Denney yosemite at accesscom.com
Don't anthropomorphize computers. They don't like it.