Question:
Hi Friends.
HR Production Server.
It is regarding DB02 transaction. In DB02 sceen date is not upto date ,it shows 12-02-07 than 26-04-07(we also run the refresh_db02 job but no use). could u please tell me the procedure to show the currect time.
And also we are getting some abap dumps every day. like..
1)DBIF_DSQL2_SQL_ERROR (dailey once same user same time)
20.04.2007 at 08:10:13
21.04.2007 at 08:13:43
23.04.2007 at 08:10:03
24.04.2007 at 08:10:43
25.04.2007 at 08:10:24
26.04.2007 at 08:10:34
2)TIME_OUT
This al so daily many times different users.
4)DYNPRO_SEND_IN_BACKGROUND .
how to solve this issue.
In Earleywatch report we are getting Top 5 trasactions, how it will take top 5 transactions( I mean in ST03n, bassed on which responce time it will take). and please gide me how it will resove?
[/code]
Answer:
Please provide more details on the ABAP dumps. What table is involved? Can be a DDIC inconsistency or DB error?
Answer:
Hi snmsee ,
I am posting abap dumps error.. could u please give me the procedure to solv this dumps. And also give me some suggations about Top 5 transactions and DB02..
Thank you.
1)DBIF_DSQL2_SQL_ERROR
21.04.2007 at 08:13:43
08:10:00
SQL error "-1224" occurred when executing EXEC SQL.
User, transaction...
Client.............. 400
User................ "CSZPBAT"
Language key........ "E"
Transaction......... " "
Program............. "RSDB2T2M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "RSDB2T2M" in GET_TABLE_SIZES".
The main program was "RSDB2T2M ".
The termination occurred in line 1385 of the source code of the (Include)
program "B2T2MF04"
of the source code of program "B2T2MF04" (when calling the editor 13850).
The program "RSDB2T2M" was started as a background job.
2)TIME_OUT
20.04.2007 at 11:47:15
User, transaction...
Client.............. 400
User................ "CARTWRK01"
Language key........ "E"
Transaction......... "PC00_M08_CP46_STD”
Program............. "SAPLRPIB"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
What happened?
The program "SAPLRPIB"and "SAPFP50P" (Basis:- "/SDF/SAPLMEC") has exceeded the maximum permitted runtime without Interruption, and has therefore been terminated.
Information on where terminated
The termination occurred in the ABAP program "SAPLRPIB" in "RE510I".
The main program was "RPCP46G0 ".
The termination occurred in line 397 of the source code of the (Include)
Program "LRPIBF30" of the source code of program "LRPIBF30" (when calling the editor 3970).
Error analysis
After a certain length of time, the program is terminated. In the case
of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.
The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
program. The
current setting is 300 seconds. Once this time limit has been exceeded,
the system tries to terminate any SQL statements that are currently
being executed and tells the ABAP processor to terminate the current
program. Then it waits for a maximum of 60 seconds. If the program is
still active, the work process is restarted.
successfully processed, the system gives it another 300 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".
3)UNCAUGHT_EXCEPTION
CX_HRPA_INVALID_PARAMETER
24.04.2007 at 13:49:51
An exception that could not be caught occurred.
What happened?
The exception 'CX_HRPA_INVALID_PARAMETER' was raised but was not caught at any stage in the call hierarchy.
Since exceptions represent error situations, and since the system could
not react adequately to this error, the current program,
'CL_HRPA_RESOLVE_EXCEPTION=====CP', had to
be terminated.
User, transaction...
Client.............. 400
User................ "FERLETB01"
Language key........ "E"
Transaction......... "SARP "
Program............. "CL_HRPA_RESOLVE_EXCEPTION=====CP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "CL_HRPA_RESOLVE_EXCEPTION=====CP"
in "RESOLVE".
The main program was "ZHRR0032 ".
The termination occurred in line 80 of the source code of the (Include)
program "CL_HRPA_RESOLVE_EXCEPTION=====CM001"
of the source code of program "CL_HRPA_RESOLVE_EXCEPTION=====CM001" (when
calling the editor 800).
Processing was terminated because the exception "CX_HRPA_INVALID_PARAMETER"
occurred in the
procedure "RESOLVE_EXCEPTION" "(FORM)" but was not handled locally, not
declared in the RAISING clause of the procedure.
The procedure is in the program "SAPFP50P ". Its source code starts in line 2138
of the (Include) program "FP50PE10 ".
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_HRPA_INVALID_PARAMETER',
was neither
caught nor passed along using a RAISING clause, in the procedure
"RESOLVE_EXCEPTION" "(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:
Invalid parameter EXCEPTION, value
The occurrence of the exception is closely linked to the occurrence of a
previous exception, "CX_HRPA_VIOLATED_PRECONDITION", which occurred in the
program "CL_HRPA_MASTERDATA_FACTORY====CP" -
specifically in line 6 of the (Include) program
"CL_HRPA_MASTERDATA_FACTORY====CM004".
The reason for the exception was:
Precondition violated
4) DYNPRO_SEND_IN_BACKGROUND
20.04.2007 at 10:34:32
Screen output without connection to user.
What happened?
Error in ABAP application program.
The current ABAP program "SAPMSSY0" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program. User, transaction...
Client.............. 400
User................ "RFCADM"
Language key........ "E"
Transaction......... " "
Program............. "SAPMSSY0"
Screen.............. "SAPMSSY0 0120"
Row of screen....... 0
Information on where terminated
The termination occurred in the ABAP program "SAPMSSY0" in "%_CTL_OUTPUT".
The main program was "RPRHRDOC ".
The termination occurred in line 30 of the source code of the (Include)
program "<SYSINI>"
of the source code of program "<SYSINI>" (when calling the editor 300).
Error analysis
During background processing, the system attempted to send a
screen to a user.
Current screen: "SAPMSSY0 " 0120.
Answer:
All causes of these dumps are described on the SAP Support Market Place. Perform search and have a look at the solutions.
Answer:
Try checking the Date / Time at OS level in your server. Also check the Time Zone in your Server (At OS Level)
KR