Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

Progress 9.1D

SYMPTOM(s):

The fields change to case-sensitive each time perform update on the MS SQL Server schema holder

The SQL Server is case-insensitive

The _DB.Db-MISC1[1] is set to unknown value (?) for the schema holder

CAUSE:

Someone changed the meta-schema data of _DB._db-Misc1[1] value from 1 (case-insensitive) to unknown value. The value for case-sensitive is 0. But in this case since the value is unknown, it is defaulting to case-sensitive. Therefore, during the update of a table, all the fields change back to case-sensitive.

FIX:

There are two workaround to fix this issue:

Before you perform the following steps, use the solution P7262 to change the case-sensitive flag to case-insensitive.

1. Change the _DB._Db-Misc1[1] to 1 using the following syntax:

FOR FIRST _DB:
ASSIGN _DB._Db.Misc1[1] = 1.
END.

Or,

2. Follow the steps below:

a. Dump the .df from the schema holder using Data Administration > Admin > Dump Data and Definitions > Data Definitions (.df files)...
b. Open the .df file and change or add the "DB-MISC11 1" with out the double code just above the "DRIVER-NAME" parameter on the top of the file and save the .df file
c. Delete the DataServer Schema using the Data Administration > DataServer > MS SQL Server Utilities > Delete DataServer Schema...
d. Load the .df file using the Data Administration > Admin > Load Data and Definitions > Data Definitions (.df files)...