Job SAP_COLLECTOR_FOR_PERFMONITOR getting delay.

Hi Friends,
In one of my customer system, the job SAP_COLLECTOR_FOR_PERFMONITOR is getting delay on particular time.
Normally every hour it is getting finished with 5 to 40 secs.
But at a particular the job starts at i.e. 02:26am is finishing successfully but taking much time. It's nearly taking 37,000 secs.
Job log:
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Job finished
My system details are:
Comp version :BBPCRM 4.0
Database system: ORACLE , 10.2.0.4.0.
Kernel release : 640
SAP_BASIS:SAPKB62063
I can submit if any information required. Earlier solution is much aspirated.
Regards
Sudhakar

Sorry Guys I was not well to answer your replies.
Thanks for your replies.
Still the issues persists. Here are some more information which would help you to help me.
I have checked BTC are available.
In SM51 one BTC is running for long time for this with a entry of u201CSAPLSTUW   000 DDICu201D
& Daily BTC process is Disconnecting from oracle at 2 Ou2019clk then this job is taking that BTC. Is there any relation between this?
Wed Oct 6 01:50:01 2010
got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
Client NLS settings:
Logon as OPS$-user to get SAPCRM's password
Connecting as /@SID on connection 1 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
   0 UTF8                                                      1 0x114876050 0x114888db0 0x114888668
Starting user session (con_hdl=1,svchp=0x1160b89c8,srvhp=0x11488bd68,usrhp=0x1160b85b0)
Now '/@SID' is connected: con_hdl=1, nls_hdl=0, session_id=687.
Got SAPCRM's password from OPS$-user
Disconnecting from connection 1 ...
Close user session (con_hdl=1,svchp=0x1160b89c8,usrhp=0x1160b85b0)
Now I'm disconnected from ORACLE
Connecting as SAPCRM/<pwd>@SID on connection 1 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
   0 UTF8                                                      1 0x114876050 0x114888db0 0x114888668
Starting user session (con_hdl=1,svchp=0x1160b89c8,srvhp=0x11488bd68,usrhp=0x1160b85b0)
Now 'SAPCRM/<pwd>@SID' is connected: con_hdl=1, nls_hdl=0, session_id=687.
Connection 1 opened (DBSL handle 1)
Wp Hdl ConName          ConId     ConState     TX PRM RCT TIM MAX OPT Date     Time   DBHost
134 000 R/3              000000000 ACTIVE       NO YES NO 000 255 255 20100930 152615 host05
134 001 R/3*WORKFLOWTRAC 134000057 ACTIVE       NO NO NO 004 255 255 20101006 015001 host05
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
Wed Oct 6 02:08:47 2010
Disconnecting from connection 1 ...
Close user session (con_hdl=1,svchp=0x1160b89c8,usrhp=0x1160b85b0)
Now I'm disconnected from ORACLE
Disconnected from connection con_da={R/3*WORKFLOWTRACE,134000057,1}
Job is taking much time to finish at 02:26 with a lock entry in MONI table. In ST03n sometimes 3:26 job is showing error but it is not failing.
Error log:
System name                            Host name                        Report   Date       End time
Error message
Host05_SID_00                       Host05                        RSCUECRM 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSHOSTDB 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSORACOL 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSORAHCL 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSRFCDLT 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSRFCDMN 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSSTAT60 06.10.2010 03:26:06
Table MONI is locked by user DDIC
Host05_SID_00                       Host05                        RSSTAT87 06.10.2010 03:26:06
Host05a_SID_01                      Host05a                       RSHOSTDB 06.10.2010 03:26:07
Host05a_SID_01                      Host05a                       RSRFCDMN 06.10.2010 03:26:07
Host05_SID_00                       Host05                        RSSTAT83 06.10.2010 03:26:11
Begin error recovery:
Host05_SID_00                       Host05                        RSSTAT60 06.10.2010 03:27:16
Table MONI is locked by user DDIC
Contents of TCOLL
Report      Days of Week                                   Hours of Day                                Repe-    System
                                                                                titions
         Mo    We    Fr    Su 0     2     4     6     8    10    12    14    16    18    20    22
RSCUECRM X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSDBPREV X X X X X X X X     X     X     X     X     X X X     X     X     X     X     X        1         C
RSDB_PAR X X X X X X X                          X              X                 X                 1         C
RSDB_TDB X X X X X X X                       X                                      X              1         C
RSDB_WDB                    X                                      X                                      1         C
RSHOSTDB X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         *
RSHOSTDC X X X X X X X X     X     X     X     X     X     X     X     X     X     X     X        1         C
RSHOSTPH X X X X X X X                             X        X                    X                 1         *
RSORA811 X X X X X X X                                      X                    X                 1         C
RSORACOL X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSORAHCL X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSRFCDLT X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSRFCDMN X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         *
RSSDBDLY X X X X X X X     X                                                                       1         C
RSSTAT60 X X X X X X X           X        X        X     X        X     X        X        X        1         C
RSSTAT83 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSSTAT87 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSSTAT90 X X X X X X X                                         X                 X                 1         *
RSSTAT98 X X X X X X X              X        X        X        X        X        X                 1         *
RSSTATPH X X X X X X X                             X        X                 X                    1         *
RSTUNE80 X X X X X X X                             X              X                          X     1         *
RSXRPM          X                             X                                                           1         C

Similar Messages

SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND

Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.

Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text                                                                                        |
|    Program "RSORA811" not found.                                                                 |
|What happened?                                                                                    |
|    There are several possibilities:                                                              |
|                                                                                                  |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|    or                                                                                            |
|    Error in the SAP kernel.                                                                      |
|                                                                                                  |
|    The current ABAP "RSCOLL00" program had to be terminated because the                          |
|    ABAP processor detected an internal system error.                                             |
|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                                                                                    |
|    On account of a branch in the program                                                         |
|    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                              |
|    or a transaction call, another ABAP/4 program                                                 |
|    is to be loaded, namely "RSORA811".                                                           |
|                                                                                                  |
|    However, program "RSORA811" does not exist in the library.                                    |
|                                                                                                  |
|    Possible reasons:                                                                             |
|    a) Wrong program name specified in an external PERFORM or                                     |
|       SUBMIT or, when defining a new transaction, a new                                          |
|       dialog module or a new function module.                                                    |
|    b) Transport error                                                                            |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
|     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
|    The main program was "RSCOLL00 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 535                                 |
|    of the (Include) program "RSCOLL00".                                                          |
|    The program "RSCOLL00" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. " bharath"                                                                       |
|    Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.

Jobs are getting delayed.

Hi All,
We are monitoring many jobs daily. But now some of the jobs are getting delayed (2 to 3days). We have deleted that job and rescheduled to solve that issue. But we are unable to find the reason why it was happening suddenly.
Any suggestions will be awarded.
Thanks,
Praveen.

hi
jus have a look at this function BP_JOBLOG_READ
hope it helps
regards'
Aakash Banga

Hot backup getting delayed everyday

Hi All,
Everyday our hot backup job is getting delayed by a significant time. Before the tablespaces are placed into begin backup mode we spotted the alert log flooded with the below message ,
Mon May 21 00:23:46 2012
Incremental checkpoint up to RBA [0x396b.3365.0], current log tail at RBA [0x396
b.3386.0]
Mon May 21 00:54:03 2012
Incremental checkpoint up to RBA [0x396b.3b81.0], current log tail at RBA [0x396
b.3b98.0]
Mon May 21 01:24:21 2012
Incremental checkpoint up to RBA [0x396b.495a.0], current log tail at RBA [0x396
b.497a.0]
Mon May 21 01:54:47 2012
Incremental checkpoint up to RBA [0x396b.5109.0], current log tail at RBA [0x396
b.5137.0]
Mon May 21 02:25:13 2012
Incremental checkpoint up to RBA [0x396b.6771.0], current log tail at RBA [0x396
b.67b6.0]
Also after the tablespaces are placed into begin backup mode before the end backup occurs the altert log is also flooded with the below messages,
Incremental checkpoint up to RBA [0x396b.24107.0], current log tail at RBA [0x39
6b.24afe.0]
Mon May 21 05:58:39 2012
Incremental checkpoint up to RBA [0x396b.2569e.0], current log tail at RBA [0x39
6b.257f2.0]
Mon May 21 06:28:56 2012
Incremental checkpoint up to RBA [0x396b.2815a.0], current log tail at RBA [0x39
6b.28925.0]
Mon May 21 06:59:14 2012
Incremental checkpoint up to .
Then the tablespaces are placed into end backup mode resulting in significant delay.
Please help how we can reduce the backup time and also please throw some light on these checkpoint related messages.

