UNIX/NT Interoperability

sbeavers · Post by **sbeavers** » Tue Mar 06, 2001 10:54 pm

We have texis running on both UNIX(64 bit) and NT systems. Can I create a database on one machine ( the NT box ) and copy it via FTP to the UNIX machine, or vice-versa, and have it all hold together?

Post by **John** » Tue Mar 06, 2001 11:57 pm

No. The database files are not compatible. You would need to either recreate the database, or use cpdb to copy the tables across.

sabety · Post by **sabety** » Wed Mar 07, 2001 6:08 am

I have similar issues. Trying to go from NT to Digital unix, but no cpdb utility on NT only copydb. I tried running cpdb from digital like this

cpdb -d /usr/netscape/server4/docs/webinator/db -h myhost -r myhost/db -t mytable.tbl -g

but error message resulted "connection refused in the function ezclientsock/could not connect"

is cpdb running on some other port number? or is the error indicative of something else?

I am able to see the remote data directory when browsing in netscape and even tried running the NT texis daemon (even though docs say don't need it), but still no help.

thanks

Post by **John** » Wed Mar 07, 2001 9:27 am

Cpdb is a newer utility, but it does exist for NT. Which version of Texis are you using on NT? You need to run cpdb on one end to act as a server.

sabety · Post by **sabety** » Wed Mar 07, 2001 10:15 am

I have the following version:

Commercial Version 3.01.977332554 of Dec 20, 2000

Post by **John** » Wed Mar 07, 2001 10:35 am

That should have it. You can copy monitor.exe to cpdb.exe, and that will work.

sabety · Post by **sabety** » Thu Mar 08, 2001 11:22 am

excellent! works both ways. But, when pulling tables up from the digital machine (with -g option), the NT process ended with this message after the data transfer was complete:

000 Internal logic error
000 ABEND exception 0xC0000005 (ACCESS_VIOLATION)

should I be concerned about the integrity of the data in the new database on the alpha?

Post by **John** » Thu Mar 08, 2001 11:39 am

I would do a quick SELECT count(*) on both sides to make sure all the records made it across. If it was after the transfer was complete then the problem occurred during the connection teardown, and will not have compromised the data that was transferred.

sabety · Post by **sabety** » Fri Aug 24, 2001 6:03 am

On some largish database tables I am getting an error on the NT end of things as follows:

read: Bad file descriptor
fillbuf: Bad file descriptor

I checked the disk space on both machines and there is plenty.

I noticed a pattern however. On the alpha server, cpdb stops at the same point each time and I get back to the command prompt. On the NT side, cpdb keeps running for a while before it gives the above error. The connection is obviously lost and NT can no longer see the host.

I ran a kdbfchk on the tables that copied unsuccessfully and no corruption was found. I also did a count(*) select to see if it was just the teardown but the number of records were much fewer than the source tables.

Post by **John** » Fri Aug 24, 2001 9:43 am

How large are the tables? Are you maybe hitting the
2GB limit on NT? The "Bad file descriptor" message is due to the connection being dropped. How many records of how many were copied?