Long Running Transport in BI

Hi,
I am trying to import few transport requests in production in BI environment.
The transport status is in Progress "Import running" (Truck Icon) since 2 hours.
As checked there are no RDD* jobs running in Sm37. TRJOBS table is empty and TRBAT had 5 entries for 5 transports.
If I check Import Monitor, the last step executed is "SET VERSION FLAGS for ...req..no... finished with return code 0" for all of them. I do not have OS level access to check TP and R3TRANS programs.
Once I tried to delete the transport entry from import monitor and restarted the transport but still it is stuck in the same status again.
Can anybody help resolve this problem?
Thank you!!
- Pranali

Pranali Patil wrote:
Hi,
> Anybody can help me in here?
>
> Pranali
probably not here.
Forum: SAP TM (Transportation Management)
This is an expert forum for questions around the SAP Transportation Management (SAP TM) solution that allows to plan real world logistics like moving of pallets in containers, finding routes for trucks, scheduling rail cars or calculating freight costs for an ocean shipment. [Homepage] Questions regarding Software Logistics, Transport of customizing entries, copying of system settings between development and quality management systems should not be placed here.
Regards
Clemens

Similar Messages

Note 1287382 To Help With Long Running Transport (DataStore)

Hey Everyone.
I am wondering if anyone has tried the steps in note 1287382 to help with the long run times when transporting new fields on large DataStore objects. I understand the idea behind the note, but am slightly skeptical about how long the end step with the workaround may take (that would be running the SAP_NOT_NULL_REPAIR_ORACLE program on the active and change log tables).
I have thought about just writing the active table data to a temporary table, delete active table data, send transport, write the data back from custom table directly to active table. I realize this goes against typical handling for a standard DataStore but this is what I was leaningt towards when I found the SAP note.
If anyone has taken the steps in the note, I would appreciate if you could let me know the transport time gains, how long the program took to rebuild/synchronize the tables, and the amount of data you were working with. I am working with a DSO of around 300 million or more.
Thanks

Thank you for that reply. So the 2 hours is how long that program took, right? I assume after making the RSADMIN table updates, the transport went very quickly? Did you encounter any issues afterwards with further updates to cubes (assuming you have them)?
Thanks again

Long Running Transport

Hi All,
Since yesterday ,import in Production is not happening. When we checked the TP system log its showing that Job RDDIMPDP is getting failed. After checking the job log from SM37 we found this error "Logon for Client 000 failed with user id ddic".
To resolve this issue I scheduled the report RDDIMPDP in production client 710 and its getting successfully ececuted after every 5 mins but again same error "Logon for Client 000 failed with user id ddic" for user id DDIC is coming and import is not happening.
Pls help me to resolve this issue.
Regards,
Prashant

Hi,
Dear,
First, check TP System log and see if any errors have occurred
during the transport.
Check if /usr/sap/trans/tmp folder contains this transport logs
or have they been shifted to log folder. if tmp folder does not
have the logs, ur transport has finished. in this case, go to
import monitor and delete the entry that says 'tp running' for
this request.
Also check using se16 if the tables trjob and/or trbat contain
any entries. u can delete those entries if transport is hung.
Warm Regards.
Mohammed Hassan Naveed
Associate SAP Basis Consultant

Whats better for my mbp 2013 retina in the long run? Keep it plugged in as much as possible or letting the battery hit 10% and then recharge it?

Whats better for my mbp 2013 retina in the long run? Keep it plugged in as much as possible or letting the battery hit 10% and then recharge it?