Hi Jonathon ,
Thanks for your valuable suggestion.
Here in our environment all the tablespaces go into hot backup mode at a time instead of one by one through a script.
Previously when the hot backup used to work fine the number of incremental checkpoints between begin backup and end backup were significantly less. It is also evident from the excerpt of the alert log file.
alter tablespace PROAIMIS01 begin backup
Completed: alter tablespace PROAIMIS01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace SYSTEM begin backup
Completed: alter tablespace SYSTEM begin backup
Mon Apr 19 01:02:47 2010
alter tablespace MAPDS01 begin backup
Completed: alter tablespace MAPDS01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace ADMN01 begin backup
Completed: alter tablespace ADMN01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace PACESIS01 begin backup
Completed: alter tablespace PACESIS01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace CTPDS01 begin backup
Completed: alter tablespace CTPDS01 begin backup
Mon Apr 19 01:07:47 2010
***Completed checkpoint up to RBA [0x1ced.2.10], SCN: 10912956469916***
***Mon Apr 19 01:14:13 2010***
***Incremental checkpoint up to RBA [0x1ced.fd.0], current log tail at RBA [0x1ced.***
***10a.0]***
***Mon Apr 19 01:44:32 2010***
***Incremental checkpoint up to RBA [0x1ced.73f.0], current log tail at RBA [0x1ced***
***.89e.0]***Mon Apr 19 01:51:58 2010*alter tablespace CTPIS01 end backup*Mon Apr 19 01:51:58 2010
Completed: alter tablespace CTPIS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace MAPDS01 end backup
Completed: alter tablespace MAPDS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace SYSAUX end backup
Completed: alter tablespace SYSAUX end backup
Mon Apr 19 01:51:58 2010
alter tablespace AUDT01 end backup
Completed: alter tablespace AUDT01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMIS01 end backup
Completed: alter tablespace PROAIMIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace MAPIS01 end backup
Completed: alter tablespace MAPIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace UNDO01 end backup
Completed: alter tablespace UNDO01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace USER01 end backup
Completed: alter tablespace USER01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMDS01 end backup
Completed: alter tablespace PROAIMDS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PACESIS01 end backup
Completed: alter tablespace PACESIS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace XDB01 end backup
Completed: alter tablespace XDB01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace ADMN01 end backup
Completed: alter tablespace ADMN01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYMANTEC_I3_ORCL end backup
Completed: alter tablespace SYMANTEC_I3_ORCL end backup
Mon Apr 19 01:52:00 2010
alter tablespace CTPDM01 end backup
Completed: alter tablespace CTPDM01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace PACESDS01 end backup
Completed: alter tablespace PACESDS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYSTEM end backup
Completed: alter tablespace SYSTEM end backup
Mon Apr 19 01:52:01 2010
alter tablespace CTPDS01 end backup
Completed: alter tablespace CTPDS01 end backup
Mon Apr 19 01:52:01 2010
alter tablespace PERF01 end backup
Completed: alter tablespace PERF01 end backup
Mon Apr 19 01:52:01 2010
alter database backup controlfile to trace
Completed: alter database backup controlfile to trace
Mon Apr 19 01:52:01 2010
alter database backup controlfile to '$CTLBKPDIR/$ORACLE_SID-$dt-$tm.ctl'
Completed: alter database backup controlfile to '$CTLBKPDIR/$ORACLE_SID-$dt-$tm.
ctl'
Mon Apr 19 01:52:03 2010
Beginning log switch checkpoint up to RBA [0x1cee.2.10], SCN: 10912957698129
Thread 1 advanced to log sequence 7406
Completed: alter tablespace PACESDS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYSTEM end backup
Completed: alter tablespace SYSTEM end backup
Mon Apr 19 01:52:01 2010
alter tablespace CTPDS01 end backup
Completed: alter tablespace CTPDS01 end backup
Mon Apr 19 01:52:01 2010
alter tablespace PERF01 end backup
Completed: alter tablespace PERF01 end backup
Mon Apr 19 01:52:01 2010
alter database backup controlfile to trace
Completed: alter database backup controlfile to trace
alter tablespace ADMN01 end backup
Completed: alter tablespace ADMN01 end backup
Completed: alter tablespace CTPDS01 begin backup
Mon Apr 19 01:07:47 2010
Completed checkpoint up to RBA [0x1ced.2.10], SCN: 10912956469916
Mon Apr 19 01:14:13 2010
Incremental checkpoint up to RBA [0x1ced.fd.0], current log tail at RBA [0x1ced.
10a.0]
Mon Apr 19 01:44:32 2010
Incremental checkpoint up to RBA [0x1ced.73f.0], current log tail at RBA [0x1ced
.89e.0]
Mon Apr 19 01:51:58 2010
alter tablespace CTPIS01 end backup
Mon Apr 19 01:51:58 2010
Completed: alter tablespace CTPIS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace MAPDS01 end backup
Completed: alter tablespace MAPDS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace SYSAUX end backup
Completed: alter tablespace SYSAUX end backup
Mon Apr 19 01:51:58 2010
alter tablespace AUDT01 end backup
Completed: alter tablespace AUDT01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMIS01 end backup
Completed: alter tablespace PROAIMIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace MAPIS01 end backup
Completed: alter tablespace MAPIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace UNDO01 end backup
Completed: alter tablespace UNDO01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace USER01 end backup
Completed: alter tablespace USER01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMDS01 end backup
Completed: alter tablespace PROAIMDS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PACESIS01 end backup
Completed: alter tablespace PACESIS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace XDB01 end backup
Completed: alter tablespace XDB01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace ADMN01 end backup
Completed: alter tablespace ADMN01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYMANTEC_I3_ORCL end backup
Completed: alter tablespace SYMANTEC_I3_ORCL end backup
Mon Apr 19 01:52:00 2010
alter tablespace CTPDM01 end backup
Completed: alter tablespace CTPDM01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace PACESDS01 end backup
Completed: alter tablespace PACESDS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYSTEM end backup
Completed: alter tablespace SYSTEM end backup
Mon Apr 19 01:52:01 2010
alter tablespace CTPDS01 end backup
Completed: alter tablespace CTPDS01 end backup
Mon Apr 19 01:52:01 2010
alter tablespace PERF01 end backup
Completed: alter tablespace PERF01 end backup
But for the last couple of days the number of incremental checkpoints seem to be higher between begin backup and end backup like below,
Incremental checkpoint up to RBA [0x396d.3129.0], current log tail at RBA [0x396
d.366c.0]
Tue May 22 03:14:23 2012
Incremental checkpoint up to RBA [0x396d.147a8.0], current log tail at RBA [0x39
6d.15ac8.0]
Tue May 22 03:44:45 2012
Incremental checkpoint up to RBA [0x396d.1c679.0], current log tail at RBA [0x39
6d.1d177.0]
Tue May 22 04:15:08 2012
Incremental checkpoint up to RBA [0x396d.20387.0], current log tail at RBA [0x39
6d.205dd.0]
Tue May 22 04:45:30 2012
Incremental checkpoint up to RBA [0x396d.20dcf.0], current log tail at RBA [0x39
6d.2109e.0]
Tue May 22 05:15:48 2012
Incremental checkpoint up to RBA [0x396d.23af5.0], current log tail at RBA [0x39
6d.23d6a.0]
Tue May 22 05:46:05 2012
Incremental checkpoint up to RBA [0x396d.245e3.0], current log tail at RBA [0x39
6d.245ef.0]
Tue May 22 05:47:08 2012
Also the parameter log_checkpoint_interval is set to zero here.
log_checkpoint_interval integer 0
And the parameter fast_start_mttr_target is set to 300
fast_start_mttr_target integer 300
Please suggest ..

