[DB Cleaner on Steroids] Error accessing overview log tables

Forge Component
(20)
Published on 19 May by Miguel 'Kelter' Antunes
20 votes
Published on 19 May by Miguel 'Kelter' Antunes

Good afternoon, when I try to access the overview of the log tables I get the following error in servicecenter:

"Error executing query. Error in advanced query CountRecords in GetMaxDateForLog in DBCleanerOnSteroids (SELECT MAX(Instant) FROM @LogTable ): Invalid object name 'dbo.osLog_Error_0'."

Anyone has any idea of what might be the cause?

Do you have your logs in a separate catalog or under a different owner?

Solution

It is not currently possible due to limitations in what's available in the platform to manage logs in separate catalogs via a forge component You could create a database connection string and then modify the extension to use that connection string. Alternatively, you can do that part through direct database access outside the platform


Stacey

Solution

It is in a different catalog.

Ok thanks for the response.

Hello Stacey Levine,


I am using only the Main Catalog and getting the same error!


We are using OutSystems On-Premise Server, Is this a problem?

Mohamed Emam wrote:

Hello Stacey Levine,


I am using only the Main Catalog and getting the same error!


We are using OutSystems On-Premise Server, Is this a problem?

What version of the platform are you using?  What is the platform database? Are you using the latest version of the component??



Stacey Levine wrote:

Mohamed Emam wrote:

Hello Stacey Levine,


I am using only the Main Catalog and getting the same error!


We are using OutSystems On-Premise Server, Is this a problem?

What version of the platform are you using?  What is the platform database? Are you using the latest version of the component??



Platform Version 11.0.212.3

SQL Server Database

And I just downloaded the DBCleaner version 1.0.3 and suddenly the Log Tables Menu Item has disappeared and can't find in the module anymore!


I am getting this error:

I wonder if possibly you installed it under a different schema than "dbo". My only suggestion would be to get with a DBA and see if you can check the underlying SQL tables and see what it's actually called.


Stacey