Kbase P132634: Receiving error _File record not on file (138) with Security Administration tool when adding a Secur
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/06/2009 |
|
Status: Verified
SYMPTOM(s):
_File record not on file (138) displayed when trying to update security settings of a database using Security Administration tool
_File record not on file (138) with Security Administration tool
** <file-name> record not on file. (138)
Database was created prior to 10.1A
Database was migrated from Progress version 9 to OpenEdge 10 using command: proutil <dbname> -C conv910.
Database has not been dumped and loaded since migrating to 10.1X
Database has not had a proutil <dbname> -C updateschema ran against it since migrating from version 9 to 10.
FACT(s) (Environment):
prostrct builddb was performed against the database since migration from Progress version 9 to 10.
OpenEdge 10.1x
CAUSE:
Bug# OE00170630
CAUSE:
The error occurs because the security utility in the dictionary/data administration tool was updated to change the _File records for 2 tables which are _Db-option and _Db-detail. These tables do not exist in pre-10.1A databases. These tables are only available in new databases created new in 10.1A or later. These tables can also be added to databases that were converted to 10.1A or later by making use of the updateschema option to proutil.
FIX:
Run the command:
proutil <dbname> -C updateschema
The updateschema option to the proutil command updates an existing database from a prior release with the newest meta-schema for the current release. All new tables, fields and indexes are added.
If your schema needed updating, the output from the updateschema command will contain the version of OpenEdge you are running as well as the statement:
Database schema has been updated
If you ran updateschema against a database that was created within the current release of OpenEdge, the output from the updateschema command will contain the version of OpenEdge you are running as well as the statement:
The database already has the latest schema definition.
Once the proutil <dbname> -C updateschema command is ran in 10.1X, the schema for your current database will be updated.
The security utility in the dictionary/data administration tool can now be ran without receiving the "_File record not on file. (138) error.