This discussion is archived
0 Replies Latest reply: Dec 19, 2013 6:27 AM by skjb RSS

OPSM 1.2 [Oracle pedigree and Serialization manager] installation is failed

skjb Newbie
Currently Being Moderated

Hi All,

We are doing OPSM 1.2 installation on Oracle Enterprise Linux 5.6 [64-bit].

Steps we have done:

####################################################################

1. installed 11g db and created repositories for soa server.

2. installed weblogic server 10.3.6

3. Installed soa server & created two managed servers soa_server1 and pas_server1 in weblogic as per the doc " Oracle Pedigree and Serialization Manager Installation Guide"

4. And created required schemas in db for OPSM.

5. and ran $MW_ORA_HOME/common/bin/wlst.sh ./pasMasterInstall.py

######################################################################

 

 

Below are The error we are getting at the time of deployment is:


Deploying the PasSerializationManager application...

Deploying application from /u01/ORASOA/Middleware/Oracle_SOA1/pas/applications/install/PasSerializationManager.ear to targets pas_server1 (upload=false) ...

<Dec 19, 2013 7:56:03 AM EST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, PasSerializationManager [archive: /u01/ORASOA/Middleware/Oracle_SOA1/pas/applications/install/PasSerializationManager.ear], to pas_server1 .>

....................................................................................................No stack trace available.

This Exception occurred at Thu Dec 19 08:01:04 EST 2013.

weblogic.management.scripting.ScriptException: Error occured while performing deploy : The action you performed timed out after 300,000 milliseconds.

 

 

Error: Unable to deploy the Ear Files.

 

 

-------------------------------------------------------------------------

Shutting down the AdminServer...

-------------------------------------------------------------------------

Stopping the AdminServer...

Finished stopping the AdminServer.

 

 

-------------------------------------------------------------------------

Moving the Installed Files to the Install Directories...

-------------------------------------------------------------------------

Finished moving files to install directory.

 

 

-------------------------------------------------------------------------

Restoring Backup...

-------------------------------------------------------------------------

Finished restoring backup.

 

 

-------------------------------------------------------------------------

ERROR: Installation Failed!

 

 

Note: Please review the above output buffer to determine what error(s)

      have occurred. You must fix any errors before attempting to

      retry the installation.

 

 

WARNING: System failed to register the MDS Repository with WebLogic. It is likely

that the MDS Repository has already been registered. Please verify the registered

metadata repositories using Oracle's Enterprise Manager application. Once logged

into Enterprise Manager, expand the Metadata Repositories node and verify an entry

exists for mds-mds-ApplicationMDSDBDS. In addition, click on the repository and

verify it is targeted to the appropriate servers.

 

 

-------------------------------------------------------------------------

 

Exiting WebLogic Scripting Tool.

 

 

<Dec 19, 2013 8:01:09 AM EST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>

 

 

In pas_server1.log file:

 

Caused By: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config"

MDS-01370: MetadataStore configuration for metadata-store-usage "MAR_TargetRepos" is invalid.

MDS-00929: unable to look up name "jdbc/mds/opsm" in JNDI context

Unable to resolve 'jdbc.mds.opsm'. Resolved 'jdbc.mds'

 

 

        at oracle.mds.config.PConfig.loadFromBean(PConfig.java:1008)

        at oracle.mds.config.PConfig.<init>(PConfig.java:767)

        at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:1151)

        at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:1218)

        at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:781)

        at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:728)

        at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:529)

        at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:211)

        at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)

        at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:77)

        at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)

        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)

        at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)

        at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)

        at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)

        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)

        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)

        at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)

        at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)

        at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)

        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)

        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)

        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)

        at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)

        at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)

        at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)

        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)

        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)

        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)

        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

 

 

 

 

Any one please  provide resolution to fix the issue.

 

 

 

Thanks

skjb    

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points