#48 asemon with no_sa mode

[BOUHNASS Abdelilah]

Hi,

I found an issue when asemon is used with no_sa mode and there is database in read only mode: in this case, the database is an archive.

I tested the request used by asemon to get list of databases:
.../...
1> select dbid
2> from master..sysdatabases
3> where name != 'sybsecurity'
4> and status&32!=32 / db created for load /
5> and status&64!=64 / recovery started /
6> and status&256!=256 / db suspect /
7> and status&2048!=2048 / dbo use only /
8> and status&4096!=4096 / single user /
9> and status2&16!=16 / db offline /
10> and status2&32!=32 / db offline until recovery /
11> and status2&512!=512 / db upgrading /
12> and status3&8!=8 / db is being shut down /
13> and status3&4096!=4096 / db has been shut down /
14> and status3&9192!=8192 / a drop database is in progress /
15> and object_name(1,dbid) is not null
16>
17> go
dbid

---

  4

Msg 968, Level 16, State 1:
Server 'XX_XXXX_XXX', Line 1:
Database 'database 'Archive2010' (49)' is not upgraded and hence is not available for access. Please retry your query after database has been upgraded.
Msg 968, Level 16, State 1:
Server 'XX_XXXX_XXX', Line 1:
Database 'database 'xxxxxxxxx' (49)' is not upgraded and hence is not available for access. Please retry your query after database has been upgraded.
dbid

---

  5
  6
 18
 27

.../...

Regards,

[Jean-Paul Martin]

Hi Abdelilah,
which ASE version ?
which asemon_logger version ?
I already fixed some situations like this in the past
Jpm

[BOUHNASS Abdelilah]

The sybase version is 15.7 sp136 with Asemon 3.0.8b.
The status of the database is 1024.

[Jean-Paul Martin]

Ok thanks.
I did tests with ASE V15.7SP140 and asemon_logger V3.0.10 (but this new version contains no change relative to this problem)
with an archive database
not mounted
(status=1024, status2=274, status3=281149440 , status4=16384)
and mounted
(status=1024, status2=258, status3=281149440 , status4=16384)
and asemon login with no sa_role

In any case , I cannot reproduce the problem (with activity on the server and in archive database when mounted)

Can you tell me in which collector the problem occurs ?

Cheers
Jpm