Odd you ask that, since both are HORRIBLE,   ... especially often draining your battery low.
General consideration of your MacBook battery
Contrary to popular myths about notebook batteries, there is protection circuitry in your Macbook and therefore you cannot ‘overcharge’ your notebook when plugged in and already fully charged.
However if you do not plan on using your notebook for several hours, turn it off (plugged in or otherwise), since you do not want your Macbook ‘both always plugged in and in sleep mode’.
A lot of battery experts call the use of Lithium-Ion cells the "80% Rule", meaning use 80% of the full charge or so, then recharge them for longer overall life. The only quantified damage done in the use of Lithium Ion batteries are instances where the internal notebook battery is “often drained very low”, this is bad general use of your notebook battery.
A person who has, for example, 300 charge cycles on their battery and is recharging at say 40% remaining of a 100% charge has a better battery condition state than, say, another person who has 300 charge cycles on their battery and is recharging at say 10-15% remaining on a 100% charge. DoD (depth of discharge) is much more important on the wear and tear on your Macbook’s battery than the count of charge cycles. There is no set “mile” or wear from a charge cycle in specific. Frequent high depth of discharge rates (draining the battery very low) on a Lithium battery will hasten the lowering of maximum battery capacity.
All batteries in any device are a consumable meant to be replaced eventually after much time, even under perfect use conditions.
If the massive amount of data that exists on lithium batteries were to be condensed into a simplex, helpful, and memorable bit of information it would be:
1. While realistically a bit impractical during normal everyday use, a lithium battery's longevity and its chemistry's health is most happy swinging back and forth between 20% and 85% charge roughly.
2. Do not purposefully drain your battery very low (10% and less), and do not keep them charged often or always high (100%).
3. Lithium batteries do not like the following:
A: Deep discharges, as meaning roughly 10% or less on a frequent basis.
B: Rapid discharges as referring to energy intensive gaming on battery on a frequent basis (in which case while gaming, if possible, do same on power rather than battery). This is a minor consideration.
C: Constant inflation, as meaning always or most often on charge, and certainly not both in sleep mode and on charge always or often.
From Apple on batteries:
http://www.apple.com/batteries/notebooks.html
http://support.apple.com/kb/HT1446
"Apple does not recommend leaving your portable plugged in all the time."
Keep it plugged in when near a socket so you keep the charging cycles down on your LiPo (lithium polymer) cells / battery, but not plugged in all the time. When not being used for several hours, turn it off.
DoD (depth of discharge) is far more important on the wear and tear on your Macbook battery than any mere charge cycle count. *There is no set “mile” or wear from a charge cycle in general OR in specific.    As such, contrary to popular conception, counting cycles is not conclusive whatsoever, rather the amount of deep DoD on an averaged scale of its use and charging conditions.
                          (as a very rough analogy would be 20,000 hard miles put on a car vs. 80,000 good miles being something similar)
*Contrary to some myths out there, there is protection circuitry in your Macbook and therefore you cannot overcharge it when plugged in and already fully charged
*However if you don’t plan on using it for a few hours, turn it OFF (plugged in or otherwise) ..*You don’t want your Macbook both always plugged in AND in sleep mode       (When portable devices are charging and in the on or sleep position, the current that is drawn through the device is called the parasitic load and will alter the dynamics of charge cycle. Battery manufacturers advise against parasitic loading because it induces mini-cycles.)
Keeping batteries connected to a charger ensures that periodic "top-ups" do very minor but continuous damage to individual cells, hence Apples recommendation above:   “Apple does not recommend leaving your portable plugged in all the time”, …this is because “Li-ion degrades fastest at high state-of-charge”.
                    This is also the same reason new Apple notebooks are packaged with 50% charges and not 100%.
