Last successful 'svd' operation older than ... do not comply db17 value

[benoit-schmid]

Hello,

On one of our system, we regularly have:

BR0973W Database operation alert - level: WARNING, operation: aeizjdix.svd, time: 2012-07-14 22.49.15, condition: Last successful 'svd' operation older than 10 days

In db17, DBO ARCHIVE_TOO_OLD is set to > 15 D.

Therefore it should not complain as far as I can see.

Would you know, why brconnect does not use the 15D threshold?

Thanks in advance for your answers.

[Former Member · Accepted solution]

In DB17 look for an additional line starting with:

DBO OPERATION_TOO_OLD svd ...

(Or perhaps without svd)

[benoit-schmid · Accepted solution]

Hello,

I had a configuration that was a little different in PRD than in my other instances.

It used to work the same and the behaviour changed after applying sps.

In PRD I had a duplicate check:

LAST_OPERATION_FAILED and LAST_OPERATION_FAILED with object=chk.

I have disabled LAST_OPERATION_FAILED and let the one restricted to chk.

See you,

[Former Member]

Check init<DBSID>.sap. It could be read from the profile.

Additionally, check the condition is active (green light)

Best regards,

Orkun Gedik

[benoit-schmid]

Hello,

There is no check threshold in my init<SID>.sap.

Which parameter were you thinking about?

But as far as I know all these check settings are from db17.

Am I right?

Orkun Gedik wrote:
Check init<DBSID>.sap. It could be read from the profile.
Additionally, check the condition is active (green light)
Best regards,
Orkun Gedik

Regards,

[Former Member]

>> But as far as I know all these check settings are from db17.

You are correct, but;

It could be configured by the "check_cond" parameter in the init<DBSID>.sap, also. Check the note 892294 - Enhanced support for non-ABAP database in BRCONNECT 7.00

Did you check the parameter is active on DB17?

Best regards,

Orkun Gedik