Illegal access to a string (length too large) in broadcasting option

[Former Member]

Hi All,

I'm working with BW 7 SP 16 and Portal 7 SP 14

I'm getting this error in the portal:

"Error when processing your request

The following error text was processed in the system DBW : Illegal access to a string (length too large)

The error occurred on the application server SRVJRZSAPDBW_DBW_00 and in the work process 0 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: IS_QUERY_CACHE_USABLE of program CL_RSR_MONITOR_SERVICES=======CP

Method: IF_RSRD_F_PRODUCER_RT~PRODUCE of program CL_RSRD_PRODUCER_PRECALC======CP

Method: EXECUTE_NODES of program CL_RSRD_SETTING===============CP

Method: EXECUTE of program CL_RSRD_SETTING===============CP

START-OF-SELECTION of program RSRD_BROADCAST_PROCESSOR

"

When executing a new setting for Fill Olap Cache in the Bex Query Designer Tool Publish menu --> BEx Bradcaster... New setting and then execute.

and in the rst22 BW transaction the following dump appears:

"Err.tmpo.ejec. STRING_LENGTH_TOO_LARGE

Excep. CX_SY_RANGE_OUT_OF_BOUNDS

Fecha y hora 06.05.2008 20:56:07

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

caught in

procedure "IS_QUERY_CACHE_USABLE" "(METHOD)", nor was it propagated by a

RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

In the running program "CL_RSR_MONITOR_SERVICES=======CP", part of a string was

about to be accessed

with an explicitly specified length.

However, this length (50) exceeded the current length of the string

(17).

This kind of access is illegal.

Notas para corregir errores

Reduce the length with which to access the string.

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"STRING_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"

"CL_RSR_MONITOR_SERVICES=======CP" or "CL_RSR_MONITOR_SERVICES=======CM002"

"IS_QUERY_CACHE_USABLE"

"

Does anybody know what can be happening??

Thanks in advance.

Yolanda.

[Former Member]

Hi There,

I get the same error dump "STRING_LENGTH_TOO_LARGE" , "CX_SY_RANGE_OUT_OF_BOUNDS" in the process chain event "Trigger Event data change (for Broadcaster)" where it generates a short dump saying

================================================================

STRING_LENGTH_TOO_LARGE

CX_SY_RANGE_OUT_OF_BOUNDS

An exception occurred that is explained in detail below.

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

caught in

procedure "IS_QUERY_CACHE_USABLE" "(METHOD)", nor was it propagated by a

RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

In the running program "CL_RSR_MONITOR_SERVICES=======CP", part of a string was

about to be accessed

with an explicitly specified length.

However, this length (50) exceeded the current length of the string

(17).

This kind of access is illegal.

=================================================================

Have already searched on the OSS and SDN but couldn't find any existing note/posts related to this issue.

Does anybody has a solution for this.

regards

Kulmohan

[denis_dyachenko]

Go the same short-dump

We are on BW SPS18

No solution found so far

[Former Member]

Hi Everyone,

I had the same problem when trying to fill the OLAP cache through running the BEx broadcaster for a particular query. I also received the same error message in ST22. Whilst the error message isn't entirely clear, the following part of the exception, with reference to the query cache being usable, points us in the right direction.

An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
caught in
procedure "IS_QUERY_CACHE_USABLE" "(METHOD)", nor was it propagated by a
RAISING clause.

My error was due to the fact that the query I was trying to broadcast contained virtual key figures. By default queries with virtual key figures are not cacheable, as the query result values for virtual chars can be incorrect in certain circumstances. In my case the cached result values for virtual key figures would produce the correct result, hence I changed the query to being cacheable by:

1. Going into the query monitor (RSRT)

2. Entering the query name, clicking on Properties

3. Checking the check box for 'Cache Use Despite Virtual Characteristics/Key Figs'

After doing this I was able to Execute the BEx broadcaster for the query without any problems. Hope you found this helpful.

Cheers,

Campbell