Error SQL313 reported from DBACockpit

[Former Member]

Hello,

Did you find a fix for this issue: SQL Message: [ASE Error SQL313][SAP][ASE ODBC Driver][Adaptive Server Enterprise]The optimizer could not find a unique index which it could use to perform an isolation level 0 scan on table 'master..monProcessActivity'?

If yes, can you please share the solution? I am having the same issue now and every information can be very useful for me.

Thank you,

Roxana

[crisnormand · Accepted solution]

Hello Roxana,

Are you remotely monitoring an ASE for non-Business Suite applications?

Regards,

Cris

[Former Member · Accepted solution]

Hello Cris,

Yes, it's a BI/BO application.

Thank you,

Roxana

[crisnormand · Accepted solution]

Hello

In an ASE for custom applications, the default locking scheme is 'allpages locking' .

And on an ASE for Business Suite, it is 'datarows locking' (mandatory).

So, the issue here is that to monitor from DBA Cockpit an ASE for non-Business Suite applications, 'datarows locking' scheme at ASE level is required when creating the MDA tables.

Regards,

Cris

[Former Member · Accepted solution]

Hi Cris,

You are right, this was the issue. My MDA tables were on All Pages locking scheme and after recreating them with datarows scheme, the error disappeared.

Thanks a lot for your help!

Roxana

[crisnormand · Accepted solution]

Hi Roxana,

Glad to help

Regards,

Cris