ASM instance in the cluster shows status pending in grid control

All,
I have the ASM instance in separate home and the cluster database in another home .
I am able to see the cluster database up and running in the grid control but somehow cant see the ASM instance .
I will appreciate any pointers .
thanks in advance
Pk

Try these two things:
1) Deployments=>Refresh Host Configuration=>Select the hostname and then hit on "Refresh Hosts".
If that doesn't work
2) Targets=>Databases=>Select the ASM Instance=>Configure
HTH
Thanks
-Chandra Pabba

Similar Messages

Status Pending on Grid Control

Hi,
On the Grid Control -> All Targets Type=Cluster
I have the "Status Pending" on my target Cluster.
All the nodes are up as also as all the agents, instances, etc...except the cluster that appears to be "Status Pending".
I tried to restart all the agents and refreshing the configuration, but the "status pending" remains.
Anyone has any idea?
Thanks.
Best regards,
José Carlos

Grid Control server can connect to target database 1521(listener port)?
Grid Control server -> target database:1521
Grid Control server -> target database:agent port (3872)
target database -> Grid Control server: 4889 ; (upload agent file)
http://download.oracle.com/docs/html/B12013_03/firewalls.htm
Please check your connect
After that clear state
1. Stop the agent on the target node
emctl stop agent
2. Delete any pending upload files from the agent home
cd $AGENT_HOME/<hostname>/sysman/emd/
rm -r state/*
rm -r collection/*
rm -r md/upload/*
rm lastupld.xml
rm agntstmp.txt
rm blackouts.xml
3. Issue an agent clearstate
emctl clearstate agent
4 Start the agent
emctl start agent
5. Force an upload to the OMS
emctl upload agent
Good Luck

Multiple ASM instances using single cluster install - Is it possible??

Hi,
I have 2 node RAC cluster installed on Linux. All the storage is on EMC. I need to setup another environment using HP storage on the same hosts. Is it possible to created second ASM instance using the same cluster install?? I wanted to have clear separation b/w EMC and HP environments and that's wondering if it's feasible to do that.
Haven't tried it yet to see if it complains.
Thx
Anitha

Anitha,
The data migration won't happen (at least not aggressively) until you do step 2 in your list where you remove the EMC disks. That removal operation will take a long time as Oracle will have to move the data before it can complete the operation. If you want to be sure, I'd recommend creating a new disk group with one of your new disks, put a small tablespace in it, create some data in it, then add a disk to that new group and remove the original disk. Then you'll have some confidence in the procedure and verify that it works without risking your production data. After you test, you can drop the disk group and use the disks for their intended purposes.
To answer your question, yes, that's the process exactly as I suggested it above. Should work fine--but will probably take a while to do the remove, so be prepared to leave that running for quite a while (i.e. don't expect to close the terminal and go home right after running the remove).
Dan

Workflow: Even if PO is released the log shows status as 'In Progress'

Dear All,
I have created custom workflow for PO approval procedure. I have 3 step approval process and have specified same User ID as agent to all 3 levels. Now I am facing below issues in my workflow
1) It is getting triggered twice, I have specified only one start condition as RELEASESTEPCREATED, why is this happening?
2) If I execute the workflow from SWBP for release, even after release of PO the step shows status as 'In Progress' in SWIA, its not going to complete status. Hence not going to next step.
Please guide me on the above issues.
Thanks and Regards,
Aniket

If you are using standard Workflow WS20000075 on releasing the PO a notification workitem is ent to the Initiator which displays the PO. On executing this workitem the workflow instance get completed. This is a standard solution if you need to change it then copy it and customize it accordingly.
Thanks
Arghadip

ASM instance removal not happening: showing ora.asm still runing

I am trying to remove the ASM instance, though the ASM instance is down, still it shows resouce ora.asm is running.
Could you please help me to remove the ASM instance.
oracle@tbardbb2:/usr/home/rcummins> srvctl remove ASM -n tbardbb2
-n option has been deprecated and will be ignored.
PRCR-1025 : Resource ora.asm is still running
Now I stopped the resource: crsctl stop resource ora.asm -n tbardbb2 -f
now while deleting it shows:
oracle@tbardbb2:/usr/home/rcummins> srvctl remove asm -n tbardbb2
-n option has been deprecated and will be ignored.
PRCR-1001 : Resource ora.asm does not exist
How will I check if my ASM instance is removed..
Edited by: 784786 on Jul 29, 2011 5:26 PM

784786 wrote:
I am trying to remove the ASM instance, though the ASM instance is down, still it shows resouce ora.asm is running.
Could you please help me to remove the ASM instance.
oracle@tbardbb2:/usr/home/rcummins> srvctl remove ASM -n tbardbb2
-n option has been deprecated and will be ignored.
PRCR-1025 : Resource ora.asm is still running
Now I stopped the resource: crsctl stop resource ora.asm -n tbardbb2 -f
now while deleting it shows:
oracle@tbardbb2:/usr/home/rcummins> srvctl remove asm -n tbardbb2
-n option has been deprecated and will be ignored.
PRCR-1001 : Resource ora.asm does not exist
How will I check if my ASM instance is removed..
Edited by: 784786 on Jul 29, 2011 5:26 PM
HI,
Please read note How to remove an ASM instance and its corresponding database(s) on UNIX [ID 357261.1] for the details
CHeers

EM12c: Target SQL Server 32-bit shows "Status Pending"

Configuration:
EM12c platform:
Oracle Enterprise Linux 6.2(x86_64)
Oracle Enterprise Database 11.2.0.3 (x86_64)
Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) (x86_64)
Microsoft SQL Server Plug-In 12.1.0.2.0 deployed in the Management Server
Target:
Windows Server 2003 Standard Edition Service Pack 2 (32-bit)
SQL Server 2005 SP2 (Standard Edition) (32-bit)
Microsoft SQL Server Plug-In 12.1.0.2.0 deployed in the Management Agent
Problem:
EM12C: Targets > Databases
The SQL Server 32-bit target shows "Status Pending"
Verified the Target Agent Logs and found.
D:\oracle\Middleware\agent_inst\sysman\log\gcagent.log
2012-09-20 17:36:25,833 [14939:C578F997] INFO - Adding a new target [microsoft_sqlserver_database.mssql_peregrine.esri.com]
2012-09-20 17:36:28,271 [15029:7DDB51EF:GC.DPExecutor2.57 (CDProps:microsoft_sqlserver_database.mssql_peregrine.esri.com:agent_host)] WARN - Found a row with more columns than declared for the metric for TargetID = mssql_peregrine.esri.com, Metric = OSType_Agent_DynamicProperty
Row = Microsoft Windows Server 2003 Standard Edition,,C:\\WINDOWS,\\Device\\Harddisk0\\Partition2
2012-09-20 17:36:28,583 [15031:1C41A703:GC.DPExecutor2.58 (CDProps:microsoft_sqlserver_database.mssql_peregrine.esri.com:win_host_name)] WARN - Found a row with more columns than declared for the metric for TargetID = mssql_peregrine.esri.com, Metric = OSType_TargetHost_DynamicProperty
Row = Microsoft Windows Server 2003 Standard Edition,,,C:\\WINDOWS,\\Device\\Harddisk0\\Partition2
2012-09-20 17:36:28,755 [15073:9240A7B9:GC.DPExecutor.27 (CDynamic:microsoft_sqlserver_database.mssql_peregrine.esri.com)] INFO - Target: [microsoft_sqlserver_database.mssql_peregrine.esri.com] is broken: Dynamic Category property error
2012-09-20 17:36:28,755 [15073:9240A7B9] INFO - Target: [microsoft_sqlserver_database.mssql_peregrine.esri.com] is broken: Dynamic Category property error,Get dynamic property error
2012-09-20 17:36:29,286 [15073:9240A7B9] INFO - Starting collection for target: [microsoft_sqlserver_database.mssql_peregrine.esri.com$12]
2012-09-20 17:36:29,286 [14939:C578F997] INFO - >>> Reporting response: AddTargetsResponse (request id 1) <<<
2012-09-20 17:36:29,286 [14939:C578F997] INFO - (end processing requests for OMS@[email protected]=>[134818747370001])
Tried the following without success:
- remove target and add target again
Database Username (Required for SQL Authentication): sa
Password of Database User (Required for SQL Authentication): ****
Role (Optional)
System Password (Needed when SQLServer is at remote location): <empty>
System Username (Needed when SQLServer is at remote location): <empty>
Connect Using Windows Integrated Authentication (Yes/No): No
JDBC Driver (Optional): com.microsoft.sqlserver.jdbc.SQLServerDriver
JDBC URL (Example : jdbc:sqlserver://<host>:<port>): jdbc:sqlserver://peregrine.esri.com:1433
- Add Target don't let me fill the System Password and System Username, get message that says is not required.
- Configure target, usernames/passwords are set correctly, it let me fill the System Password and System Username, but the Target still shows "Pending Status".
- Oracle support: EM12C : Agents Show As Status Pending After Fresh Install [ID 1478880.1]
EM12c: Agents > peregrine.esri.com:3872 > Agent > Resynchronization
Still Target shows "Pending Status"
Have you seen this problem before? Any suggestions?
Thanks,
Marcelo Marques
Esri-Technical Manager

Hi,
https://peregrine.esri.com:3872/emd/browser/main/
Displays the page:
TargetType TargetName BrokenCode BrokenReason Status Version     RunTime Version Blackout Status     Severities     Schedule     CollectionItems
Host     peregrine.esri.com     0     MONITORED     1     false     Severities     Schedule     CollectionItems
Clicked on TargetName link "peregrine.esri.com"
This table displays
Target=(host,peregrine.esri.com)
Metric Name Collection History Detail Merged History Metric Definition Execution Descriptor Query Row source trace Row source statistics Incremental Config State
Response     ""     Response     Response     ""     Response     "" ""
Click on "Response" links and see follow.
Link column "Metric Name-Response":
"The following exception has occurred:
     Process invocation failure: java.io.IOException: Cannot run program "echo": CreateProcess error=2, The system cannot find the file specified"
Link column "Metric Definition-Response":
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<metric metric_type="TABLE" metricLabel="Response" metricLabelNLSID="host_response" usageType="VIEW_COLLECT" keysFromMultiColls="false" test_Metric="false" keys_Only="false" long_Running="false" is_Config="false" is_Raw="false" is_Remote="false" is_Force_Cache="false" numCacheValues="1" is_Incremental="false" is_DeletionAllowed="true" is_Purgeable="true" isMetricExtension="false">
<tabledescriptor anyComputeExpr="">
<column column_name="Status" is_key="false" column_type="0" is_transient="false" is_timestamp="false" is_target_seperator="false" is_filename="false" is_clob="false" columnLabel="Status" columnLabelNLSID="host_response_status" replacedFetchedValue="false"/>
</tabledescriptor>
<QueryDescriptor cacheAggregation="false">
<QD fetchletId="OSLineToken"/>
<prop name="command" scope="GLOBAL" optional="false" content="echo"/>
<prop name="args" scope="GLOBAL" optional="false" content="em_result=1"/>
<prop name="startsWith" scope="GLOBAL" optional="false" content="em_result="/>
<prop name="delimiter" scope="GLOBAL" optional="false" content="|"/>
</QueryDescriptor>
</metric>
Link column "Row source trace - Response":
Metric=Response
Row source name     Table name     Operation     Row
TableRowSource          Alloc
TableRowSource     Response     Start
TableRowSource     Response     Rewind
Timestamp = 2012-09-25T14:38:33.072-07:00
Thanks, Marcelo.

Configure ASM Instance in RAC cluster - problem

Linux RH4 with Oracle 11.1.0.6
I previously had ASM working in a RAC environment, but have uninstalled on all 3 nodes following Oracle guidelines.
When I attempt to re-configure ASM it states that an ASM instance is located in nodes 2 and 3. Previous ASM software has been removed, and there are no entries in the /etc/oratab files on any of the nodes.
How do I locate and then remove these instances on nodes 2 and 3
Thanks

Steps in Note 311350.1 have been followed, and there are no occurances of ASM appearing in the crs_stat output. Also the fact that the ASM software has also been removed from all of the various, where are these ASM instances being started?
I am unable to proceed past the "Select Configuration Screen" which gives you the option to 1)Create Database, 2)Configure ASM or 3) Install Software only.
When I select option 2 and enter ASM SYS password, I get the error message that ASM instances are present in the other nodes.
Would appreciate any help in how I can progress past this stage.
Thanks

OEM: for 3rd party target it showing status pending and not getting up

hi,
I've develop a 3rd party plug-in for monitoring my application. After deploying that plug-in I'm getting status pending for my target instead of status up.
1. not sure where is the problem. any help is this regard is appreciated
2. if I update my plug-in xml file (default collection file) why it's not updating the schedule/threshold. Is there any need that if I've to update the schedule/threshold for metric through my custom script then I've to re-jar it and re-deploy it? Can't it be possible that I update the custom script file and reload the agent and OEM start capturing the metric info?

hi,
I've develop a 3rd party plug-in for monitoring my application. After deploying that plug-in I'm getting status pending for my target instead of status up.
1. not sure where is the problem. any help is this regard is appreciated
2. if I update my plug-in xml file (default collection file) why it's not updating the schedule/threshold. Is there any need that if I've to update the schedule/threshold for metric through my custom script then I've to re-jar it and re-deploy it? Can't it be possible that I update the custom script file and reload the agent and OEM start capturing the metric info?

SIA in the cluster shows it is stoped but the servises are runnig

After clustering 2 nodes strange behavior of SIA's observed. SIA is stopped but the services are still running. SIA can not be restarted from the node.
BOE 3.1 SP3 Java with Tomcat installed on (32bit) Window 2008 standard server. It is virtual servers. CMS DB is an Oracle 10.2 on the Linux box. 2 nodes in the cluster. Set up was done installing BOE on the first box then installing second one without reinitializing CMS. Stopped the both SIA and added cluster name. I did changed the xml to include cluster. in :\Program Files\Business Objects\Tomcat55\webapps\PlatformServices\WEB-INFand xml for the infoview in :\Program Files\Business Objects\Tomcat55\webapps\InfoViewApp\WEB-INF.
Any Ideas will be welcomed.

When you look at each BO servers properties in the CMC, do you see a line in red saying: "The server is not managed by Server Intelligence Agent. Current command line arguments could not be retrieved. Server restart would be required if the command line arguments are modified."?

What's the correct order to install OEM Grid Control + DB + AS?

Hi everbody! I'm getting start on OracleAS and Grid Control.
What's the correct order to install:
* Enterprise Manager 10g Grid Control
* Database 10gR2
* Application Server 10gR3
(on RHEL4-Upd2)
or the order is not important?
I need have the environment for each oracle software ($ORACLE_HOME, $ORACLE_BASE)? Or install first one, and change the environment and install, change again and install, etc.. ? :)
Tks!

Hey Rafael! You only have to use the Grid Control CDS, AS, repository database and grid control software are installed automatically, so you dont have to worry about the order u should have to follow.
Anyways if u have already installed a database u can use that one as a repository.
about the enviorment variables i guess u´ll be prompted for just one only directory cause u only need to install the software only one time.
hope u find this interesting!!
Regards, Luis

Webi reports show status pending despite occuring in the past

When I go into Instance Manager there are lots of reports showing that are 'recurring' but the next scheduled run time is in the past. There are no errors appearing that I can see to explain why they haven't run.
The reports are generally scheduled for 7-10 in the morning. I have scheduled tasks which stop and start the SIA every evening and the reports seem to finally arrive at their intended rescipient when the SIA restarts.
We have: -
XI 3.1/Tomcat/Server 2003
Does anyone have any ideas? Thank you in advance.

There were absolutely no errors in WUAhandler.log on existing machines - all looked normal, which baffled me. Machines with newly installed SCCM client only had machine and user policy update, so could not check for Software Updates.
However, I through web searches, I found a solution on another discussion here:
https://social.technet.microsoft.com/Forums/en-US/1cefa9e0-a7f9-48d1-83b9-34d2293bab64/sccm-2012-r2-problem-with-device-deployment-user-deployments-ok?forum=configmanagerapps
Basically the issue was described as a "corrupt PADBID in the database". A SQL query code detects if the issue is present, and another SQL code fixes the issue.
What lead me to this fix was searching for this error in "CCMEXEC.LOG" online: "System task 'PolicyEvaluator_Unlock' returned error code 0x8000ffff".

Oemd_oms_csa_collector showing as down (10GR2 Grid Control)

The oemd_oms_csa_collector target is showing as down.
Yes I know its bug fixed in the next patch. Has anyone attempted to remove the target, edit the targets.xml to stop it showing up?
Barry

See if my response to this posting will help
Database Control always gets "The database status is currently unavailable"

Rebooting the server with ASM instance............

Hi folks
I have to go for reboot of the server as I am adding a RAW device for having one more mount and also will be adding a disk to disk group.
1) alter diskgroup diskgroupname add disk '/u09'; Is this correct to add a new disk to the diskgroup of ASM instance?
2) I will have to shutdown all the six instances within the ASM instance and shutdown the ASM instance? Is this correct
After a successfull Rebbot is done
3) I will have to startup the ASM instance first and one by one startup the other six instances? Is it the right sequence.
Please reply at the earliest.
Thanks
Shiva

Hi
If you want to shutdown the server to add the RAW device then:
1. Shutdown all instances but shutdown ASM instance in the end.
2. Shutdown server and add the RAW device.
3. Startup server
4 Add the diskgruop and also you can increase the value of rebalance parameter.
5. Start all the instances that are using this ASM instance.
Hope this Help
Regards

Re: Throughput drops dramatically when I increase the number of instances in a cluster

Thanks for the quick reply.
          Yes, we are running WLS with the performance pack.
          "Bernie Wong" <[email protected]> wrote in message
          news:[email protected]...
          > Fellow clusterers ....
          >
          > I have an EJB driver program that pumps work into a WLS cluster. For
          > scalability, I increase the number of drivers. The drivers have a big pool
          > of work to pump into the cluster.
          >
          > I noticed that with 6 (nothing special about that number) drivers, I can
          get
          > 500K worked items per hour in a single instance (clustered). That is, the
          > instance is cluster enabled and is watching for multicast, etc..
          >
          > When I add the second instance into the cluster, the cluster-wide
          throughput
          > with the six drivers drops to 370K items per hour. When I add the third
          > instance, the cluster-wide throughput drops further to 250K items per
          hour.
          > When I kill an instance, the throughput grows back to 370K items per hour.
          > When I kill another instance (to get back to one instance), the throughput
          > grows back to 500K/hr.
          >
          > Can somebody point out what we are doing wrong - do we need to tweek some
          > WLS parameters, do we have to avoid some features that limit cluster
          > scalability, etc..
          >
          > My WLS configuration is .....
          > - WLS 5.1, SP5
          > - JDK 1.2.1_04c with JIT, no Hotspot
          >
          > My hardware/software configuration consists of:
          > - an E4500 - 8 processor database server - this is only running at 15%
          > server busy
          > - three E4500 - all 8 processors/6GB RAM - application processors
          >
          > The cluster is implemented with one instance per application server.
          > Each application server is only 10-15% busy.
          >
          > My driver and application is ....
          > - stateless EJB driver and stateless EJB bean
          >
          > Your thoughts and comments would be greatly appreciated.
          >
          > Bernie
          >
          >


Thanks. It works. We screwed up the settings.
          "Bernie Wong" <[email protected]> wrote in message
          news:[email protected]...
          > Thanks for the reply.
          >
          > We ran the benchmark again and got the same scaling profile. This
          afternoon,
          > we are going to run a benchmark with a really simple driver + bean (a do
          > nothing bean) and see if we get the same scaling profile. From all the
          > responses, it would appear that WLS can scale therefore we want to isolate
          > the problem to either our code or our configuration (or both).
          >
          > I will let you know.
          >
          > Bernie
          >
          > "Rob Woollen" <[email protected]> wrote in message
          > news:[email protected]...
          > > Make sure that this was set on the client not the server.
          > >
          > > -- Rob
          > >
          > > Bernie Wong wrote:
          > > >
          > > > Jim,
          > > >
          > > > Thanks for the suggestions. One of my performance engineers ran
          several
          > > > experiments last week where he set the executeThreadCount to 6 and to
          10
          > > > along with a percentSocketReaders to 50. He saw no improvement. We
          will
          > > > rerun that experiment again since that seems to be the most common
          > > > recommendation.
          > > >
          > > > Bernie
          > > >
          > > > "Jim Zhou" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > > One possible reason is not enough socket reader execute threads, try
          > to do
          > > > > this:
          > > > > "-Dweblogic.system.executeThreadCount=10"
          > > > > "-Dweblogic.system.percentSocketReaders=50" on your client JVM
          startup
          > > > > command line.
          > > > >
          > > > > http://www.weblogic.com/docs51/admindocs/tuning.html#tuning clients
          > > > >
          > > > > WebLogic RMI
          > > > > If you are using WebLogic RMI clients and there are more than 2
          > Weblogic
          > > > > servers in a cluster, you may encounter a significant performance
          > > > > degradation (very long round trip times for stateless session beans,
          > for
          > > > > instance). The solution is to make some property changes on the
          client
          > > > side
          > > > > as explained below.
          > > > >
          > > > > The solution to this problem is to ensure that there are at least as
          > many
          > > > > socket reader threads as there are connections to the server and
          also
          > > > > allowing for some extra threads for processing other tasks. This is
          > > > > accomplished by starting the client with the command line argument
          > > > > "-Dweblogic.system.percentSocketReaders" set to a sufficiently high
          > > > > percentage (say 50) and by ensuring that there sufficient number of
          > > > execute
          > > > > threads for other processing on the client. A metric of twice the
          > number
          > > > of
          > > > > execute threads as there are servers in a cluster should work fine
          if
          > the
          > > > > above percentage is at 50. The command line argument affecting the
          > number
          > > > of
          > > > > execute threads is
          > > > >
          > > > > "-Dweblogic.system.executeThreadCount".
          > > > >
          > > > > For instance, we could use:
          > > > >
          > > > > "-Dweblogic.system.executeThreadCount=10"
          > > > >
          > > > > and
          > > > >
          > > > > "-Dweblogic.system.percentSocketReaders=50"
          > > > >
          > > > > when testing with 3 or 4 servers in a cluster.
          > > > >
          > > > >
          > > > > Bernie Wong <[email protected]> wrote in message
          > > > > news:[email protected]...
          > > > > > Thanks for the quick reply.
          > > > > >
          > > > > > Yes, we are running WLS with the performance pack.
          > > > > >
          > > > > >
          > > > > > "Bernie Wong" <[email protected]> wrote in message
          > > > > > news:[email protected]...
          > > > > > > Fellow clusterers ....
          > > > > > >
          > > > > > > I have an EJB driver program that pumps work into a WLS cluster.
          > For
          > > > > > > scalability, I increase the number of drivers. The drivers have
          a
          > big
          > > > > pool
          > > > > > > of work to pump into the cluster.
          > > > > > >
          > > > > > > I noticed that with 6 (nothing special about that number)
          drivers,
          > I
          > > > can
          > > > > > get
          > > > > > > 500K worked items per hour in a single instance (clustered).
          That
          > is,
          > > > > the
          > > > > > > instance is cluster enabled and is watching for multicast, etc..
          > > > > > >
          > > > > > > When I add the second instance into the cluster, the
          cluster-wide
          > > > > > throughput
          > > > > > > with the six drivers drops to 370K items per hour. When I add
          the
          > > > third
          > > > > > > instance, the cluster-wide throughput drops further to 250K
          items
          > per
          > > > > > hour.
          > > > > > > When I kill an instance, the throughput grows back to 370K items
          > per
          > > > > hour.
          > > > > > > When I kill another instance (to get back to one instance), the
          > > > > throughput
          > > > > > > grows back to 500K/hr.
          > > > > > >
          > > > > > > Can somebody point out what we are doing wrong - do we need to
          > tweek
          > > > > some
          > > > > > > WLS parameters, do we have to avoid some features that limit
          > cluster
          > > > > > > scalability, etc..
          > > > > > >
          > > > > > > My WLS configuration is .....
          > > > > > > - WLS 5.1, SP5
          > > > > > > - JDK 1.2.1_04c with JIT, no Hotspot
          > > > > > >
          > > > > > > My hardware/software configuration consists of:
          > > > > > > - an E4500 - 8 processor database server - this is only
          > running at
          > > > > 15%
          > > > > > > server busy
          > > > > > > - three E4500 - all 8 processors/6GB RAM - application
          > processors
          > > > > > >
          > > > > > > The cluster is implemented with one instance per application
          > > > server.
          > > > > > > Each application server is only 10-15% busy.
          > > > > > >
          > > > > > > My driver and application is ....
          > > > > > > - stateless EJB driver and stateless EJB bean
          > > > > > >
          > > > > > > Your thoughts and comments would be greatly appreciated.
          > > > > > >
          > > > > > > Bernie
          > > > > > >
          > > > > > >
          > > > > >
          > > > > >
          > > > >
          > > > >
          >
          >

Throughput drops dramatically when I increase the number of instances in a cluster

Fellow clusterers ....
I have an EJB driver program that pumps work into a WLS cluster. For
scalability, I increase the number of drivers. The drivers have a big pool
of work to pump into the cluster.
I noticed that with 6 (nothing special about that number) drivers, I can get
500K worked items per hour in a single instance (clustered). That is, the
instance is cluster enabled and is watching for multicast, etc..
When I add the second instance into the cluster, the cluster-wide throughput
with the six drivers drops to 370K items per hour. When I add the third
instance, the cluster-wide throughput drops further to 250K items per hour.
When I kill an instance, the throughput grows back to 370K items per hour.
When I kill another instance (to get back to one instance), the throughput
grows back to 500K/hr.
Can somebody point out what we are doing wrong - do we need to tweek some
WLS parameters, do we have to avoid some features that limit cluster
scalability, etc..
My WLS configuration is .....
- WLS 5.1, SP5
- JDK 1.2.1_04c with JIT, no Hotspot
- we enabled performance pack
My hardware/software configuration consists of:
- an E4500 - 8 processor database server - this is only running at 15%
server busy
- three E4500 - all 8 processors/6GB RAM - application processors
The cluster is implemented with one instance per application server.
Each application server is only 10-15% busy.
My driver and application is ....
- stateless EJB driver and stateless EJB bean
Your thoughts and comments would be greatly appreciated.
Bernie

The short answer is to set the following tuneables on the client side:
java -Dweblogic.system.executeThreadCount=10
-Dweblogic.system.percentSocketReaders=50 <your client program>
http://www.weblogic.com/docs51/admindocs/tuning.html#tuning clients
Srikant, [email protected], http://weblogic.bea.com/, etc.
Bernie Wong wrote:
Fellow clusterers ....
I have an EJB driver program that pumps work into a WLS cluster. For
scalability, I increase the number of drivers. The drivers have a big pool
of work to pump into the cluster.
I noticed that with 6 (nothing special about that number) drivers, I can get
500K worked items per hour in a single instance (clustered). That is, the
instance is cluster enabled and is watching for multicast, etc..
When I add the second instance into the cluster, the cluster-wide throughput
with the six drivers drops to 370K items per hour. When I add the third
instance, the cluster-wide throughput drops further to 250K items per hour.
When I kill an instance, the throughput grows back to 370K items per hour.
When I kill another instance (to get back to one instance), the throughput
grows back to 500K/hr.
Can somebody point out what we are doing wrong - do we need to tweek some
WLS parameters, do we have to avoid some features that limit cluster
scalability, etc..
My WLS configuration is .....
- WLS 5.1, SP5
- JDK 1.2.1_04c with JIT, no Hotspot
- we enabled performance pack
My hardware/software configuration consists of:
- an E4500 - 8 processor database server - this is only running at 15%
server busy
- three E4500 - all 8 processors/6GB RAM - application processors
The cluster is implemented with one instance per application server.
Each application server is only 10-15% busy.
My driver and application is ....
- stateless EJB driver and stateless EJB bean
Your thoughts and comments would be greatly appreciated.
Bernie

ASM instance in the cluster shows status pending in grid control

Similar Messages

Maybe you are looking for