SAP Standard Jobs are getting canceled

Hi Basis Gurus,
In our Quality BW 3.5 system the SAP Standard jobs are getting canceled.
The jobs are as follows
SAP_APPLICATION_STAT_COLLECTOR
SAP_CCMS_CPH_HRCOLL
SAP_CCMS_MONI_BATCH_DP
SAP_COLLECTOR_FOR_JOBSTATISTIC
SAP_COLLECTOR_FOR_NONE_R3_STAT
SAP_COLLECTOR_FOR_PERFMONITOR
SAPCONNECT ALL SEND
SAP_REORG_ABAPDUMPS
SAP_REORG_SPOOL
SAP_RSICFDLT
In SM37 when i click on the job log for the above mentioned jobs the system is promting a message saying as "Error reading job log"
Please let me know how can troubleshoot it and resolve this issue.
Our is qulaity BW 3.5 system
Solaris OS
Oracle Database
Please help me.
Regards,
Anil.

Hi ,
For log display reason, try the note suggested. Jobs cancel reason may be due to that the user who schedule that job are locked or not exist on that client. Or other reason will be clear only after log display.
Ankit

SAP_COLLECTOR_FOR_PERFMONITOR getting cancelled

Dear All,
The job SAP_COLLECTOR_FOR_PERFMONITOR is getting cancelled daily at 7.00 AM. It is scheduled to run hourly. All other times it finishes succesfully. But only 1 time at 7 it gets cancelled. The job log is :-
Date       Time     Message text                                                Message class Message no. Message type
15.11.2007 07:00:17 Job started                                                      00           516          S
15.11.2007 07:00:17 Step 001 started (program RSCOLL00, variant , user ID DDIC)      00           550          S
15.11.2007 07:00:38 ABAP/4 processor: CONNE_IMPORT_WRONG_COMP_TYPE                   00           671          A
15.11.2007 07:00:38 Job cancelled                                                    00           518          A
the Dump is pasted below:-
                                                                                ShrtText
Error when attempting to IMPORT object "HIST2".
What happened?
Error in ABAP application program.
The current ABAP program "RSORAT4M" had to be terminated because one of the
    statements could not be executed.
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data
    type of the stored data was not the same as that specified in the
    program.
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
     was neither
    caught nor passed along using a RAISING clause, in the procedure
     "AKT_DAY_HIST2" "(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:
    When importing the object "HIST2", the component no. 8 in the
    dataset has a different type from the corresponding component
    of the target object in the program "RSORAT4M".
The data type is "I" in the dataset, but "P" in the program.
How to correct the error
    Try to find out why the type of the object is different.
    There are several possible reasons:
--- In the ABAP Dictionary, the type of the imported
field has changed. Make sure that the type of the imported
field matches the length of the Dictionary field.
|   If the data could not be restored from another source, this data
    |   must be read with the "old" structure, then converted and exported
    |   back with the new structure, so that future IMPORTs always work
    |   with the new structure.
    |
--- A new program version is active, and it no longer matches the
        dataset. Try to solve the error by generating the program "RSORAT4M" again
        as follows:
        In the SAP System, choose the transaction SE38. Enter the program
        name "RSORAT4M". Then choose the "Activate" function.
===
It is saying
The data type is "I" in the dataset, but "P" in the program.
But it runs 23 times correctly except 1 time.
Can Anyone help me in this please
Thanks
Tajinder

Hi,
Can u please suggest me what will be the monikey here. below is the dump for that
154   DATA: FLAG VALUE ' '.
155   LOOP AT HIST2.
156     IF HIST2-DATE = DATE. DELETE HIST2. FLAG = '*'. ENDIF.
157   ENDLOOP.
158   IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.
159 ENDFORM.
160
161 FORM AKT_DAY_HIST2.                    " Aktualisiere Tage-Historie
162   PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie
>>>>   IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
164   IF SY-SUBRC <> 0.
165     REFRESH HIST2. CLEAR HIST2.
166     PERFORM LOGBUCH_INIT USING 1.
167     PERFORM TRANSFORM_ALL_HISTORIES.   " Strukturaenderung fuer Dynami
168     PERFORM PREPARE_MONIKEY USING 36.    " Lese Historie
169     IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
170   ENDIF.
171   READ TABLE HIST2 INDEX 1.
172   IF SY-SUBRC <> 0.
173     REFRESH HIST2. CLEAR HIST2.
174     PERFORM LOGBUCH_INIT USING 1.
175   ENDIF.
176   PERFORM DELETE_AKT_DAY_HIST2.        " Delete aktuellen Tag
177   LOOP AT HIST2_DAY.                   " Füge neue Analyse an
178     MOVE-CORRESPONDING HIST2_DAY TO HIST2.
179     APPEND HIST2.
180   ENDLOOP.
181   ADD 1 TO LOGBUCH-ANZDAYS.
182   MOVE DATE TO LOGBUCH-LASTDAY.
Thanks
tajinder

Incorrect time of CCMS alerts, alerts getting delayed by more than a day

