Processing overdue issue

Hi All,
we are facing an issue while loading data to PSA from R/3. There is huge amount of data getting extracted from R/3, But after some 20 datapackages are extracted the load gets fail and the error occured is Processing overdue. when we see in the source system we can see the extracting job to be in active state. Even when we tried reducing the variant size to a period level , we are facing this Process over due error.Can some one help in understanding this issue also suggest some solution for the same.
Thanks,
Archana

Hi,
there are lots of reason for this failure....
processing overdue error occurs when there is huge volume of data need to be extracted to BW system.which will occupy all the system resource and which may lead to dead locks or may decrease the performance of other loads.
You are getting the error as there is huge volume of data in ECC.
its a good practice to Split the load using multiple selection.
Check the source system job is active or finished?
Check the iDocs or TRFCs got stuck from source.
Check if there are any short dumps in source system and Bw system
If the source system job is finisehd then check if there are any failed TRFCs from source, if any try to find that are related to this load and try to flush them manually (select the TID -->press F6).
Also check the below thread
processing overdue problem
Contact BASIS person n ask them to check the system logs n temp table spaces and any thing unusual at the source system level.

Similar Messages

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

Process Overdue

Hi i am loading transaction data and there was no psa and it was directly updating Infocube.I got an error like Process overdue and in the details tab we have like this ..
Short dump in the Warehouse
Diagnosis
The data update was not completed. A short dump has probably been logged in BW providing information about the error.
System response
"Caller 70" is missing.
Further analysis:
Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
Error correction:
Follow the instructions in the short
then i deleted the bad request and tried to reload manually but it the status of this job is in scheduled since 3 hrs now with my username...(Sm37) so what will be the reasin?
Thanks for replies

Your job doesn't have a higher priority, may it has class C and right now the process is executing job class A and B that is the reason your job is just scheduled for more than 3hrs. I don't know if you have access to change the job class in your system, if you do, you could change the job class to A. Otherwise, most likely the operations or basis will have access to change the job class so you can request them by giving them the job name.
thanks.
Wond

How to solve Caller 70 Missing-Processing overdue

Hi Folks,
Plz tell me how to rectify Processing overdue error which i m getting during data loading from PSA to Data Target.
Thanks
Ranjan Singh

Hi,
processing time for loading is too long.
You can manually book data if all records from source system has arrived into PSA. Just right click on the data packet that was not updated and select "Manual Update".
See the below links.
Short dump in the Warehouse Caller 70" is missing
collor 70 missing
Error :Processing is overdue
GTR

Regarding the process overdue

hello everybody,
i got an error saying that process is overdue.please tell me what shud i do ?
thank you,
madhusudhan

hi,
atually this process overdue error comes only if the transfer of data is taking much time.
go to status tab make the QM status to red .then goto edit->update reversal->readeverything manually.then automatically every thing will be corrected.
regards,
jack

Error: process overdue

hi gurus,
what might be reasons for the error: process over due.
how can we try to solve it?
regards,
Rajesh

Rajesh,
Processing overdue can occur due to several reasons
1. Less number of background processes in BW. Increase the number.
2. Multiple infosources are trying to update one infoprovider.
3. Loading the cube without dropping the Index. Delete index first before loading cube.
4. Tablespace / table extend problem. Check w/Basis person.
5. All source system records have not come into BW and the BW process has time out. Check the timeout settings.
Thanks,
Bharath

Process overdue error asynchronus transmission of info idoc 2 error

Hi
For an r/3 job i am getting the below message and it is not progressing from last 2 days and failing in BW with Process overdue error. Can somebody advise me on this.
data soucrce :0CO_OM_OPA_6
The job stucked for last 10 hrs and showing 0 records in BW.
Thanks
Subbu

Hi,
What are you trying to do...
are you performing any loads from the above said DataSource from R/3 to BW or
are you replicating the DataSource from your source system to BW side...
in any of the above cases..please check whether you have connected well to your source system from your BW system...
for this right click on source system in source system section of RSA1..and check..if everything is fine...then it should take such long time to complete your activity.
if not check in Tcode:SM59 to make sure the connectivity..which your problem can be solved sucessfully...
hope this is clear for you...
Regards
Ramsunder

Process overdue error

Hi all,
How to reslove the process overdue error and TRFC errors.Plz tell me
Rgds
Bharath

HI
Follow these threads
Process Overdue error
error: process overdue
Process is overdue (during dataload)
error like process ovedue in extraction data
Khaja

Processing overdue problem

