Dump

[Former Member]

Hi all.

Please look at this dump and help me to splve this...

<b>Runtime Errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Occurred on 21.11.2007 at 16:06:46

An SQL error occurred when accessing a table.

What happened?

What can you do?

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was

neither

caught nor passed along using a RAISING clause, in the procedure "SAVE_DATA"

"(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

How to correct the error

The exception must either be prevented, caught within the procedure "SAVE_DATA"

"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Database error text........: "ORA-01654: unable to extend index

SAPPRD.ZRDSSTOCK~0 by 128 in tablespace PSAPPRDUSR"

Internal call code.........: "[RSQL/INSR/ZRDSSTOCK ]"

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

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC

"YKSD010 " or "YKSD010 "

"SAVE_DATA"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

</b>

Regards.

Prajwal.k

[Former Member]

While debugging check at which statement it is giving dump and paste that particular code here, then it will be for us to solve.

Regards,

Satish

[matt]

<b>ORA-01654: unable to extend index

SAPPRD.ZRDSSTOCK~0 by 128 in tablespace PSAPPRDUSR</b>

You've probably run out of space in your tablespace. Go talk to your Basis team.

matt

[Former Member]

here is the code...

006690 INDT1-WERKS = WERKS.

006700 INDT1-DAT1 = VDFRM.

006710 INDT1-DAT2 = VLDTO.

006720 * indt1-kunnr = kunnr.

006730

006740

006750 MODIFY INDT1.

006760

006770 ENDLOOP.

006780 *if indt1 is not initial.

006790 *select pkunag werks from s886 into corresponding fields of table

006800 *lv_test where pkunag = indt1-rdscode and werks = indt1-werks.

006810 *if sy-subrc = 0.

006820

006830 & changed by prajwal.k &

006840

> <b> INSERT ZRDSSTOCK FROM TABLE INDT1 ACCEPTING DUPLICATE KEYS. </b> 006860 *loop at

am getting dump in insert statement..

indt1.

006870 * INSERT ZRDSSTOCK FROM INDT1.

006880 *if sy-subrc <> 0.

006890 *message w013 WITH INDT1-MATNR.

006900 *endif.

006910 *endloop.

006920

006930

006940 & end *&

006950 * MESSAGE I004.

006960 *else.

006970 *message 'Please chek the RDS Code' type 'W'.

[Former Member]

hi

in dump, if u get such an error, normally its bcoz of field mismatch, ie u r taking the fileds from database in different order in ur select query

hope this ll solve or otherwise send the coding

regrads

karthikeyan

[former_member386202]

Hi,

Its a BASIS error u have to increase memory space, Definatelly its giving dump on select statement.

Reward Points

Regards,

Prashant

[Former Member]

hi

who to increase memory space.... by changing technical settings in database or is there any other method..

[matt]

By changing technical settings in the database. It's a Basis/DBA task.

matt

[former_member386202]

Hi prajwal k,

Basis people will do that, i faced same problem in one upgrade project.

Regards,

Prashant