Execution of mapping gets hanged in OWB Deployment Manager

Description:
Scenario - 1
1. Source schema (rapid) to staging schema (radar01)
We have a few mappings where we need to load data from the source to target. These mappings are successfully validated, deployed and executed.
Both schemas reside in same database.
Scenario - 2
2. Staging schema (radar01) to Warehouse schema (radar02)
We have a few mappings where we need to load from staging to warehouse.
Please note the staging schema here is a target schema in the scenario-1 and in scenario - 2
It is the source. The mappings where successfully validated, but a warning message is displayed while deploying.
Warning:
VLD-2771: System privileges may not allow extraction from source STG_ULD.
Skipped the warning and then executed, Till 22nd the mapping was getting executed and data was getting loaded into the target schema from staging.
From 22nd onwards, while executing these mappings, execution remains hanged forever
Runtime Audit Browser:
In Runtime Audit Browser shows the status for the above mappings as BUSY
Actions Taken:
1. Purged all previous mappings
2. Analysed all the runtime repository tables.
3. Purged the BUSY status mappings also by using the procedure.
4. Grants given (SELECT ON) on all the staging schema tables to warehouse schema.
5. Restarted the database.
Even after the above actions also the problem has not yet been solved. Kindly suggest us how to go about.
Environment:
OWB 10g Client - 10.1.0.2.0
OWB 10g Repository - 10.1.0.1.0
Workstation OS - Windows XP
Oracle database - 9.2.0.1.0
Database server installed on Unix OS (Solaris)

May be you would like to check at the database of what exactly is getting executed. Just check if there is a query running on either source or target objects. If this is a case then you would like to grab it and optimize the same.
If this is not a case then it could be that the mapping is waiting for some locks.

Similar Messages

Executing Process Flow from OWB Deployment Manager results in RPE-01008

Hi,
I'm using OWB 10.1.0.1.0 (10g) and just installed Oracle Workflow Server 2.6.3.
I can build, validate and generate Process Flows just fine. But every time I try to execute a Process Flow using OWB Deployment Manager, I'm getting a "RPE-01008: Recovery of this request is in progress". Execution of deployed Process Flows using Oracle Workflow Interface works just fine.
Anyone has an idea?
Thanks and regards
Andreas Kopp

Hi Dirk-Jan,
youÃre right, there are some ugly-looking NUllPOinterExceptions in that log file. However, I cannto interpret them:
2005/05/02-13:30:04-CEST [97A560] AuditId=80916: Processing execute request
2005/05/02-13:30:05-CEST [97A560] Free Memory(bytes)=49410200 Total Memory(bytes)=66715648 Used Memory(bytes)=17305448
2005/05/02-13:30:05-CEST [F1DD49] Initializing execution for auditId= 80916 parentAuditId= null topLevelAuditId=80916 taskName=TEST
2005/05/02-13:30:05-CEST [F1DD49] Attempting to create adapter 'class.RuntimePlatform.0.NativeExecution'
2005/05/02-13:30:05-CEST [F1DD49] Attempting to create native operator 'class.RuntimePlatform.0.NativeExecution.ProcessFlow'
2005/05/02-13:30:05-CEST [F1DD49] java.lang.NullPointerException
     at java.lang.String.<init>(String.java:166)
     at oracle.sql.CharacterSet.AL32UTF8ToString(CharacterSet.java:1378)
     at oracle.jdbc.driver.DBConversion.CharBytesToString(DBConversion.java:527)
     at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:621)
     at oracle.jdbc.driver.T2CCallableStatement.execute_for_describe(T2CCallableStatement.java:846)
     at oracle.jdbc.driver.T2CCallableStatement.execute_for_rows(T2CCallableStatement.java:1007)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1028)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2888)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:2960)
     at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(OracleCallableStatement.java:4124)
     at sqlj.runtime.ExecutionContext$OracleContext.oracleExecuteUpdate(ExecutionContext.java:1556)
     at oracle.wh.runtime.platform.operator.owf_process.NativeOWFProcessOperator.defineProcessFlow(NativeOWFProcessOperator.java:1029)
     at oracle.wh.runtime.platform.operator.owf_process.NativeOWFProcessOperator.executeDefault(NativeOWFProcessOperator.java:476)
     at oracle.wh.runtime.platform.operator.owf_process.NativeOWFProcessOperator.execute(NativeOWFProcessOperator.java:227)
     at oracle.wh.runtime.platform.adapter.rtp.NativeExecutionAdapter.execute(NativeExecutionAdapter.java:43)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:63)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:23)
     at oracle.wh.runtime.platform.service.ExecutionManager.run(ExecutionManager.java:36)
     at java.lang.Thread.run(Thread.java:534)
