on 10-24-2007 9:55 AM
Hi Friends,
When i have checked the DB13 i have see the following errors:
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.ACCTCR~0, value: 524280 KB * 1 / PSAPBTAB (> 517320/517120/517120/516112/512000 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.ACCTIT~0, value: 524280 KB * 1 / PSAPBTAB(> 517320/517120/517120/516112/512000 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.ACCTIT~1, value: 524280 KB * 1 / PSAPBTAB (> 517320/517120/517120/516112/512000 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.ARFCSDATA~0, value: 524280 KB * 1 / PSAPB(> 517320/517120/517120/516112/512000 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.BKPF~0, value: 524280 KB * 1 / PSAPBTABI(> 517320/517120/517120/516112/512000 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.BKPF~1, value: 524280 KB * 1 / PSAPBTABI (> 517320/517120/517120/516112/512000 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.BKPF~2, value: 524280 KB * 1 / PSAPBTABI (> 517320/517120/517120/516112/512000 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.BKPF~6, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.BSIS~0, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.CE1REXM~0, value: 524280 KB * 1 / PSAPBT
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.CE1REXM~1, value: 524280 KB * 1 / PSAPBT
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.CE1REXM~2, value: 524280 KB * 1 / PSAPBT
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.CE1REXM~3, value: 524280 KB * 1 / PSAPBT
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.CE1REXM~4, value: 524280 KB * 1 / PSAPBT
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.CE1REXM~Z1, value: 524280 KB * 1 / PSAPB
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.COEP~0, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.COEP~1, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.GLFUNCA~0, value: 524280 KB * 1 / PSAPBT
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.GLFUNCA~1, value: 524280 KB * 1 / PSAPBT
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.GLPCA~7, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.GLPCA~Z01, value: 524280 KB * 1 / PSAPBTA
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.LTAP~0, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.LTAP~M, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.LTAP~V, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.LTAP~Z1, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.LTAP~Z2, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.LTAP~Z3, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.MLICHECK~0, value: 524280 KB * 2 / PSAPDD
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.MSEG~0, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.MSEG~M, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.MSEG~R, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.MSEG~S, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.S033~0, value: 524280 KB * 1 / PSAPBTABI
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.S033~A, value: 524280 KB * 1 / PSAPBTABI
I had a look at the tablespaces, but it is not the table space problem because there is nearly 50% free in the table space.
Please help somebody help me as it is urgent. This occured in the production system
thanks.
Dear xyz
The messages say that these objects have a next extent of 524280 KB and there is no space for such an extent in the tablespaces PSAPBTAB/PSAPBT and PSAPBTABI. An extent has to be one continous space in the tablespace.
You can manually reduce the next extents a smaller value. See sap note 855187 if you want to use BR*Tools.
If you still have dictionary tablespaces, you should think of switching to locally managed tablespaces.
Regards
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi XYZ
Yes the action can be perfomed online and you can specify more than one object on the command line.
However i cannot give you the exact command, just an example:
brconnect -u / -f next -m 64M -t "MARC,MARA~0"
This sets the next extent to 64M or below on table MARC and on index MARA~0.
Please check the doku:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/10/46e93a96233343e10000000a114084/frameset.htm">Brconnect - Adapt next extents</a>
Regards
Michael
Hi again
BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (index) SAPR3.ACCTCR~0, value: 524280 KB * 1 / PSAPBTAB (> <b>517320/517120/517120</b>/516112/512000 KB)
From the above log, we can see that for example PSAPBTAB has a max continouus free space of 517320 KB. So if you use <b>-m 400M</b> you will be fine, because 400M is less than 517320KB. But there might not be that many chunks of this size left in your tablespace, so i suggest using an extent size which is a bit smaller (-m 64M).
Do not forget: In a second step, you will need to think about moving to locally managed tablespaces.
Regards
Michael
see also this explanation to this warning:
http://help.sap.com/saphelp_nw04/helpdata/en/4d/a241ecee0d11d5996600508b5d5211/content.htm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
search please in Oracle on SAP Forum in SDN after CRITICAL_SEGMENT, you will see helpful threads.
See please also this SAP Note:
<b><u>483856</u></b> - Description of the alerts for Oracle database monitoring
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.