Hi Friends,
I am doing daily loads , some body did some changes (don't know changes) all loads got failing and the error message is *" processing overdue" . I thought that changed in global settings, I changed the global settings waiting time is 1 day... but still loads are failing in RSMO (Monitor) , when i am doing refresing every load it get chaning status to yelow and successs.
Please help me on this , we have so many process chains unable to do this manully.
Who ever has given correct post will assigned points.
Advance Thanks,
Ramesh..

Process over due may occur due to lots of reasons mainly bcoz
Check whether any Idocs were hanged. Go to sm58 and selct those Idocs and process them manually. Check the RFC also.
unavailability of resources.check the availability of Background jobs
Check if there are any TRFCs or IDOCs got hung... check for the dumps in the ST22 tcode.
Check the Source system connectivity.
Try to reduce the package size and load the data once again.You can specify, the selection condition and create several InfoPackages to load all data. You also need to ensure that your datapacket size is optimal.
Check in table ROOSPRMS table and update the MAXSIZE, STATFRQU, MAXPROCS and MAXDPAKS values accordingly.
This table will help u to overwrite current system settings for data transfer process.
If there are any dumps in ST22, can you post the dumps.
Edited by: prashanthk on Aug 31, 2010 11:09 AM

Processing overdue error when loading master data

Hello,
While loading data for master data infoobject, i'm getting peculiar error like processing overdue. what might be the problem.
Please respond as soon as possible it is very urgent.
REGARDS,
SRINIVAS OLETI

hi,
is this your first upload ? the rfc connection to source system is established well ?
try to check in monitoring
- tab 'status', click step by step analysis, what's the status of 'RFC to source system success ?' grey ?
- transaction st22 and sm21, any message ?
- check menu 'environment' - shortdump - in datawarehouse, check for source system also, then transaction rfc, ale management, system log ...

Process overdue error:Idocs inflow BW

Hi All,
When we are scheduling an infopackage we are encountering an error as "Process is overdue" and also says Idocs inflow BW.In the status tab we are finding the following details:
Non-updated Idocs found in Business Information Warehouse
Diagnosis
IDocs were found in the ALE inbox for Business Information Warehouse that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
When we go to <b>Detail tab</b> we found red status in the extraction itself as:
Extraction (messages): Missing messages
If we are going for manual updation of the IDOCs by process manually we get :Data packets were found that have not yet been read
Data packets have to be processed manually
and finally we recieve a message as
You can only process data idocs in simulated form in warehouse.
How to go about resolving this issue.

Hi,
Try this
solution to these kind of problem is to use your mouse to click on every possible drill down field/line
You can use We05/We02 ..a lot many other Xns to see the status and actual error message associated.
But as I said use drill down & find the real error.
Re: ALE IDOC inbound processing
Regards
Siddhu
Message was edited by: sidhartha

Outbound BPEL Process deployment Issue in SOA (binding.jca-12600)

Hi,
I have Designed an Outbound BPEL Process for Siebel CRM Service Integration using Jdeveloper (11.1.1.3.0). After that I am facing the deployment issue of this application in SOA suite (11.1.1.6.0). Following is the deployment.log status in jdeveloper:-
[10:57:54 AM] ---- Deployment started. ----
[10:57:54 AM] Target platform is (Weblogic 10.3).
[10:57:54 AM] Running dependency analysis...
[10:57:54 AM] Building...
[10:57:58 AM] Deploying profile...
[10:57:58 AM] Wrote Archive Module to C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Deploying sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:57:58 AM] Processing sar=/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Adding sar file - C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Preparing to send HTTP request for deployment
[10:57:59 AM] Creating HTTP connection to host:10.10.22.81, port:7001
[10:57:59 AM] Sending internal deployment descriptor
[10:57:59 AM] Sending archive - sca_QueryWithView_Invoke_rev1.0.jar
[10:58:00 AM] Received HTTP response from the server, response code=500
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] HTTP error code returned [500]
[10:58:00 AM] Error message from server:
#;There was an error deploying the composite on AdminServer: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
#;: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
[10:58:00 AM] Check server log for more details.
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] #### Deployment incomplete. ####
[10:58:00 AM] Error deploying archive file:/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
And the following is the SOA Server Side log file status:-
####<Jun 3, 2013 10:36:05 AM AST> <Info> <Health> <HOSADDAT02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-00000000000000f4> <1370244965280> <BEA-310002> <36% of the total memory in the server is free>
####<Jun 3, 2013 10:36:12 AM AST> <Error> <ServletContext-/soa-infra> <HOSADDAT02> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-000000000000182b> <1370244972343> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
{rootCauses=[]}
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy314.load(Unknown Source)
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: BINDING.JCA-12600
Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterBindingConfig.addAdapterReference(AdapterBindingConfig.java:206)
     at oracle.integration.platform.blocks.adapter.AdapterReference.setupAdapterReference(AdapterReference.java:506)
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:425)
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy314.load(Unknown Source)
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Kindly help me in this regard

