Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

Progress 8.3x
UNIX

SYMPTOM(s):

Code page conversion table for <table-name> to <table-name> was not found in <file-name>. (6063)

Code page conversion table for GB2312 to ISO8859-1 was not found in convmap.cp. (6063).

CHANGE:

Codepage changed from ISO8859-1 to GB2312.

CAUSE:

OIB/OID process shipped with database license does not support DBE.

FIX:

The problem is due to a build issue where certain DBE OBJs/LIBs weren't linked. Thus, the V8 Open Interface Driver(OID) that is shipped with our database product is NOT double-byte enabled(DBE). Therefore the Asian double-byte SQL89 applications using the open interface broker and driver(OIB and OID) will not work properly. However, customers can use Progress' PROBUILD utility to customize and build their own DBE OID driver using the following instructions below:

A. Run PROBUILD to generate the *.lnk script for OID:
- Run probuild.
- Choose "OPEN INTERFACE DRIVER" from the "product list".
- Select "TCP-IP NETWORK PROTOCOL" from the "Configurable Elements" - Then exit the PROBUILD
- The "ldoidrvr" will be generated in the directory specified

B. Modify the "ldoidrvr":
- Find the original:
../4gl/hlidynlx.o
../4gl/dblang.o
../4gl/ccxlate.o
../4gl/fmebase.o
../4gl/smdtypn.o
../4gl/runtime.o
../4gl/compiler.o
../4gl/ut.o
Replace those "4gl" with "asian" and change to:
../asian/hlidynlx.o
../asian/dblang.o
../asian/ccxlate.o
../asian/fmebase.o
../asian/smdtypn.o
../asian/runtime.o
../asian/compiler.o
../asian/ut.o

C. Build the DBE OID:
- Make sure the C/C++ compiler/linker installed
- Run "ldoidrvr"
- "_prooidv" will be generated.

D. Use the DBE OID instead:
- Set the PROOIDRV environment variable to point to the DBE "_prooidv".
OR:
- Rename the old DLC/bin/_prooidv and copy over the DBE "_prooidv" instead.
- Make sure to shut down the OIB and the database if they are running and
restart them.