Warning in CheckDB in Production server

[Former Member]

Dear All,

I scheduled CheckDB in DB13, from last three days it is throwing warning. Please give me some solution for this. BRCONNECT Detail Log for Database is as:

BR0973W Database operation alert - level: WARNING, operation: cdunacse.nxt, time: 2007-02-01 13.39.20, condition: Last successful 'nxt' operation older than 10 days

BR0973W Database operation alert - level: WARNING, operation: sdtkglps.tbr, time: 2006-09-02 11.25.32, condition: Last 'tbr' operation failed with rc = 4

BR0973W Database operation alert - level: WARNING, operation: 0607071128.rsi, time: 2006-07-07 11.29.00, condition: Last successful 'rsi' operation older than 10 days

BR0973W Database operation alert - level: WARNING, operation: adsypacp.sve, time: 2006-07-02 17.57.07, condition: Last successful 'sve' operation older than 10 days

BR0973W Database operation alert - level: WARNING, operation: cdsvhvsv.cln, time: 2006-06-15 10.08.29, condition: Last successful 'cln' operation older than 10 days

BR0973W Database operation alert - level: WARNING, operation: sdsuygoa.dfa, time: 2006-06-13 11.21.00, condition: Last 'dfa' operation failed with rc = 2

BR0973W Database operation alert - level: WARNING, operation: sdsuygkv.tse, time: 2006-06-13 11.19.37, condition: Last 'tse' operation failed with rc = 2

BR0973W Database operation alert - level: WARNING, operation: sdsuyggr.dfa, time: 2006-06-13 11.17.49, condition: Last successful 'dfa' operation older than 10 days

Thanks in advance

[Former Member]

Hi senthil,

When ever u find such a line in db13

<b>condition: Last successful 'xxx' operation</b>

Goto db14 and search for the 'xxx' in the function id.It will tell u which is the operation related to that fn.Like in ur case

for example for 'nxt' its

nxt BRCONNECT Adapt next extents.

execute that adapt next extents from DB13 and once its completed u will not get that warning again in checdb

But the cache is i guess DB14 works only for Oracle database as for SQL its not working.

Hope u find this useful

[former_member204746]

BR0973W Database operation alert - level: WARNING, operation: cdunacse.nxt, time: 2007-02-01 13.39.20, condition: Last successful 'nxt' operation older than 10 days

--> in DB13, schedule NEXTextents job

BR0973W Database operation alert - level: WARNING, operation: sdtkglps.tbr, time: 2006-09-02 11.25.32, condition: Last 'tbr' operation failed with rc = 4

--> last time you manipulated brtools, it ended with an error, check log sdtkglps.tbr

BR0973W Database operation alert - level: WARNING, operation: 0607071128.rsi, time: 2006-07-07 11.29.00, condition: Last successful 'rsi' operation older than 10 days

-->

BR0973W Database operation alert - level: WARNING, operation: adsypacp.sve, time: 2006-07-02 17.57.07, condition: Last successful 'sve' operation older than 10 days

--> run a brarchive run in DB13

BR0973W Database operation alert - level: WARNING, operation: cdsvhvsv.cln, time: 2006-06-15 10.08.29, condition: Last successful 'cln' operation older than 10 days

--> run a CLEANUP job in DB13

BR0973W Database operation alert - level: WARNING, operation: sdsuygoa.dfa, time: 2006-06-13 11.21.00, condition: Last 'dfa' operation failed with rc = 2

--> last time you manipulated brtools, it ended with an error, check log

BR0973W Database operation alert - level: WARNING, operation: sdsuygkv.tse, time: 2006-06-13 11.19.37, condition: Last 'tse' operation failed with rc = 2

--> last time you manipulated brtools, it ended with an error, check log

BR0973W Database operation alert - level: WARNING, operation: sdsuyggr.dfa, time: 2006-06-13 11.17.49, condition: Last successful 'dfa' operation older than 10 days

--> last time you manipulated brtools, it ended with an error, check log

[Former Member]

Hello, I have the same alerts in my DB13 Check.

I saw the logs and my question is: How can I remove the alerts from the DB13 Check log?

Thanks.

[Former Member]

>>You should have opened another thread than re-opening 3 year old query.

The above setting maintained under DB17 tcode.

Try to correct the error than changing the values in DB17.

(ie. if the archive backup not taken more than 10 days. you will get an warning in your DB check. as the value maintained in DB17)

[Former Member]

Thanks Sunil, I modified the values of the metrics in DB17 and the warnings have disappeared.

I don´t understand why I should open other thread, if I would open other thread I will duplicate the information.

Thank you.

[Former Member]

>>I don´t understand why I should open other thread, if I would open other thread I will duplicate the information.

Yes correct, I thought the thread was answered thats why I mentioned. My apology.