Solution Manager 7.1 SP04 - Job SAP_COLLECTOR_FOR_PERFMONITOR

Dear Experts
I got an issue with some differences between what SolMan Setup did and SAP Note 966309 for TCOLL in SAP_BASIS 700 - 702 sais.
SolMan Setup creates the job SAP_COLLECTOR_FOR_PERFMONITOR with the following step in working client 001:
1 RSCOLL00 ABAP SOLMAN_BTC EN
According to SAP Note 966309, this job is supposed to run as user DDIC (or any other with same rights) in client 000. On top, there are a lot of differences between SAP Note 966309 and the content of TCOLL.
Would you change TCOLL according to this SAP Note or would you hang on what SolMan Setup did?
Thanks for short answer.
Regards, Michael

Michael,
This note is clear regarding the client and user:Note 16083 - Standard jobs, reorganization jobs
and this note is release independent.
If you check using RTCCTOOL you'll be able to see a recommendation regarding TCOLL:
7. [Note 12103 ]    Collectors and TCOLL
Description     Planning table TCOLL for SAP workload collectors for 700 (note 966309 )
Implementation Press the lights icon to get the detailed check log.
                Add missing entries to table TCOLL using ST03N > Expert Mode > Collector
                and Performance DB > Performance Monitor Collector > Execution Times.
                Schedule RSCOLL00 as an hourly batch job if not scheduled.
"schedule standard jobs" steps is required if the jobs are not scheduled already:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Basic+Configuration
"In the activities schedule Background jobs and standard jobs different jobs are scheduled. The Background job that are scheduled are jobs for the housekeeping of SAP Solution Manager. The standard jobs are the same jobs as the jobs scheduled in transaction SM36 --> u201EStandard Jobs" and schedules jobs for general SAP housekeeping. Please make sure that the jobs are not already scheduled in SM36 before executing this activity. "
Cheers,
Diego.

Similar Messages

Job Scheduling in Solution Manager - Error creating Periodic Job

Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Hello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul

Solution Manager - Error when executing Job SM:EXEC SERVICES

Hi,
I am trying to get the data from the earlywatch alert report and when i start the job SM:EXEC SERVICES.
The jobs starts but i get an error during is execucion:
Runtime errors         SYNTAX_ERROR
       Occurred on     17.01.2008 at   14:06:28
Syntax error in program "RDSVASAEW_DBMSS____________052 ".
What happened?
The following syntax error occurred in the program
RDSVASAEW_DBMSS____________052 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000208" not found."
Error in ABAP application program.
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because one of
the
statements could not be executed.
This is probably due to an error in the ABAP program.
I tried to generate all the function modules and i get this error:
Logical function: MSQ_TEMPDB_DOWNLOAD            :
Error      1 during generation of /1CAGTF/IF_LOGFUNC_000208
Syntax error.
Can you help me on this error?
Best regards,
Nuno Silva

Hi Pedro,
I insert my answer from a similar thread.
As a pitty, that's a well known error.
Please check [SAP Note 727998|http://service.sap.com/sap/support/notes/727998]
Basically, these three steps needs to be performed:
1) BDL_DELETE_ALL_TABLES
2) SDCCN - Refresh Service Definitions
3) Generate Logfuncs
SE37: /BDL/_GENERATE_LOGFUNCINCLUDES
OPTION: ALL
It's also described in the Implementation Guide (IMG), transaction SPRO in the SAP Solution Manager system:
SAP Solution Manager -> Configuration -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> Service Data Control Center
-> Activate the Service Data Control Center in the Solution Manager
-> Generate Includes for Service Data Contol Center
With the next ST-PI Support Package. The steps can be triggered via the menu of transaction SDCCN.
Best regards,
Ruediger Stoecker

Solution manager 7.1 SP04 dump

Dear Experts,
I am getting follwing abap dump after configuring managed system in Solution manager.
I have already implemented SAP central note for Solman 7.1 SPS 04. Please suggest me how to resolve this issue as i am getting morethan 5000 dumps a day.
Regards,
Cinu

Hi Sinu,
Refer below note also,
1680556 - E2E Root Cause Analysis causes "CREATE_DATA_UNKNOWN_TYPE
Regards
K.N

Multiple Duplicate Jobs in Solution Manager.

Greetings,
We see duplicates of Job CCMS_CPH_AGGR_DATA_UPDATE and CCMS_CPH_RAW_DATA_UPDATE in our Solution Manager.
I understand these jobs are used to transfer data from the CCMS monitoring infrastructure to the associated BI of the SAP Solution Manager. The data is written directly to a number DSOs. Job CCMS_CPH_AGGR_DATA_UPDATE should be scheduled once every day and Job CCMS_CPH_RAW_DATA_UPDATE should be executed every hour.
However, we see huge number or duplicate jobs. I wanted to know if it’s alright to delete the duplicates?
Thank you,
Haseeb Ahmed.

