topic Re: Dump on Program Display and activation in Application Development and Automation Discussions

Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 05:35:08 GMT

Hi frens

i am getting a dump when i try to activate my Z program . Usually , either error message or warnings are displayed on activation ...Moreover , iam getting a dump even wen i try to display (F7) my program.

The error analysis in ST22 states "An SQL error occured when accessing a table" .

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

"PREPARE_FOR_DISPLAY" "(FORM)"

The dump point is listed below for reference ....

002830

002840 * Inactive objects

002850 DESCRIBE TABLE l_objectlist LINES sy-tabix.

002860 IF sy-tabix > 0.

002870 SORT l_objectlist.

002880 DELETE ADJACENT DUPLICATES FROM l_objectlist.

> SELECT object obj_name FROM dwinactiv INTO TABLE l_inactivetab

002900 FOR ALL ENTRIES IN l_objectlist

002910 WHERE obj_name = l_objectlist-obj_name

002920 * AND object = l_objectlist-object " commented

002930 .

002940 SORT l_inactivetab.

002950 ENDIF.

The entries in l_objectlist are the names of the developments objects (screens , includes , subroutines etc) used in the programs ..

Any pointer on the above issue would be of help...

Regards

Pankaj

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 06:47:00 GMT

Hi,

First, a short dump never can occur in displaying of a source code of a program. If this really happens, then you have a problem! You must check the installation and check the program!!! There could be an inconsistency in your standard tables.

A short dump for a program occurs if and only if you execute the program!

From the description of the short dump, it's not very clear if it is about the source code of your zprogram or the code of the se38 (or other) transaction.

Please be clearer.

Would be useful to indicate the following:

- SAP release

- the source code specified by you belongs to standard or z* program

- the source code of your z* program itself (you may retrieve it with a small program in which use read report and export to a local file)

- if the dump occurs only for that z* program or for any program

doru

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 07:04:44 GMT

Some times this happens due to a patch update.

Shut down and restart your SAP again.

also check with others they should also face the same problem.

If the problem persists check with your basis admin.

Mohi

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 07:04:58 GMT

Looks like there is a problem with your SELECT

SELECT object obj_name FROM dwinactiv INTO TABLE l_inactivetab

Are you sure your table l_inactivetab has object obj_name fields in the same order.

Try using INTO CORRESPONDING FIELDS OF TABLE instead of just TABLE.

Regards,

Ravi

Note - Please mark all the helpful answers

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 07:16:25 GMT

thanks for ur feedback...

wd like to update on a few points..

-- SAP Release.............. "620"

Operating system......... "OS400"

Release.................. "5.3"

-- the dump is random in nature and specific to one logon ID.Itis very inconsistent

and even activates the program at times...

--- the DBtables used have been verified for consistency...

--- the source code above is from the STD SAP program that runs wen we try

to display / activate / check a Z program.

-- the problem is not specific to one Z program .

Plz do let me know if d problem is due to SAP installation and if som1 has faced

a similar one before..

Thanks

Pankaj

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 07:18:32 GMT

Hi certain steps to debug could be try to do exception handling for the codes u getting erros, put it in try block ( class:'CX_SY_OPEN_SQL_DB',) and see if the program proceeds, may be if u know coding in abap objects it can help u a little.......just a guess

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 08:23:16 GMT

Hi,

Which is the transaction you are getting in errors? SE38? What about SA38? But SE80? Did you try these? I'm trying to get more info on ur problem.

I never got this kind of problem, at least not in a such higher release.

Try to logon with different credentials and see if problem still occurs.

Try to analyze with ST01 and ST12

I look forward for your feedback

doru

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 08:28:11 GMT

Hi,

While you are loged-on with different credentials, and if you can display correctly the program, you may check also Version Management of programs, since DWINACTIV entries are user id related.

c u

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 09:57:01 GMT

Hi Doru

i appreciate your initiative and thank u for d same...

here , i like to add a few points :

i have checked it for se30 and se80 transactions .... with two different logon credentials..still d problem persists..

i have checked d version management for the program ...there is only one version in the development database and that is active.... besides no versions r there in the version database.....

I have even reinstalled my SAP GUI ....bt d problem persists. ..

awaiting a reply..

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 12:30:43 GMT

ok,

- is not a problem related to SAP GUI at all

- if for different credentials behave in same way, then is a problem related to system!

- go to ST22 and tell me the program name in which dump occured (to which that form belongs to)

- get also from there (ST22) all dump texts up to detailed info (immediately after the portion of source code indicated)

- get the info about the last SAP and DB patches applied

Re: Dump on Program Display and activation

athavanraja — Mon, 04 Dec 2006 12:54:57 GMT

did you go for any patch update recently? may be try SGEN transaction to regenerate objects.

Regards

Raja

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 13:34:19 GMT

A few of the details are below :

The procedure is in the program "SAPLSEWORKINGAREA ". Its source code starts in line 759 of the (Include) program "LSEWORKINGAREAU06 ".