Contrary to what some might say, Lithium batteries have an "ideal" break in period. First ten cycles or so, don't discharge down past 40% of the battery's capacity. Same way you don’t take a new car out and speed and rev the engine hard first 100 or so miles.
Proper treatment is still important. Just because LiPo batteries don’t need conditioning in general, does NOT mean they dont have an ideal use / recharge environment. Anything can be abused even if it doesn’t need conditioning.
Storing your MacBook
If you are going to store your MacBook away for an extended period of time, keep it in a cool location (room temperature roughly 22° C or about 72° F). Make certain you have at least a 50% charge on the internal battery of your Macbook if you plan on storing it away for a few months; recharge your battery to 50% or so every six months roughly if being stored away. If you live in a humid environment, keep your Macbook stored in its zippered case to prevent infiltration of humidity on the internals of your Macbook which could lead to corrosion.
Considerations:
Your battery is subject to chemical aging even if not in use. A Lithium battery is aging as soon as its made, regardless.
In a perfect (although impractical) situation, your lithium battery is best idealized swinging back and forth between 20 and 85% SOC (state of charge) roughly.
Further still how you discharge the battery is far more important than how it is either charged or stored short term, and more important long term that cycle counts.
Ultimately counting charge cycles is of little importance. Abuse in discharging (foremost), charging, and storing the battery and how it affects battery chemistry is important and not the ‘odometer’ reading, or cycle counts on the battery.
Everything boils down to battery chemistry long term, and not an arbitrary number, or cycle count.
Keep your macbook plugged in when near a socket since in the near end of long-term life, this is beneficial to the battery.
In a lithium battery, deep discharges alter the chemistry of the anode to take up lithium ions and slowly damages the batteries capacity for the cathode to transport lithium ions to the anode when charging, thereby reducing max charge levels in mAh. In short, radical swings of power to lithium cells disrupts the chemical ecosystem of the battery to hold charges correctly which likewise impedes the perfect transfer of lithium ions both in charging and discharging. In charging your lithium battery, lithium ions are “pushed uphill” (hard) to the anode, and discharged “downhill” (easy) to the cathode when on battery power. Deep discharges, damages this “upward” electrolyte chemistry for the battery to maintain a healthy charge and discharge balance relative to its age and cycles.
Optimally, in terms of a healthy lithium battery and its condition, it is most happy at 50% between extremes, which is why low-power-drain processors such as the Haswell are ideal on lithium battery health since a partially charged battery with a low-drain processor has, in general, much more usage in hours
Battery calibration, battery memory, battery overcharging, battery training, …all these concepts are mostly holdovers from much older battery technology, and on older Apple portable Macbooks ranging from early nicads, NiMh and otherwise; and these practices do not apply to your lithium battery and its smart controllers.
Calibrating the battery on older Apple portable Macbooks with removable batteries.
http://support.apple.com/kb/PH14087
There is no calibration of current Apple portable Macbooks with built-in batteries.
http://support.apple.com/kb/ht1490
There is no battery calibration with current Apple portable Macbooks with built-in batteries. Lithium batteries have essentially a 0-‘memory’, and all such calibration involve the estimations fed to the system controller on the SOC (state of charge) of the battery over long periods of time as the battery degrades. The software based battery controller knows the battery's characteristics, or SOC and adjusts itself. This is why there is both no need and purpose to periodically deeply drain your macbook battery, since it doesn’t affect the characteristics of the battery, and further still deep discharges are something you should not do on purpose to any lithium battery.
From BASF: How Lithium Batteries work
https://www.youtube.com/watch?v=2PjyJhe7Q1g
Peace

WIJ 20002 error on long running reports

When trying to run a long running report, an error message is received .
Quote:
*"The Web Intelligence Java Report Panel cannot connect to the server. Close
the report panel and try to connect again or see your BusinessObjects
administrator. (Error: WIJ 20002)"*
What happens next is you are advised to "close" (twice) and are then advised to close this window.
If you select Details on the first error message:
Server: https://test.i3access.iowa.gov:443/desktoplaunch/InfoView/CrystalEnterprise_Webi/cdzServlet?
java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 502 for URL: https://test.i3access.iowa.gov:443/desktoplaunch/InfoView/CrystalEnterprise_Webi/cdzServlet
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
     at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
     at com.businessobjects.wp.cpi.CPIConnection.postRequest(CPIConnection.java:437)
     at com.businessobjects.wp.xml.XMLViaHttp.loadScript(XMLViaHttp.java:144)
     at com.businessobjects.wp.xml.XMLViaHttp.getPromptList(XMLViaHttp.java:1284)
     at com.businessobjects.wp.xml.XMLLoader.getPromptList(XMLLoader.java:279)
     at com.businessobjects.wp.om.OMQuery.loadPromptsAndContexts(OMQuery.java:359)
     at com.businessobjects.wp.om.OMQuery.getActiveContextCount(OMQuery.java:384)
     at com.businessobjects.wp.tc.query.TCQueryPropertie.buildQueryContextFromUI(TCQueryPropertie.java:496)
     at com.businessobjects.wp.tc.query.TCQueryTab.buildQueryContextFromUI(TCQueryTab.java:846)
     at com.businessobjects.wp.tc.query.TCQueryTab.modifyQueryProperties(TCQueryTab.java:638)
     at com.businessobjects.wp.tc.query.TCQueryTabManager.modifyQueryTabs(TCQueryTabManager.java:306)
     at com.businessobjects.wp.tc.query.TCQueryPanel.modifyQueryTabs(TCQueryPanel.java:310)
     at com.businessobjects.wp.tc.query.TCQueryPanel.load(TCQueryPanel.java:383)
     at com.businessobjects.wp.tc.TCMainPanel.switchToQueryPanel(TCMainPanel.java:563)
     at com.businessobjects.wp.tc.TCMainPanel.actionPerformed(TCMainPanel.java:506)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at com.jidesoft.plaf.basic.BasicJideButtonListener.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
     at com.businessobjects.wp.cpi.CPIConnection.postRequest(CPIConnection.java:441)
     at com.businessobjects.wp.xml.XMLViaHttp.loadScript(XMLViaHttp.java:144)
     at com.businessobjects.wp.xml.XMLViaHttp.getPromptList(XMLViaHttp.java:1284)
     at com.businessobjects.wp.xml.XMLLoader.getPromptList(XMLLoader.java:279)
     at com.businessobjects.wp.om.OMQuery.loadPromptsAndContexts(OMQuery.java:359)
     at com.businessobjects.wp.om.OMQuery.getActiveContextCount(OMQuery.java:384)
     at com.businessobjects.wp.tc.query.TCQueryPropertie.buildQueryContextFromUI(TCQueryPropertie.java:496)
     at com.businessobjects.wp.tc.query.TCQueryTab.buildQueryContextFromUI(TCQueryTab.java:846)
     at com.businessobjects.wp.tc.query.TCQueryTab.modifyQueryProperties(TCQueryTab.java:638)
     at com.businessobjects.wp.tc.query.TCQueryTabManager.modifyQueryTabs(TCQueryTabManager.java:306)
     at com.businessobjects.wp.tc.query.TCQueryPanel.modifyQueryTabs(TCQueryPanel.java:310)
     at com.businessobjects.wp.tc.query.TCQueryPanel.load(TCQueryPanel.java:383)
     at com.businessobjects.wp.tc.TCMainPanel.switchToQueryPanel(TCMainPanel.java:563)
     at com.businessobjects.wp.tc.TCMainPanel.actionPerformed(TCMainPanel.java:506)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at com.jidesoft.plaf.basic.BasicJideButtonListener.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Please let me know what the solution is.

