Kbase P181365: Unable to connect processes directly to database after log file deleted while in multi-user mode.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/01/2011 |
|
Status: Unverified
SYMPTOM(s):
Can't run promon against a database after log file was removed
Unable to connect mlti-user mode to database directly after log file was removed
Can't run online probkup against a database after log file was removed
Unable to open or create test.lg, error 2. (2257)
dbDelUsrctl: SemLockLog ret = -1
Error connecting to database after .lg file was deleted
FACT(s) (Environment):
UNIX
Progress 9.x
OpenEdge 10.x
CAUSE:
The log file was removed while the database was running. New process connecting directly to the database cannot write to a non-existing file.
FIX:
Either create the dbname.lg file using touch or run proshut dbname. Both of these commands will create a new .lg file and this allow the new connections.
Already spawned remote server process (_mprosrv and _sqlsrv2) will continue to connect remote users, but will not log information to the newly created database log file. To fix this problem, use promon to disconnect the remote server process via promon.
The proper method for trimming the database log file is to use the PROLOG command.