Kbase P98727: Adding BLOB field fails with error 138
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/4/2006 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.X
SYMPTOM(s):
Adding BLOB field fails with error 138
Adding CLOB field fails with error 138
** _Area record not on file. (138)
Error 138 appears on leaving the Data-Type field
Cannot add a LOB field
CAUSE:
What /should/ happen when you leave the "Data-Type" field, is that a new window pops up, titled "Blob filed Attributes", so that you can select the Storage Area for the LOB amongst other categories. This is where the error message is coming from. The engine can't read the _area meta schema table to populate the "Area" drop-down box. How this metaschema corruption was introduced is at the time of writing unknown. The fix detailed below rectified the situation.
FIX:
The following workarounds have succeeded:
1.) Create a new table with a CLOB field, then copy that field to the original table where the CLOB field is needed. Creating a new CLOB field in the original table afterwards still fails.
2.) Dump and load the database to correct the meta-schema