Consultor Eletrônico

Status: Verified

SYMPTOM(s):

Cannot access any information in the database

Cannot modify permissions on tables anymore

Changing permissions through Data Administration returns error (499)

** Invalid access to change security for <file name> File. (499)

Changing permissions through application returns error (234)

Running 4GL that reads updates or deletes records returns error 234

** Insufficient access privilege for table <table>. (234)

** FIND FIRST/LAST failed for table _File (565)

FACT(s) (Environment):

All Supported Operating Systems
Progress/OpenEdge Product Family

CHANGE:

Changed the Table permissions to <blank>

CAUSE:

The following errors occur when accessing some metaschema tables that your userid does not have access to, or trying to change the security through a 4GL program:

** Insufficient access privilege for table <table>. (234)
** Invalid access to change security for <file name> File. (499)
** FIND FIRST/LAST failed for table _File (565)

When there are many tables user permissions to be updated, this task is typically executed with 4GL code accessing the _Field table. If the "Can-Read" field (for example) is set to <blank>:

FOR EACH _file WHERE _file-num > 0 AND _owner = "PUB":
ASSIGN _file._CAN-READ = "".
END.

This will effectively lock all and everyone out of the database. Subsequently trying to re-set the permission is no longer possible, because no-one has access to the table. When making such changes, as always, it is advisable to take a reliable backup beforehand.

FIX:

The only course of action in this circumstance is to go to backup.