Before you start installing Oracle
SOA Suite 11g:
Plan your installation topology as
appropriate to business requirements
Ensure your platform and environment
has sufficient resources
Install and configure an Oracle
Database or supported database
Install Oracle WebLogic Server
10.3.x
Use Oracle WebLogic Server 10.3.2
for an Oracle SOA Suite 11.1.1.2.0 PS1 installation
Use Oracle WebLogic Server 10.3.3
for an Oracle SOA Suite 11.1.1.3.0 PS2 installation
Supported Software Platforms
• Supported
platforms:
– Linux
– Solaris
– HP-UX
– Windows
2000, 2003 Server, XP
• Supported
JDKs:
– Sun JDK
(32-bit and 64-bit)
– JRockit
(32-bit and 64-bit)
• Supported
Web browsers:
– Enterprise
Manager requires Firefox 3 or IE 7+
– BAM
requires IE 7
System Requirements
• Processor:
– Dual-core,
at least one 1.5 GHz CPU is recommended.
– x86,
x64, and SPARC processors are supported.
• Hard
disk drive:
– A full
installation requires approximately 15 GB of disk space.
– Swap
space (Linux) / Page file (Windows) requires 2048 MB.
– The
Linux value for file descriptors must be 4096 or greater.
• Memory:
– A
minimum of 4 GB RAM is recommended for Oracle SOA Suite 11g with Oracle
BAM
– More is
required if adding BPM Suite 11g and SOA Composite applications
Preparing the Installation
Before
starting SOA Suite 11g installation, you should have:
• Installed:
– A
Database
– A
WebLogic Server
• Created
a staging area with product software or have access to the Installation CDs
Checking and Configuring the
Database
• Supported
databases include:
– Oracle
Database 10g (10.2.0.4 or later)
– Oracle
Database 11g (11.1.0.7 or later)
• After
starting the Oracle Database, using SQL*Plus:
– Set the
processes parameter to >=300
– Set the
sessions parameter to >= 200
Note:
Restart the database for these changes to become active before you install
Oracle SOA Suite 11g.
Q. SOA infra is failed. You
are getting below error in your server
oracle.mds.lcm.exception.MDSLCMException:
MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element
"persistence-config"
MDS-01370: MetadataStore
configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body
"DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find
program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1
at
oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:710)
at
oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:198)
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:613)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at
weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
at
weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at
weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at
weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at
weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at
weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at
weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at
weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at
weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at
weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at
weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at
weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at
weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by:
oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS
configuration document
MDS-01329: unable to load element
"persistence-config"
MDS-01370: MetadataStore
configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body
"DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find
program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1
at
oracle.mds.config.PConfig.loadFromBean(PConfig.java:690)
at
oracle.mds.config.PConfig.loadFromBean(PConfig.java:517)
at
oracle.mds.config.PConfig.<init>(PConfig.java:341)
at oracle.mds.internal.lcm.MDSLCMManager.getContentConfig(MDSLCMManager.java:2015)
at
oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:505)
... 27 more
Caused by:
oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element
"persistence-config"
MDS-01370: MetadataStore
configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body
"DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find
program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1
Solution:
If you
are using Oracle XE as your database, you need to set the RCU_JDBC_TRIM_BLOCKS environment
variable to TRUE prior to running RCU.
GO to command prompt and then to the directory where RCU
is extracted.
To do
so: Right click on ‘My Computer’->Advanced Tab->Click on ‘Environment
Variables’->Under ‘System Variables’ click ‘New’->
Name:
RCU_JDBC_TRIM_BLOCKS, Value: TRUE
set RCU_JDBC_TRIM_BLOCKS environment variable.
C:\>set
RCU_JDBC_TRIM_BLOCKS=TRUE
C:\>echo
%RCU_JDBC_TRIM_BLOCKS% this should return TRUE.
Run RCU
again. Drop all the schemas. Note down the password that you gave earlier. Then
in a new command window, run above commands and in the same window run RCU and
this time create. Make sure to give the same password. The reason is you DO NOT
have to make any changes to your Domain DataSources that point to above
schemas.
Increase session and processes:
Open CMD Prompt-> type sqlplus give username and
password:
SQL> connect sys/password as sysdba;
SQL> show parameter session
SQL> show parameter processes
SQL> ALTER SYSTEM SET processes=500 SCOPE=spfile;
SQL> ALTER SYSTEM SET open_cursors=500 SCOPE=spfile;
SQL> commit;
SQL> shutdown immediate
SQL> connect sys/password as sysdba;
SQL> startup
SQL> show parameter session
SQL> show parameter processes

No comments:
Post a Comment