Solution:
Workaround the issue immediately by removing the "ns1:" qualification on the operation for the binding.jca entry in the composite.xml and redeploying.
For example:
From:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="ns1:BAPI_COMPANYCODE_GETDETAIL"/>
To:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="BAPI_COMPANYCODE_GETDETAIL"/>
Regards,
Shaheer Badar

SAP BI 7 - Background process performance Issue

This question is about efficiency of dialog process compared to inefficiency of the background process and I want suggestions from SAP Basis/BI experts on this.
We have observed that our background processes on BI server are not running as efficiently as we would like them to run.
For example
DSO activation:
When I use Dialog mode for DSO Activation with 3 parallel processes, I can activate a certain DSO with in 15 seconds. But the same DSO and the same data package when activated using background mode with 3 parallel process takes about 15 minutes.(there are plenty of background processes available on the system when this activation is running). So dialog process runs 60 times faster than background process.
In BI 7 most of the operations can be executed only in the background parallel mode. And from the activation example we know that our background processes are not as efficient as dialog processes. It
is understood that in general the background processes will not be as efficient as dialog processes, but in our case the difference is a factor of 60. We want help to identify, why the background processes are not as efficient as dialog processes. What SAP Basis settings need to be changed to make them as efficient as we can. Any suggestion or help will be highly appreciated.

Hello Eswaran
Generally a dialog process is not faster by any means than a background workprocess. Nevertheless i trust you on your observations, so there must be some difference. I just did a small test, i ran SE16 chose a big table and selected 10000 rows, i did 3 tries in dialog and 3 in background. The results:
dialog: 10.2s, 9.4s, 9.6s
background: 26s, 24s, 24s
So even in my simple example the background execution took more time. The issue here is, that the resulting output (which is pretty large) had to be saved additionally in a spool (a total of 167 pages) when executed in background. The selection of the data certainly did not take more time in either case.
The most important difference between dialog and batch processes is the memory management. Dialog processes work with a shared memory segment (extended memory). Background processes have their private heap memory.
Nevertheless, background processes are not "slower" in general, not at all. You will need to observe closer, what your processes are doing. Maybe watching SM50 while running the DSO activation is enough to see it, maybe you need to trace a process. If you see large spools generated, or huge amounts of memory consumed, we might already have an answer.
Regards
Michael

Supplier Process chain issue

Hello,
We loaded supplier(LSUPPLIER) from ECC to SPM. The data got loaded to PSA and info objects. But when I release the supplier load, the process chain is running for last 7 hours.
We had same issue in QA where it ran for almot 2 days and even after 2 days it did not finish - in fact there was no progress as well. When I checked in SM50, there was a process with sequential read on /BI0/PXALOCSUPP for almost 2 days.
Has anyone faced similar issue and any pointers for this issue?
Regards,
Prasanna

WE have seen this happen if too many of local supplier point to the same cleansed supplier(generally a dummy cleansed supplier). Is that the case for you.
If not then try recuding the package size of the PSA. That might improve performance for you.

Adobe Acrobat Distiller Process. Issue with Font(L0420P not found, using courier)

Hi Everybody,
We are working for upgrade activities, which involves moving applications from Windows 2000 to Windows 2003 Servers.
My applications uses Adobe Acrobat distiller, which is also getting upgraded along with the server from Adobe 4.0 to 5.0 (Installed licensed Adobe distiller).
I have been using Adobe distiller to convert .PS files into .PDF files. The conversion process requires the PSFonts such as (MB006, L0B, L0420P etc..), each font got a separate PFB and PFM extension files, which are kept in the folder name called "Psfonts" and has been included in "Font location" under Distiller settings.
Using Distiller( Adobe Acrobat distiller 4.0 ) in Windows 2000 didn't create any issues or error while converting .PS files into .PDF files, all the PDF files are generated by Distiller as expected and process without any Font issues.
In Windows Server 2003, I installed Adobe Acrobat distiller 5.0 and moved the Font Folder "Psfonts" from older server(Windows 2000 server) to the new server(Windows 2003) and started Adobe Acrobat distiller process(5.0) to convert .PS to .PDF, most of the .PS files gets converted into .PDF files but when .PS files which require the Font L0420P comes in for Distilling, it displays an error message as "L0420P not found, using courier".
I checked with the old Server's (Windows 2000) font folder (Psfonts), it has the same files(PFB and PFM) as present in the new Server(Windows 2003).
I tried to check the Particular Font name(L0420P) in Distiller-->Setting-->Job options-->Font-->Embedding-->Psfonts, but L0420P font alone is missing in the List.
Could you please help in resolving this Font issue.

You may like to try deleting the PsFonts entry from distiller and closing it. Restart the machine, make the entry of PSFonts agina and try creating PDF.

Processing overdue issue

Similar Messages

Maybe you are looking for