Kbase P10125: When trying to start a database, on another machine, getting error 598.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/3/2008 |
|
Status: Verified
SYMPTOM(s):
When trying to start a database, created on another machine, getting error 598.
<file-name> is a copy of <file-name>. Database cannot be opened. (598)
Cannot connect to a database on an_other PC
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
Progress 9.x
CHANGE:
Created database through Data Dictionary which creates an Absolute Path Database
CAUSE:
When a database is created with the "procopy" command, the database is an "Absolute Path" database and can only be connected to remotely via Client/Server or through shared memory.
As soon as the .st is amended and prostrct repair utility used, the database becomes an Absolute Path database, in which case, it will have to be connected via Client Server.
Relative Path Databases create the Application Data and Schema in the same directory and are useful in Development environments. Production databases however, should have these in seperate directories, so Absolute Path databases will result.
FIX:
Create a "Relative Path" database with the "prodb" executable, from the remote PC or from the drive that the remote pc is mapped to.
prodb source target
In the following example, assume the remote PC directory path is mapped to R:\ and we need to create an empty database called "test".
1) Start proenv session where current directory is the Progress Working Directory and $DLC is set to DLC/bin
2) at command prompt, enter mapped drive letter
proenv>R:
3) prodb empty test #message: Database copied from $DLC\empty (1365)
4) prostrct list test test.st #will provide the "Relative path" structure file
The test database can now be accessed in single user mode from a remote PC