Deployed with warnings

Hello All,
I have a SC in a track. I have a used another SC in the same track. I can not create DCs from the used track as it is added only as a dependency.
I am using an external library DC from that SC in one the DCs of my original SC. The DC gets buils properly. But it gives the follwing error when deploying the DC
Finished with warnings: development component 'ezp3/scezp3/dc_oachanges'/'pg.com'/'GGD_EZP3DEV_D'/'20101015163419'/'0':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application pg.com/ezp3/scezp3/dc_oachanges and wait. Reason: Clusterwide exception: server ID 98155850:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application pg.com/ezp3scezp3dc_oachanges for startup. Reason=Clusterwide exception: Failed to start dependent library ''pg.com/susezpscsusezpdc_ext_lib'' of application ''pg.com/ezp3scezp3dc_oachanges''. Status of dependent component: STATUS_MISSING. Hint: Is the component deployed correctly on the engine? at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1507) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4713) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4618) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4591) at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Regards
Mrinalini

Thanks Aashtha,
I have used few web dynpro components in "used web dynpro components" in my DC. When I build the DC, it gives me the following error
[wdgen] ERROR: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to parse XML document containing VMO=com.pg.dc_utils.components.buyercodesearchcomp.BuyerCodeSearchComp., C:/Documents and Settings/283818/.dtc/0/t/CA1424309DCE741FB83B7DE1E71CAA69/gen_wdp/configuration/Components/com.pg.dc_oachanges.components.oachangescomp.OAChangesComp/OAChangesComp.xml
As soon as I remove the used web dynpro components, the rror goes off and the DC builds fine.
How do I resolve this ?
Regards
Mrinalini

Similar Messages

EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

Hi All ,
 I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
1 . 3 EJB3.0 session DCs
2. 1 JPA DC
I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
--- Deploying file(s):
 D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
--- Status:
 Deploy finished with warnings.
--- Description:
 S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 1
Failed deployments: 0
~~~~~~~~~~~~~~~~~~~
1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
 Name:erecapp
 Vendor:asianpaints.com
 Location:J2N_ERECTT_D
 Version:20090217100038
 Deploy status:Warning
 Version:HIGHER
 Description:
 1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
 at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
 at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
 at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
 at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
 at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:Warning

You have to give an explicit data source in your persistence.xml to solve this error normaly.
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
 <persistence-unit name="YOUR_UNIT">
 <jta-data-source>DSNAME</jta-data-source>
Frank

Deploy with warning

Hi.All.
when i deployed WD application , it end with warning ,could someone tell me how to do.
--- Deploying file(s):
     E:\Documents and Settings\MrBryant\workspace_rt.jdi\LocalDevelopment\DCs\demo.sap.com\tutorial_pagenavigation\_comp\gen\default\deploy\demo.sap.com~tutorial_pagenavigation.ear
--- Status:
     Deploy finished with warnings.
--- Description:
            S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed:           0
Deployed with warnings:           1
Failed deployments:                0
~~~~~~~~~~~~~~~~~~~
1. File:E:\Documents and Settings\MrBryant\workspace_rt.jdi\LocalDevelopment\DCs\demo.sap.com\tutorial_pagenavigation\_comp\gen\default\deploy\demo.sap.com~tutorial_pagenavigation.ear
     Name:tutorial_pagenavigation
     Vendor:demo.sap.com
     Location:localDevelopment
     Version:20090421170011
     Deploy status:Warning
     Version:HIGHER
     Description:
          1. Exception has been returned while the [demo.sap.com/tutorial_pagenavigation] was starting. Warning/Exception :[
][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 48033250:can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB
           -> com.sun.enterprise.iiop.POAEJBORB
------------------------- Loader Info -------------------------
ClassLoader name: [service:deploy]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [library:core_lib]
   [library:tc~bl~txmanager~plb]
   [service:iiop]
   [service:file]
   [library:tc~je~jlinee~lib]
Resources:
   /usr/sap/C04/J04/j2ee/cluster/bin/services/deploy/lib/private/sap.com~tc~je~deploy~impl.jar
server ID 48033250:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [demo.sap.com/tutorial_pagenavigation] cannot be started. Reason: it has hard reference to resource [tc~wd~api] with type [application], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
     at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
     at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:467)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:560)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3432)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3418)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3308)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3280)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/tc~wd~api] cannot be started. Reason: it has hard reference to resource [tc~wd~dispwda] with type [application], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
     at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
     at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:142)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:582)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3229)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3221)
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
     ... 35 more
Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application [sap.com/tc~wd~dispwda].
     at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.prepareStart(StartAction.java:246)
     at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.prepareStart(WebContainer.java:420)
     at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:228)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:194)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3229)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3221)
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
     ... 46 more