The details of the Dump are below (copied from st22 ) :

Runtime Error DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Occurred on 04.12.2006 at 06:34:14

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

"FOREIGN_ITEMS_CHECK" "(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

"FOREIGN_ITEMS_CHECK"

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

To prevent the exception, note the following:

Database error text........: "SQL system error. MSGID= Job=098999/RD001/WP01"

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

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

"SAPLSEWORKINGAREA" or "LSEWORKINGAREAU06"

"FOREIGN_ITEMS_CHECK"

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.

System environment

SAP Release.............. "620"

Application server....... "R3DEV"

Operating system......... "OS400"

Release.................. "5.3"

Hardware type............ "0010000E3BEE"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 1

Short dump setting....... "full"

Database server.......... "R3DEV"

Database type............ "DB400"

Database name............ "RD0"

Database owner........... "R3RD0DATA"

Character set............ "en_US.ISO8859-1"

SAP kernel............... "640"

Created on............... "Feb 15 2006 23:00:46"

Created in............... "AIX 1 5 00538A4A4C00 (iSeries)"

Database version......... "DB4_52"

Patch level.............. "113"

Patch text............... " "

Supported environment....

Database................. "V5R2, V5R3"

SAP database version..... "640"

Operating system......... "OS400 2 5, OS400 3 5"

User, transaction...

Client.............. 100

Language key........ "E"

Transaction......... "SE38 "

Program............. "SAPLSEWORKINGAREA"

Screen.............. "SAPMSSY0 0120"

Screen line......... 7

Information on where terminated

The termination occurred in the ABAP program "SAPLSEWORKINGAREA" in

"FOREIGN_ITEMS_CHECK".

The main program was "RSABAPPROGRAM ".

The termination occurred in line 763 of the source code of the (Include)

program "LSEWORKINGAREAU06"

of the source code of program "LSEWORKINGAREAU06" (when calling the editor

7630).

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in

the

procedure "FOREIGN_ITEMS_CHECK" "(FORM)" but was not handled locally, not

declared in the

RAISING clause of the procedure.

The procedure is in the program "SAPLSEWORKINGAREA ". Its source code starts in

line 759

of the (Include) program "LSEWORKINGAREAU06 ".

Source code extract

007330 *& *

007340 * text

007350 * *

007360 * > p1 text

007370 * < p2 text

007380 * *

007390 FORM work_items_project_all.

007400 * Gleicht die ermittelten Members gegen die tatsächlich in der eigenen

007410 * Workingarea stehenden ab

007420 LOOP AT work_items.

007430 READ TABLE working_area WITH KEY object = work_items-object

007440 obj_name = work_items-obj_name.

007450 IF sy-subrc <> 0.

007460 DELETE work_items.

007470 ENDIF.

007480 ENDLOOP.

007490

007500 ENDFORM. " WORK_ITEMS_PROJECT_ALL

007510 *& *

007520 *& Form FOREIGNE_ITEMS_CHECK

007530 *& *

007540 * text

007550 * *

007560 * > p1 text

007570 * < p2 text

007580 * *

007590 FORM foreign_items_check.

007600 DATA: l_dwinactiv LIKE dwinactiv OCCURS 0 WITH HEADER LINE,

007610 l_tabix LIKE sy-tabix.

007620

SELECT * FROM dwinactiv INTO TABLE l_dwinactiv FOR ALL ENTRIES

007640 IN work_items

007650 WHERE obj_name = work_items-obj_name

007660 AND object = work_items-object.

007670 LOOP AT work_items.

007680 READ TABLE l_dwinactiv WITH KEY object = work_items-object

007690 obj_name = work_items-obj_name.

007700 l_tabix = sy-tabix + 1.

007710 IF sy-subrc <> 0.

007720 DELETE work_items.

007730 ELSE.

007740 IF sy-uname <> l_dwinactiv-uname.

007750 * Ab sofort soll doch noch angekreuzt werden.

007760 * work_items-foreign_flag = 'X'.

007770 work_items-uname = l_dwinactiv-uname.

007780 * Merken, daß Fremdbeteiligung

007790 ELSE.

007800 READ TABLE l_dwinactiv INDEX l_tabix.

007810 IF sy-subrc = 0.

007820 IF work_items-object = l_dwinactiv-object AND

Contents of system fields

SY field contents..................... SY field contents.....................

SY-SUBRC 0 SY-INDEX 0

SY-TABIX 21 SY-DBCNT 21

SY-FDPOS 119 SY-LSIND 1

SY-PAGNO 0 SY-LINNO 1

SY-COLNO 1 SY-PFKEY LIST

SY-UCOMM WB_ACTIVATE

SY-TITLE Maintain Status MAIN100 of Interface ZZMM_25_REPORT

SY-MSGTY S SY-MSGID EC

SY-MSGNO 101 SY-MSGV1 ZZMM_25_REPORT