Hi All,
We have SOLMAN 4.0 and configured the autoreaction method for alert on e-mail centrally on SOLMAN for a client in DEV(100). The configuration is correct and we are able to receive the CCMS alerts, however, the alerts are getting delayed by more than a day. Alerts are getting generated every 3-5 minutes and in the central autoreaction method zCCMS_OnAlert_Email_Central i have added a parameter TIME_ZONE and gave the value as PST as our servers are all on PST.
The following is an example of the alert that I received:
ALERT for DEV \ Workload Collector \ Workload Collector Frame \ Collectorframe Messages at 20070910 215114 ( Time in UTC )
System: DEV at 20070910 145114 ( Time in PST ) RED CCMS alert for monitored object Collectorframe Messages Alert Text:Determination of component from SCR failed System:DEV Segment:SAP_CCMS_e47dev_DEV_00 MTE:DEV\Workload Collector\Workload Collector Frame\Collectorframe Messages Client:000 User:DDIC
Severity: 0
I received the above alert at 15:45 after changing the "set wait time" to 15:30. However, in Tx. SOST, this alert was supposed to reach at 23:52 on 2007 09 10 which is like almost a day to receive the alert?
Is this any configuration issue? The job which was scheduled to run every 3 minutes in SCOT to send e-mails is running fine without any delay.
Please help me!!!

> Hi All,
> We have SOLMAN 4.0 and configured the autoreaction
> method for alert on e-mail centrally on SOLMAN for a
> client in DEV(100). The configuration is correct and
> we are able to receive the CCMS alerts, however, the
> alerts are getting delayed by more than a day. Alerts
> are getting generated every 3-5 minutes and in the
> central autoreaction method
> zCCMS_OnAlert_Email_Central i have added a parameter
> TIME_ZONE and gave the value as PST as our servers
> are all on PST.
>
> The following is an example of the alert that I
> received:
>
> ALERT for DEV \ Workload Collector \ Workload
> Collector Frame \ Collectorframe Messages at 20070910
> 215114 ( Time in UTC )
> System: DEV at 20070910 145114 ( Time in PST ) RED
> CCMS alert for monitored object Collectorframe
> Messages Alert Text:Determination of component from
> SCR failed System:DEV Segment:SAP_CCMS_e47dev_DEV_00
> MTE:DEV\Workload Collector\Workload Collector
> Frame\Collectorframe Messages Client:000 User:DDIC
> Severity: 0
>
> I received the above alert at 15:45 after changing
> the "set wait time" to 15:30. However, in Tx. SOST,
> this alert was supposed to reach at 23:52 on 2007 09
> 10 which is like almost a day to receive the alert?
>
> Is this any configuration issue? The job which was
> scheduled to run every 3 minutes in SCOT to send
> e-mails is running fine without any delay.
>
> Please help me!!!
Any ideas on the above issue?

Rollup Getting Delayed

Hi All,
I am doing the Rollup for ZIC_C03 cube manually,the problem is after execute the Rollup it is getting delayed to complete. I have started one job on 02/01/06 that particular job is still in active mode in SM37 and while trying to cancel the job it's not getting canceled.
I have found some errors in Details tab for the particular load at monitor level the error says that <b>System error: CONDENSE_AGGREGATES RSCDS_CONDENSE_CUBE</b>
Any suggestions let me know
Thanks in Advance

Hi Kris,
Refer OSS Note - 642819 and 834829.
Bye
Dinesh

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.

Job is getting cancelled in CPS

Hi,
We have implemented CPS on SOLMAN, and when we were submitting a job for one of the SAP system and we are using Job chain method for submiting the job.
Job is getting cancelled with the below error,please find the below error and log.
Failed to create the job in the SAP system
BAPI exception while calling BAPI_XBP_JOB_ADD_ABAP_STEP: E XM 034 Internal problem (function BAPI_XBP_JOB_ADD_ABAP_STEP) [BAPI_XBP_JOB_ADD_ABAP_STEP, , , ]
     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.checkBapiReturnCode(ClientConnectionImpl.java:818)
     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:605)
     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$4.doPerform(AbstractRfcConnection.java:289)
     at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:130)
     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:445)
     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.execute(AbstractRfcConnection.java:282)
     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunctionModuleWrapper.execute(SapFunctionModuleWrapper.java:194)
     at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule.execute(AbstractSapFunctionModule.java:107)
     at com.redwood.scheduler.connector.sap.rfc.command.impl.AbapRunPrintCommand.doAddSteps(AbapRunPrintCommand.java:353)
     at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpJobRunCommand.execute(AbstractXbpJobRunCommand.java:177)
     at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:123)
     at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)
     at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:107)
     at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:59)
     at java.lang.Thread.run(Thread.java:770)

This message is most of the times thrown when the parameters you specify for the job to run are inconsistent. Possibly a variant name that does not exist or is missing, maybe a printer/sap user name/application server name that does not exist in the target system.

Job is getting cancelled

Hi Friends !
We have job name RSIMPCUST scheduled by the USER ID ABC. Now this ABC ID no longer exists. Hence job is getting cancelled. In the SM37, I did tried "Repeat Schedule" but thatz also getting cancelled. How I can schedule this job on my ID? Please advise.
With Regards
Rekha

Hi Rekha,
In order to be able to use the job with your Id please make setting according to this docuement ::
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b6b739-47a6-2e10-9abf-bdac1124dde1?QuickLink=index&overridelayout=true
Regards,
Arpit

Network Print Jobs Always Get Stuck in Queue

Hello,
I have, perhaps, the most frustrating problem on the planet. In my home network, I have a HP Color LaserJet 2600n connected to my main PC, with 2 other PC's on the network. All 3 run Windows 7. Printing from my main PC works fine, but if I try to print over the network, the print job always gets stuck in the queue. I can see it stuck in the queue on my main PC, but I can't do anything about it. I can't delete it, nothing. If I restart the spooler, then it magically prints and clears the queue, but it's annoying to have to do that all the time. I've reinstalled the drivers several times to no avail. Tips?
RPGillespie