2005/05/02-13:30:05-CEST [F1DD49] Initializing execution for auditId= 80916 parentAuditId= null topLevelAuditId=80916 taskName=TEST
2005/05/02-13:30:05-CEST [F1DD49] oracle.wh.runtime.platform.service.controller.RecoveryInProgress: RPE-01008: Recovery of this request is in progress.
     at oracle.wh.runtime.platform.service.controller.AdapterContextImpl.initialize(AdapterContextImpl.java:1307)
     at oracle.wh.runtime.platform.service.controller.ExecutionContextImpl.initialize(ExecutionContextImpl.java:789)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.initialize(ExecutionController.java:32)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:50)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:76)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:23)
     at oracle.wh.runtime.platform.service.ExecutionManager.run(ExecutionManager.java:36)
     at java.lang.Thread.run(Thread.java:534)
2005/05/02-13:30:05-CEST [F1DD49] Attempting to create adapter 'class.RuntimePlatform.0.NativeExecution'
2005/05/02-13:30:05-CEST [F1DD49] Attempting to create native operator 'class.RuntimePlatform.0.NativeExecution.ProcessFlow'
2005/05/02-13:30:05-CEST [F1DD49] Native execution operator initiating recovery by recoverable operator oracle.wh.runtime.platform.operator.owf_process.NativeOWFProcessOperator
2005/05/02-13:30:05-CEST [F1DD49] report_execution_result auditId=80916
2005/05/02-13:30:05-CEST [F1DD49] java.lang.NullPointerException
     at java.lang.String.<init>(String.java:166)
     at oracle.sql.CharacterSet.AL32UTF8ToString(CharacterSet.java:1378)
     at oracle.jdbc.driver.DBConversion.CharBytesToString(DBConversion.java:527)
     at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:621)
     at oracle.jdbc.driver.T2CCallableStatement.execute_for_describe(T2CCallableStatement.java:846)
     at oracle.jdbc.driver.T2CCallableStatement.execute_for_rows(T2CCallableStatement.java:1007)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1028)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2888)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:2960)
     at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(OracleCallableStatement.java:4124)
     at sqlj.runtime.ExecutionContext$OracleContext.oracleExecuteUpdate(ExecutionContext.java:1556)
     at oracle.wh.runtime.platform.operator.owf_process.NativeOWFProcessOperator.defineProcessFlow(NativeOWFProcessOperator.java:1029)
     at oracle.wh.runtime.platform.operator.owf_process.NativeOWFProcessOperator.executeDefault(NativeOWFProcessOperator.java:476)
     at oracle.wh.runtime.platform.operator.owf_process.NativeOWFProcessOperator.execute(NativeOWFProcessOperator.java:227)
     at oracle.wh.runtime.platform.adapter.rtp.NativeExecutionAdapter.execute(NativeExecutionAdapter.java:38)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:63)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:76)
     at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:23)
     at oracle.wh.runtime.platform.service.ExecutionManager.run(ExecutionManager.java:36)
     at java.lang.Thread.run(Thread.java:534)
2005/05/02-13:30:06-CEST [97A560] Free Memory(bytes)=49283952 Total Memory(bytes)=66715648 Used Memory(bytes)=17431696
2005/05/02-13:30:06-CEST [97A560] AuditId=80916: Request completed
Any idea?
Thanks an regards
Andreas

Executing OWB generated code outside OWB deployment manager

We are thinking to develop data loading programs using OWB but ship the generated code directly to user. We're looking at possibility to let end-user to invoke generated mappings w/o installing OWB. Because we plan not to offer customization to our users in our first release, there is no point to make OWB a mandatory pre-requisite.
Other than running mappings from OWB deployment manager and OEM, could user execute mapping code from something like SQL plus and eBizSuite's concurrent program? My guess is yes.
Then what is the minimum installation requirement for end-user to perform. Does user have to install run-time repository and target schema from OWB installation CD?
Thanks a lot!

