Skip to Content
author's profile photo
Former Member

ST22 // SYSTEM_NO_ROLL + UNCAUGHT_EXCEPTION

Hello All,

In BI system lot of ABAP Dumps found in the system.

1) SYSTEM_NO_ROLL

Unable to fulfil request for 268435456 bytes of memory space.

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

Note which actions and input led to the error.

2) UNCAUGHT_EXCEPTION

An exception occurred that was not caught.

Error analysis

An exception occurred which is explained in detail below.

The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not

caught and

therefore caused a runtime error.

The reason for the exception is:

An error occurred in the program:

The occurrence of the exception is closely related to the occurrence of

a previous exception "CX_SQL_EXCEPTION", which was raised in the program

"CL_SQL_STATEMENT==============CP",

specifically in line 31 of the (include) program

"CL_SQL_STATEMENT==============CM002".

The cause of the exception was:

ORA-04031: unable to allocate 62904 bytes of shared memory ("shared

pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")#ORA-06508: PL/SQL:

could not find program unit being called: "SYS.DBMS_STATS"#ORA-06512: at line 1

...

can you please help me to resolve the issue.

Regards

Mohsin Mulani

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers