on 11-02-2010 1:18 PM
We have recently upgraded kernel patch to 254 on our ECC 6.0, AIX 5 on oracle database. But we have so many dumps SYSTEM_CORE_DUMPED.
SAP_BASIS 700 0009 SAPKB70009
SAP_ABA 700 0009 SAPKA70009
PI_BASIS 2005_1_700 0009 SAPKIPYJ79
PI_BASIS 2005_1_700
SAP has suggested that need to implement that disp+work package to 277.
Kindly suggest can we implement disp+work package on our system because it is database independent.
Regards,
PANU
Hi,
As suggested by SAP, go ahead and upgrade the disp+work to 277 and revert to us if the same issue persists.
Regards,
Varadharajan M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Yes, indeed you should patch it. SAP note 19466 will help you on this.
Br,
Javier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your replay...
We have successfully implemented it on our Development system but give an error in our Quality system while applying disp+work package to 277.
x dw_gui.o
SAPCAR: could not open for writing /sapmnt/XXX/exe/dw_gui.o (error 28). Text file busy.
Then we revert back to old kernel.
Kindly suggest any one have face same issue before..
Regards,
PANU
Edited by: kumar panu on Nov 5, 2010 10:22 AM
This issue means that some files from your kernel are still in use so you have to options stop completly you SAP System to be sure search your SAP procees on windows with taskmanager --> process in UNIX with this command
ipcs |grep <sid>adm
an clean those proces after that you can try again
the second option is that you copy your SAPCAR in a tmp where you also copy all you new SAR's and uncompress there.
Regards
Hi All,
Thanks to all for your replays...
we finally implemented disp+work patches in our production system but new dump generated in our only production system.
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Date and Time 08.11.2010 06:52:00
-
-
Short text |
The ABAP/4 Open SQL array insert results in duplicate database records. |
-
-
What happened? |
Error in the ABAP Application Program |
The current ABAP program "RSORACOL" had to be terminated because it has |
come across a statement that unfortunately cannot be executed. |
-
-
What can you do? |
Note down which actions and inputs caused the error. |
To process the problem further, contact you SAP system |
administrator. |
Using Transaction ST22 for ABAP Dump Analysis, you can look |
at and manage termination messages, and you can also |
keep them for a long time. |
-
-
Error analysis |
An exception occurred that is explained in detail below. |
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught |
in |
procedure "LOG_AND_STATISTICS" "(FORM)", nor was it propagated by a RAISING |
clause. |
Since the caller of the procedure could not have anticipated that the |
exception would occur, the current program is terminated. |
The reason for the exception is: |
If you use an ABAP/4 Open SQL array insert to insert a record in |
the database and that record already exists with the same key, |
this results in a termination. |
(With an ABAP/4 Open SQL single record insert in the same error |
situation, processing does not terminate, but SY-SUBRC is set to 4.) |
-
-
-
Information on where terminated |
Termination occurred in the ABAP program "RSORACOL" - in "LOG_AND_STATISTICS". |
The main program was "RSORACOL ". |
In the source code you have the termination point in line 499 |
of the (Include) program "RSORACOL". |
The program "RSORACOL" was started as a background job. |
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR" |
Job Initiator.. "BASIS" |
Job Number..... 05515505 |
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in |
procedure "LOG_AND_STATISTICS" "(FORM)", but it was neither handled locally nor |
declared |
in the RAISING clause of its signature. |
The procedure is in program "RSORACOL "; its source code begins in line |
490 of the (Include program "RSORACOL ". |
-
-
Source Code Extract |
-
Line | SourceCde |
-
469 | collupload |
470 | collrcode. |
471 | |
472 | IF collrcode > 9. |
473 | PERFORM inactive_module USING con_name smon_id. |
474 | ELSEIF collduration > max_runtime. |
475 | collrcode = 32. |
476 | PERFORM inactive_module USING con_name smon_id. |
477 | ELSEIF collupload > max_upload. |
478 | collrcode = 31. |
479 | PERFORM inactive_module USING con_name smon_id. |
480 | ENDIF. |
481 | ENDFORM. "check_module_behaviour |
482 | |
483 | &---- |
484 | *& Form log_and_statistics |
485 | &---- |
486 |
|
487 | ---- |
488 |
|
489 | ---- |
490 | FORM log_and_statistics USING con_name. |
491 | |
492 |
|
493 | DATA: last_date type d. |
494 | last_date = curr_date - wa_conn_info-log_life. |
495 | DELETE FROM DB02_COLL_LOG |
496 | WHERE con_name = con_name AND coll_date < last_date. |
497 | |
498 |
|
>>>>> | INSERT DB02_COLL_LOG FROM TABLE tab_coll_log. |
500 | |
501 |
|
502 | UPDATE DB02_COLL_PLAN FROM TABLE tab_coll_plan. |
503 | |
504 |
|
505 | UPDATE ORA_MON_DBCON FROM TABLE tab_conn_info. |
506 | |
507 |
|
508 | REFRESH: tab_coll_plan, tab_coll_log. |
509 | |
510 | ENDFORM. "log_and_statistics |
511 | |
512 | &---- |
513 | *& Form db_connect |
514 | &---- |
515 |
|
516 | ---- |
517 |
|
518 | ---- |
-
-
Contents of system fields |
-
Hi,
As far i know This issue will not come due to kernel , this will ahppen if have any number range issue from functional end.
May be checking with them for particular transaction will help you out.
Just noted , its for Standard job, delete job once and reschdule .
Regards,
Edited by: Gagan Deep Kaushal on Nov 8, 2010 10:21 PM
Edited by: Gagan Deep Kaushal on Nov 8, 2010 10:23 PM
You should be able to apply disp+work without any issues.
Go to ST22 and analyze the dump, I hope you get your solution in dump.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.