Jerry,
There are several alternatives for running OWB mappings in addition to Deployment Manager:
1. From SQL Plus. Requires no part of OWB install to work, it just connects remotely to Runtime repository. See template in [OWB install Home]/owb/rtp/sql/sqlplus_exec_template.sql
2. From OEM. Same: requires no part of OWB install, connects remotely to Runtime repository. See template in [OWB install Home]/owb/rtp/sql/oem_exec_template.sql. Also see "Oracle9i Warehouse Builder User's Guide
Release 9.2", page 13-19, "Scheduling Mappings and Process Flows".
3. From Oracle Workflow. OWB Deployment Manager deploys into Workflow in this case.
4. From any XPDL complaint process flow engine.
Nikolai

Error RTC-5346 in registering target location in OWB Deployment manager.

Hello!
Dear experts, I've got DB 10GR2 and I downloaded OWB 10.1. I've installed OWB successfully and began to look through the samples. And during my trying to register a target location (when I looked through the sample "Deploying targets") Ive got an error : RTC-5346 :the oracle database location 10.1 is not equal to target version 10.2. As I mentioned before, my DBs version is 10.2 and OWBs version is 10.1. May be it is the matter?
So, what would you suggest me in such a situation? Do I have to fulfill any patches or something like that?
Thanks in advance,
Alexey.

Detlef,
your right. Apparently, the information I got only applied to OWB 10g versions 10.1.0.2.0 and 10.1.0.3.0 which are not certified against an DB 10g R2, because of BUG 4537766...
For 10.1.0.4.0 there is indeed no problem.
Grtz.
Philip.
Message was edited by:
[email protected]
Message was edited by:
[email protected]

Tuning Deployment Manager

Folks,
I have been experiencing very slow browsing issues with the OWB deployment Manager Interface. Often it will freeze and every click of a mouse to open an object will occur 5 to 10 seconds later. Did anybody experience the same? and what is the action taken to resole it?
-My laptop and development machine have 1gb of RAM and plenty of storage disk space -40gb...
Any suggestions will be greatly appreciated.
Thanks.

I will re-post the info for a previous post:
Can you verify whether there are any relevant messages in the runtime log files in the <OWB HOME>/owb/log directory?
Also, you might want to increase some of the maximum memory usage for the run-time service. You can do that by editing the -Xms64M -Xmx256M parameters in the <owb
home>\owb\bin\win32\run_service.bat file (if you are on Windows) or <owb home>/owb/bin/unix/run_service.sh for unix platforms. If you have enough memory, I would suggest to put these parameters to -Xms256M -Xmx512M or more.
After that you can stop and start the runtime service by running the scripts in the <owb home>/owb/rtp/sql directory (stop_service.sql and start_service.sql) from the runtime repository schema.
Regards:
Igor

Mapping runs through Deployment Manager but hangs in Process Flow

Hi,
I have a Mapping bound in a simple Process Flow.
The mapping deploys through Deployment Manager and runs. It currently processes no rows and takes a couple of seconds to do that. It completes with a Success message.
However, when I wrap it into a simple Process Flow...
--- w ---> END_WARNING
START ---> MY_MAPPING ---- s ---> END_SUCCESS
--- e ---> END_ERROR
.., deploy this and run it through the Deployment Manager, it hangs. I get the 'Execution in progress...' window with the moving graphic forever.
The Runtime Repository Browser Execution Report tells me that it is 'Busy', and if I drill down to the Process Flow Run Execution Report, I see an identical Start and End Time, an Elapsed Time of 0 seconds, and no other details (Execution Parameters, Activity Details or Error Messages).
Looking under 'Find Processes' on the Workflow Home Page, my workflow has no status in the Process List. Drilling down to the Diagram, I have a green line from the 'Start' element to my Mapping but the Mapping itself has no special colour.
I go back to the Deployment Manager and cancel the job - which it does and reports that it 'Completed with errors'.
The Runtime Repository Browser Execution Report now tells me that it is 'Busy' (with an information bubble), and if I drill down to the Process Flow Run Execution Report, I see different Start and End Times, and Elapsed Time of n seconds, a single Error Message 'RPE-01002: The operation was aborted at user request.', and no other details (Execution Parameters, Activity Details).
Looking under 'Find Processes' on the Workflow Home Page, my workflow has a status of 'Complete' in the Process LIst. Drilling down to the Diagram, I still have a green line from the 'Start' element to my Mapping and the Mapping itself still has no colour and no indication that it has stopped.
I'm running:
Oracle9i EE 9.2.0.5.0
Oracle10g OWB Client 10.2.0.1.0
Oracle10g OWB Repository 10.1.0.1.0
Anybody know how I can go about tracking down why this Process Flow is hanging - and, of course, getting it unhung :-)
Regards
Steve

