cancel
Showing results for 
Search instead for 
Did you mean: 

DBIF_RSQL_SQL_ERROR with Exception CX_SY_OPEN_SQL_DB

Former Member
0 Kudos

How to Resolve this issue....I am pasting the information required.

''

Short text

SQL error in the database when accessing a table.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

How to correct the error

Database error text........: "SQL0101N The statement is too long or too

complex. SQLSTATE=54001"

Internal call code.........: "[RSQL/OPEN/EKKO ]"

Please check the entries in the system log (Transaction SM21).

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:

"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"

"SAPLMEPOLDB" or "LMEPOLDBU02"

"ME_READ_EKKO_MULTIPLE"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"ME_READ_EKKO_MULTIPLE" "(FUNCTION)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAP-Release 700

Application server... "FCLAPP1"

Network address...... "192.168.5.24"

Operating system..... "SunOS"

Release.............. "5.10"

Hardware type........ "sun4v"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... "FCLPROD"

Database type..... "DB6"

Database name..... "FCP"

Database user ID.. "SAPFCP"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Aug 23 2009 21:08:22"

create on........ "SunOS 5.9 Generic_117171-13 sun4u"

Database version. "DB6_81 "

Patch level. 221

Patch text.. " "

Database............. "DB6 08.02., DB6 09."

SAP database version. 700

Operating system..... "SunOS 5.9, SunOS 5.10"

Memory consumption

Roll.... 16192

EM...... 4189848

Heap.... 0

Page.... 0

MM Used. 1644400

MM Free. 2542848 ''

Accepted Solutions (0)

Answers (1)

Answers (1)

vincentlim826
Employee
Employee
0 Kudos

This is DB6 related issue.

Database error text........: "SQL0101N The statement is too long or too

complex. SQLSTATE=54001"

-> consider increase DB parameter for SQL statement heap (STMTHEAP) and PCKCACHESZ.

These parameters are mentioned in SAP note 584952.

Regards,

Vincent