Subject | Cannot see logged on users |
---|---|
Author | dmarmur2002 |
Post date | 2005-03-16T20:59:57Z |
Hello!
A client that ran FB 1.5 SS without problems upgraded to 1.5.2 SS when
installing a new server. They run Suse Linux. After this was done I
experience some strange symptoms:
I can no longer see which users are logged on. It always says SYSDBA
and only one SYSDBA (usually there can be more due to the way IBExpert
works).
When I give the wrong password all other installations reply 335544472
'Your user name and password are not defined. Ask your database
administrator to set up a Firebird login.'. This installation replies
335544345 'lock conflict on no wait transaction. Your user name and
password are not defined. Ask your database administrator to set up a
Firebird login.'
When I logon as SYSDBA to change a procedure I get 'object in use'
error where on other installations the same operation is mostly
possible without doing a database shutdown. Here I have to do a
database shutdown first.
In other respects, the system seems to be fine (30 users, 150 tables,
200MB database, dialect 3).
The client copied security.fdb from the previous machine when
upgrading. Can this have anything to do with things? It was a new
server and he did a clean install before this.
Thanks a lot,
/Dany
A client that ran FB 1.5 SS without problems upgraded to 1.5.2 SS when
installing a new server. They run Suse Linux. After this was done I
experience some strange symptoms:
I can no longer see which users are logged on. It always says SYSDBA
and only one SYSDBA (usually there can be more due to the way IBExpert
works).
When I give the wrong password all other installations reply 335544472
'Your user name and password are not defined. Ask your database
administrator to set up a Firebird login.'. This installation replies
335544345 'lock conflict on no wait transaction. Your user name and
password are not defined. Ask your database administrator to set up a
Firebird login.'
When I logon as SYSDBA to change a procedure I get 'object in use'
error where on other installations the same operation is mostly
possible without doing a database shutdown. Here I have to do a
database shutdown first.
In other respects, the system seems to be fine (30 users, 150 tables,
200MB database, dialect 3).
The client copied security.fdb from the previous machine when
upgrading. Can this have anything to do with things? It was a new
server and he did a clean install before this.
Thanks a lot,
/Dany