Loading UNIX v9.1 binary dump files to Windows v10.0 database

R

RayL

New Member
Short question - should it be possible to load binary dump files from v9.1D09 on Unix into a 10.0B database on Windows XP?

Trying to help a colleague in India. Don't have all the details yet, just interested to know if this should work.

Some details - We have Mfg/Pro eB2.1 SP1 on a 9.1D09 database running on HPUX 11.23. Dumped the .df and sequences in ASCII, Dumped the tables in Binary format. Made a tar archive of all the files and then gzip'ed it. This file was copied (cp -p ...) to a CIFS share mounted on a windows XP server. From there they copied the archive to a USB drive, connected it their development pc and extracted all the files. They have installed Mfg/Pro eB2.1 SP4 on v10.0B. Apparently they can load the .df file into their empty database, but can not get the binary files to load. Unfortunately I don't have the error codes yet.

I know that Progress v9.1D09 on HPUX 11.23 is non-standard.

I'll check the platform availability guides for both QAD and Progress, but would appreciate comments / direction from the forum DBA's.

Thanks,
Ray
 
Hi Tom,
Thanks for confirming that. I hope to have hands-on access to the problem installation tomorrow. Got a list of questions ready. I'll post back any results.

List all error code(s) / error messages received.
Does the load fail immediately or after reaching a specific point?
Have they attempted to load several different files or is it the same file each time?
Have they succeeded to load any of the files?
Is there enough disk space allocated to load the data?
What is the complete command line entered to load each file?
What code page does the Windows database use? (the dump files are cpstream=iso8859-1)

Ray
 
AFAIK, -cpstream is not relevant for binary dump/load. The binary load writes all character data as it is - no conversion. Therefore the source and target databases need to have the same code page.


Heavy Regards, RealHeavyDude.
 
Okay, finally got enough details to determine the problem - no indexes! Apparently they loaded several tables and each time got a warning message "If you are certain the .bd file originated from a database with code page <name> then enter Y to continue. (10853)". Exactly as described in ID: P17987. Thinking there was a problem with the load, they wanted to verify the records existed in the database. Instead of running table analysis, they tried using their Mfg/Pro client - which couldn't find any records. They forgot one key step - they hadn't built the indexes... I suggested they use "build indexes" with each table load and then a simple for each in the Editor to see the records.

Thanks for the responses!
Ray
 
You must log in or register to reply here.
Back
Top