Kbase P5342: Cannot connect to 2nd database with logical name (4612)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/08/2010 |
|
Status: Verified
SYMPTOM(s):
Cannot connect to 2nd database with logical name (4612)
Attempt to connect to 2nd database with logical name <logical name> (4612)
can run prostrct, procopy, proutil or proserve
pro physical_dbname -ld logical_dbname connects to database
no corruption found in database
FACT(s) (Environment):
Progress/OpenEdge Product Family
Progress 7.x
Progress 9.x
CAUSE:
In this particular case, the database was migrated from Progress 7.x (Windows) to 9.x (UNIX). In the auto-connect list, an entry for database that they're trying to connect to still existed post migration, which is now redundant.
Progress uses information stored in a primary database to connect to a secondary application database, before running compiled procedures that access the second database. The primary database (the one that contains the auto-connect information for one or more databases) must be connected before Progress can perform an auto-connect.
If the primary database is a schema holder for a DataServer schema, it is automatically included in the auto-connect list, but does not appear on the auto-connect list. In the Data Dictionary, a _Db table record is the auto-connect entry for the non-Progress database in the schema holder database.
FIX:
1. Access the Data Administration tool
2. Utilities -> Edit Progress Auto-Connect List
3. Delete or Edit redundant connection information for secondary database