Matt,
A namesake of yours is my client for this issue.
Coming to the problem, the customer says there is proxy configured between HTTP server and WebSphere. This proxy server times out for long running reports. If the HTTPServer is bypassed, things work fine.
A colleague of mine opened a case with BOBJ. I can get you the case# if you need it. We got this reply:
From: Takano, Hitomi
Sent: Tuesday, November 04, 2008 10:26 AM
Hi Matt,
I was away for the last two days, so I couldn't reply to you sooner.
Extending the timeout setting from Webi and Infoview in BOXI R2 will not
make the long running reports work as your proxy setting at the lower
layer than BOXI just allows 5 minutes and after that the connection will
be cancelled by the proxy. I'm not sure why this setting was effective
for https only or timeout out after 2 min. This is out of scope of BOXI
R2 and your network admin would be the best person to handle. You were
getting 502 error in Java Report Panel. I googled with "502 error and
ProxyTimeout", and I got the some articles returned which say when
backend doesn't answer on requests(because it timed out), it returns to
a client an error 502.
I'll close this thread as the n/w admin at the client are working things out.
Thanks for your support.

1st gen iPod Touch, old app no longer runs

I have a first generation iPod Touch, version 3.1.3. About a year ago I bought an app, "Converter Plus (Universal)", and it worked fine until recently when I received notice of an update. There were a few app updates and all loaded successfully except the Converter Plus (Universal) which gave me an error message that the software I have does not support the updated app. I understand and accept that my old iPod Touch does not support most (almost all) new apps. The problem, however, is that the old Converter Plus (Universal) app that worked fine for a year no longer runs. I try to open it, the initial screen pops up but shuts down right away. I can only assume that when the recent update was attempted but failed it somehow messed up the old app. Is there any way to restore the old version of the app so I can go back to using it? The app only cost $1.99 so it is hardly the end of the world if I cannot use it any more, but I am worried all my other older apps (some of which receive regular updates) might also stop working and that just seems wrong to me. Feels like I am being robbed. Thanks for any suggestions.

Try:
- Reset the iPod. Nothing will be lost
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Try deleting the version of that app that is in your iTunes library. Then do the following:
iTunes Store: Transferring purchases from your iOS device or iPod to a computer
Then delete the app from your iPod and sync the app back to your iPod and see if it works.
- Next try restoring from backup. Make sure that all the apps that are compatible with 3.1.3 are in your iTunes library so they can be synced back as part of the restore from backup.
- Last, restore to factory settings/new iPod and sync your media to the iPod.

We have two users that have been using Creative Cloud for almost a year. Recently, sometime in the last 4ish weeks, the users can no longer run Creative Cloud apps. (Yes, our subscription is paid.) Error simply says administrator access is required

