Error during deploying a mapping

Hi,
I have created a mapping which reads data from one table and inserts into another table (one to one, with no filter). Both the tables exists in the same schema.
When I try to DEPLOY the mapping by giving the connection parameters (userid/psswd) of the schema on which the tables exists, I get this error.
PLS-00201: identifier "WBPRTI.AUDIT_BEGIN" must be declared.
PL/SQL: Statement ignored.
... and lists the undeclared variables in the package script.
Can anyone help me in figuring what the problem is:
Regards,
S. Karthik.

Guys,
You need to install runtime objects using OWB Runtime Assistant.
See the thread I have started just before.
Re: Class loading issue in 10.1.2? commons-codec
hth,
Alexandre

Similar Messages

Error when deploying a map

hello i have the following error when deploying a map in a local database, the mapping is a simple transfert of data between two table,
ORA-06550: line 0, column 0:
ORA-04052: erreurs lors de la consultation de l'objet distant [email protected]@KCDBDEV
ORA-00604: une erreur s'est produite au niveau SQL récursif 1
ORA-01882: région de fuseau horaire introuvable
ORA-02063: pré
any help please
thanks,
tarek

Hello thank u for helping, i have exactly the same problème in Error executing a query using a DB-Link
but i am not inderstanding the solution, i found the same probleme in metalink, and the solution posted is:
1. Create an errorstack of the ORA-1882 to see the ALTER SESSION SET TIME_ZONE statement that is causing the ORA-1882 during deployment. To create this errorstack, follow step 1 to 4 below:
1. Just before you reproduce the error, open a SQL*Plus session with user SYSTEM.
SQL> alter system set events '1882 trace name ERRORSTACK level 3'
2. Deploy the mapping to reproduce the ORA-1882
3. Disable the system event
SQL> alter system set events '1882 trace name errorstack off';
4. Take a look at the errorstack (located in the udump directory). Suppose the following statement is in there:
ALTER SESSION SET TIME_ZONE = 'GMT+02:00'
2. Modify the run_service.sh(.bat) file as follow:
* For UNIX:
Modify owb_server_home/owb/bin/unix/run_service.sh as follows:
Add the parameter -Duser.timezone="+02:00" to the line where java is started (last line of run_service.sh)
$JAVAPATH/bin/java -Xmx768M -Djava.awt.headless=true -DORACLE_HOME.....
e.g:
$JAVAPATH/bin/java -Xmx768M -Duser.timezone="+02:00" -Djava.awt.headless=true -DORACLE_HOME
* For Windows:`
Modify owb_server_home\owb\bin\win32\run_service.bat as follows:
Add the parameter -Duser.timezone="+02:00" to the line where java is started
%JAVAPATH%\jre\bin\javaw.exe %JVM_OPTIONS%
e.g.:
%JAVAPATH%\jre\bin\javaw.exe -Duser.timezone="+02:00" %JVM_OPTIONS%
3. Save the file and re-start the Runtime Service using stop_service.sql/start_service.sql.
but in creating the errorstack of the ORA-1882 i not found the ALTER SESSION SET TIME_ZONE
and i Modify the run_service i fixed -Duser.timezone="+01:00" cause the time zone here is Europe/Paris but there is no changes.
the db link is from Oracle 10.2.0.2.0 to 9.2.0.1.0. and owb 10g R2
other solution?
thanks,
tarek

Error while deploying BPEL Process(Error during deployment: Deployment Fail

Hi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/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.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PM

Hi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/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.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PM

Error during deploying the java patches.

Hi gurus.
error during deploying   jtechf patch.through SDM.when deploying SQL TRACE the probelm occured.

SDM LOG
Dec 8, 2008 5:09:21 PM   Info: Finished saving the repository
Dec 8, 2008 5:09:24 PM   Info: Starting: Update: Selected software component 'SA
P_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9' updates curren
tly deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.12.0.
20070507085740''/'3'.
Dec 8, 2008 5:09:24 PM   Error: Aborted: software component 'SAP_JTECHS'/'sap.co
m'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9':
Failed deployment of SDAs:
development component 'SQLTrace'/'sap.com'/'SAP AG'/'7.0013.20070703111935.0000'
/'9' : aborted

Error during deployment - NoSuchMethodError DatabaseLogin.clone()

Hi All,
I'm running Jdeveloper 11.1.1.6.0 and I have a SOA composite that contains a BPM process wired to a BPEL process which is connected to a DBAdapter. I suddenly started getting these errors when deploying my app today.
<Mar 28, 2013 11:08:30 AM EDT> <Error> <ServletContext-/soa-infra> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [Ver2_NoEOorVO.getSTN/1.0]Unable to complete load due to: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;
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)
Truncated. see log file for complete stacktrace
Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [Ver2_NoEOorVO.getSTN/1.0]Unable to complete load due to: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin; {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)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoSuchMethodError: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;
at oracle.tip.adapter.db.DBManagedConnectionFactory.buildServerSession(DBManagedConnectionFactory.java:1316)
at oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:1172)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:635)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:379)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:264)
Truncated. see log file for complete stacktrace
Could this be due to the fact that the db adapter getSTN jca connection factory location is bound to a jndi name that has a multi-data source (load-balanced) ?
thanks,
Vikram

Never mind. I found the problem. But you have to admit - The error does throw you off completely though.
I had a database adapter referencing a jndi name like eis/DB/MySTN which did exist earlier but I removed it from the DbAdapter connection factory on the weblogic console before deploying. Also I referenced the DbAdapter connection factory xaDataSource to a generic data source instead of multi - that seemed to help as well.

ConfigureListener contextInitialized Critical error during deployment: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver

Hi Techies,
I am facing small problem with deployment thru cosole deployment.. details below.I am using Jdeveloper 11.1.2.1.0 ver.
I am able to deploy the application thru Jdeveloper Run/Debug Option. But If i create an EAR file and deploying thru server console , then i am getting below error. hence its not deploed.
.Till yesterday it was working ..Just to day i am facing this issue.What can be the reasons for this ?
Can anyone help me plz..
---------------------- Error Message on log---------------------------------------------------------------------------------
<ConfigureListener> <contextInitialized> Critical error during deployment:
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
at com.sun.faces.util.Util.loadClass(Util.java:291)
at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
... 38 more
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver.
java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:294)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
Truncated. see log file for complete stacktrace
Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<ConfigureListener> <contextDestroyed> Unexpected exception when attempting to tear down the Mojarra runtime
java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804)
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306)
at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:108)
at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:327)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3224)
at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1535)
at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:507)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:642)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1374785326461' for task '2'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'EmersonMMI_QACerts'.>
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'EmersonMMI_QACerts'.>
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<Jul 25, 2013 8:50:55 PM GMT> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
at com.sun.faces.util.Util.loadClass(Util.java:291)
at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)..
[03:58:26 AM] Deployment cancelled.
[03:58:26 AM] ---- Deployment incomplete ----.
[03:58:26 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Thanks,
Rajesh

java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
Add the jsf-api.jar to the runtime classpath of the server.

Fatal error during deployment!

I'm getting the following error message whenever I try to deploy my (server-side)
app:
Internal VM (14:41:29): Fatal error during deployment! Deployment failed
Any ideas on how to resolve this?

Seems like problem in setup in Visual Cafe. See the message
Dir/File 'C:\WebGain\VCafe\bin\components\wqaplugin.jar'
does not exist
Can you try other tools for deployment like ant task wldeploy or directly using
command line Weblogic.Deployer?
"Fred Bloggs" <[email protected]> wrote:
>
I click the "Project" menu item, then "Build Application". No problem
doing that,
then I click "Project" again, then "Deploy". The attempt to deploy fails:
VisualCafe (09:45:40): wjc -sysclasspath C:\WebGain\VCafe\bin\..\JDK13\JRE\LIB\RT.JAR;C:\WebGain\VCafe\bin\..\JDK13\LIB\TOOLS.JAR
-g -O -d C:\WebGain\VCafe\Projects\ -classpath
VisualCafe (09:45:40): S:\general\superjar\superjar.jar;C:\WebGain\VCafe\Projects\;C:\WebGain\VCafe\jdk13\jre\lib\rt.jar;C:\WebGain\VCafe\jdk13\lib\tools.jar;C:\WebGain\VCafe\jdk13\lib\dt.jar;C:\WebGain\VCafe\jdk13\jre\lib\i
VisualCafe (09:45:40): 18n.jar;C:\WebGain\VCafe\JAVA\LIB\;C:\WebGain\VCafe\JAVA\LIB\SYMCLASS.ZIP;C:\WebGain\VCafe\JAVA\LIB\CLASSES.ZIP;C:\WebGain\VCafe\swing-1.1\SWINGALL.JAR;C:\WebGain\VCafe\bin\xutil.ZIP;C:\WebGain\VCafe\b
VisualCafe (09:45:40): in\components\sfc.jar;C:\WebGain\VCafe\bin\components\symbeans.jar;C:\WebGain\VCafe\java\lib\eradtools.jar;C:\WebGain\VCafe\java\lib\eradpublic.jar;C:\WebGain\VCafe\java\lib\dbaw.zip;C:\WebGain\VCafe\b
VisualCafe (09:45:40): in\components\dbaw_awt.jar;C:\WebGain\VCafe\bin\components\databind.jar;C:\WebGain\VCafe\java\lib\collections.zip;C:\WebGain\VCafe\java\lib\icebrowserbean.jar;C:\WebGain\VCafe\java\lib\servlet.jar;C:\W
VisualCafe (09:45:40): ebGain\VCafe\java\lib\webserver.jar;C:\WebGain\VCafe\java\lib\jspengine.jar;C:\WebGain\VCafe\java\lib\symtools.jar;C:\WebGain\VCafe\bin\components\deploy.jar;C:\WebGain\VCafe\bin\components\templates.j
VisualCafe (09:45:40): ar;C:\WebGain\VCafe\bin\components\vcservlet.jar;C:\WebGain\VCafe\bin\components\vcjsp.jar;C:\WebGain\VCafe\bin\components\flexlm.zip;C:\WebGain\VCafe\bin\components\vcejbwl.jar;C:\WebGain\VCafe\java\l
VisualCafe (09:45:40): ib\javax_ejb.zip;C:\WebGain\VCafe\java\lib\jndi.jar;C:\WebGain\VCafe\java\lib\jts.zip;C:\WebGain\VCafe\java\lib\jdbc2_0-stdext.jar;C:\WebGain\VCafe\bin\sb\;C:\WebGain\VCafe\bin\sb\classes\sb.jar;C:\Web
VisualCafe (09:45:40): Gain\VCafe\bin\components\wqaplugin.jar;C:\WebGain\QAnalyzer\lib\mrt.jar;C:\WebGain\QAnalyzer\lib\metamata.jar;C:\WebGain\VCafe\bin\components\TurboXMLPlugin.jar;C:\WebGain\VCafe\bin\components\Dreamwe
VisualCafe (09:45:40): averPlugin.jar;c:\jaxp-1.2_01\dom.jar;c:\jaxp-1.2_01\jaxp-api.jar;c:\jaxp-1.2_01\sax.jar;c:\jaxp-1.2_01\xalan.jar;c:\jaxp-1.2_01\xercesImpl.jar;c:\jaxp-1.2_01\xsltc.jar;c:\WebGain\bea\wlserver6.1sp1\sa
VisualCafe (09:45:40): mples\eval\cloudscape\lib\cloudscape.jar -make
-cdb incidentAlertPrj.cdb
C:\WebGain\VCafe\Projects\incidentAlert.java C:\WebGain\VCafe\Projects\appRoles.java
VisualCafe (09:45:40): C:\WebGain\VCafe\Projects\abstractAlertSDFBean.java
C:\WebGain\VCafe\Projects\sdfTextBean.java
C:\WebGain\VCafe\Projects\alertXMLBean.java C:\WebGain\VCafe\Projects\alertSDFBeanFactory.java
VisualCafe (09:45:40): C:\WebGain\VCafe\Projects\nullAlertSDFBean.java
VisualCafe (09:45:40): Warning 61: Dir/File 'C:\WebGain\VCafe\bin\components\wqaplugin.jar'
does not exist
VisualCafe (09:45:40): Build Successful
Internal VM (09:45:46): Starting deployment to WebLogic Server 6.1 ...
Internal VM (09:46:07): Building deployment descriptor...Building generic
WAR
file...
Internal VM (09:46:07): Fatal error during deployment! Deployment failed
Rob Woollen <[email protected]> wrote:
I think we'll need some more info. That doesn't look like a WLS error
message.
Can you show us your logs, stdout etc?
How are you deploying the app?
-- Rob

RTC-5161 Error when deploying a MAP

Hello,
I recently upgraded OWB 11.1.0.7 to 11.2.0.3 and within the Design Center, I receive error RTC-5161 when deploying a MAPPING. My process flows and all other objects deploy successfully but the MAPPING pops up the RTC-5161 error
Here is how I went about my upgrade, can anyone tell me if I am missing something?
-Installed OWB 11.2.0.3 on a new server, configured Workspaces, workflow workspace user
-Exported an OWB 11.1.0.7 project MDL and imported into the 11.2.0.3 and the Design Center automatically UPGRADED my project.
-Registered all locations
-Revalidated all locations within the ROPOSITORY BROWSER(the statuses were previously showing UNKNOWN, now they are all valid)
I need help PLEASE, if anyone could point me to something I am overlooking....
AGAIN, ONLY the MAPPING will not deploy, but the Process Flows generates and deploys with no issues.
I tried running the DEPLOYMENT of the Project from the command line(OMBPLUS), here is the error generated:
Processing module LOCATIONS ...
Deploying module name: FFL_DL_BMFENT_FFM_BMFENT
module name is FFL_DL_BMFENT_FFM_BMFENT
Deploying module name: DBL_EFDS_DL_BMFENT_DBM_TGT_EFD
module name is DBL_EFDS_DL_BMFENT_DBM_TGT_EFD
Deploying ... CONNECTOR : DBL_EFDS_DL_BMFENT_DBM_TGT_EFD/CONN_FFL_DL_BMFENT_FFM_BMFENT
Error deploy drop action plan for DBL_EFDS_DL_BMFENT_DBM_TGT_EFD/CONN_FFL_DL_BMFENT_FFM_BMFENT, err msg= "OMB05602: An error occurred during deployment: DeploymentContextImpl.generate WBGeneratedObject[] is null or length 0 for CONN_FFL_DL_BMFENT_FFM_BMFENT"
Error deploy LOCATIONS : CONNECTOR

Fixing this actually entailed going through the repository browser and checking the first optional feature during the configuration of the workspaces etc
thanks for all your help!
Now I have another issue with synchronization:
I noticed that doing an inbound synching of my staging table using replace option and by object name, the preview window that pops up shows my objects to be updated not matching one to one.
Has anyone ran into something like this?
The synchronization preview shows source to target columns NOT MATCHING one to one.....

Deployment error during deployment of the process flow...

i have made a program using OMB to deploy an OWB process flow. i have used tcl programming to run it on UNIX.
when i run the program it gives me a strange error saying:
an unknown error has occured during deployment .
when i open the OWB design center to check the status i find the the process folw is stuck during the generation part and it continues but the generation never takes place.. for that i wrote an OMBALTER to alter the generation language of the mappings used in the process flow ,but it does not help...
also after the error in the program when i see the mapping through the desibn center i do not see the original mapping when i open the mapping editor.
then if I run the again program again i get the process flow deployed successfully ,obviously with the incorrect mappings.
can anybody plz help me out with it???

Hello!
I searched metalink on error RTC-5161 and found a reference in note 392263.1
It is a bug but there is a patch available ( bug 5504848, patch number 5525337).
Read the note on metalink to check if you really hit this bug and apply the patch.
Regards,
Robert

Error while deploying a mapping in OWB.

Hi All,
OWB configuration is as follows:
Oracle9i Warehouse Builder Client: 9.2.0.2.8
Oracle9i Warehouse Builder Client: 9.2.0.2.0
OS: Windows XP Professional.
Following is error message displayed when i tried to deploy a mapping thru OWB Client.
RTC-5260 Failed to connect to runtime platform. Please check you have provided the correct host,user, password, service_name.
RTC-5324" This Runtime Access user is not associated with the specified runtime repository. Please use the OWB Runtime Assistant to ressolve this problem.
Steps followed are as follows:
1> Defined Source Module, Added Connection & Location information.
Dblink created to point to source schema. Tables imported from the source schema.
2> Defined Target Module, Added Connection & Location information. Dblink created to point to target schema. Tables imported from the target schema.
3> Created a simple mapping which involves a source & target table, Aggregator operator.
4> Validated & Generated the mapping.
5> Created Runtime Repository Connections.
6> Selected the Repository Connection at time of Deploy entered the password.
Am i missing few steps for deployment of the mapping?
The error message RTC-5260 suggests that
This Runtime Access user is not associated with the specified runtime repository. How this can be done?
Thanks in Advance.
Regards,
Vidyanand

Hi Vidyanand,
Did you create the runtime access user using the runtime assistant? Did you select the correct runtime repository (if you have more) to associate your runtime access user with?
Note that there are 4 database roles being created when you create a runtime repository owner:
- OWB_A_<runtime repository owner>
- OWB_D_<runtime repository owner>
- OWB_R_<runtime repository owner>
- OWB_U_<runtime repository owner>
If you would grant those roles to a user, then that user becomes an access user for the user with username <runtime repository owner>.
Note that you can also use the runtime repository credentials to connect to the runtime repository for deployment purposes, but you may not want that because of security concerns.
Thanks,
Mark.

Error while deploying a mapping in owb 11.2

Hi,
I am using OWB 11.2 and when i try to deploy a mapping i get the following error. Is it some permission issue.
Please let me know if anyone has faced similar issue. Its very urgent.
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_LOB' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_LOB' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
     at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:202)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1005)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3530)
     at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(OracleCallableStatement.java:4718)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1062)
     at sqlj.runtime.ExecutionContext$OracleContext.oracleExecuteUpdate(ExecutionContext.java:1570)
     at oracle.wh.service.impl.runtime.runtime_access.RuntimeDeploymentDefiner.defineDeployment(RuntimeDeploymentDefiner.java:1094)
     at oracle.wh.service.impl.runtime.RuntimePlatformServiceImpl.createDeploymentAuditId(RuntimePlatformServiceImpl.java:1409)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy._internalDeploy(WHRuntimeCommandGenerateDeploy.java:2382)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.doDeploymentAsynch(WHRuntimeCommandGenerateDeploy.java:2117)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.doDeploymentAsynch(WHRuntimeCommandGenerateDeploy.java:2112)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandHandler$3.construct(WHRuntimeCommandHandler.java:1194)
     at oracle.wh.ui.runtime.SwingWorker$2.run(SwingWorker.java:124)
     at java.lang.Thread.run(Thread.java:595)

Hi,
have you tried to grant the user you use for connecting:
GRANT EXECUTE ON DBMS_LOB TO your_usr WITH GRANT OPTIONYou need the "WITH GRANT OPTION" if the sql is executed within some view or package.
Regards,
Carsten.

Error while deploying the mapping in owb 10gR2

Hi friends,
when i tried to deploy the mapping firstly i got the below error like
Name
Action
Status
Log
COPY_OF_ORG_FINAL_MAPPING
Create
Warning
ORA-06550: line 11, column 3: PL/SQL: SQL Statement ignored
COPY_OF_ORG_FINAL_MAPPING
Create
Warning
ORA-06550: line 18, column 59: PL/SQL: ORA-00942: table or view does not exist
COPY_OF_ORG_FINAL_MAPPING
Create
Warning
ORA-06550: line 33, column 3: PL/SQL: SQL Statement ignored
COPY_OF_ORG_FINAL_MAPPING
Create
Warning
ORA-06550: line 40, column 59: PL/SQL: ORA-00942: table or view does not exist
COPY_OF_ORG_FINAL_MAPPING
Create
Warning
ORA-06550: line 216, column 7: PL/SQL: SQL Statement ignored
COPY_OF_ORG_FINAL_MAPPING
Create
Warning
ORA-06550: line 237, column 59: PL/SQL: ORA-00942: table or view does not exist
From the above error, it states like table doesn't exist. Hence after checking that the source table connections that i used in the mapping seems to be wrong.
so what i did is, in the control center i right clicked the source module where i have used source table and changed the connection but soon after i pressed the ok button as a part of registering i got the below error like
>> RTC-5318 Invalid Location Type pair for Name oracle db and version 11.1
I ignored the above error and continued to deploy the mapping, but as a result of mapping i got the below error like
Name
Action
Status
Log
None
INFORMATIONAL
ORA-04052: error occurred when looking up remote object [email protected]@PEOPLE_SOURCE_LOCATION ORA-00604: error occurred at recursive SQL level 1 ORA-02019: connection description for remote database not found
COPY_OF_ORG_FINAL_MAPPING
Create
Warning
ORA-06550: line 0, column 0: ORA-04052: error occurred when looking up remote object [email protected]@PEOPLE_SOURCE_LOCATION ORA-00604: error occurred at recursive SQL level 1 ORA-02019: connection description for remote database not found
Not sure, where im missing.
Kindly help me friends,
Thanks
Brgds,
Mini

Hi Vidyanand,
Did you create the runtime access user using the runtime assistant? Did you select the correct runtime repository (if you have more) to associate your runtime access user with?
Note that there are 4 database roles being created when you create a runtime repository owner:
- OWB_A_<runtime repository owner>
- OWB_D_<runtime repository owner>
- OWB_R_<runtime repository owner>
- OWB_U_<runtime repository owner>
If you would grant those roles to a user, then that user becomes an access user for the user with username <runtime repository owner>.
Note that you can also use the runtime repository credentials to connect to the runtime repository for deployment purposes, but you may not want that because of security concerns.
Thanks,
Mark.

OWB Error while deploying the mapping Io exception: The Network Adapter co

Hi,
We are using OWB 10.2 in our production environment.Actually we are using OWB only for development.
After deploying each mapping we will create scheduler job for execution of these mappings.
Recently our staging DBs port has been changed to 1522 from 1521 and i have gone throgh the below steps.
1) Changed the port in tnsnames.ora file.
2) In Start Control Centre Servioce ,i have changed the port to 1522 for owbownr user and started the service successfully.
3) i have run the script UpdateLocation.sql from the OWBOWNR schema and updated the port number.
4) I tried to run the UpdateControlCenter.sql in owbownr schema and staging schema also,but i am getting an error like below.
SQL> @UpdateControlCenter.sql
This sql script sets the host:port:service parameters for a control center
in the OWB Client Repository.
The connection type must be host:port:service and cannot be changed
using this script.
Enter Control Center Name: DEFAULT_CONTROL_CENTER
Host: 10.109.65.62
Port: 1522
Service Name: DWHOWNR
Update location properties for DEFAULT_CONTROL_CENTER
Location Type =
Control Center DEFAULT_CONTROL_CENTER Found
Connection Type SQL*NET Connection cannot be updated
PL/SQL procedure successfully completed.
5) When i am running the service_doctor.sql on owbownr schema i am getting incorrect port number like below
SQL> @service_doctor.sql
There are errors in one or more PL/SQL packages and functions
Platform properties have been loaded correctly
Platform location has been seeded correctly
NLS messages have been loaded correctly
The platform service is available
There is a problem accessing the service startup script from the database
server
Here is the detailed error message which contains the name of the start
script file:-
Service startup file 'null/owb/bin/unix/run_service.sh' is not
accessible from the database server on instance number 1
Please verify that the disk containing the file is visible to the
database server
Please verify that the database server account has access rights on the
file
There is a problem with the repository connection information used to
start the service
Here is the detailed error message which contains the connection
information passed to the service:-
Cannot connect: user=DWHOWNR host=10.109.65.62 port=1521
service-name=DWHSTG
Please verify that this information is accurate
If this information is correct, then please use the
'set_repository_password.sql' script to reset the stored password
PL/SQL procedure successfully completed.
6) After login to OWB ,i have checked the Location,OWB Repository Location And Control center In OWB connection Explorer,
and all the connections are successful.
After this i took Control Centre from Tools and i tried to deploy one mapping.
And i got some error like below.
Name
Type
Status
Log
COPY_OF_ICDMAPFCTAWB
Description : Runtime User : ICGSTG Started : 2011-10-24 19:32:19.0
Name
Action
Status
Log
None
Error
Io exception: The Network Adapter could not establish the connection
None
Error
Io exception: The Network Adapter could not establish the connection
None
RECOVERY
RPE-01008: Recovery of this request is in progress.
Job Summary
Updated : 2011-10-24 19:32:19.0 Job Final Status : Completed with errors Job Processed Count : 0 Job Error Count : 0 Job Warning Count : 0
I think the issue is due to the wrong port number .
Can any one help me to solve this issue??
Edited by: 892899 on Oct 24, 2011 6:01 AM

Hi Allan,
Thanks for your quick reply.
I have checked in OWB\Locations\Database\Oracle\Location\DB Connectors and also in Control Center\Location\Connectors,seems like there is no connectors created.
Do you have any other suggestions?
Also i analyzed the UpdateControlCenter.sql in that
select value into v_connectiontype from cmpstringpropertyvalue_v where logicalname = 'CMPLocation_ConnectionType' and propertyowner = v_elementid;
the qry returns 'SQL*NET'.
Any workaround for these???
Please reply.

Error during deployment of Message Driven Bean

Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          I am getting some error (or perhaps warning) during deployment of Message
          Driven Bean. Any one seen this before?
          This error only comes on a machine with Dual Network card.
          Thanks.
          ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
          <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
          enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
          Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
          is of a non-final version of the appropriate specification. It is subject to
          change in future releases once the specification becomes finalized. This may
          cause application code developed for BEA WebLogic Server 6.1 that uses the
          new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          supported in future releases of BEA WebLogic Server.>
          ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          container will automatically attempt to re-establish the connection with the
          JMS server. This warning may occur during WebLogic Cluster start-up if the
          JMS destination is located on another server. When the JMS server connection
          is re-established, the Message-Driven EJB will again receive JMS messages.
          The Error was:
          Unable to create a JNDI InitialContext to lookup the JMS destination. The
          error was:
          javax.naming.CommunicationException. Root exception is
          java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          nested exception is:
          java.net.ConnectException: Connection refused: connect; No available router
          to destination
          at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:307)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:211)
          at
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          ory.java:149)
          at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          rivenBeanInfoImpl.java:641)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          nPoller.java:474)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          .java:418)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          nectionPoller.java:286)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          foImpl.java:511)
          at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          at weblogic.j2ee.Application.addComponent(Application.java:170)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          arget.java:360)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          Target.java:285)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          eploymentTarget.java:239)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          entTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy34.updateDeployments(Unknown Source)
          at
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          ServerMBean_CachingStub.java:2977)
          at
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          icationManager.java:372)
          at
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          r.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy49.start(Unknown Source)
          at
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          >
          ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010009> <EJB Deployed EJB with JNDI name
          ASYNCMessageDrivenBean.>


Hi Tom
          Yes we do have an URL provided in the descriptor. It's
          t3://jms.server.net:7001.
          and the jms.server.net is resolved via a hosts file in Win2K
          eg,
          192.168.100.200 jms.server.net
          You are right in saying that the loopback in a dual-net card is a problem.
          But our solution
          above solves the issue as long as your host file does not use 127.0.0.1 as
          the IP.
          We need the URL b/c depending on our client's deployment , the JMS Server
          may be remote or may be local.
          "Tom Barnes" <[email protected]> wrote in message
          news:[email protected]...
          > Hi x,
          >
          > Something to do with the loopback and dual-network cards is
          > messin' with WLS' mind. I do not know what the problem is,
          > but I can guess:
          >
          > You have specified an URL in the MDB descriptor when there
          > is no need for one. If t3://127.0.0.1:7001 is in the same
          > cluster the MDB is running in (I suspect this URL is
          > actually the same WL server), then don't specify the URL.
          > This URL is only useful for connecting an MDB to a JMS
          > server that is outside local server and outside the cluster.
          > The URL may be working on single-network card systems
          > as perhaps then WL has enough info to guess that you
          > actually mean the local WL server, and simply converts
          > the context to a local context.
          >
          > Note that the URL option in the MDB descriptor is actually
          > a WebLogic extension of J2EE.
          >
          > Tom
          >
          >
          >
          > x wrote:
          > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          > >
          > > I am getting some error (or perhaps warning) during deployment of
          Message
          > > Driven Bean. Any one seen this before?
          > > This error only comes on a machine with Dual Network card.
          > >
          > > Thanks.
          > >
          > >
          > >
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
          features
          > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
          1.2,
          > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
          6.1
          > > is of a non-final version of the appropriate specification. It is
          subject to
          > > change in future releases once the specification becomes finalized. This
          may
          > > cause application code developed for BEA WebLogic Server 6.1 that uses
          the
          > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          > > supported in future releases of BEA WebLogic Server.>
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          > > container will automatically attempt to re-establish the connection with
          the
          > > JMS server. This warning may occur during WebLogic Cluster start-up if
          the
          > > JMS destination is located on another server. When the JMS server
          connection
          > > is re-established, the Message-Driven EJB will again receive JMS
          messages.
          > > The Error was:
          > > Unable to create a JNDI InitialContext to lookup the JMS destination.
          The
          > > error was:
          > > javax.naming.CommunicationException. Root exception is
          > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          > > nested exception is:
          > > java.net.ConnectException: Connection refused: connect; No available
          router
          > > to destination
          > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:307)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:211)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          > > ory.java:149)
          > > at
          javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          > > at
          javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          > > at javax.naming.InitialContext.init(InitialContext.java:217)
          > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          > > rivenBeanInfoImpl.java:641)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          > > nPoller.java:474)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          > > .java:418)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          > > nectionPoller.java:286)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          > > foImpl.java:511)
          > > at
          weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          > > at weblogic.j2ee.Application.addComponent(Application.java:170)
          > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          > > arget.java:360)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          > > Target.java:285)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          > > eploymentTarget.java:239)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          > > entTarget.java:199)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy34.updateDeployments(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          > > ServerMBean_CachingStub.java:2977)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          > > icationManager.java:372)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          > > r.java:160)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy49.start(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          > > ApplicationManagerMBean_CachingStub.java:480)
          > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > > at weblogic.management.Admin.finish(Admin.java:644)
          > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > > at weblogic.Server.main(Server.java:35)
          > >
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010009> <EJB Deployed EJB with JNDI name
          > > ASYNCMessageDrivenBean.>
          > >
          > >
          >

Error during deploying *.ear to sap using ant

I want to deploy ear to sap with ant script,but it can not work.The error information as follows,can anybody give me some advice if you had the similar error,thanks.
C:\usr\sap\LJ1\J00\j2ee\deployment\ant>ant -f example_build.xml deploy -v
Apache Ant version 1.7.0 compiled on December 13 2006
Buildfile: example_build.xml
Detected Java version: 1.6 in: D:\Java\jdk1.6.0_18\jre
Detected OS: Windows 2003
parsing buildfile C:\usr\sap\LJ1\J00\j2ee\deployment\ant\example_build.xml with
URI = file:/C:/usr/sap/LJ1/J00/j2ee/deployment/ant/example_build.xml
Project base dir set to: C:\usr\sap\LJ1\J00\j2ee\deployment\ant
parsing buildfile jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!/org/apache/t
ools/ant/antlib.xml with URI = jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!
/org/apache/tools/ant/antlib.xml
[property] Loading C:\usr\sap\LJ1\J00\j2ee\deployment\ant\cfg\ant.properties
Build sequence for target(s) `deploy' is [deploy]
Complete build sequence is [deploy, import_ear, undeploy, params, ]
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error str
ategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'localhost', server
port '50004', user name 'Administrator'.]
[sapdeploy] Deploy timeout: null
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir c:\temp
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'c:\temp\dataservices-samples.war'
[sapdeploy] 2: 'c:\temp\test.ear'
[sapdeploy] Starting validation for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
BUILD SUCCESSFUL
Total time: 0 seconds

The problem has been resolved,I make a stupid mistake.The reason caused the error is that the user of server was locked.I hope these will be helpful for people troubled by the same mistake.

Error during deploying a mapping

Similar Messages

Maybe you are looking for