Kbase P160483: OpenEdge Architect uses wrong DB schema in some projects
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/03/2010 |
|
Status: Unverified
SYMPTOM(s):
OpenEdge Architect uses wrong DB schema in some projects
Multiple projects open at the same time
Projects connect to different databases
Different databases have different schema
Projects use the same logical database names
All open projects use the schema for 1 of the databases only
** _File record not on file. (138)
OpenEdge Architect content assist snafu
FACT(s) (Environment):
OpenEdge 10.2x
All Supported Operating Systems
CAUSE:
The schema information is cached at a workspace level, to optimize for cases where multiple projects work on the same databases (for example, when various application modules each have their own project).
The filename for the cache is based on the databases' GUID if it has one. If no GUID is available, the logical database name used in the database connection is used instead.
Different databases can end up using the same cache file if they are copies of each other or never had a GUID specified. This causes issues unless the schemas of the different databases are exact matches.
FIX:
Make sure each database has it's own GUID.
The GUID can be regenerated via the Data Administration tool (Admin - > Database Identification -> Database Identification Maintenance -> New DB Passkey/Identifier)