Caused by: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB vmcid: 0x0 minor code: 0 completed: No
     at org.omg.CORBA.ORB.create_impl(ORB.java:297)
     at org.omg.CORBA.ORB.init(ORB.java:336)
     at com.sap.engine.services.servlets_jsp.server.application.NamingResources.bindNamingResources(NamingResources.java:147)
     at com.sap.engine.services.servlets_jsp.server.application.ApplicationContext.init(ApplicationContext.java:937)
     at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.createContext(StartAction.java:305)
     at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.prepareStart(StartAction.java:141)
     ... 56 more
Caused by: java.lang.ClassNotFoundException: com.sun.enterprise.iiop.POAEJBORB
------------------------- Loader Info -------------------------
ClassLoader name: [service:deploy]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [library:core_lib]
   [library:tc~bl~txmanager~plb]
   [service:iiop]
   [service:file]
   [library:tc~je~jlinee~lib]
Resources:
   /usr/sap/C04/J04/j2ee/cluster/bin/services/deploy/lib/private/sap.com~tc~je~deploy~impl.jar
     at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:274)
     at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:243)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:363)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
     at org.omg.CORBA.ORB.create_impl(ORB.java:295)
     ... 61 more
Result
Status:Warning
Edited by: zhenhua peng on Apr 21, 2009 11:24 AM

Hi,
From the logs it is clear that your application is dependent on [tcwdapi] which is either not deployed on the target server or failed to start. This is called as class loader exception. To overcome this issue, you have to either deploy the reference application or see to that it is in "Started" status in the target server. If you have trouble in starting the application, then it might be necessary to restart the java server and then do the deployment.
Regards,
Pranav

ESS/MSS business packages "Deployed with Warning"

Hello All,
 We are on NW04s SP10 on MS SQL server and Windows server. The Database and portal installations or on different machines. I installed the business packages ESS 1.0, MSS 1.0 and the XSS components - 600 using the JSPM.
After I deploy, I get the message "Deployed with Warning"
When I opened the log files and checked for errors, I found errors in deployment on these SDAs
sap.com/essfiaddr - WEBDYNPRO
sap.com/essinaddr - WEBDYNPRO
sap.com/essinpdata - WEBDYNPRO
sap.com/mssexpdyn - WEBDYNPRO
sap.com/mssexpssa - WEBDYNPRO
sap.com/mssoprogeneraldescription - WEBDYNPRO
And I get the following exceptions for all the SDAs above.
07/01/11 09:54:10 - sap.com/essfiaddr - WEBDYNPRO
07/01/11 09:54:10 - ***********************************************************
Jan 11, 2007 9:54:11 AM Info: End of log messages of the target system.
Jan 11, 2007 9:54:11 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 11, 2007 9:54:11 AM Warning: Finished with warnings: development component 'ess/fi/addr'/'sap.com'/'MAIN_ERP05PAT_C'/'795293':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/addr and wait.
Reason: Clusterwide exception: server ID 11376250:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfiaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfiaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
 at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:231)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:317)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:227)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4684)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4589)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4562)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Now, after this, when I log into the portal and see the MSS role, the links are all missing. I see only Overview and its worksets and pages and Reports and its worksets. Everything else is missing. The warning that I see is "Linked object is unavailable"
Could anyone please suggest me what could be wrong?
Thanks,
Sunitha

