Consultor Eletrônico

C-ISAM 5.0 upgrade produces Progress error (2172).

The following Notebook Entry describes how to resolve a "Fatal
internal dataserver error.(2172)" which PROGRESS can generate when
you use C-ISAM 5.0 with C-ISAM 4.0 files.

One possible cause of error 2172 is that the C-ISAM 5.0 locking
mechanism was changed from C-ISAM 4.0.

To resolve this error against files created with C-ISAM 4.0,
in particular the files sent with PROGRESS and with the CISHOLDER
database, follow these steps to migrate the files.

1) Define the RESETLOCK environment variable as follows. The
variable does not have a value.

RESETLOCK=;export RESETLOCK

2) Run the C-ISAM utility that converts the C-ISAM 4.0
locking mechanism to C-ISAM 5.0 against your C-ISAM files.

bcheck -iyq <filename> < filename2> < filename3> . . .

The files are listed as shown in the following example.

C-ISAM File: shipping

Checking dictionary and file sizes.
Index file node size = 1024
Current C-ISAM index file node size = 1024
force locking method to agree? yes

Checking indexes and key descriptions.
Index 1 = unique key 0,5,0)
4 index node(s) used -- 2 index b-tree level(s) used
Checking data record and index node free lists.
6 index node(s) used, 0 free -- 51 data record(s) used,27 free.

3) Create a back up copy of all of your C-ISAM 4.0 files.

4) Convert your C-ISAM 4.0 files to C-ISAM 5.0 in your environment.

After each file has been converted, you can use the C-ISAM
Gateway with C-ISAM 5.0, the CISHOLDER database, and the files
included with the PROGRESS C-ISAM Gateway product.

NOTE: If you follow these steps and they do not resolve the error,
you must either upgrade PROGRESS to Version 6.3 or downgrade
C-ISAM to 4.0.

For more information, see the following documentation:

* ENGREL_5.0 - Informix C-ISAM ONLINE documentation

* ISAM_5.0 and Installation Instructions for C-ISAM 5.0

* Informix C-ISAM 5.0 Reference Manual

Progress Software Technical Support Note # 12139