I have a similar problem, I have a directly connected 1300 and a network P3015. The 1300 is connected via USB, the 3015 is connected by RJ45 cable right to the router. Both printers have their print queues get stuck, but only from my HP Pavilion Elite HPE running HP-installed Windows 7. All the other machines in the office can use the 3015 printer perfectly well. One is an older Pavilion using XP-Pro, another is a Dell using XP-Pro and the third is a Lenovo laptop using Windows 7. All our toners are not refills (seems like a stupid suggestion that the toner cartridge could cause a queue to lock up). The problem is definitely between my machine and the HP printers. I have a Brother printer and a couple of Seiko/Epson printers that all work perfectly fine.
Rebooting several times a day is getting old.

Job its getting stuck on SIL_PurchaserOrderCostFact_Full

Hi Gurus,
I am running a DAC a job after rebuilding a new env but the Job takes an Hour in prodn env but now taking almost 2 hours in the new env. After investigation, the issue is the Job its getting stuck on SIL_PurchaserOrderCostFact_Full for almost an hour but in prod it complete in 2minutes or less. The job ends up completing in 2 hours.
I applied the following patches EBF189068, EBF191169 and patch 10052370
BI APPS 7.9.5
DAC 10.1.3.4.1
OBIEE 10.1.3.4.0
Below is the log detail for SIL_PurchaseOrderCostFact_Full
Thanks
Simmz
WRITER_1_*_1> WRT_8167 Start loading table [W_PURCH_COST_F] at: Thu May 26 16:29:03 2011
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:30:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 10008 Applied: 10008 Rejected: 0 Affected: 10008
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:31:31 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 20016 Applied: 20016 Rejected: 0 Affected: 20016
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:32:52 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 30024 Applied: 30024 Rejected: 0 Affected: 30024
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:34:20 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 40032 Applied: 40032 Rejected: 0 Affected: 40032
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:35:44 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 50040 Applied: 50040 Rejected: 0 Affected: 50040
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:37:02 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 60048 Applied: 60048 Rejected: 0 Affected: 60048
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:38:21 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 70056 Applied: 70056 Rejected: 0 Affected: 70056
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:39:49 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 80064 Applied: 80064 Rejected: 0 Affected: 80064
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:41:18 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 90072 Applied: 90072 Rejected: 0 Affected: 90072
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:42:36 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 100080 Applied: 100080 Rejected: 0 Affected: 100080
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:43:42 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 110088 Applied: 110088 Rejected: 0 Affected: 110088
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:44:56 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 120096 Applied: 120096 Rejected: 0 Affected: 120096
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:46:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 130104 Applied: 130104 Rejected: 0 Affected: 130104
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:47:28 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 140112 Applied: 140112 Rejected: 0 Affected: 140112
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:48:41 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 150120 Applied: 150120 Rejected: 0 Affected: 150120
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:49:56 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 160128 Applied: 160128 Rejected: 0 Affected: 160128
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:51:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 170136 Applied: 170136 Rejected: 0 Affected: 170136
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:52:31 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 180144 Applied: 180144 Rejected: 0 Affected: 180144
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:53:46 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 190152 Applied: 190152 Rejected: 0 Affected: 190152
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:54:46 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 200160 Applied: 200160 Rejected: 0 Affected: 200160
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:56:05 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 210168 Applied: 210168 Rejected: 0 Affected: 210168
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:57:29 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 220176 Applied: 220176 Rejected: 0 Affected: 220176
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:58:50 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 230184 Applied: 230184 Rejected: 0 Affected: 230184
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:00:03 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 240192 Applied: 240192 Rejected: 0 Affected: 240192
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:01:17 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 250200 Applied: 250200 Rejected: 0 Affected: 250200
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:02:32 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 260208 Applied: 260208 Rejected: 0 Affected: 260208
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:03:49 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 270216 Applied: 270216 Rejected: 0 Affected: 270216
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:05:04 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 280224 Applied: 280224 Rejected: 0 Affected: 280224
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:06:21 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 290232 Applied: 290232 Rejected: 0 Affected: 290232
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:07:38 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 300240 Applied: 300240 Rejected: 0 Affected: 300240
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:09:03 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 310248 Applied: 310248 Rejected: 0 Affected: 310248
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:10:33 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 320256 Applied: 320256 Rejected: 0 Affected: 320256
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:12:04 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 330264 Applied: 330264 Rejected: 0 Affected: 330264
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:13:31 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 340272 Applied: 340272 Rejected: 0 Affected: 340272
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:14:58 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 350280 Applied: 350280 Rejected: 0 Affected: 350280
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:16:14 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 360288 Applied: 360288 Rejected: 0 Affected: 360288
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:17:44 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 370296 Applied: 370296 Rejected: 0 Affected: 370296
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:19:06 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 380304 Applied: 380304 Rejected: 0 Affected: 380304
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:20:38 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 390312 Applied: 390312 Rejected: 0 Affected: 390312
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:21:55 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 400320 Applied: 400320 Rejected: 0 Affected: 400320
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:23:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 410328 Applied: 410328 Rejected: 0 Affected: 410328
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:24:39 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 420336 Applied: 420336 Rejected: 0 Affected: 420336
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:25:58 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 430344 Applied: 430344 Rejected: 0 Affected: 430344
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:27:17 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 440352 Applied: 440352 Rejected: 0 Affected: 440352
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:28:39 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 450360 Applied: 450360 Rejected: 0 Affected: 450360
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:29:57 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 460368 Applied: 460368 Rejected: 0 Affected: 460368
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:31:22 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 470376 Applied: 470376 Rejected: 0 Affected: 470376
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:32:52 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 480384 Applied: 480384 Rejected: 0 Affected: 480384
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:34:16 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 490392 Applied: 490392 Rejected: 0 Affected: 490392
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:35:36 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 500400 Applied: 500400 Rejected: 0 Affected: 500400
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:37:03 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 510408 Applied: 510408 Rejected: 0 Affected: 510408
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:38:22 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 520416 Applied: 520416 Rejected: 0 Affected: 520416
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:39:36 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 530424 Applied: 530424 Rejected: 0 Affected: 530424
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:40:58 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 540432 Applied: 540432 Rejected: 0 Affected: 540432
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:42:20 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 550440 Applied: 550440 Rejected: 0 Affected: 550440
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:43:37 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 560448 Applied: 560448 Rejected: 0 Affected: 560448
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:44:25 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 570456 Applied: 570456 Rejected: 0 Affected: 570456
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:45:09 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 580464 Applied: 580464 Rejected: 0 Affected: 580464
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:46:19 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 590472 Applied: 590472 Rejected: 0 Affected: 590472
READER_1_1_1> BLKR_16019 Read [597399] rows, read [0] error rows for source table [W_INT_ORG_D] instance name [W_INT_ORG_D]
READER_1_1_1> BLKR_16008 Reader run completed.
TRANSF_1_1_1> DBG_21216 Finished transformations for Source Qualifier [Sq_W_PURCH_COST_FS]. Total errors [0]
WRITER_1_*_1> WRT_8168 End loading table [W_PURCH_COST_F] at: Thu May 26 17:47:08 2011
WRITER_1_*_1> WRT_8141
Commit on end-of-data Thu May 26 17:47:08 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 597399 Applied: 597399 Rejected: 0 Affected: 597399
WRITER_1_*_1> WRT_8035 Load complete time: Thu May 26 17:47:08 2011
LOAD SUMMARY
============
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 597399 Applied: 597399 Rejected: 0 Affected: 597399
WRITER_1__1> WRT_8043 ****END LOAD SESSION*****
WRITER_1_*_1> WRT_8006 Writer run completed.
MANAGER> PETL_24031
***** RUN INFO FOR TGT LOAD ORDER GROUP [1], CONCURRENT SET [1] *****
Thread [READER_1_1_1] created for [the read stage] of partition point [Sq_W_PURCH_COST_FS] has completed: Total Run Time = [4877.310545] secs, Total Idle Time = [187.907454] secs, Busy Percentage = [96.147314].
Thread [TRANSF_1_1_1] created for [the transformation stage] of partition point [Sq_W_PURCH_COST_FS] has completed: Total Run Time = [4875.388657] secs, Total Idle Time = [4867.607283] secs, Busy Percentage = [0.159605].
Thread [WRITER_1_*_1] created for [the write stage] of partition point [W_PURCH_COST_F] has completed: Total Run Time = [4817.325787] secs, Total Idle Time = [4796.966177] secs, Busy Percentage = [0.422633].
MAPPING> CMN_1793 The index cache size that would hold [411967] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Inventory_Product_D_Inventory_Prod_Wid], in memory, is [107673600] bytes
MAPPING> CMN_1792 The data cache size that would hold [411967] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Inventory_Product_D_Inventory_Prod_Wid], in memory, is [9912320] bytes
MAPPING> CMN_1793 The index cache size that would hold [1] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_PRODUCT_D_Supplier_Prod_Wid], in memory, is [25600] bytes
MAPPING> CMN_1792 The data cache size that would hold [1] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_PRODUCT_D_Supplier_Prod_Wid], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Requestor_Wid], in memory, is [1945600] bytes
MAPPING> CMN_1792 The data cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Requestor_Wid], in memory, is [188416] bytes
MAPPING> CMN_1793 The index cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Buyer_Wid], in memory, is [1945600] bytes
MAPPING> CMN_1792 The data cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Buyer_Wid], in memory, is [188416] bytes
MAPPING> CMN_1793 The index cache size that would hold [7070] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Cost_Center_D_Cost_Center_Wid], in memory, is [1868800] bytes
MAPPING> CMN_1792 The data cache size that would hold [7070] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Cost_Center_D_Cost_Center_Wid], in memory, is [180224] bytes
MAPPING> CMN_1793 The index cache size that would hold [2] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PROFIT_CENTER_D_Profit_Center_Wid], in memory, is [25600] bytes
MAPPING> CMN_1792 The data cache size that would hold [2] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PROFIT_CENTER_D_Profit_Center_Wid], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [211199] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PRODUCT_D_Product_Wid], in memory, is [55219200] bytes
MAPPING> CMN_1792 The data cache size that would hold [211199] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PRODUCT_D_Product_Wid], in memory, is [5087232] bytes
MAPPING> CMN_1793 The index cache size that would hold [31568] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_GL_ACCOUNT_D_Gl_Account_Wid], in memory, is [8294400] bytes
MAPPING> CMN_1792 The data cache size that would hold [31568] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_GL_ACCOUNT_D_Gl_Account_Wid], in memory, is [14376960] bytes
MAPPING> CMN_1793 The index cache size that would hold [99] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_Codes_UOM], in memory, is [14000] bytes
MAPPING> CMN_1792 The data cache size that would hold [99] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_Codes_UOM], in memory, is [24576] bytes
MAPPING> CMN_1793 The index cache size that would hold [92117] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_D_Supplier_Wid], in memory, is [24115200] bytes
MAPPING> CMN_1792 The data cache size that would hold [92117] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_D_Supplier_Wid], in memory, is [2228224] bytes
MAPPING> CMN_1793 The index cache size that would hold [1] rows in the lookup table for [mplt_Curcy_Conversion_Rates.GET_GLOBAL_CURR_CODES_AND_RATE_TYPES], in memory, is [20480] bytes
MAPPING> CMN_1792 The data cache size that would hold [1] rows in the lookup table for [mplt_Curcy_Conversion_Rates.GET_GLOBAL_CURR_CODES_AND_RATE_TYPES], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [0] rows in the lookup table for [Lkp_W_PURCH_COST_F], in memory, is [20480] bytes
MAPPING> CMN_1792 The data cache size that would hold [0] rows in the lookup table for [Lkp_W_PURCH_COST_F], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [1] rows in the lookup table for [mplt_Get_Etl_Proc_Wid.LKP_ETL_PROC_WID], in memory, is [2800] bytes
MAPPING> CMN_1792 The data cache size that would hold [1] rows in the lookup table for [mplt_Get_Etl_Proc_Wid.LKP_ETL_PROC_WID], in memory, is [16384] bytes
MANAGER> PETL_24005 Starting post-session tasks. : (Thu May 26 17:47:10 2011)
MANAGER> PETL_24029 Post-session task completed successfully. : (Thu May 26 17:47:10 2011)
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_25W32] for transformation [Lkp_W_PURCH_COST_F].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_524289W32] for transformation [mplt_Get_Etl_Proc_Wid.LKP_ETL_PROC_WID].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1507331W32] for transformation [mplt_Curcy_Conversion_Rates.GET_GLOBAL_CURR_CODES_AND_RATE_TYPES].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572874W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_Inventory_Product_D_Inventory_Prod_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_2031617W32] for transformation [MPLT_LKP_W_SUPPLIER_PRODUCT_D.LKP_W_SUPPLIER_PRODUCT_D_Primary].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572876W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Requestor_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572865W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_PRODUCT_D_Product_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572867W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_GL_ACCOUNT_D_Gl_Account_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572878W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_Cost_Center_D_Cost_Center_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572866W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_PROFIT_CENTER_D_Profit_Center_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572868W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_Codes_UOM].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572869W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_D_Supplier_Wid].
MAPPING> TM_6018 Session [SIL_PurchaseCostFact_Full] run completed with [0] row transformation errors.
MANAGER> PETL_24002 Parallel Pipeline Engine finished.
DIRECTOR> PETL_24012 Session run completed successfully.
DIRECTOR> TM_6022