Hi Roland, Thanks for your reply. These jobs are completing successfully and No errors have been recorded. In our Solution Manager System, we see Job CCMS_CPH_RAW_DATA_UPDATE and CCMS_CPH_AGGR_DATA_UPDATE has been created multiple times by user SM_EXTERN_WS. There are like hundreds of same jobs created. Since these are weekly and daily jobs, it does not make sense to keep them all. I wanted to know if its okay to clean-up the duplicates or not? I don't understand why duplicate jobs were created and is there a specific case when once of them will be active? Thanks, Haseeb Ahmed.

Configuration Guide Job Scheduling Management with SAP Solution Manager

Dear Gurus
Could you please help me with the configuration guide of the Job Scheduling Management with SAP Solution Manager
Best Regards

Hello Luis,
the configuration activities can be accessed via the "Implementatiopn Guide" by calling transaction SPRO in your SAP Solution Manager system.
In SPRO navigate to -> SAP Solution Manager -> Scenario-Specific Settings -> Job Scheduling Management -> Standard Configuration and execute the following two activities.
1. Activate Solution Manager Services
2. Set Up Work Center for Job Scheduling Management
Make sure that your user has role SAP_SM_SCHEDULER_EXE (or_ADMIN) assigned.
Afterwards you should be able to access the Job Management Work Center and to create Job Documentation or to import Jobs from a Managed System into new Job Documentations.
The following SAP notes might be usefuly as well:
1054005 - FAQ on Job Scheduling Management
1117355 - Work Center roles
Kind regards,
Martin
http://service.sap.com/jsm

Master Data synchronisation between two Solution Manager systems

Hi all,
does anyone know if it is possible to synchronise master data (smsy, ibase and such) between two Solution Manager systems with standard jobs?
Thanks!
Regards

I asked a likewise question on the OSS earlier and I was told
"Use MDM" (which is a separate product and must be licensed separately).
Markus

Documentation for Solution Manager 4

Hi all!
Iam going crasy..
At the moment I am just customizing the solution manager 4. In the reference guide section create background jobs they refer to the configuration guide of the solution manager 4. 0 to get a complete list of background jobs for the solution manager 4.0.
Ive downloaded the configuration guide for solution manager 4.0 but there is no information about this. I know the place of documentation on the sap market \solutionmanager.
Did anybody know something more?
Thank you for help!
Best regards
Thomas

Hello Thomas,
Please in spro go to Basic Settings->SAP Solution Manager System->Schedule Background Jobs
The information of this point is more than enough to configure these jobs.
In a previous Configuration Guide you can see:
Periodic Jobs
Periodic Job scenario
REFRESH MESSAGE STATUS used to collect responses from SAP for messages
and Issues sent from the SAP Solution Manager
SOLMAN_ISSUE_STATUS_REFRESH Service Desk
SM:SCHEDULER Solution Monitoring
BTC_CMS_COLLECTOR Change Manager
LANDSCAPE_FETCH Implementation and distribution
CRM_ISSUE_REFRESH Implementation and distribution (testing)
Best regards,
Dolores

Background job failing - ECC 6.0, Solution Manager 7.0

Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700)      146
SAP_BASIS           0014
SAP_ABA           0014
PI_BASIS(2005_1_700)      0014
ST-PI                0005
SAP_BW                0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date       Time     Message text                                                           Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started                                                                 00           516          S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER)              00           550          S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings                                       DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV                       on server gcbeccd     DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3                                  DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:finished                                                        DB6PM         000          S
15.05.2008 06:25:18 Database system not supported                                               S1           101          S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR                                      00           671          A
15.05.2008 06:25:36 Job cancelled                                                               00           518          A
SAP_REORG_UPDATERECORDS
=======================
Date       Time     Message text                                                          Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started                                                                00           516          S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER)      00           550          S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch                         15           100          A
14.05.2008 00:31:02 Job cancelled                                                              00           518          A
SAP_WP_CACHE_RELOAD_FULL
========================
Date       Time     Message text                                                                                Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started                                                                                00           516          S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER)      00           550          S
15.05.2008 00:30:11 No component system chosen                                                                   URL_GEN_MSGS      031          E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE                                                00           564          A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip Ghosh

Hi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Date and Time          15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
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.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO   monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*&      Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM.                               " FILL_DBVSE
57
58
59
*&      Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM.                               " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         RSORAVSH                            RSORAVSH                               48
FILL_DBVSE
1 EVENT        RSORAVSH                            RSORAVSH                               25
START-OF-SELECTION
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No.       1 Ty.          EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000                                                                ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program RSORAVSH
SYST                                     09.09.2004 14:18:12   00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI                                       . .       : :     00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip

