Kbase P17401: Errors (1531) and (1552) when starting -RO session
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/03/2003 |
|
Status: Unverified
FACT(s) (Environment):
IBM AIX POWER 5.1
FACT(s) (Environment):
Progress 9.1D
SYMPTOM(s):
Errors (1531) and (1552) when starting -RO session
Warning: another user is using this database in update mode.
Accessing the database with -RO may give unexpected results. (1531)
WARNING: Before-image file of database <name> is not truncated. (1552)
CAUSE:
A server is running for the database.
Read-only (-RO) is used to open a database for read-only access. Use -RO to access a database stored on read-only media (a read-only optical disk, for example).
If you use the -RO parameter when other users are updating the database, you might see invalid data, such as stale data or index entries pointing to records that have been deleted.
A read-only session is essentially a single-user session. Read-only users do not share database resources (database buffers, lock table, index cursors). However, unlike a normal single-user database, a read-only database can be simultaneously accessed by multiple -RO users.
When a read-only session starts, it does not check for the existence of a lock file for the database. Furthermore, a read-only user opens the database file, but not the log or before-image files. Therefore, read-only user activity does not appear in the log file.
FIX:
Don't start a server for a read-only database. Progress does not support servers for read-only users.