[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Workaround for Error 598 ?

Status
Not open for further replies.
G

gus bjorklund

Guest
to elaborate further, the database's ".db" file contains a list of the pathnames of all the other files that belong to the database (data extents, transaction log extents, etc). each of those other files has a header that contains the pathname of the ".db" file. when you try to open a database and the two don't match, then you get error 598. when you make a copy of a database using operating system copy tools, the .db file and the extent headers do not get updated to reflect the new location of the copy -- the copy's extent headers point back to the original .db file. this is easy to fix using the ".st" file. the .st file contains a human readable form of the .db file contents. it is optional and not used during normal database operation. as james explained, you edit the .st file to have the new path names and then run the repair tool to fixe the database.=

Continue reading...
 
Status
Not open for further replies.
Top