We have two users that have been using Creative Cloud for almost a year. Recently, sometime in the last 4ish weeks, the users can no longer run Creative Cloud apps. (Yes, our subscription is paid.) Error simply says administrator access is required to install. The apps have already been installed. The users cannot run them unless they are in the local admin group.Using "Run as admin" does not work. It gives the same error.
I have opened a case with adobe support and was basically told to suck it up and put the users in the admin group. Actually, what was said was that it is "mandated that the users have administrative rights".
There are a couple of things wrong with this. It was working for both users until recently - a recent required creative cloud update. The users have never been local admins yet the apps were working (poorly, but working).
We are in an enterprise environment and users simply do not have administrative rights on the computers.
I have changed permissions on all adobe folders, granting users or authenticated users modify or full control rights, did the same in whatever Adobe registry HKLM keys I could find. Nothing has allowed the users to run the apps - unless they are put in the local admin group.
Someone has to have a fix for this. Adobe apps have proved to have far too many vunerabilities to even entertain the idea of elevating user rights. I can't imagine that enterprise environments are allowing this.
Any help or suggestions are greatly appreciated.

Jeff,
Thank you for your response. The users in question are "standard" domain users. We do not reduce users permissions below the standard level.
The apps do not load with their current standard user permissions.
The thing that makes this odd, is that up until recently they did this issue with cloud apps. The only way I can make it work for them now is to put them in the local administrator group on their pc's - which is not going to happen.
This is what they now see. As I said before, this was not a problem up until recently they would see all their available apps. If I put them in the local admin group the apps are listed without having to install. Everything is there, just not accessible to the user.

Long running DBAdapter partnerlink activities (transactions)

Hello,
I try to use nonBlockingInvoke = true for long running DBAdapter partnerlink activities,
but i'm not succesfull.
In BPELConsole the activity seems to be running, but there is an entry
in Manual Recovery > Activity TAB and OraBPEL~OC4J_BPEL~default_island~1
log says:
<2006-02-10 09:32:05,130> <INFO> <test.collaxa.cube.ws> <AdapterFramework::Outbound> file:/ora/app/oracle/product/bpel/integration/orabpel
/domains/test/tmp/.bpel_ZalozeniObjednavky_1.2.jar/ZapisObjednavky.wsdl [ ZapisObjednavky_ptt::ZapisObjednavky(InputParameters) ] - Using
JCA Connection Pool - max size = <unbounded>
<2006-02-10 09:32:05,390> <ERROR> <test.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube engine": Callback in
vocation failed.
An attempt to invoke the method "handleCallback" on the performer "bpel.p0.BPEL_BIN$$BPELC_BpInv0" failed. The reported exception is: "".
Please ensure that the signature of the method "handleCallback" is: ( IWorkItem, ICubeContext ).
<2006-02-10 09:32:05,406> <ERROR> <test.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ...
exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.CallbackInvokerMessage";
the exception is: Callback invocation failed.
An attempt to invoke the method "handleCallback" on the performer "bpel.p0.BPEL_BIN$$BPELC_BpInv0" failed. The reported exception is: "".
Please ensure that the signature of the method "handleCallback" is: ( IWorkItem, ICubeContext ).
Does anybody succeed with nonBlockingInvoke = true on DBAdapter partnerlink?
I use BPEL 10.1.2 patch02
Thank you
Karel

Hi Jon,
 
 
You can set the maxConnections which represents the Maximum number of connections in the pool in oc4j-ra.xml.
Please refer to the section Oracle Application Server Adapter for Databases in Oracle® BPEL Process Manager Developer's Guide
for more information.
 
 
Aruna

Long running threads (Jasper Reports) and AM-Pooling

Hi,
we are developing quite large application with ADF an BC. We have quite a lot of reports generated through Jasper that take quite long time to complete. The result is a PDF document that user gets on the UI so he can download it over download link. Reports that take over an hour to finish are never completed and returned to the user on UI. I think the problem is in AM-Polling because we are using default AM-Polling settings:
<AM-Pooling jbo.ampool.maxinactiveage="600000" jbo.ampool.monitorsleepinterval="600000" jbo.ampool.timetolive="3600000"/>
The AM is destroyed or returned to pool before reports finishes. How to properly configure those settings that even long running threads will do there jobs to the end.
We also modified web.xml as follows:
<session-config>
<session-timeout>300</session-timeout>
</session-config>
Any help appreciated.
Regards, Tadej