SM:SELFDIAGNOSIS background job getting failed in Solution manager

Hi All,
SM:SELFDIAGNOSIS background job getting failed in Solution manger server :
Job Log:
2-22-2012 16:44:02 Job started                                                                                00           516          S
2-22-2012 16:44:02 Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000000324, user ID BASISUSER)      00           550          S
2-22-2012 16:45:07 Internal session terminated with a runtime error (see ST22)                                     00           671          A
2-22-2012 16:45:07 Job cancelled                                                                                00           518          A
ST22: Dump:
Runtime Errors         ITAB_DUPLICATE_KEY
Date and Time          02-22-2012 16:45:07
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" 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 entry was to be entered into the table
"\CLASS=CL_DSWP_SD_DIAGNOSE_CONSISTENT\METHOD=CHECK_USERS_BP\DATA=LT_USCP"
(which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ITAB_DUPLICATE_KEY" " "
"CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" or "CL_DSWP_SD_DIAGNOSE_CONSISTENTCM00M"
"CHECK_USERS_BP"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
KIndly Suggest to resolve the above issue
Thanks
Nekkalapu

HI,
Deatils:
SAP EHP 1 for SAP Solution Manager 7.0
SAP_ABA                701          0006    SAPKA70106
SAP_BASIS              701          0006    SAPKB70106
PI_BASIS               701          0006    SAPK-70106INPIBASI
ST-PI                  2008_1_700   0002    SAPKITLRD2
CRMUIF                 500          0004    SAPK-50004INCRMUIF
SAP_BW                 701          0006    SAPKW70106
SAP_AP                 700          0019    SAPKNA7019
BBPCRM                 500          0016    SAPKU50016
BI_CONT                704          0007    SAPK-70407INBICONT
CPRXRPM                400          0016    SAPK-40016INCPRXRP
ST                     400          0024    SAPKITL434
ST-A/PI                01M_CRM570   0000         -
ST-ICO                 150_700      0009    SAPK-15079INSTPL
ST-SER                 701_2010_1   0002    SAPKITLOS2
Thanks
Nekkalapu

HOw to schedule ''landscape fetch' job in Solution Manager???

HI,
Can any one please help me in scheduling LAndscape fetch job in solution Manager?
rEgards,
fAisal

Hi Venkatesh,
Thanks for your reply.
I checked by executing SLDCHECK. It opened the SLD page successfully. However, before that in the ABAP screen, it gave me error saying that:
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Summary: Connection to SLD does not work
=> Check SLD function and configurations
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
The RFC LCRSAPRFC was of type 3 ABAP. It asked me to change it to T (TCP/IP). I did so.
However, now I get this below error:
Properties of RFC destination LCRSAPRFC
RFC host:
program id:
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Timeout dur
I even tested this RFC in SM59. It gave the same error.
CAn you please help me?
REgards,
Faisal

Background job canceled in Solution Manager system

Dear all expert ,
Two background jobs canceled in solution manager system before some time.
details-
Background jobs :
                    1 - LANDSCAPE FETCH
    Program name : RSGET_SMSY
Job log : Job started
Step 001 started (program RSGET_SMSY, variant ,
The SLD server connection is inactive
Job cancelled after system exception ERROR_MESSAGE
                   2 - SEND_SYSTEM_RELATIONSHIP_TO_SUP
    Program name : AI_SC_SEND_SYSTEM_RELATIONSHIP
Job log :
                   Job started
Step 001 started (program AI_SC_SEND_SYSTEM_RELATIONSHIP, variant ,
SOL determined as monitoring Solution Manager system
SAP customer number unknown for installation number 0020606335
Job cancelled after system exception ERROR_MESSAGE
please help me , what should i do ?
I am waiting for your positive response.
Regards
Shubh

hi,
You can try following ....
For the job SEND_SYSTEM_RELATIONSHIP_TO_SUP
Program : AI_SC_SEND_SYSTEM_RELATIONSHIP
1. Up to Support Package 09:
a) Start transaction SMSY.
b) Choose Shft+F5.
c) Select the system named in the message.
d) Choose F6.
e) Select the "System Data in SAP Support Portal" tab.
f) Using the input help, fill the system number field with the correct system.
g) Save the data.
2. Up to and including Support Package 08:
a) Start transaction SOLMAN_CONNECT.
b) Select the system in question in the ID field and choose the filter pushbutton.
c) Select the system and select "Create configuration".
d) Fill the system number field using the input help with the correct system.
e) For example, select the "BW GUI Connection" service type.
f) Carry out all of the subsequent steps of the Configuration Assistant until you see the "Finish" pushbutton.
This establishes a unique relationship between your system in the Solution Manager and the system number in the SAP Support Portal. Problems no longer occur with this system when the SEND_SYSTEM_RELATIONSHIP_TO_SUPP job is next run. However, the problem may still exist for other systems (in these cases, you should follow the same steps).
Hope this will help to solve your issue..
Regards
Bhuban
RKFL