There is another log file for Informatica that will give you detailed information on the issue. You should be looking into that log file.

R/3 job and get the details of variants like (from and to)

Hi,
How to find R/3 job and get the details of variants like (from and to) for that job.
the job is extraction job and running for 4 hours in R/3 once atfer this job completes BW job will start executing. Now i have to analyse R/3 job that how many years of data it is extracting (from, to) and other useful information why it is taking time for 4 hours.
Please let me know what transaction i have to use and how to check this information in R/3 side.
Thanks,

Hi........
Go to SM37 >> select the job >> Click on Job log.........Check there whether u r getting any Clue or not...........Is this load is through PSA..........? if so check the records of the First data packet...........then the Last data packet............from there u can get some idea..................
Also u can check the data in the Extractor.......is it a full load?.............Go to RSA3 >> Execute..........there check the data........
Is it a LO datasource ? if so................Go to LBWE >> Click on maintenance link for your datasource........>> Here in the Right pane u can see the Structute associated with that Datasource ...........If u remove MC from those structure name............u will get the table name..............In those tables also u can check the data...............there should be some data field.............from where u can get some idea.........
If ur Extractor is extracting data using some Function Module.............then open the datasource using RSA2.............there double click on the Exrtractor..............u will get the function module.................u can try to analyze the function module............
For Variants..................select the job >> click on Step in the top >> then Go to in the top >> Variant..............but I don't think this will help u............this will tell u that this Extraction job is part of which chain or IP......
Regards,
Debjani..........

File getting Delayed

Hi,
My scenario is that daily I am getting one file at a specified time but sometime that file gets delayed by 3 hour or 4 hours.
when I check log in moni I get following.
Where I can see that the message took time in DB_ENTRY_QUEUING.
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="cipip">20090830133000.143302</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="cipip">20090830133000.143309</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="cipip">20090830221511.553973</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_XML_VALIDATION_RQ_INB</SAP:Name>
<SAP:Timestamp type="begin" host="cipip">20090830221511.557395</SAP:Timestamp>
Can somebody please suggest what this problem is as I am facing this problem only for this particular inteface.
Regards,
Nidhi

Hi Nidhi,
No you are looking at the Perfomance node of SOAP Header. There you will not find the Queue into which this interface message went.
Either check SAP:QIdInternal parameter in Runtime (in SOAP Header) or in SXMB_MONI scroll toward right and see the column Queue ID.
See whether all messages of this interface goes to the same queue, if yes then check sxmb_admin to see whether some queue configuration is made for this queue (which is resulting in the delay)
Regards
Suraj

Job SAP_COLLECTOR_FOR_PERFMONITOR getting delay.

Similar Messages

Maybe you are looking for