Skip to Content
author's profile photo Former Member
Former Member

Warning al realizar un Check database DB13

Buenos dias a todos,

Me estoy iniciando en SAP, me gustaria que me ayudaran en esto, tengo programado en el calendario (DB13) la accion Check database, al verificar el resultado me encuentro con el siguiente Warning:

<b>BR0970W Database administration alert - level: WARNING, type: CRITICAL_SEGMENT, object: (table) SAPR3.RSDMTA_LEAD_DET, value: 327680 KB * 2 / PSAPBTABD (> 330072/245760/204800/204800/204800* KB)</b>

Estaria muy agradecido si me ayudaran a interpretarlo y mejor aun a resolverlo.

Muchisimas gracias.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Sep 29, 2011 at 03:16 PM


    En la nota 435290:


    This condition checks whether there are tables or indexes that can cause an overflow of the tablespace with the allocation of up to 5 Next-Extents. As a default, all tables and indexes are checked against the same threshold value. However, you can define different threshold values for individual segments or tablespaces by specifying their names in the OBJECT field of the DBCHECKORA table (transaction DB17).

    Possible checking operands, threshold values, value units:

    17a. <= 1, 2, 3, 4, 5 <none>

    When you allocate up to 1, 2, 3, 4 or 5 Next-Extents, the tablespace overflows.

    Important: The check condition CRITICAL_SEGMENT is irrelevant for locally managed tablespaces (LMTS), where the NEXT extents are determined automatically by Oracle. If space is limited, the system tries to fully utilize the available freespace, regardless of the size of the last extent allocated and the size of the freespace extent. For this reason, you should concentrate on monitoring the check condition TABLESPACE_FULL for LMTS.


    MAXSIZE ha alcanzado el límite?

    También mire las siguientes notas:

    214995 Oracle locally managed tablespaces in the SAP environment

    666061 FAQ: Database objects, segments and extents

    599694 LMTS autoallocate: Extent allocation


    Eduardo Rezende

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.