Oracle BR0973W Database operation alert warning

[Former Member]

Hello experts,

I hope you can help me with the following:

In transaction DB13 the checkdb job reports the following errors:

BR0973W Database operation alert - level: WARNING, operation: sdvgirhz.dbp, time: 2007-05-14 15.46.27, condition: Last 'dbp' operation failed with rc = 4

BR0973W Database operation alert - level: WARNING, operation: sduxubpz.tse, time: 2007-03-30 08.58.27, condition: Last 'tse' operation failed with rc = 4

BR0973W Database operation alert - level: WARNING, operation: sduxuaou.dfa, time: 2007-03-30 08.46.40, condition: Last 'dfa' operation failed with rc = 2

I would like to get rid of these messages in dbcheck but can't figure out how to do it.

I searched the notes database, google and this forum and still couldn't find an answer.

Some data regarding oracle and sap versions:

SAP_ABA 700 0009 SAPKA70009 Cross-Application Component

SAP_BASIS 700 0009 SAPKB70009 SAP Basis Component

PI_BASIS 2005_1_700 0006 SAPKIPYJ76 PI_BASIS 2005_1_700

ST-PI 2005_1_700 0003 SAPKITLQI3 SAP Solution Tools Plug-In

SAP_BW 700 0006 SAPKW70006 SAP NetWeaver BI 7.0

SAP_AP 700 0003 SAPKNA7003 SAP Application Platform

BBPCRM 500 0003 SAPKU50003 BBPCRM

ST-A/PI 01I_CRM500 0000 - Application Servicetools for CRM 500

Database system ORACLE

Release 10.2.0.2.0

Thanks in advance for helping.

Regards

Dirk Visser

[andreas_herzog · Accepted solution]

the operations mentioned were not succesfully done...check the corresponding logfiles

-> dbp = alter database parameter (brspace)

-> tse = extend tablespace (brspace)

-> dfa = alter data file (brspace)

GreetZ, AH

[Former Member · Accepted solution]

Hi Andreas,

Thanks for your answer.

There is only one logfile still present on the system. The logfiles regarding the other 2 errors are long gone.

How can I arrange it so that dbcheck stops reporting about those 3 errors.

Dirk Visser

[andreas_herzog · Accepted solution]

you could manipulate the check conditions...have a look at transaction DB17

also, check sapnotes 483.856 & 435.290

GreetZ, AH

[Former Member · Accepted solution]

Hi Andreas,

I solved the problem by modifying the check conditions in db17, just as you suggested.

All errors older than 30 days are now discarded in the LAST_OPERATIONS_FAILED check.

Thanks for your time....

Grtz

Dirk

[andreas_herzog · Accepted solution]

great...thx 4 the points! 😄

GreetZ, AH