E2E BI HOUSEKEEPING
Hello,
In our solman 7.1 system the job E2E BI HOUSEKEEPING finished but the spool has different errors & there st22 dumps too.
Found this note 1844955 but my question is :
1. We have not been using End to End analysis tab in solman workcenter tcode -> root cause analysis so is this job still necessary to run in solman ?
2. If not, its been running for a while what would be the affect of un-scheduling the job now ?
3. Do I have to carry out any steps to check if doesn't affect any steps in solman or connected systems ?
Spool Errors :
Target Infocube: 0DB4_C04D
Source Infocube: 0DB4_C04H
Destination : NONE
Aggregator :
E2E_HK_AGGREGATE_MDX
Delta : 90
HK: Calling SMD_HOUSEKEEPER at NONE
HK: Cube aggregation: SMD_HK_AGGREGATE_MDX
HK: Error detected by SMD_HK_AGGREGATE_MDX
HK: Status : 3-
HK: Message:
Target 0DB4_C04D does not exist
Runtime [s]: 0
Target Infocube: 0ORA_C03D
Source Infocube: 0ORA_C03H
Destination : NONE
Aggregator :
E2E_HK_AGGREGATE_MDX
Delta : 90
HK: Calling SMD_HOUSEKEEPER at NONE
HK: Cube aggregation: SMD_HK_AGGREGATE_MDX
System Failure:
Time limit exceeded.
Runtime [s]: 17.985
ST22 ( two dumps)
Category
ABAP Programming Error
Runtime Errors
DBIF_RSQL_TABLE_UNKNOWN
ABAP Program
SAPLRSDRD
Application Component BW-BEX-OT
Date and Time
03/19/2014 05:31:31
Short text
A table is unknown or does not exist.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRSDRD" 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
A table is referred to in an SAP Open SQL statement that either does not
exist or is unknown to the ABAP Data Dictionary.
The table involved is "/BI0/F0ORA_C02D" or another table accessed in the
statement.
Category
ABAP Programming Error
Runtime Errors
TIME_OUT
ABAP Program
SAPLRSDRD
Application Component BW-BEX-OT
Date and Time
03/19/2014 05:30:23
Short text
Time limit exceeded.
What happened?
The program "SAPLRSDRD" has exceeded the maximum permitted runtime without
interruption and has therefore been terminated.
Thanks
Shradha
Hi Shradha,
E2E BI HOUSEKEEPING is must run job in solution manager. it is actually needed for your BI house cleaning.
1. We have not been using End to End analysis tab in solman workcenter tcode -> root cause analysis so is this job still necessary to run in solman ?
In 7.1, there is no dedicated guided concept for RCA, if you have done managed system configuration iteself, most of the extractors were active for the system, the data collection and storing to BI has started. You must have this housekeeping job. Recently solution manager has UPL integration too. All these features would go long term if you have proper housekeeping activity scheduled. hence please make this job running without fail.
2. If not, its been running for a while what would be the affect of un-scheduling the job now ?
3. Do I have to carry out any steps to check if doesn't affect any steps in solman or connected systems ?
This is the independent job, will not affect any other scheduled jobs.
Refer my blog How Is The Health Of Your SAP Solution Manager BI Content? and the sap note 1480588 - ST: E2E Diagnostics - BI Housekeeping - Information
Please check
Thanks
Jansi
Similar Messages
-
E2E BI HOUSEKEEPING Job failing due to timeout
Hi Folks,
Reviewing our Solman system I found that some tables are getting really large, I found SMD_HASH_TABLE is over 71GB compressed. I found the note 1958979 - Solution Manager - Tablespace increase which in turn directs you to the attached document of the note 1480588 - ST: E2E Diagnostics - BI Housekeeping - Information.
Per the document, I executed TAANA transaction and ran analysis on the table and got the following data,
Per the next steps, I added the following entry in the table E2E_BI_DELETE.
the next run of the job, I got an ABAP dump with timeout.
Looks like while selecting the data for deletion, it timed out.
Has someone faced this issue and can suggest ways I can run this outside of this job one time to clean up this table. I believe the subsequent runs will be ok as long as the housekeeping job is run regularly.
regards
YogeshHello Yogesh,
I experience exactly the same issue. Can you share the solution if you resolved this?
Thank you,
Paul. -
E2E Root cause analysis in solution manager
Hi
How to add the E2E root cause analysis, the new functionality in solution manager 4.0 with the E2E root cause analysis functionality does it require support pack which level of SP required to use the new functionaltiy
Regards
Dinaker vikasHi,
If you have PI system in your landscape, I would strongly recommend to upgrade to SP15.
Trace monitoring for PI is to be available from SP17 (Not yet released)
Check [this Link.|http://service.sap.com/e2e].
Hope this solves your problem.
Feel free to revert back.
--Ragu -
What is the diff of Solution monitoring and E2E Root cause analysis
Hi,
I want to know what is the different for Solution Manager Solution Monitoring and End to End root cause analysis. Currently we have implemented change management and Implementing and Upgrading SAP Solutions, if i would like to explore the solution monitoring, and end to end root cause analysis, what is the steps of configuration i need?
if i would like to have a check on the system whether is performing well, or setup the functionality of sending alert when system is having problem, which feature would be better? end of end functionality or Solution Monitoring?
Please advice..
thanks
-FungHi,
If you have PI system in your landscape, I would strongly recommend to upgrade to SP15.
Trace monitoring for PI is to be available from SP17 (Not yet released)
Check [this Link.|http://service.sap.com/e2e].
Hope this solves your problem.
Feel free to revert back.
--Ragu -
Getting an error in E2E analysis
Hi,
In E2E analysis we are getting an error: The system you selected do not contain any software component currently supported by E2E Analysis.
Thanks
ShailHi Rajeev
this is java sever and getting an error in worklad analysis.
componets are :
ADSSAP 7.01 5 ADOBE DOCUMENT SERVICES 7.01
BASETABLES 7.01 5 J2EE ENGINE BASE TABLES 7.01
BI_MMR 7.01 5 BI META MODEL REPOSITORY 7.01
BI_UDI 7.01 5 BI UDI 7.01
CAF 7.01 5 SAP CAF 7.01
CAF-UM 7.01 5 SAP CAF-UM 7.01
CORE-TOOLS 7.01 5 J2EE ENGINE CORE TOOLS 7.01
DI_CBS 7.01 5 DI COMPONENT BUILD SERVER 7.01
DI_CMS 7.01 5 DI CHANGE MGMT. SERVER 7.01
DI_DTR 7.01 5 DI DESIGN TIME REPOSITORY 7.01
JLOGVIEW 7.01 5 JAVA LOG VIEWER 7.01
JSPM 7.01 5 JAVA SP MANAGER 7.01
KM-KW_JIKS 7.01 5 SAP_IKS_7.01
JLOGVIEW 7.01 5 JAVA LOG VIEWER 7.01
JSPM 7.01 5 JAVA SP MANAGER 7.01
KM-KW_JIKS 7.01 5 SAP_IKS_7.01
LM-TOOLS 7.01 5 LIFECYCLE MGMT TOOLS 7.01
SAP-JEE 7.01 5 SAP J2EE ENGINE 7.01
SAP-JEECOR 7.01 5 SAP J2EE ENGINE CORE 7.01
SAP_JTECHF 7.01 5 SAP TECH S OFFLINE 7.01
SAP_JTECHS 7.01 5 SAP JAVA TECH SERVICES 7.01
SWLIFECYCL 7.01 5 SOFTWARE LIFECYCLE 7.01
UMEADMIN 7.01 5 UME ADMINISTRATION 7.01
Pleasse advise us.
Thanks
Shail -
No data in overview tab of E2E work load analysis
Hi All,
I am using solman 7.1, am unable to see the data in the over view tab for my solution manager system both in ABAP and JAVA. For the remaining product systems i can able to see the data except one managed system(solman system). DAA is already running in the system. I am attaching the screen shot for the same. Kindly help me on this.
Thanks,
Chowdary.Hi bodepudi,
Start with this note
Note 1435043 - E2E Workload Analysis - No applicable data found
Regards,
Divyanshu -
Workload Analysis tab is missing in E2E Anaysis
Hi Guru,
I am in process of generating EWA reports for portal ,below are the steps I have completed successfully.
1. SMD agent installation on portal.
2. Defined portal system in SMSY.
3. completed SOLMAN_SETUP.
4. Completed Setup Wizard for managed system.
5. Deploy IS agent via SDM in Solman.
6. Introscope agent setup done for managed system
7. Managed system data is visible in IS Enterprise Manager.
When I checked t code solman_workcenter->RCAtab-> E2E Anaysis->selected the portal system i cant find Workload Analysis tab i.e Workload Analysis tab is missing could you please help me to resolve this issue.
System Configuratoi: SAP EHP 1 for SAP Solution Manager 7.0 and portal is netweaver 7.0
Thanks
AbullaisHi,
Kindly check security guide for RCA authorization,
https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000718044&_SCENARIO=01100035870000000202
It may be due to authorization issue.
Regards,
Karthik -
Periodic housekeeping/data deletion in OLAP cube
Hi All,
We have a cube partitioned on date.Our agreed retention period of data is one year.Can you please suggest any standard daily housekeeping way to drop all the partitions older than 365 days.(Grateful if you give little details as-well).
NB. We do not want to delete all the data and load last 365 days data - daily!
Many Thanks,
AvishekWell, got the answer in the oracle documentation: Whenever a Calendar value is deleted from the Time dimension, the corresponding empty partition is deleted from the cube.Thought the info could be useful to others-may be;) .. ~Avishek
-
Firefox 13.0 not installing properly - Hangs @ "A little housekeeping"
Every single time I try to install Firefox the installation hangs on "A Little Housekeeping." This is a Windows 7 portable w/ 4 GB
I have no idea what could be causing this. I have uninstall and reinstalled Firefox multiple times trying to get it to install correctly. When I use task manager to close out of the process Firefox appears to have installed, and I am able to remove the program in the control panels Add/Remove Programs list.I am just using this forum on Windows XP as my Windows 7 Firefox is OOC.
-
This application is not yet configured. Please refer to the E2E post-instal
Hi,
I have configured the SMD on Solution Manager 4.0 SP 11, LMSERVICE SP12 (Before it was SP 11 but is still had the same error)
Wily Introscope 7.1.
The solution has been published and I able to use all the other diagnostic modules except for E2E.
When I click on any E2E Workload/Exception etc I get the following message
"This application is not yet configured. Please refer to the E2E post-installation steps"
What are the specific steps to enable my application for E2E?
Thanks,
VikramHi Bernd
Thanks for the detailed steps. My comments interspersed
> Hi Vikram,
>
> 2 steps have to be performed:
>
> 1) Scheduler Configuration
> 1. Connect to the Diagnostics system.
> 2. Start the Scheduler application
> o Diagnostics Administration  Managed Systems
>  Scheduler
> 3. Select the E2E Log Analysis Task. This task
> analyses log and dumps files to collect Error and
> Dump messages from the associated managed system.
> 4. Activate the Task for the host belonging to the
> managed landscapes
> N.B.: Please be aware that this task will fail as
> long as the configuration step Setup RFC
> Destinations has not been successfully performed.
> Navigation Activation
This step has been completed, and there are no errors. I don't think I need an RFC since my managed system is a J2ee stack Netweaver ( 2004s SP12 ). This is the message that I see in the E2E Log Analysis scheduler "Execution succeeded in 3188 ms. Next execution in 60 min(s)."
>
> 2)
> 1. Start Visual admin
> 2. Go to Server -> Services -> Configuration
> Adapter.
> 3. In the Display Configuration tab drill in:
> apps -> sap.com -> tcwebadminstratornavigation~ejb
> -> appcfg
> 4. Enter the edit mode and set the custom value to
> true for the three properties named:
> o e2e_*_configured ( where * is the name of the E2E
> application you want to enable)
> 5. Restart the navigation and the corresponding E2E
> applications can now be started.
I have set the custom values to true for the following:
e2e_log_analysis_configured
e2e_trace_configured
e2e_ workload_analysis_configured
In the Propertysheet.application.global.properties, restarted the apps
But I still get the same error.
Is there any other configuration involved?
BTW, Is there any document that details the above steps you have pointed out? I guess I must have gone through all the diagnostics set up guide, but have not come across this uptill now
Once again Thanks a lot!
Vikram -
Housekeeping of Query Views in Portal
Hi,
I am looking to provide housekeeping with Query Views on our Portal. At the moment all Query Views appear when you choose 'Bex Portfolio' and there are a large number in there now - most of which are redundant.
At the moment, I have two issues -
I want to be able to delete Query Views via the Portal (or possibly get the users to delete these).
(ii) If all query views appear in the Bex Portfolio, is there a way to create a Folder Structure in here that would allow an easier maintenance and 'ease of use' option for the end user.
Our users create their own views, but I need ways of keeping this maintained.
Can anyone help with how I can resolve any of the above?
Much appreciated,
ScottGet rid of the table qualifier:
SELECT * FROM view_mytbl" WHERE UID IN (#URL.UID#)
Tom Muck
co-author Dreamweaver MX 2004: The Complete Reference
http://www.tom-muck.com/
Cartweaver Development Team
http://www.cartweaver.com
Extending Knowledge Daily
http://www.communitymx.com/
"sp515" <[email protected]> wrote in message
news:eqcle1$as$[email protected]..
Hello,
I have recently migrated from MSAccess to MySQL. In CF 5
everything was
working fine, but when we moved to CFMX 7, there is this one
query that
fails
and I have tried many different ways (putting single quotes,
parathesis
etc.)
I have created a "View" in MySQL database called
"view_mytbl" .In this view
I
have queried two different tables, tbl1,and tbl2. Now in my
source code
of
CFMX, I query this view by passing a where clause.
<cfquery name="myquery" datasource="#DSN#">
SELECT * FROM view_mytbl" WHERE tbl1.UID IN (#URL.UID#)
</cfquery>
This was fine in CF 5 , but now I get the error as "Unknown
column
'tbl1.UID'
in 'where clause' "
I have tried putting single quotes around #URL.UID# but that
does not
work.
Please help, I am exhausted in searching for this solution.
Thanks, -
Dear all.
What are the main E2E process supported by SAP?
Where can I find regarding information about each E2E process flow?
How BPM and E2E are related to?
I really appreciate your comments, support and help.
BEst Regards.
JB.Hi Juan,
You are asking a very wide questions. I would recommend toy to have a look at the solution maps provided by sap in service marketplace. There are solution maps for all main processes supported from a certain level and also included sub-processes.
You find the solution maps including tools such as the solution composer under the following link:
https://websmp201.sap-ag.de/bmet
Hope you find this helpful.
Fredrik -
Premier CS3 Essential Project Housekeeping Query
I hope someone will help with their experience
I have created several home film projects over the years, which take me a long time as I am constantly working out how to work the program. Typically after a year or so and I become more accomplished, I wish to revisit the old projects to iron out those glitches and blemishes which will finally make the film fully professional.
The problem is all the files are someplace else, colour bars keep appearing and usually a whole series of 'where is .. file' appear and I have to go and search around and find them and then it seems that I have to go look for them again the next time I open the file. Also a whole bunch of quite large files are thrown into a folder somewhere not very well signposted with not very intuitive names/extensions which cause further uncertainty as to what is what and probably might be part of the problem also.
I'me sure this does not happen to most users who have basic housekeeping skills and procedures, and I am wondering if someone could enlighten with some simple workflow guidelines which will get me out of Free Parking and up and away in film making and essentially bring all my efforts of the past to fruition. I typically move files from disk to disk to offset strorage problems. ThanksWelcome to the forum.
Most of that "housekeeping" starts when one chooses New Project, and then progresses from there.
For each New Project, I create a Project Folder (in some cases, these will be under a "Client Folder," but are often just located on E:\. Under each Project Folder, [Project Name], I create sub-folders, say Videos, Audio, Music, Still Images, Captures, etc., and in Edit Preferences, I point the Scratch Disks to "Same as Project." Everything is in the [Project Name] folder hierarchy.
In my case, and with the exceptions of Captures from miniDV tapes, I keep the originals of all of my Assets elsewhere (on a NAS in my case), and will Copy all of them to the appropriate sub-folders. I will then Import those Copies into my Project. Everything stays within the [Project Name] folder hierarchy. This makes everything easy to handle.
When one Imports an Asset, PrPro creates a link in the PRPROJ file, in XML code, with the Absolute Path, i.e. the full Path to where that Asset is located. In my case, say for a Video file, the Path will be: E:\[Project Name]\Videos. Note: if anything changes with that Path, one will get the "Where is file ____?"query. This is any part of that Path, including the file's name. PrPro will follow that linked Path, when reopening that Project, and if anything has changed, been Deleted, Moved or Renamed, PrPro cannot find it, without the user's help. This is where you are having issues.
If one has Imported Assets from all around a system, there are two potential problems: if anything changes in the Path to those Assets, PrPro is lost. If one Moves their Still Images to another folder or sub-folder, PrPro needs your help. Also, PrPro can have issues, when one uses Project Manager to archive a Project, where Assets are scattered about. This is one reason that I work with Copies of all Assets, and keep them in the [Project Name] folder hierarchy. Project Manager can locate everything easily, and depending on the settings that one chooses in Project Manager, all Assets can be archived, along with the PRPROJ file.
For archiving older Projects, the Project Manager is a great tool. I would read all about it in the Help File, as there are several useful settings, and understanding what each offers will be VERY helpful.
When one has used Project Manager, and they have a folder structure, as I described, one should check the archived Project (the output from Project Manager), to insure that EVERYTHING is in place. I archive to a set of external HDD's. I then test each archived Project, and when I am certain that they function 100%, and that all Assets have been included, I will just go to the [Project Name] folder, and Delete it. This takes ALL of the sub-folders and Asset Copies with it, but I never do that, until I have fully tested the archived version of the Project. Housekeeping is then just three clicks: select [Project Name] folder, click Delete, then OK.
As mentioned above, the reason that you are getting the "Where is file _____?" is because something has changed in that Absolute Path, since the Assets were Imported into the Project - could be a Move, a Delete or a Rename. In the "Move" area, it could be that those Assets were on an external, and that day, the OS assigned the drive letter H:\, but today, when you plug that same external into the computer, the OS assigns the drive letter G:\. The way around this is to set the drive letter of each external HDD to a unique drive letter. Then, every time you plug it in, it will always get the same drive letter. If you work with those externals on several computers, then you must go into the OS on each computer, and set that drive letter.
Good luck, and please spend some time with the Help File, on Project Manager. If you then have any questions with any aspect of Project Manager, drop by here, and ask what _____ means, and someone will help explain that to you. Several options, and each has a use, and is important.
Hunt
PS - do not recall if PrPro CS3 had a manual, but if so, then spend some time reading of Project Manager there. -
SMD on SP15: no data for E2E Workload Analysis are shown
Hello!
I have successfully run Setup Wizard for the satellite solution "EP Portal on 6.40".
Unfortunately no data for E2E Workload Analysis are shown since more than one month.
I use SAP Solution Manager with SP 15, BI CONT 9
I have implemented the following SAP notes:
1088163, 1107804, 110782, 1119766
The jobs E2E_EXTRACTOR_CONTROLLER are running without errors.
Enclosed one of those for portal solution:
09.04.2008 E2E: Extractor Controller 1
EC: 09.04.2008 13:05:52 UTC Extractor Controller started for SID B11
EC: 09.04.2008 15:05:52 CET Installation Number 0020198811
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component
EC: 13:05:52 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:52 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:52 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:54 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/APPLOG_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/APPLOG_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/APPLOG_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/DUMP_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
09.04.2008 E2E: Extractor Controller 2
ME: 13:05:54 UTC Calling Extractor /SDF/DUMP_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/DUMP_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/SYSLOG_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/SYSLOG_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/SYSLOG_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/UPDATE_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/UPDATE_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/UPDATE_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
09.04.2008 E2E: Extractor Controller 3
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:55 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:55 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 13:05:56 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 13:05:56 UTC Receiving return code 6 from
E2E_JAVA_EXTRACTOR_IF
ME: Error:
DATA_RETRIEVAL_EXCEPTION
EC: 13:05:56 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 13:05:56 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:57 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:57 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR
09.04.2008 E2E: Extractor Controller 4
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:05:58 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 08.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 08.04.2008 12 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 08.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:58 UTC Calling Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR ,
Extractor Class:
ME: 13:05:58 UTC Receiving return code 98 from
/SDF/IDOC_THROUGHPUT_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:58 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F60_XI_E2E_PROXY_STATS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:05:58 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:58 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
ME: No Data Found.
ME: 13:06:00 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_C_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_C_TRANSPORTS
09.04.2008 E2E: Extractor Controller 5
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_NOTES
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_NOTES
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_W_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_W_TRANSPORTS
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:01 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
09.04.2008 E2E: Extractor Controller 6
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:06:02 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:06:02 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F55_XI_IDOC_ADAPTER
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:02 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:02 UTC Calling Extractor F55_XI_IDOC_ADAPTER
ME: No Data Found.
ME: 13:06:02 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F60_XI_E2E_PROXY_STATS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_C_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_C_TRANSPORTS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
09.04.2008 E2E: Extractor Controller 7
EC: Extractor F90_CA_NOTES
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_NOTES
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_W_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_W_TRANSPORTS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_SSR_EXTRACTOR_IF
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: Local Execution of Extractor.
EC: ME called in Multi-Mode.
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor E2E_SSR_EXTRACTOR_IF ,
Extractor Class:
E2E_SSR_EXTRACTOR_0CCMSATPH
ME: 13:06:06 UTC Receiving return code 0 from
E2E_SSR_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:06:06 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
Any helpful information will be appreciated
regards
ThomSame problem being observed in our Solman system (SP15). Below are the errors observed in the spool output of E2E framework jobs,
1] ME: Data Loader Error occurred.
EC: 21:05:44 UTC Main Extractor raises exception. No Data returned by extractor.
2] No action - TSL parameter detected.
This extractor is not allowed to run outside time frame
3] ME: 21:05:45 UTC Receiving return code 98 from
/SDF/UPDATE_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 21:05:45 UTC Main Extractor raises exception. No Data returned by extractor.
4] ME: Error:
DATA_RETRIEVAL_EXCEPTION
EC: 21:05:46 UTC Main Extractor raises exception. No Data returned by extractor.
Tried referring E2E workload analysis guide...no use..the issues have not been covered in that. -
SMD: no data for E2E Workload Analysis are shown
Hello,
I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 3) and would set up the SMD functionality for SAP EP 6.40 SP19.
The Set up Wizards runs without any errors and I could see the data in all the steps (E2E Workload, E2E Change Analysis).
Unfortunately since 2 months I can see any data in (E2E Workload, E2E Change Analysis, E2E Exception Analysis).
The E2E_EXTRACTOR_CONTROLLER job runs and is enclosed here
16.04.2008 E2E: Extractor Controller 1
EC: 16.04.2008 14:05:11 UTC Extractor Controller started for SID E11
EC: 16.04.2008 16:05:11 CET Installation Number 0020198811
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component
EC: 14:05:11 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:11 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:12 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:14 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 14:05:14 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:14 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:16 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:16 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 14:05:16 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
16.04.2008 E2E: Extractor Controller 2
RR: Scanned Interval: From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:16 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:18 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:18 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 7
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product 01200314690900000192
EC: Main Instance (1) 7
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 14:05:18 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:18 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:20 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:20 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product 01200314690900000192
EC: Main Instance (1) 7
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 14:05:20 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:20 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
16.04.2008 E2E: Extractor Controller 3
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:21 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:21 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
Can some one help to solve this problem.
Thank you very much
regards
ThomHello,
I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 3) and would set up the SMD functionality for SAP EP 6.40 SP19.
The Set up Wizards runs without any errors and I could see the data in all the steps (E2E Workload, E2E Change Analysis).
Unfortunately since 2 months I can see any data in (E2E Workload, E2E Change Analysis, E2E Exception Analysis).
The E2E_EXTRACTOR_CONTROLLER job runs and is enclosed here
16.04.2008 E2E: Extractor Controller 1
EC: 16.04.2008 14:05:11 UTC Extractor Controller started for SID E11
EC: 16.04.2008 16:05:11 CET Installation Number 0020198811
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component
EC: 14:05:11 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:11 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:12 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:14 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 14:05:14 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:14 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:16 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:16 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 14:05:16 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
16.04.2008 E2E: Extractor Controller 2
RR: Scanned Interval: From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:16 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:18 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:18 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 7
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product 01200314690900000192
EC: Main Instance (1) 7
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 14:05:18 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:18 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:20 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:20 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product 01200314690900000192
EC: Main Instance (1) 7
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 14:05:20 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:20 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
16.04.2008 E2E: Extractor Controller 3
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:21 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:21 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
Can some one help to solve this problem.
Thank you very much
regards
Thom
Maybe you are looking for
-
How do I bring a window to the front from a different VM ?
The problem I am facing is as follows: We have an application the loads a plugin which the starts another VM. This VM has some UI components as does the initial VM. I need to be able to bring a window from either VM to the front. It appears that Wind
-
Element's 6.0's Bridge doesn't open anymore - says application "unexpectedly quit"
Hello. I purchased my MacBook Pro in late September, and purchased and installed Elements 6.0 for Mac. Elements and Bridge were both working fine until late October, when one evening its Bridge CS3 application suddenly froze, so I had to force-quit
-
Participant cannot log into workspace In BPM 10.3.1.0
Hi, I create a project and want to test it on the workspace. I try to click on button START -> Launch workspace. The IE bring me to the page which require me to key in the username. I keyed in the username and click on button Log in. I cannot log int
-
Printing Chinese using XMLP Templates
Hi, I am trying to print Chinese data from EBS on to the Report created by XMLP Template. I am able to see the propoer chinese characters when I preview from MS Word as PDF or HTML. But, when the report is launched from SRS, I see only "???" instead
-
Why cant I view my RAW files from my canon 5D Mark III, even after installing the 7.1 Raw update? last week an Adobe phone rep said it was because CS5 doesn't support my camera. Now that I'm getting the same message with CS6 I'm confused.