Hello Steve,
It's a little difficult to read the exact flow from your ASCII graphics.
However, from your description it seems your workflow task only has an outgoing success connector, and your execution was not a success. This will stop the execution of that branch of your process flow, since there are no valid routes to take. If you only have a single branch in your workflow, the process flow is stuck.
To expedite your hung process you just click on the task icon in the Workflow Monitor graph window that does not have a green outgoing connector, press the Expedite button and select skip.
Corollary: If you use conditional connectors, always use all 3 from a task. I not using all 3, have a very good understanding of why you don't.
Regards, Hans Henrik

Owb Process Flow getting hanged/stuck .

Hi,
Problem description :- We have designed a Process Flow in OWB our project. The Process Flow is scheduled to run at 12.00 AM daily Dutch timings.
We have been facing a problem for around 3 months wherein the process gets hanged/stuck in between without giving any specific error message.
There isn't any kind of locking happening in the background as well. The OWB log gives the message "Forcibly deactivating execution with audit ID 1660235 ",
During the time at which the process hangs The process gets hanged in different timings in different sub processes(not in a particular process, so no specific pattern has been observed.)
To complete the process flow, we need to kill the process and rerun it again. When reran, it runs perfectly without any error.
The above error message appears in the log only when a process hangs. There is no such kind of logging during a successful execution.
Can you please let us know when and why does this message appear in the OWB log file.
Is there any specific kind of settings or configuration parameters that needs to be set to resolve this.
Regards,
Rosy Mukherjee

You might want to check to see if you have anything "parallel" running
We recently had an issue with one of our mappings where one day it decided to just stop working and "freeze"
Our DBA found that we had a Oracle hint for "Parallel" in the code and removed it. After that the mapping ran fine.
Best of luck

Deployment Manager hangs during execution

We use OWB 10.1.0.4 with 10G release 2 DB. Everything was working, until recently - the deployment manager hangs while trying to execute any mapping. Deployment of mappings however works well. Also executing the mapping from SQL*Plus works well.
We are not aware of any changes done recently. We tried re-registering all the locations and redeploying all the mappings as well. Execution of mappings leads to core dumps
Here is an example of the core dump and what OWB is trying to, it happens even before the parameter page is displayed which prompts to enter the execution mode, bulk size etc:
RA-07445: exception encountered: core dump [kkosbn()+236] [SIGSEGV] [Address not mapped to object] [0x000000070] [] [] Current SQL statement for this session:
select
parameter_name,
parameter_type,
parameter_kind,
parameter_mode,
is_fixed,
is_required,
parameter_uoid,
default_value
from
wb_rtv_task_parameters
where
task_id = :1
and
(parameter_mode = :2 or
parameter_mode = :3 or
parameter_mode = :4 )
and
(parameter_kind = :5 or
parameter_kind = :6 )
order by
parameter_mode, parameter_name

Hi,
There are atleast two possibilities :
1. If core dump is happening over and over again, then take the trace file and report to Oracle technical support. I had one such case of core dumps where it was later found out to be a oracle bug and a patch had to be applied.
2. If the mapping hangs then there is a high possibility of version mismatch between the location and the actual database. Try to re-regsiter all the locations and deploy all the mappings.
All the best
Regards
-AP

Error when deploying a mapping to Staging in OWB 11gr2

