If you are getting warning situation for your CHECKDB operation as a result and issue is related to “Missing Index” situation then you can check this note to eliminate this condition.
Everything About SAP Basis
Posts Tagged With 'BR0970W'
IN_WRONG_TABLESPACE After SAP Version Upgrade
If you get a message “IN_WRONG_TABLESPACE” in your CHECKDB log especially after a SAP upgrade project then you should check the following steps…
Oracle Datafile Resize
Sometimes we get a message from DB13 “Check DB” operaion like ;
BR0970W Database administration alert – level: WARNING, type:
TABLESPACE_FULL, object: PSAPSR3DB, value: 95.46% (> 95%)
BR0970W Database Alert type: CRITICAL_TABLESPACE : MAX EXTENT
After DB13 – CHECKDB operation we could see the message like below ;
“BR0970W Database administration alert – level: WARNING, type: CRITICAL_FILE, object: N:\ORACLE\SID\SAPDATA3\ROLL_3\ROLL.DATA3, value: (max_extn) 146021 KB (> 111239 KB)”.
Featured Posts
-
Performance Issues on ABAP Stack
-
What is RISE with SAP ?
-
SAP Spool : “Waiting in host spooler (Position 1)”
-
SAP Security Patch Day for December 2022
-
ITAB_DUPLICATE_KEY in XPRA phase
-
“Upgrade is running! No import possible” in ACT_UPG
-
ORA-12154: TNS:could not resolve the connect identifier specified
-
SAP Security Mandate: SAP Software and Log4J Remote Code Execution
-
SAP HANA 2.0 Revision Strategy
-
SSH Login Without Password using PUTTY on SUSE Linux
Recent Comments