We would only suspect possible db corruption if: error 3191 is reported by a) SVR tablename provided b) USR tablename provided c) USR table 0
only client memory corrupt if: SVR table 0
Table 0 is a pseudo-table where 4GL variables are stored. Therefore error 3191 with table 0 does not indicate database corruption, but rather that the memory is corrupt on the remote client.
In this case it was because certain privaleges on user accounts only allow one login. When the second TS session is opened through the same terminal server, the first TS session that was connected to the database is terminated aggressively and as a result the shared memory on the client is in an inconsistent state. |