Hi,
I recieve the following error when I try to deploy a simple Source to Stage mapping:
RPE-01012: Cannot deploy PL/SQL maps to this target schema. The target schema must be in the same instance as the Control Center and have the OWB_USER role granted.
I have spent few hours researching it, but have not yet found a solution.
My environment:
DB 11gr2 on Red Hat Linux. (OWB Server is on linux and the same machine as its Repository and the 11gr2 db).
Source is on an Oracle 10.2 DB server in Texas;
Target (Staging env) is in California, also on Oracle 10.2.
I can validate the mapping and the Staging table was deployed sucessfully to the Staging DB.
Do I need to create a repository and workspace on the Target DB (Oracle 10.2) using Repository Assistant? (If that's the case, then would one also need to create OWBSYS?)
Please help.

This is an urgent request. Would appreciate it if someone could point out what I may be doing wrong.
To summarize, my target DB is on Oracle 10.2 in a remote location, so I ran the 3 scripts that OWB Install documents require: Section: Configuring OWB Installed as a Standalone Instance.
Cat_web.sql, reset_owbcc_home.sql, and remote_owb_install.sql.
But, when I run the Repository assistant, I get the error above (asking me to install compatible OWB version.)
Here are the detailed steps:
1. Ran clean_owbsys.sql
2. Ran cat_owb.sql (Against USERS Tablespace)
3. reset_owbcc_home.sql (?? Ora home for Target???)
4. Ran remote_owb_install.sql (??Ora Home for Target???) -- I have tried different combinations, but no difference.
For Repository Assistant, here are the detailed steps:
1. Provide connect info for the remote db (host:Port:Service)
2. Selected "Managed Warehouse Build Workspaces"
3. Selected "Create a new Warehouse Builder Workspace"
4. Select "Create a workspace with an existing user as workspace owner" (Since we have user already defined for this role. Should I create a new one??)
5. Entered Workspace Owner's User Name, Password and created WKS1 as the Workspace.
6. Entered System / and Password to logon
7. Provided Owbsys user id and Password and clicked on Next
8. As soon as I hit Next on the OWBSYS Information screen, I get the error:
"OWB software with the compatible version must be installed locally on the database server machine". If it is installed, acquire the DBA user credentials,
and run the remote_owb_install.sql script on the Oracle Database server machine..."
(I have tried with different paths for the reset_owbcc_home and remote_owb_install scripts)

OWB deploy system error

Hello,
I'm having issues deploying large mappings:
"ORA-04030: out of process memory when trying to allocate 4000 bytes (PLS non-lib hp,pdzdM80_Allocate_Block)"
I'm getting the same error when deploying via either XP Client or OMB*Plus on the server. This started to happen a couple of days ago on a brand new system. On the old system it is still a OK. I CAN get source code for the mapping (package) in question off of the old system and compile it on a new system using SQL*PLUS?!
What could be wrong with OWB install/ setup? Some notes on Metalink suggest that it is purely DB/ HOST issue, but then how come via SQL*PLUS deploy works?
Thanks in advance,
Alex.

Mark
Thank you for your response, I have figure out and I now successfully deploy, I deployed through Deployment Management. But when I go to database as a target and the table is create there but empty, (no data)
I have 2 questions:
1. When I deploy the mapping itself sucessfully, do I need to Execute the mapping ? I tried to right click / Execute then it saying something like this :
Starting Execution COLLEGE_YR_CODES_MAP
Starting Task COLLEGE_YR_CODES_MAP
RPE-1013-SQL_LOADER_ERROR SQL Loader reported error condition, number 3.
Completing Task COLLEGE_YR_CODES_MAP
Completing Execution COLLEGE_YR_CODES_MAP
(college_yr_codes_map is the mapping name, i map a flat file to a relational table)
2. I have to map multi flat files as source file to target as oracle table, do I need to create multi connector for each flat files.
Thank you very much for all the help I can get here.

Getting following error while deploying my webservice on weblogic 10.3

hi
I am tring to deploy a webservice (spring + cxf ) in weblogic 10.3
applicationContext.xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:p="http://www.springframework.org/schema/p"
xmlns:aop="http://www.springframework.org/schema/aop"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:jee="http://www.springframework.org/schema/jee"
xmlns:tx="http://www.springframework.org/schema/tx"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xsi:schemaLocation="
http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd
http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd
http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd">

<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-http-binding.xml"/>
<import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
<context:component-scan base-package="com.persistent.rest"/>
<context:annotation-config />
<jaxws:endpoint
id="accountProcess"
implementor="com.persistent.rest.GetAccountListImpl"
address="/"
bindingUri="http://apache.org/cxf/binding/http" >
<jaxws:serviceFactory>
<bean class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean">
<property name="wrapped" value="false" />
</bean>
</jaxws:serviceFactory>
</jaxws:endpoint>
<bean>...........</bean>
</beans>
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>springCXFWeb</display-name>
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>WEB-INF/applicationContext.xml</param-value>
</context-param>
<listener>
<listener-class>
org.springframework.web.context.ContextLoaderListener
</listener-class>
</listener>
<servlet>
<servlet-name>CXFServlet</servlet-name>
<servlet-class>
org.apache.cxf.transport.servlet.CXFServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>CXFServlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
</web-app>
Getting following error while deploying my webservice on weblogic 10.3
<Dec 4, 2009 2:04:04 PM PST> <Error> <org.springframework.web.context.ContextLoader> <BEA-000000> <Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
Truncated. see log file for complete stacktrace
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
<Dec 4, 2009 2:04:04 PM PST> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
Truncated. see log file for complete stacktrace
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
<Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1259964185054' for task '2'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
<Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'springCXFApp'.>
<Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'springCXFApp'.>
<Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
thanks

hi
I am tring to deploy a webservice (spring + cxf ) in weblogic 10.3
applicationContext.xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:p="http://www.springframework.org/schema/p"
xmlns:aop="http://www.springframework.org/schema/aop"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:jee="http://www.springframework.org/schema/jee"
xmlns:tx="http://www.springframework.org/schema/tx"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xsi:schemaLocation="
http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd
http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd
http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd">

<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-http-binding.xml"/>
<import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
<context:component-scan base-package="com.persistent.rest"/>
<context:annotation-config />
<jaxws:endpoint
id="accountProcess"
implementor="com.persistent.rest.GetAccountListImpl"
address="/"
bindingUri="http://apache.org/cxf/binding/http" >
<jaxws:serviceFactory>
<bean class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean">
<property name="wrapped" value="false" />
</bean>
</jaxws:serviceFactory>
</jaxws:endpoint>
<bean>...........</bean>
</beans>
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>springCXFWeb</display-name>
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>WEB-INF/applicationContext.xml</param-value>
</context-param>
<listener>
<listener-class>
org.springframework.web.context.ContextLoaderListener
</listener-class>
</listener>
<servlet>
<servlet-name>CXFServlet</servlet-name>
<servlet-class>
org.apache.cxf.transport.servlet.CXFServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>CXFServlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
</web-app>
Getting following error while deploying my webservice on weblogic 10.3
<Dec 4, 2009 2:04:04 PM PST> <Error> <org.springframework.web.context.ContextLoader> <BEA-000000> <Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
Truncated. see log file for complete stacktrace
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
<Dec 4, 2009 2:04:04 PM PST> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
Truncated. see log file for complete stacktrace
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
<Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1259964185054' for task '2'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
<Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'springCXFApp'.>
<Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'springCXFApp'.>
<Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
Truncated. see log file for complete stacktrace
java.lang.InternalError: erroneous handlers
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
Truncated. see log file for complete stacktrace
thanks

Getting an error after deploying

My web.xml file is this
<?xml version="1.0" encoding="UTF-8"?>
<web-app >
<servlet>
<description>This is the description of my J2EE component</description>
<display-name>This is the display name of my J2EE component</display-name>
<servlet-name>Rating</servlet-name>
<servlet-class>com.Mamatha.Rating</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>Rating</servlet-name>
<url-pattern>/Rating</url-pattern>
</servlet-mapping>
</web-app>
And the error i am getting is
<[BillingSystem.war]: Deployment descriptor "web.xml" is malformed. Check against the DTD: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'web-app'. (line 6, column 52).>
Please help me out
Thanks

As Parvez mentioned it looks like the weblogic server is not able to pick up the custom classes.
Did you deploy the classes in RUN filesystem or PATCH filesystem ?
Have a look at Note 1577661.1 in metalink for detailed instruction on deploying the Business Logic Extensions
(Section 1.6.3.4: Developing OA Framework Business Logic Extensions):
(Section 1.6.3.4: Deploying OA Framework Business Logic Extensions):
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=464975502584896&id=1577661.1&_adf.ctrl-state=1bz4njrrqx_…
Cheers
AJ

What are the best approaches for mapping re-start in OWB?

What are the best approaches for mapping re-start in OWB?
We are using OWB repository 10.2.0.1.0 and OWB client 10.2.0.1.31. The Oracle version is 10 G (10.2.0.3.0). OWB is installed on Linux.
We have number of mappings. We built process flows for mappings as well.
I like to know, what are the best approches to incorportate re-start options in our process. ie a failure of mapping in process flow.
How do we re-cycle failed rows?
Are there any builtin features/best approaches in OWB to implement the above?
Does runtime audit tables help us to build re-start process?
If not, do we need to maintain our own tables (custom) to maintain such data?
How did our forum members handled above situations?
Any idea ?
Thanks in advance.
RI

Hi RI,
How many mappings (range) do you have in a process flows?Several hundreds (100-300 mappings).
If we have three mappings (eg m1, m2, m3) in process flow. What will happen if m2 fails?Suppose mappings connected sequentially (m1 -> m2 -> m3). When m2 fails then processflow is suspended (transition to m3 will not be performed). You should obviate cause of error (modify mapping and redeploy, correct data, etc) and then repeat m2 mapping execution from Workflow monitor - open diagram with processflow, select mapping m2 and click button Expedite, choose option Repeat.
In re-start, will it run m1 again and m2 son on, or will it re-start at row1 of m2?You can specify restart point. "at row1 of m2" - I don't understand what you mean (all mappings run in Set based mode, so in case of error all table updates will rollback,
but there are several exception - for example multiple target tables in mapping without corelated commit, or error in post-mapping - you must carefully analyze results of error).
What will happen if m3 fails?Process is suspended and you can restart execution from m3.
By having without failover and with max.number of errors=0, you achieve re-cycle failed rows to zero (0).This settings guarantee existence only two return result of mapping - SUCCSES or ERROR.
What is the impact, if we have large volume of data?In my opinion for large volume Set based mode is the prefered processing mode of data processing.
With this mode you have full range enterprise features of Oracle database - parallel query, parallel DML, nologging, etc.
Oleg