Hi Sunitha,
First of all I was not able to find if your backend is ERP 2004 or ERP 2005. It should be ERP 2005 if you want to user ESS 1.0 and MSS 1.0 BP
Please check in Content Administrator if you can locate these applications and test the same. If yes then you can ignore this warning. If No, in that case you have to redeploy XSS, ESS and MSS using SDM again.
The links in portal comes from your backend Area Page Customizing. To verify if the problem is with your Portal Business Package or with your backend customizing run your ESS applications using
http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTESS
and MSS using
http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTMSS
If you can see all the links correctly here, your backend customization is fine and there is a problem with your BP of ESS and MSS. So you will have to import the same again in the portal. However if you are not able to view the links in the page, then there is a problem with you Area Page Customization. You will need to check your config with the Client 000 configuration to find out the missing config.
Hope this helps.
Regards,
Shubham

Java DC not deployed with WebDynPro DC

Hi,
I've been testing the DC functionality and I'm trying to create the following:
1) WebDynPro DC (DCA)
2) Java DC (DCB)
DCB has code for reading data from a database table (three classes, one is set as a public part). This code is functioning ok in another WebDynpro project where I've used it as an external jar file located in the lib directory and added to classpath.
DCA has a small table in the view that I'm filling (or trying to) with data from the database.
DCB has one java class as a Public Part. DCA has this PP defined in the Used DC's (DC Metadata --> DC definition --> Used DC's). I can see the DCB code fine from the DCA's view (I can use the methods from the class).
I see no code errors and everything compiles ok. I've built the DCA and DCB separately (Development Component --> Build) before doing the project build and deployment.
When I deploy, I'm getting java.lang.NoClassDefFoundError for the DCB class (User.class) when the program starts. So it seems that the DCB is not deployed with the DCA. I've tried to look at the properties and java classpath but nothing I've done has helped.
Purpose is set to compilation, and there is a
<at-build-time/>
tag in the .dcdef file.
Deployment of normal (no DC) Webdynpro projects works fine and the jars in the lib directory are deployed to the server OK.
Seems like I've tried everything but have found no solution yet. Refreshed every part, re-created everything, re-built, re-deployed etc...
Shortly: how to get DCB to deploy ?
Any help is appreciated here
Kind Regards,
Jari Pakarinen

Hi,
What is the Java DC for then ? If it cannot be used as a part of another DC (deployable unit) then how should it be used ? What is the use if it does not end up at the server with Webdynpro code ?
The scenario I'm looking for is to include Java classes in a Webdynpro project as a part of the project (not jars done somewhere else, I can do that already) deployed to the server with the Webdynpro.
Thank you for your help, I'm not blaming you or anything
Regards,
Jari

How to use MDS deploying with EAR file

