Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

Dbtool option to scan and fix SQL-width fails with protrace file

Dbtool option 2 fails to correct SQL-width

Dbtool option 2 fails

Dbtool option 2 fails when auditing is enabled.

Dbtool option 2 does not work.


Errors in database log file

Disconnecting dead user <userid>. (2527)

Begin transaction backout. (2252)

Transaction backout completed. (2253)


user xxx died holding the audit policy latch

Progress stack trace reads:
_thr_slot_offset
_sema_post
fileInfoGet
audFilePolicyLoad

FACT(s) (Environment):

All Supported Operating Systems
OpenEdge 10.1C

CAUSE:

Bug# OE00176247

FIX:

Two workarounds are:
1. a) Disable auditing
b) run dbtool option 2
c) Enable auditing again.
2. a)Scan the entire database and check to see whether data contained in character fields exceeds the SQL-WIDTH. Please reference Progress solution P13348, "How to detect problematic SQL-WIDTH with a 4GL program", to do this.

b) Expand the SQL-WIDTH by following these steps:

i) From the Data Dictionary on UNIX:
1) Select Schema.
2) Select SQL Properties.
3) Select the desired table.
4) Change the width for desired field to a number that your data length is (less than 2K).
5) Save.

ii)From Data Dictionary on Windows:
1) Select "SQL Properties" from "Options" menu.
2) Select "Adjust Field Width".
3) Change the width for desired field to a number that your data length is (less than 2K).
4) Save.

iii) To change the width programmatically (via the Progress 4GL):
find first _file where _file._file-name = "<table>".
find first _field of _file where _field._field-name = "<column>".
update _field._width.