TheBestRunBusinessesRunSAP

TechnologyPlatform

SAPNetWeaver

7.0EHP2

DatabaseSystemCheckwith
BRCONNECT
Use
YoucanuseBRCONNECTtochecktheOracledatabasesystem.Theaimistopreventdatabase
problemsthatmightleadtodowntimeforthedatabase.
YoucanuseBRCONNECTtocheckthefollowingconditions:
Databaseadministration,suchasconfiguration,spacemanagement,stateofthedatabase,andso
on
Databaseoperations,suchasbackupresults,failedoperations,andsoon
CriticaldatabasemessagesintheOraclealertfile,suchasORA00600
Incorrectlysetdatabaseprofileparametersintheinit<DBSID>.orafile,suchas
log_archive_start=false
Whenacriticalsituationisdiscovered,BRCONNECTwritesanalertmessagetothedetaillogandtothe
resultstableDBMSGORA.

Integration
ThecheckconditionsarespecifiedinthecontroltableDBCHECKORA.Youcanchangethesewith
transactionDB17.Detectedalertsarealsoreportedtothedatabasemonitor(transactionRZ20).For
moreinformation,see
DB16.

MonitoringtheOracleDatabase.Youcanalsoviewalertswithtransaction

Prerequisites
BRCONNECTcanalsouseinternaldefaultconditions,whichmostlycorrespondtotheinitialstateofthe
DBCHECKORAtablewhenwedeliverit.

ForuptodateinformationontheBRCONNECTdefaultconditions,seeSAPNote
435290.

BRCONNECTDefaultConditionsforDatabaseAdministration
SeeBRCONNECTDefaultConditionsforDatabaseAdministration.

BRCONNECTDefaultConditionsforDatabaseOperations
SeeBRCONNECTDefaultConditionsforDatabaseOperations.

BRCONNECTDefaultConditionsforDatabaseMessages
YoucanenteranyOracleerrorcodesorerrortextasaconditionnameforthisconditiontype.
BRCONNECTsearchestheOracleAlertlogforcorrespondingOracleerrormessagesandmight
generateAlertmessages.TheOracleerrorcodesaretakenintoaccountforthestandardtestconditions
(doption).
SeeOracleMessagesin

DatabaseHealthAlerts.

YoucaneasilyaddanyOracleerrorcodesasnewtestconditionsfordatabase
messagesusingtransactionDB17.Youcanalsosearchanytexts(characterstrings)in
theOracleAlertfilebyspecifyingthetextinthePARAMfield.Sincethesearchinthe
OracleAlertfiletakestheupper/lowercasespellingintoaccountandtheentryinthe
PARAMfieldisalwaysconvertedintouppercaselettersusingDB17,theentrymustbe
madeusingSQLwithSQLPLUS,asinthefollowingexample:

INSERTINTODBCHECKORA(TYPE,PARAM,OBJECT,ACTIVE,SEVERITY,
CHKOP,CHKVAL,UNIT,CHKREP,REPUNIT,MODFLAG,MODDATE,MODUSER,
REACTION,CORRTYPE,CORRNAME,CHKDESC)
VALUES('ORA','Checkpointnotcomplete','','Y','W','','
','','','','','','','','D',
'Increasethesizeofonlineredologfiles',
'Cannotswitchtothenextonlineredologduetopending
checkpoint')

BRCONNECTDefaultConditionsforDatabaseProfileParameters
ThesetestconditionscheckthevaluesofOracleparameters.Thestandardtestconditionsforthe
databaseprofile(doption)correspondtothecurrentSAPrecommendationsdescribedinSAPNotes
124361and180605(SAPBW)forOracle9iandSAPNote830576forOracle10g.

YoucanusetransactionDB17toeasilyadjustthetestconditionsforthedatabase
profileparameters,dependingonthechangedrecommendationsandfornewOracle
releases.

Activities
Yourunthechecksregularly(forexample,daily).WerecommendyoutousetheDatabasePlanning
CalendarintheSAPSystemforthis.Formoreinformation,see DatabaseSystemCheck.
YouusetransactionDB16toviewalertswrittenbyBRCONNECTtotheresultstableDBMSGORA.
Formoreinformation,see DisplayingAlertMessagesfromDatabaseSystemCheck.
YouusetransactionDB17toconfiguredatabasesystemcheck.Thisincludesactivatingor
deactivatingcheckconditionsandchangingthethresholdandseveritylevels(thatis,error,warning,
orexception).Formoreinformation,see ConfiguringDatabaseSystemCheck(Oracle).
Youcanexcludespecifiedtablesorindexesfromthechecksusingthe
check_excludeparameter.
Formoreinformationonthecommandlineoptionsforthedatabasechecks,seefcheck.

C OPYR I GH T BY SAP SE OR AN SAP AF F I LI AT E C OM PAN Y. ALL R I GH T S R ESER VED .

PR I N T ED F R OM SAP H ELP POR T AL. (ht t p: / / help. s ap. c om )