Hi everybody.
I would to use MDS in my web application in order to use customization across the sessions. I've performed every step to do this on JDeveloper (11.1.1.3.1). I've tested my application deploying directly from JDeveloper using Application menu > Deploy > "myApp" to "myApplicationServer" (in this way I can choose the repository with a window like this: http://i.stack.imgur.com/Kci9c.png). The repository was prevoiusly registered on the server. In this way my application works fine and they all lived happily ever after.
My problem occurs when I perform the deployment with "myApp to EAR" mode. When I try to install my EAR file in weblogic, it reply me with this error message:
An error occurred during activation of changes, please see the log for details.
+:oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.+
I've looked for a solution around the web (included this forum) and I think that I should modify something in adf-config.xml file (below).
Which steps I have to perform in order to install my application correctly with an EAR file?
Thanks in advance.
<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config"
xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
xmlns:sec="http://xmlns.oracle.com/adf/security/config"
xmlns:ads="http://xmlns.oracle.com/adf/activedata/config">
<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
<adf-property name="adfAppUID" value="BDO_GC_WEBAPP.bdogc"/>
</adf:adf-properties-child>

<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
<sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
authorizationEnforce="true"
authenticationRequire="true"/>
</sec:adf-security-child>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
<persistent-change-manager>
<persistent-change-manager-class>
oracle.adf.view.rich.change.MDSDocumentChangeManager
</persistent-change-manager-class>
</persistent-change-manager>
<taglib-config>
<taglib uri="http://xmlns.oracle.com/adf/faces/rich">
<tag name="column">
<attribute name="displayIndex">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="frozen">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="noWrap">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="selected">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="visible">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="width">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
<tag name="table">
<attribute name="filterVisible">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
</taglib>
</taglib-config>
</adf-faces-config>
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
<cust-config>
<match path="/">
<customization-class name="oracle.adf.share.config.UserCC"/>
</match>
</cust-config>
</mds-config>
</adf-mds-config>
</adf-config>

Any suggestion?

PL/SQL will compile with warnings but will not run

I have a pl/sql package that will compile with warnings but no errors but when i try to run it I get an ORA-6508 error telling me there is an error somewhere in the package but I can't find it.
I have two user schemas that use 2 slightly different versions of the package. I had to make slight code changes to one of the versions and when I made those changes it stopped running. The second version compiles and runs correctly.
After going through a line by line comparison the first copy was still not running. I copied the second version of the code into the broken schema and commented out the additional lines of code that are not needed in this version.
When I tried to compile and run this version it still fails with the same error.
I am using Oracle XE and the databases are small.
I can send on the code if necessary.
Can anyone point me in the right direction?
Thanks
Susan

I tried doing what you suggested but there are no errors as it is compiling correctly.
It is only when I run the package through the debugger that I get the error. I have posted it below
Connecting to the database Hess S3.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '2086' )
Debugger accepted connection from database on port 2086.
Processing 59 classes that have already been prepared...
Finished processing prepared classes.
Exception breakpoint occurred at line 10 of BnmSkOTQ3jz5I52ZOxC4QNw.pls.
$Oracle.EXCEPTION_ORA_6508:
ORA-04063: package body "SHIPPING.LIFTINGSCHEDULE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SHIPPING.LIFTINGSCHEDULE"
ORA-06512: at line 10
Process exited.
Disconnecting from the database Hess S3.
Debugger disconnected from database.
Regards
susan

Import Successful with warnings....ORA-01658 error..

Friends,
OS: RHEL AS 3.0
DB: Oracle 9iR2
When i try to import the dump, i am getting the below message.
"Import was successful with warnings"
when i check the log file there is
IMP-00017: following statement failed with oracle error 1658:
IMP-00003: ORACLE error 1658 encountered
ORA-01658: unable to create INITIAL extent for segment in tablespace PROD_DEFAULTPlease check the below, this is what i did before importing.
I want to import only the table structures without rows from the user "SMS" to "NMS".
After creating the below tablespace the free space in "/u02" is 3GB.
AM i have to change any value in the below statement?
CREATE TABLESPACE "PROD_DEFAULT" DATAFILE
'/u02/oradata/PROD_DEFAULT.dbf' SIZE 3072M REUSE
LOGGING ONLINE PERMANENT BLOCKSIZE 8192
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
CREATE TEMPORARY TABLESPACE "PROD_TEMP" TEMPFILE
'/u02/oradata/PROD_TEMP.dbf' SIZE 3072M REUSE
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
CREATE USER "NMS" IDENTIFIED BY "SDF345345KLSDSD8K" DEFAULT
TABLESPACE "PROD_DEFAULT"
TEMPORARY TABLESPACE "PROD_TEMP"
GRANT CONNECT,RESOURCE TO NMS
[oracle@linuxdb oracle]$ imp system/password file=/u02/today1.dmp
log=/u02/today1.log fromuser=sms touser=nms rows=n buffer=8000000 commit=yNote:
Even if i omit "buffer" and "commit" the same error occurs.
where im making a mistake? Is there any changes i have to made in the create tablespace statement.
Please point out the mistake.
thanks & regards

not for a single statement. for all the statements
its showing the error.instead of 512 tables
structures, only 490 tables structures were created.Because it was not able to allocate contiguous space in the tablespace.
>
actually i want to import "NMS_DEFAULT" tablespace's
table structures to "PROD_DEFAULT" tablespace.
also I want to import only the table structures
without rows from the user "SMS" to "NMS".Use FROMUSER/TOUSER for this and set the default tablespace for NMS as PROD_DEFAULT.
Now specify rown=N while running import or at the time of running export itself.
i created the "NMS_DEFAULT" tablespace with 3072M.
so i created the "PROD_DEFAULT" tablespace with the
same size.
actually i created the "PROD_DEFAULT" tablespace
using below output.
"select
dbms_metadata.get_ddl('TABLESPACE','NMS_DEFAULT')
from dual"You didnt allocate sufficient space to the tablespace, i guess.
Amardeep Sidhu
http://www.amardeepsidhu.com
Corrected a mistake...
Message was edited by:
Amardeep Sidhu