SY-MSGV2 SY-MSGV3

SY-MSGV4

Active calls / events

No.... Type........ Name..........................

Program

Include Line

Class

19 FORM FOREIGN_ITEMS_CHECK

SAPLSEWORKINGAREA

LSEWORKINGAREAU06 763

18 FUNCTION RS_WORKING_OBJECT_ACTIVATE

SAPLSEWORKINGAREA

LSEWORKINGAREAU06 257

17 FORM ACTIVATE_CUA

SAPLSMPE

LSMPEF91 70

16 FORM USER_COMMAND_DB

SAPLSMPE

LSMPEF09 74

15 FORM USER_COMMAND

SAPLSMPE

LSMPEF09 39

14 FORM AT_USER_COMMAND

SAPLSMPE

LSMPEF09 23

13 MODULE ATUSER-COMMAND

SAPLSMPE

LSMPEI00 9

12 FUNCTION RS_CUA_WM_EDITOR

SAPLSMPE

LSMPEU12 374

11 METHOD IF_WB_PROGRAM~PROCESS_WB_REQUEST

CL_MENU_PAINTER===============CP

CL_MENU_PAINTER===============CM004 51

CL_MENU_PAINTER

10 METHOD DO_THE_NAVIGATION

CL_WB_NAVIGATOR===============CP

CL_WB_NAVIGATOR===============CM006 149

CL_WB_NAVIGATOR

9 METHOD DO_THE_NAVIGATION

CL_WB_NAVIGATOR_VIS_AS_DYNPRO=CP

CL_WB_NAVIGATOR_VIS_AS_DYNPRO=CM006 18

CL_WB_NAVIGATOR_VIS_AS_DYNPRO

8 METHOD PROCESS_WB_REQUEST

CL_WB_MANAGER=================CP

CL_WB_MANAGER=================CM001 80

CL_WB_MANAGER

7 METHOD PROCESS_REQUEST_QUEUE

CL_WB_MANAGER=================CP

CL_WB_MANAGER=================CM006 30

CL_WB_MANAGER

6 METHOD IF_WB_MANAGER~SET_WORKSPACE

CL_WB_MANAGER=================CP

CL_WB_MANAGER=================CM00P 31

CL_WB_MANAGER

5 METHOD START_INTERNAL

CL_WB_STARTUP=================CP

CL_WB_STARTUP=================CM003 41

CL_WB_STARTUP

4 MODULE (PAI) MANAGER_START

SAPLWB_MANAGER

LWB_MANAGERU03 28

3 FUNCTION WB_MANAGER_START

SAPLWB_MANAGER

LWB_MANAGERU03 16

2 METHOD START

CL_WB_STARTUP=================CP

CL_WB_STARTUP=================CM001 23

CL_WB_STARTUP

1 EVENT START-OF-SELECTION

RSABAPPROGRAM

RSABAPPROGRAM 21

Moreover , the entries in the SM21 transaction have the following pattern

Database error -901 at SEL access to table DWINACTIV

> SQL system error. MSGID= Job=099388/RD001/WP00

Perform rollback

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

> Short dump "061204 000322 R3DEV KKAKKAR " generated .

Awaiting reply

Pankaj

Re: Dump on Program Display and activation

Former Member — Mon, 04 Dec 2006 14:31:09 GMT

It says to check the system log (ST22). Have you done that?

If this doesn't help, you should open an OSS message. This forum isn't the place to work out problems with standard SAP code.

Rob

Re: Dump on Program Display and activation

Former Member — Tue, 05 Dec 2006 04:03:21 GMT

Hi ....

i have checked the system log....

Nevertheless, i thank all for their feedback and suggestions ...

Regards

Pankaj

Re: Dump on Program Display and activation

Former Member — Tue, 05 Dec 2006 08:59:53 GMT

Hi,

Go to SM21 and check in details what exactly happened there.

Post it here if it's possible

Re: Dump on Program Display and activation

Former Member — Wed, 06 Dec 2006 06:21:40 GMT

hi ,

i checked the entries in sm 21 transaction.

the entries in the SM21 transaction have the following pattern

Database error -901 at SEL access to table DWINACTIV

> SQL system error. MSGID= Job=099388/RD001/WP00

Perform rollback

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

> Short dump "061204 000322 R3DEV <logonid>" generated .

Re: Dump on Program Display and activation

Former Member — Thu, 07 Dec 2006 05:53:46 GMT

Hi,

Try these:

1. Regeneration of the standard programs

2. "Regeneration" of the DB table DWINACTIV: SE11>Display>Utilities>Database Utility and here chose the processing type (depending on the table's content size: Direct, Background, Mass Processing) and push Activate and adjust database with option Save data.

I'll comeback with additional.

Re: Dump on Program Display and activation

Former Member — Thu, 07 Dec 2006 08:26:11 GMT

Hi Doru..

i tried doing the regeneration of the programs and the DB table DWINACTIV ,, but the problem persists....