#6 Asemon logger is filling sysystemprocs database

[Anonymous]

Since asemon_logger is collecting data into a second DB instance it starts to fill up a log in sybsystemprocs database.

For example I can see in the log DOL_DELETE on sysprocedures.

Any idea appreciated.

Regards,
Petr

[Jean-Paul Martin]

Hi, it is strange, asemon_logger does nothing in sybsystemprocs, and does not go into it !!! I never heard about such a problem. When you say " a second DB instance" do you mean it is the "archive" database where asemon writes collected data ? If yes can you check the login can enter your "asemon database" and does not enter in the sybsystemprocs database ? Where are asemon tables created ?

Regards

JP

[Anonymous]

Hi Jean-Paul,

by "a second instance" I ment "archive" database. Asemon logger is connected as "sa" so the login can access the "archive" database and also sybsystemprocs.

I have two "archive" databases called "asemon" and "asemon2". Several congfig files for asemon_logger. These have not been changed during my tests.

I tried 3 situations:
1. when data are collected into asemon ONLY the log in sybsytemprocs is fine.
2. when data are collected into asemon2 ONLY the log in sybsytemprocs is fine.
3. when data are collected into asemon AND asemon2 in the same time the log in sybsytemprocs is filling quickly.

Any idea?

Regards,
Petr

[Jean-Paul Martin]

Hi Petr,
I know sites where asemon archive collected data into several "archive databases" on same ASE server, and they don't encounter this problem.

Do you have "capture missing statistics", "abstract plan dump" or "enable metrics capture" activated on your archive server ? Can you do "select * from master..syslogshold where dbid=dbid_of_your_sybsystemprocs" and see which spid is holding log in sybsystemprocs ?
Or, do a dbcc log in sybsystemprocs to see what tables are affected and make growing the syslogs

Regards
Jean Paul