Your problem is not related to ADF ApplicationModules. AMs are returned to the pool no earlier than the end of request, so for sure they are not destroyed by the framework while the report is running. The AM timeout settings you are referring to are applicable only to idle AMs in the pool but not to AMs that have been checked out and used by some active request.
If you are using MS Internet Explorer, then most probably your problem is related to the IE's ReceiveTimeout setting, which defines a timeout for receiving a response from the server. I have had such problems with long running requests (involving DB processing running for more than 1 hour) and solved my problem by increasing this timeout. By default this timeout is as follows:
IE4 - 5 minutes
IE5, 6, 7, 8 - 60 minutes
I cannot find what the default value is for IE9 and IE10, but some people claim it is only 10 seconds, although this information does not sound reasonable and reliable! Anyway, the real value is hardly greater than 60 minutes.
You should increase the ReceiveTimeout registry value to an appropriate value (greater than the time necessary for your report to complete). Follow the instructions of MS Support here:
Internet Explorer error "connection timed out" when server does not respond
I have searched Internet for similar timeout settings for Google Chrome and Mozilla Firefox, but I have not found anything, so I instructed my customers (who execute long-running DB processing) to configure and use IE for these requests.
Dimitar

Web.Show_Document does not work with long running reports

I am using Web.Show_Document() to call reports from Forms. Everything works fine for smaller reports. However for long running reports I do not get the output instead get the page "This page cannot be displayed.". On checking the job status on the report server I find that report is still running and completes after some time but by that time my http request has already timed out. What configuration do I have to change to make my long running reports work.
Thanks

So, looks like this is an IE issue. I need to add the form server site to my list of Trusted Sites. Once I did that, everything started to work fine. Thought I'd share in case anyone is really interested.....

Script to kill long running reports in OBIEE

Hi
I have requirement to kill long running reports . I am using OBIEE version 10.1.3.4.0 which has a bug where it is not taking query limits governor and the reports are not getting killed if i am setting that parameter in RPD.
Oracle support has advised me to upgrade to next version, but for now, i cannot upgrade.
Can anyone suggest me script to run on obiee app server that can kill long running reports on obiee and database server.
I have AIX server and all reports run on database with same functional ID that is being used for ETL as well to Analytics database.

Shikhs17 wrote:
Hi
I have requirement to kill long running reports . I am using OBIEE version 10.1.3.4.0 which has a bug where it is not taking query limits governor and the reports are not getting killed if i am setting that parameter in RPD.
Oracle support has advised me to upgrade to next version, but for now, i cannot upgrade.
Can anyone suggest me script to run on obiee app server that can kill long running reports on obiee and database server.
I have AIX server and all reports run on database with same functional ID that is being used for ETL as well to Analytics database.Do you want to enforce the limitation on the database to automatically kill running sessions that run over specific period of time?

Long running reports using java servlets

Hello,
I'm running into a problem using java servlets to produce database reports and sending them back to the client browser as excel or html. The problem comes into play when the user has submitted two reports then goes to run a third and the browser hangs. I realized now that this is because of the two active connections that the user already has to the app server. Does anyone have any suggestions on how to get around this? I'm trying to now write the report to the server, and provide the browser with a url, but it seams as though the connection isn't totally closed even though I close the response printwriter.... Any suggestions would be greatly appreciated....

Unfortunately I dont have an answer to your question, but:
If the reports are large/long running, should they be generated on demand? You could schedule the reports to be generated every day, month or whenever appropriate, stored on the server and then quickly pulled by the user whenever needed.

Long Running Reports

I'm now writing some reports that are slow running. I've tuned the sql, however because the volume of data being returned and the complexity of the report queries the reports will likely never run faster then ~30 seconds.
I'm using the ApEx advanced reporting (BIP) and ApEx version 3.0.1.
What are some thoughts on how to best implement long running reports?
Thanks,
Todd
Message was edited by:
tfa