Sessions/connections gets hang during update and select operations.

A table with 3 million records, which has customer details data.
Everyday application is executing select and update queries on that table.
Sessions/connections gets hang during update and select operations.
After checking ADDM report, following are the findings:
Please suggest the solutions
Findings and Recommendations
Finding 1: Row Lock Waits
Impact is 145.22 active sessions, 99.77% of total activity.
SQL statements were found waiting for row lock waits.
Recommendation 1: Application Analysis
Estimated benefit is 145.22 active sessions, 99.77% of total activity.
Action
Significant row contention was detected in the TABLE
"AVAYA.AIRTEL_CUSTOMER_MASTER" with object ID 82155. Trace the cause of
row contention in the application logic using the given blocked SQL.
Related Object
Database object with ID 82155.
Rationale
The SQL statement with SQL_ID "974vg65j29pmv" was blocked on row locks.
Related Object
SQL statement with SQL_ID 974vg65j29pmv.
UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
Rationale
The session with ID 50 and serial number 34525 in instance number 1 was
the blocking session responsible for 100% of this recommendation's
benefit.
Symptoms That Led to the Finding:
Wait class "Application" was consuming significant database time.
Impact is 145.22 active sessions, 99.77% of total activity.
Finding 2: Top SQL Statements
Impact is 46.39 active sessions, 31.87% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
Recommendation 1: SQL Tuning
Estimated benefit is 46.39 active sessions, 31.87% of total activity.
Action
Investigate the UPDATE statement with SQL_ID "974vg65j29pmv" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID 974vg65j29pmv.
UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "974vg65j29pmv" was executed 212 times and had
an average elapsed time of 2494 seconds.
Rationale
Waiting for event "enq: TX - row lock contention" in wait class
"Application" accounted for 100% of the database time spent in
processing the SQL statement with SQL_ID "974vg65j29pmv".