Imp full db successful with warnings

Looking for options to fix those , or can i ignore them? What would be side effect if i drop/cascade users and re-run imp after increasing tablespace TS_PUBLIC size or i should not do that? and just fix the little warnings or even just ignore them?
Most of tables (i would say 95% ) & there data imported successfully after full imp , db size is 80GB around, import terminated successfully with warnings , which are below.....
IMP-00017: following statement failed with ORACLE error 1659:
"CREATE TABLE "CA_QUERY_1"
"ABLESPACE "TS_PUBLIC""
IMP-00041: Warning: object created with compilation warnings
"CREATE FORCE VIEW "ADMIN"."CHECK_EXTENTS_V"
IMP-00041: Warning: object created with compilation warnings
"CREATE TRIGGER MT1758.MEDDRA_MT1758_THE_SYN_UPD"

DBA2011 wrote:
Looking for options to fix those , or can i ignore them? What would be side effect if i drop/cascade users and re-run imp after increasing tablespace TS_PUBLIC size or i should not do that? and just fix the little warnings or even just ignore them?
Most of tables (i would say 95% ) & there data imported successfully after full imp , db size is 80GB around, import terminated successfully with warnings , which are below.....
IMP-00017: following statement failed with ORACLE error 1659:
"CREATE TABLE "CA_QUERY_1"
"ABLESPACE "TS_PUBLIC""
IMP-00041: Warning: object created with compilation warnings
"CREATE FORCE VIEW "ADMIN"."CHECK_EXTENTS_V"
IMP-00041: Warning: object created with compilation warnings
"CREATE TRIGGER MT1758.MEDDRA_MT1758_THE_SYN_UPD"; I would suggest you to look at export log and find out which are the tables that got failed and import only those tables again. Since the size is quite high as you said.
Secondly, since 95% tables are already import, so i suggest you to increase the Tablespace size by adding datafile or extending existing one, then run the import for rest 5% tables.
Third, You said can you ignore warning? During import oracle tries to create Views, it first check if the tables from which view is being create are already exists or not. If the tables doesn't exists oracle will create view forcefully, and mark these view as invalid. The only way to make the views valid is to alter the views definition to point to the correct base tables.
So there is little activity left after import is done with warning, that you have to alter the view definitions so that correct tables can be used.
Also see MOS -> IMP-00041 ORA-04063 FROMUSER/TOUSER IMPORT INTO NEW DATABASE [ID 1059520.6]
Hope my suggestions helps you

SCCM: Application deployment vs Package deployment with requirements and prerequisits.

