I wonder if I am having wrong setings in my OpenEdge 11.7 eclipse. If I start writing a dbname, it will give me hit on more than the one db that has the table. If I have tree db's, A, B and C. I have one table called invoice in db B, I will get A.Invoice, B.Invoice and C.Invoice. This is kind of messy for me. What could be wrong?
goo, I went to the Data Administration Tool, and for each database, I went to:
Admin -> Database Identification -> Database Identification Maintenance.
All databases I created from empty8 had the same identifier, so I clicked on the "New DB Passkey/Identifier" button. That brings up a dialogue where I just clicked OK and the identifier changed. I had to close all but one of the projects connected to the db though, otherwise it gave a message that the DB is in use.
After that, I had to select the following the Eclipse menu before everything worked correctly:
OpenEdge-->Refresh Cache (Ctrl+R)
Hope this helps
Simon L Prinsloo
Yes, it's a mess. I have two databases connected, only tables of the first database are shown... twice. With the first database name as prefix and with the second database name as prefix.
In this case, underlying problem is with the process of creating Database. We see this issue when we actually create database as a copy.
prodb test empty
prodb test1 empty
In the above example, even though test and test1 are two different databases, they both share same instance id. Because of the same reason, PDS OE confuses among the databases with same instance id.
If we create database either by using -newInstance or from Data Administrator, above issue will not be seen.
prodb test empty -newInstance
From Data Administrator
Hope this helps,
So how do we fix this for the existing databases? or do I have to live with this problem?
Databases supplied in the install directory for this release, contain the field for a database GUID, but the field contains the Unknown value (?) rather than a valid GUID. When PRODB is used to copy one of these databases, the GUID field of the target database is automatically set.
Thanks Simon, I will try that :-)