Kbase P100761: Clients started with the -RO parameter do not see database schema changes even when they reconnect.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/16/2009 |
|
Status: Unverified
SYMPTOM(s):
Clients started with the -RO parameter do not see database schema changes.
Read-only clients are unable to see schema changes.
Reconnecting to the database does not help.
Read-only clients are connecting via shared-memory.
Problem is seen on both ODBC and 4GL clients.
FACT(s) (Environment):
Progress 8.3x
Windows
MERANT 3.70 32-BIT Progress SQL-89
CAUSE:
The read-only (-RO) clients fail to see these changes, because multi-user sessions are using a shared buffer pool, and all database changes go into that buffer pool. These changes are not written to disk immediately. If at the same time, a client connects as a read-only session, the process does not consider the buffer activity of the other sessions and only sees what is on disk.
FIX:
Start an Asynchronous Page Writer (APW) for the database, e.g.: "proapw sports". The changes will then be written to disk periodically.