Hey,
My organization is in the process of implementing a new remote networking solution for all employees, however some employees require additional software vs others. What I am trying to find out is if there is a way to have one package with supersedes and
requirements that we can use to do a massive deployement.
Here are the different scenarios with order of installation:
Financial group Desktop:
1.Install New solution
2.Install Configuration
3.Install Token Authentication
(nothing crazy)
Financial Group Laptops
1.Install Token Authentication
2.Install New Solution
3.Install COnfiguration
4.Un-uninstall Old Solution
5.Un-install Tunnel Guard application (requires a reboot, that's why it's last). (this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 5, but do 4, when 4 is triggered, it does 3 first, etc...)
All other laptops
1.Install New Solution
2.Install COnfiguration
3.Un-uninstall Old Solution
4.Un-install Tunnel Guard application (requires a reboot, that's why it's last).(this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 4, but do 3, when 3 is triggered, it does 2 first, etc...)
Because of the different requirements, is there a way to have one deployment with multiple deployment types to say based off:
1. Computer types (we have a naming convention that identifies laptops and desktops.
2. Only install certain pieces of software (Token validator in this case if financial application is detected on the machine).
Or should I create different applications for each case with different collections or go with 3 different packages and collections with install this package first set in the package deployment
Thanks for your help.

The problem is the last uninstall, because it's not applicable to all machines. That means that if you would deploy that with all it's dependencies, it wouldn't do anything on the desktops as it's not applicable to them.
In this case, if you want to use one deployment, the easiest solution is a task sequence. That way you can target everything in one time and still build some logic to prevent some (un-)installs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Patch deployment with status "Enforcement state unknown"

Hi All
I am pretty new to the patch deployment.
I generated a report and see there is Last State column with "Enforcement state unknown", not sure if it means failed for those hostnames or will be retried for the installation.
Kindly clarify.
Regards
Ramesh
Regards Ram

They will only start to install updates automatically when there is an active update deployment with a scheduled deadline that has past. See for a lot more information:
http://technet.microsoft.com/en-us/library/gg682168.aspx#BKMK_SUMCompliance
Also, when Days since last communication is more than 0, that's usually an indication that the client is not communicating any more. That can be caused by a lot of things including something simple as that the device is turned of, or not
connected with the network.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70

SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70
Have you tried to port and run (Sneak Preview) SAPNetWeaver java 04 SP16 or 04S SP7 with a later version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_(8 or greater)?
What specifically is failing? What patches or work around have you used to overcome compatibility issues with Xalan?
When we run Sneak Preview SAPNetWeaver java 04 SP16 SP7 with a version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_11, We get error 503 Service Unavailable, Application cannot be started
Details: com.sap.engine.services.deploy.container.ExceptionInfo: Error while parsing file data-source-aliases.xml.

Hi
SAP does not allow usage of any other XML parsers with SAP web AS.
please have a look at this link
http://help.sap.com/saphelp_nw04/helpdata/en/36/ef353e39011a38e10000000a114084/frameset.htm
"Setting system properties in a system that supports more than one parser is prohibited".
The Error which you are getting is because one of the
java.system properties for parsing is
getting changed by xalan. These system properties are explictly set by the SAP XML implementation which it does not allow you to change.
Also can you please let me know where are you placing the xalan jar file ? is it deployed as a j2ee library or part of war ?
Hope this helps. please mark points for helpful answers
regards
rajesh kr

GRC 10.1, AC - BC set with Warnings and no data

Hi Gurus,
We are on GRC 10.1. We activated the BC set GRAC_RA_RULESET_SAP_R3, which ended with warnings, but no errors. Warning messages in two sets as below:
1.
VC_GRFN_CCI_TS_CONNECTOR
Customizing object VC_GRFN_CCI_TS_CONNECTOR passed to activation
VC_GRFN_CCI_TS_CONNECTOR
View V_GRFNCONNTYPE: View cluster VC_GRFN_CCI_TS_CONNECTOR does not contain data at all levels
VC_GRFN_CCI_TS_CONNECTOR
View V_GRFNCCICONNECT: View cluster VC_GRFN_CCI_TS_CONNECTOR does not contain data at all levels
VC_GRFN_CCI_TS_CONNECTOR
View V_GRFNCONNGRPTYP: View cluster VC_GRFN_CCI_TS_CONNECTOR does not contain data at all levels
VC_GRFN_CCI_TS_CONNECTOR
View V_GRFNCGRPCONLNK: View cluster VC_GRFN_CCI_TS_CONNECTOR does not contain data at all levels
VC_GRFN_CCI_TS_CONNECTOR
Activation of customizing object VC_GRFN_CCI_TS_CONNECTOR ended with warning
2.
Object
Message Text
GRFNVC_CCI_TS_CONNECTOR
Customizing object GRFNVC_CCI_TS_CONNECTOR passed to activation
GRFNVC_CCI_TS_CONNECTOR
View V_GRFNCONNTYPE: View cluster GRFNVC_CCI_TS_CONNECTOR does not contain data at all levels
GRFNVC_CCI_TS_CONNECTOR
View V_GRFNCCICONNECT: View cluster GRFNVC_CCI_TS_CONNECTOR does not contain data at all levels
GRFNVC_CCI_TS_CONNECTOR
View V_GRFNCCISSEQCON: View cluster GRFNVC_CCI_TS_CONNECTOR does not contain data at all levels
GRFNVC_CCI_TS_CONNECTOR
View V_GRFNCONNGRP: View cluster GRFNVC_CCI_TS_CONNECTOR does not contain data at all levels
GRFNVC_CCI_TS_CONNECTOR
View V_GRFNCGRPCONLNK: View cluster GRFNVC_CCI_TS_CONNECTOR does not contain data at all levels
GRFNVC_CCI_TS_CONNECTOR
Activation of customizing object GRFNVC_CCI_TS_CONNECTOR ended with warning
When we go and look for the ruleset files, which ideally should have been populated after the ruleset for the BC set is generated, we see only the Risks being populated in NWBC. Neither the functions or the ruleset names appear there and same is the case for the Business Processes, which are still not populated.
Anyone has any clue how to resolve this?
Thanks & Regards,
Hersh

Thanks for your response Harinam. Must admit I thought more people on here would have had experience of this jump, but clearly most people went from 4 to a 5.x system. In some ways it is a very good thing the customer has held back from jumping to Java.
Anyway, I had logged a message with OSS in parallel to posting here, thought I would get a good balance of views doing both.
Here is the official answer we received :
Once the GRC 10.1 plugin will be installed on the GRC 4.0 system,
though the 4.0 product is still accessible and the data will still
remain in the tables, it is no longer supported and it must be clear
to your users and administrators that the 4.0 product is not to be
used with the v10.1 plugin.
SAP Active Global Support
SAP Labs Palo Alto
So although I could argue that 4.0 is unsupported so what is the difference, this response is useful to our project team as it further justifies the need to upgrade.
I am still interested in hearing from anyone who has done this migration path and tried the old tcodes, to know for sure what the result would be.
I assume also based on the response from OSS we should lock the 4.0 tcodes to make sure no-one hits an old favourite, seeing as they clearly are not removed as part of the migration process.
cheers,
Andy

DB check finished with warnings

Hello All,
In SAPCHECK latesh .chk file finished with warnings
BR0280I BRCONNECT time stamp: 2009-03-26 10.30.46
BR0815I Number of indexes in schema of owner SAPAUTH: 2
BR0815I Number of indexes in schema of owner SAPR3: 49400
BR0815I Number of indexes in schema of owner SYS: 299
BR0815I Number of indexes/partitions in schema of owner SYSTEM: 228/24
BR0838W Table YSEX_UPL2SAP_1001 not found for segment SAPR3.YSEX_UPL2SAP_1001 - ignoring segment
Kindly help me to resolve the issue.
Regards
Mohsin Mulani

Mohsin,
Please check out following link.
[Re: ORA-03113: end-of-file on communication channel]
Please also check following notes.
Note 1137346 - Oracle Database 10g: Patches for Release 10.2.0.4
Note 871096 - Oracle Database 10g: Patch sets/patches for 10.2.0.
Hope this helps.
Manoj

DB check finished with warnings CRITICAL_TABLESPACE, object: PSAPSR3USR,

Hello All,
database >> oracle 10g
Autoextend is on for 2 datafile
cd sapcheck >> latest check file finished with warnings
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3USR, value: (max_extn of 2 files on disk 6815746) 36569088 KB (> 32505952 KB)
SQL> select FILE_NAME,BYTES/1024/1024,AUTOEXTENSIBLE,MAXBYTES/1024/1024,INCREMENT_BY from dba_data_files where TABLESPACE_NAME='PSAPSR3USR';
FILE_NAME
BYTES/1024/1024 AUT MAXBYTES/1024/1024 INCREMENT_BY
/oracle/ADE/sapdata1/sr3usr_1/sr3usr.data1
2500 YES 20000 2560
/oracle/ADE/sapdata1/sr3usr_2/sr3usr.data2
2500 YES 20000 2560
kindly help me to resolve issue
Regards
Mohsin
Edited by: mohsin m on Dec 24, 2008 10:59 PM

Hi,
Can you please check the avaliablity of free space on disk.
"CRITICAL_TABLESPACE Warning Description: Examines the data of a tablespace to see whether the file system can be brought to overflow, due to the existing parameter setting (NEXT and MAXSIZE), during the automatic file extension."
--Kishore

Deployed with warnings

Similar Messages

Maybe you are looking for