Hi,
In our Production system, we had applied Kernel upto patch level 263 and while
applying SPAM 30 for release 640 it failed. We tried applying Basis patch 15 still
it did not went through.
Since then we are getting around 1500-2500 dumps daily. The job RDDGENOLis getting cancelled and the dumps RAISE_EXCEPTION and SYNTAX_ERROR is displayed in ST22. Today, there were around 2500 dumps in the system.
When I now run the Database <-> ABAP Dictionary consistency check in
DB02, I see number of errors for missing objects in the database. There
are around of dozens of Primary Indexes, secondary Indexes, Tables,
Views listed in the result:
Objects Missing in database No.
=========================== ===
Primary indexes 6
Secondary indexes 14
Tables 37
Views 26
When I try to create each of them using SE16 or using SQL utility on OS
level, it gives an SQL system error. We are also getting thousands of
dumps each day (attached alongwith this message). Also I see the CPF327E error
in the OS Level Joblog.
Also we cannot transport any requests. There is some problem with or
due to the conversions. Is it a problem with Kernel, ABAP dictionary or
database.
Following is the extract of the dumps due to DDIC in 000:
============================================================
Runtime Error SYNTAX_ERROR
Date and Time
-
-
ShrtText |
Syntax error in program "CL_WB_CROSSREFERENCE==========CP ". |
-
-
What happened? |
Error in ABAP application program. |
|
The current ABAP program "SAPLSEWB" had to be terminated because one of the |
statements could not be executed. |
|
This is probably due to an error in the ABAP program. |
|
In program "CL_WB_CROSSREFERENCE==========CP ", the following syntax error |
occurred |
in the Include "CL_WB_CROSSREFERENCE==========CM00D " in line 8: |
| "The type "KEYWORD_TAB" is unknown."
============================================================
============================================================
Runtime Error RAISE_EXCEPTION
Date and Time
-
-
ShrtText |
Exception condition "DESTINATION_NOT_OPEN" raised. |
-
-
What happened? |
The current ABAP/4 program encountered an unexpected |
situation. |
-
-
What can you do? |
Print out the error message (using the "Print" function) |
and make a note of the actions and input that 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. |
|
is especially useful if you want to keep a particular message. |
-
-
Error analysis |
A RAISE statement in the program "SAPLCRFC" raised the exception |
condition "DESTINATION_NOT_OPEN". |
Since the exception was not intercepted by a superior program |
in the hierarchy, processing was terminated. |
|
Short description of exception condition: |
|
Specified destination is not open. |
|
For detailed documentation of the exception condition, use |
Transaction SE37 (Function Library). You can take the called |
function module from the display of active calls. |
- |
-
-
How to correct the error |
|
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: |
|
|
"RAISE_EXCEPTION" C |
"SAPLCRFC" or "LCRFCU20" |
"RFC_CONNECTION_CLOSE" |
|
or |
|
"SAPLCRFC" "DESTINATION_NOT_OPEN" |
|
or |
|
"RADBAT01 " "DESTINATION_NOT_OPEN" |
If you cannot solve the problem yourself and you wish to send |
an error message to SAP, include the following documents: |
|
1. A printout of the problem description (short dump) |
To obtain this, select in the current display "System->List-> |
Save->Local File (unconverted)". |
|
2. A suitable printout of the system log |
To obtain this, call the system log through transaction SM21. |
Limit the time interval to 10 minutes before and 5 minutes |
after the short dump. In the display, then select the function |
"System->List->Save->Local File (unconverted)". |
|
3. If the programs are your own programs or modified SAP programs, |
supply the source code. |
To do this, select the Editor function "Further Utilities-> |
Upload/Download->Download". |
|
4. Details regarding the conditions under which the error occurred |
or which actions and input led to the error. |
-
-
System environment |
SAP Release.............. "640" |
|
Application server....... "TXTPDSAP" |
Network address.......... "172.16.0.140" |
Operating system......... "OS400" |
Release.................. "5.3" |
Hardware type............ "0065000655EC" |
Character length......... 8 Bits |
Pointer length........... 64 Bits |
Work process number...... 35 |
Short dump setting....... "full" |
|
Database server.......... "TXTPDSAP" |
Database type............ "DB400" |
Database name............ "TXT" |
Database owner........... "R3TXTDATA" |
|
Character set............ "en_US.ISO8859-1" |
|
SAP kernel............... "640" |
Created on............... "Dec 11 2008 23:06:45" |
Created in............... "AIX 1 5 00538A4A4C00 (IBM iSeries with OS400)" |
Database version......... "DB4_52" |
|
Patch level.............. "263" |
Patch text............... " " |
|
Supported environment.... |
Database................. "V5R2, V5R3, V5R4, V6R1" |
SAP database version..... "640" |
Operating system......... "OS400 2 5, OS400 3 5, OS400 4 5, OS400 1 6" |
|
Memory usage............. |
Roll..................... 696832 |
EM....................... 16759712 |
Heap..................... 0 |
Page..................... 32768 |
MM Used.................. 1383120 |
MM Free.................. 3483600 |
SAP Release.............. "640" |
|
-
-
User and Transaction |
Client.............. 000 |
User................ "DDIC" |
Language key........ "E" |
Transaction......... " " |
Program............. "SAPLCRFC" |
Screen.............. "SAPMSSY0 1000" |
Screen line......... 6 |
-
-
Information on where terminated |
The termination occurred in the ABAP program "SAPLCRFC" in |
"RFC_CONNECTION_CLOSE". |
The main program was "RADBAT01 ". |
|
The termination occurred in line 22 of the source code of the (Include) |
program "LCRFCU20" |
of the source code of program "LCRFCU20" (when calling the editor 220). |
The program "SAPLCRFC" was started as a background job. |
|
Job name........ "RDDGEN0L" |
Job initiator... "DDIC" |
| Job number...... 00032101
============================================================
Kindly let me know the immediate fix. Thanks!
Regards,
Nick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.