**addm report **
          ADDM Report for Task 'TASK_7526'
Analysis Period
AWR snapshot range from 5003 to 5004.
Time period starts at 08-JUL-13 11.00.27 AM
Time period ends at 08-JUL-13 12.00.45 PM
Analysis Target
Database 'AVAYADB' with DB ID 2878789264.
Database version 11.2.0.1.0.
ADDM performed an analysis of instance avayadb, numbered 1 and hosted at
NG-LA04AVAYA01.
Activity During the Analysis Period
Total database time was 563062 seconds.
The average number of active sessions was 155.63.
Summary of Findings
   Description         Active Sessions      Recommendations
                       Percent of Activity
1 Row Lock Waits      155.44 | 99.88       1
2 Top SQL Statements 26.67 | 17.14        1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Findings and Recommendations
Finding 1: Row Lock Waits
Impact is 155.4 active sessions, 99.88% of total activity.
SQL statements were found waiting for row lock waits.
   Recommendation 1: Application Analysis
   Estimated benefit is 155.44 active sessions, 99.88% of total activity.
   Action
      Significant row contention was detected in the TABLE
      "AVAYA.AIRTEL_CUSTOMER_MASTER" with object ID 82155. Trace the cause of
      row contention in the application logic using the given blocked SQL.
      Related Object
         Database object with ID 82155.
   Rationale
      The SQL statement with SQL_ID "974vg65j29pmv" was blocked on row locks.
      Related Object
         SQL statement with SQL_ID 974vg65j29pmv.
         UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
         WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
   Rationale
      The session with ID 167 and serial number 6084 in instance number 1 was
      the blocking session responsible for 100% of this recommendation's
      benefit.
   Symptoms That Led to the Finding:
      Wait class "Application" was consuming significant database time.
      Impact is 155.45 active sessions, 99.88% of total activity.