Hi Dimitri,
You asked...
What happens when you run the report directly from BI
Publisher?There are several reports from one application. I've run the report queries in OEM SQL Tuning Advisor and tuned them.
I have not seen a noticeable difference in run times between submitting the reports from APEX or running them from BIP. The queries for these reports have the same run time when run through SQL Developer.
The slow run time of the report queries can be traced to poor table design. The application is a bit of legacy application with the front end now being rewritten using APEX. The poor table design issues are magnified by the volume of data. I have plans to partition one of the transaction tables.
Prior to rewriting the user interface in APEX the application was written in Oracle Forms. When written in Forms the application was a bolt-on to the Oracle applications. In that environment users could submit reports to the run in the background (via Concurrent Manger) then the report output was viewed later following the completion of the report.
I'm pursuing a similar solution as the concurrent manager in Oracle applications but available in the APEX, BIP environment. The reports do run between 30 seconds to 1 minute which is to long for the users to wait on the submitting page. Any thoughts on how it is possible to run these long running reports without tying up the user’s page?
I'll investigate dbms_scheduler and BIP APIs. I know BIP also has a scheduler available but I do not know much about it.
Thanks,
Todd

Long running reports end successfully - present s "page can not be found"

Long running reports and browser timeouts - page can not be found"
We are launching Oracle 9i Reports from a Portal 9ias (release 9.0.2.2) system. We are in production with about 100 users. It is not going well with respect to Report problems.
We have the following problems:
1) hanging reports,
2) reports where parameter screens will not present due to large LOV on parameter screen,
3) and the most aggravating problem is "Page can not be found" presented to user when in fact the report ran successfully and create a .pdf.
We are at our wits end with Oracle Support and the Oracle Portal and Reports product.
As I said, I am launching Oracle Reports 9i from a Portal 9.0.2.2 application. I have several long running reports that complete successfully but return to the user an error "Page can not be found". Meta-link Note: 189454.1 suggests a modification to ReceiveTimeout parameter in the pc registry. We set the ReceiveTimeout parameter to 7200000. This did not solve the problem. Users still receive "Page can not be found".
Is there a report server side setting that we must set also ... or some other setting we should check?
I need to solve this issue. Is there someone out there that can help? Are there other people having similar Oracle Reports issues? According to Oracle Support we are the only people with these issues. Are we?

1) If you can reproduce the Reports Hanging issue consistently you can push Oracle Support to file a bug.
2) I am not sure about this now, but again you can take this to Oracle Support and push for resolution.
3) There are some problems with IE - Adobe integration. This is not a Reports bug. You can try
(a) Switching off Adobe - web integration in Adobe Acrobat reader settings, so that Adobe will not automatically open pdf file in web. Instead a dialog will be shown as to which application to open the pdf file or save it to disk and user can save the file to disk and open.
(b) Use IE latest version. (or some other browser like Netscape )
[ You can roll back the ReceiveTimeout param change you made to see the impacts one at a time ]
1) To confirm that this is a Adobe - IE pdf problem run the same report to htmlcss, rtf. If these come fine, then we can ascertain that this is Adobe - IE issue.
2) Give http://host:port/reports/rwservlet/showjobs?server=server_name. You can see all the jobs and their jobids. For the concerned jobs you can click and see whether output is actually generated or not.
Thanks
The Oracle Reports Team
The statements and opinions expressed here are my own and not that of my employer

SAP R/3 Transports : How to handle long pending transports ?

How to stop active transport process?
Hi.
Generally we transport only one TR at a time.
If we find that any transport is stuck for any reason.
How do we resolve this.
When we tried to delete the Long pending transport entry, it says, long text not found.
The problem is, we started one transport. It got stuck for more than 30 min.
and when we tried to delete the entry it was giving some error of long text not found.
We tried to start another. And it also got stuck.
How do we really handle such issues of transports.
Though, one could say, restart of server, is the only option because there is nothing much can be done when the transport is done, one at a time, as a practice.
Can sap not handle requests - one by one, even if the practice is to transport one TR at a time .
Why is the system getting confused and blocks further transport requests too.
Can anyone advise.
Thanks
indu

How to stop active transport process?
Hi.
Generally we transport only one TR at a time.
If we find that any transport is stuck for any reason.
How do we resolve this.
When we tried to delete the Long pending transport entry, it says, long text not found.
The problem is, we started one transport. It got stuck for more than 30 min.
and when we tried to delete the entry it was giving some error of long text not found.
We tried to start another. And it also got stuck.
How do we really handle such issues of transports.
Though, one could say, restart of server, is the only option because there is nothing much can be done when the transport is done, one at a time, as a practice.
Can sap not handle requests - one by one, even if the practice is to transport one TR at a time .
Why is the system getting confused and blocks further transport requests too.
Can anyone advise.
Thanks
indu

Long Running Transport in BI

Similar Messages

Maybe you are looking for