Unified Job Monitoring -Share your experiences with SAP Solution Manager 7.1

Dear Forum members,
I woudl like to introduce myself as Raghav, S. I am in the development team responsible for building the unified job monitoring workcenter starting 7.1 SP10 (onwards).
Please post your feedback, current status wrt to setup, commmon issues in this area.
I will be more than glad to help you here.
Regards, Raghav
Development Manager
CLM - Solution manager team, Labs India.

Hello Raghev,
we implemented unfied job monitoring on a larger scale by now, starting out with the monitoring of SAP Standard & Reorg Jobs.
Everything seemed quiet OK at the beginning, but over time display performance of the Monitoring UI decreased drastically (exceeding 5 Min. "per click" in the UI).
I pinned this down to the following (Oracle) SQL access:
SELECT
"CLIENT", "CONTEXT_ID", "TYPE_ID", "HASH_METRIC_PATH", "START_TIMESTAMP", "IS_CURRENT", "END_TIMESTAMP",
"METRIC_PATH", "RATING_AGGREGATE", "VALUE_MIN", "VALUE_MAX", "VALUE_SUM", "VALUE_COUNT", "VALUE_LAST",
"VALUE_DATA_TYPE", "VALUE_MAX_TIME", "LAST_TEXT"
FROM
"MES_DB_AGGREGATE"
WHERE
"CLIENT"=:A0 AND "CONTEXT_ID"=:A1 AND "TYPE_ID"=:A2 AND "IS_CURRENT"=:A3 OR "CLIENT"=:A4 AND
"CONTEXT_ID"=:A5 AND "TYPE_ID"=:A6 AND "IS_CURRENT"=:A7 OR "CLIENT"=:A8 AND "CONTEXT_ID"=:A9 AND
"TYPE_ID"=:A10 AND "IS_CURRENT"=:A11 OR "CLIENT"=:A12 AND "CONTEXT_ID"=:A13 AND "TYPE_ID"=:A14 AND
"IS_CURRENT"=:A15 OR "CLIENT"=:A16 AND "CONTEXT_ID"=:A17 AND "TYPE_ID"=:A18 AND "IS_CURRENT"=:A19
The execution plan used for this SQL is:
0
SELECT STATEMENT
1
INLIST ITERATOR
2
TABLE ACCESS BY INDEX ROWID MES_DB_AGGREGATE
3
INDEX RANGE SCAN MES_DB_AGGREGATECU
MES_DB_AGGREGATE in our case has over 5 million entries.
The parameterization of the DB incl. Memory and all should be OK.
The index range scan simply takes that long.
This might be, because the MES_DB_AGGREGATECU index has the lowest cardinality column (CLIENT) first.
Header 1
Header 2
COLUMN_NAME
NUM_DISTINCT
CLIENT
1
CONTEXT_ID
433
TYPE_ID
2192
IS_CURRENT
2
Could you have your team check on this, because with the situation as is, the Job Monitoring application seemingly becomes non-usable, as soon, as you start to scale up.
Best Regards,
Thorsten

BPM Monitor job in solution manager

Hi
I am trying to monitor job's with solution manager.
In the BPM (Trans' solution_manager) I config a business process and add a job to the monitor.
But there is no support massage create when the job fails.
I don't know what i did wrong.
Help
Best regards
Lior Grinberg

Hello,
The automatic creation of a notification has to be configured separately from alerting. See documentation: http://help.sap.com/saphelp_smehp1/helpdata/en/a6/a1b52fda154614ba38a17be5243b73/frameset.htm
Please also visit the Business Process Monitoring site in Service Marketplace: http://service.sap.com/bpm
I recommend to configure the Job Monitoring from within a Job Documentation. The process is described in :
a) End user documentation
http://help.sap.com/saphelp_smehp1/helpdata/en/8e/3ad6f807e147669036d2a6aed597aa/frameset.htm
b) Tutorial on Service Marketplace
http://service.sap.com/~sapidb/011000358700001911422008E.sim
Best regards,
Martin

How to delete Job Documentation in JSM Solution Manager

Hi,
I am trying to define some job documentation in "JSM Solution Manager", how can I delete unwanted Job Documantation there.
Don't see any remove button.
Thanks for help
sahmad

Hello,
We too are facing same issue. Can you please share your solution.
Regards,
Mudasir.

Solution Manager 7.1 SP04 - Job SAP_COLLECTOR_FOR_PERFMONITOR

Similar Messages

Maybe you are looking for