Finding 2: Top SQL Statements
Impact is 26.66 active sessions, 17.14% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
   Recommendation 1: SQL Tuning
   Estimated benefit is 26.67 active sessions, 17.14% of total activity.
   Action
      Investigate the UPDATE statement with SQL_ID "974vg65j29pmv" for
      possible performance improvements. You can supplement the information
      given here with an ASH report for this SQL_ID.
      Related Object
         SQL statement with SQL_ID 974vg65j29pmv.
         UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
         WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
   Rationale
      The SQL spent only 0% of its database time on CPU, I/O and Cluster
      waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
      Look at performance data for the SQL to find potential improvements.
   Rationale
      Database time for this SQL was divided as follows: 100% for SQL
      execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "974vg65j29pmv" was executed 707 times and had
      an average elapsed time of 794 seconds.
   Rationale
      Waiting for event "enq: TX - row lock contention" in wait class
      "Application" accounted for 100% of the database time spent in
      processing the SQL statement with SQL_ID "974vg65j29pmv".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Additional Information
Miscellaneous Information
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.

Concurrent execution of mapping

Hi All,
I have quick question about concurrent execution of mapping. Let's assume a simple mapping loading data from external table to regular table.
My question is whether it is possible to execute concurrently this mapping but with different set of data (=different file as a data source for external table) ?
I'm aware that I can have external table defined over several source files. However, that is not the case since new files are delivered to the system in unpredictable intervals. What I want to do is to execute load of the new source file as soon as new file is delivered but before previous load (=previous execution of mapping) is completed. With such concurrent run (or kind of pipelining) I'm hoping to achieve better performance.
Please let me know if such approach is possible? Is it good or bad approach? Can you point any alternatives or any suggestions of some kind, including RTFM of course. ;)
Thanks & Regards,
Rafal

Hi,
When a mapping is running it first places a lock on the tables that is involved in the mapping. So you cannot run the mapping concurrently with two different datafiles as ur source and a single target.
In 10gR2 there is a option of doing this but it has its own advantages and dis advantages. The advantage would be that u can save a lot of time but there is one major disadvantage.
Assume there are 2 mappings feeding the same target table, one is insert mapping with 10k records and another insert\update mapping with 5k rows. Both the mappings share 2k rows(Common for both mappings. Gets updated in the second mapping),. In this sineario when we concurrently run the mappings and if the first mapping fails then rolling back to the original state would be tough as the second mapping would have completed successfully. Lot of data mismatch may happen and we may have to go for a point in time recovery. Its better not to run mappings concurrently..
Regards
Bharath

Execution of mapping gets hanged in OWB Deployment Manager

Similar Messages

Maybe you are looking for