FAILED_OVER for single sessions. No VIP failover

Hi all,
On a 10.2.0.3.0 2-nodes RAC (AIX 5L) I am seeing from time to time single of few sessions marked in gv$session with FAILED_OVER='YES', but no services failover occurred. Those sessions are still connected to the preferred instance, that is in their tnsnames.ora they refer to a service running, let's say, on instance 2 and they ARE running on instance 2.
I am wondering if this can be due to some kind of connectivity issue, that is the client doesn't ping the VIP address anymore (and vice-versa) and then the session is marked as FAILED_OVER.
Has anyone seen something similar?
Thanks for any feedback,
Riccardo

With Oracle 10g you do connection time failover with setting in clients tnsnames.ora file all nodes addresses: Check following link:
http://docs.oracle.com/cd/B19306_01/network.102/b14213/tnsnames.htm#i477297
If your clients tnsnames.ora file is ok, Then client tries to connect addresses one by one. And this way it does not matter even if some server of the cluster is down. But of course when you shutdown one database instance it's connections will be dropped. Althought you can have SELECT clause failovers with Transparent Application Failover (TAF).
So you can run rolling update without shutting down whole RAC database as long as your clients tnsnames.ora is configured correctly. But those dropped connections need to be handled in application level.

Similar Messages

Single session for all Application Modules

Hello,
I've got an application that has several Application Modules. All these modules need some data that are set from time to time. I've written some code that calls getSession().getUserData().put("myData",myData). After this method was called in another Application Module i want to retrieve myData with getSession().getUserData().get("myData"). But the result depends if I use 2-tier or 3-tier. In 2-tie I get myData while in 3-tier I get null. My question is:
Is there a Session object or any other data instance that could be accessed from all Application Modules for on application instance.
E.g. I've got two user (A,B) who start my application. Through using my app several instance of Application Modules are created. All Application Modules that are created for the instance of User A should be able to share his user name and some other dynamic data while the Application Modules created for B should have no access to that data.
Doe anybody know if static data of an Application Module are a possible solution?
regards
Joerg

Hi Joerg,
I am not 100% sure what you are trying to achieve, and with which version of JDeveloper/ ADF, technologies (JSP, Swing), etc, but I can tell you that I have been experimenting with single session accounts myself within a rich-client Swing environment, as I have experienced Oracle DBA guys who want to control user authentication via Oracle accounts (I have achieved this via the JCLoginDialog mechanism, and a bit of a hack)... Frank Nemphius (sp?) posted something about a white paper coming out on a related subject but I don't know where he is with that.
Anyway, I managed to do it in a prototype by nesting several application modules within a Root Application Module that was essentially simply a Container for the other application modules. Using this mechanism I was able to bind my root application module to any panel I wanted and it would inherit the roots Session.
ie. I used many application modules and it only used one Oracle Session.
However, my reservations -
1) This solution was not tested robustly!
2) I doubt this would be ideal for a distributed app with thousands of users - My solution is for a very complex app, with a limited number of users.
Finally, I cannot confirm this is a great solution - I can only tell you it worked in my prototype, and I am currently awaiting the ADF source - when my company and Oracle can decide what level of support we currently have and need!?!? - what exactly does being an "Oracle partner" mean??? Its all very boring and un-interesting to a Java person like me... ;-)
Once I have the source I will look at how it actually works and perhaps be able to answer questions like this more definitively. Hmm - I wonder if I could get the Oracle JDBC driver source too?? .... Is it written in C or C++?? I know them too... ;-)
Cheers........Dean

Failover for Single ASA

Hi All,
I want to know what all fail-over I can build for single ASA. I am planning to connect as per the attached.
Please let me know all configuration that i can build. Do i need to assign 2 ip's for that 2 interfaces connected to inside,dmz and outside.
Please let me know if you any other design.
Regards,
Satya.M

Hi Satya,
You cannot assign IP's of the same subnet to two different interfaces of the ASA in the routed mode. So as per your diagram, you cannot connect Inside interface of the ASA to both the 6504E switches or to the DMZ switches as you have shown. If you want to do such a failover, you can use 2 ASA's with Active/Standby failover while connecting ASA-1 to 6504EGa and ASA-2 to 6504EGb. You can also do Active/Active failover.
Also with 1 ASA, if you want to configure 2 ISP's on 2 interfaces, please remember policy based routing is not supported on ASA so at any gien time only 1-ISP will be active for all the traffic going out. You can have the failover configured so that everything fail's over to the secondary ISP when Primary goes down with tracks etc.
I hope this helps. If not, can you please post your exact requirements for the failover so that we can suggest you better.
Best,
Raghav

Sharing a single session among multiple portlets for single application (e.g. wInsight)

Does anyone know the best practices way for sharing a single Session for an application (running on a single Porlet server) among multiple portlets on a page?
For example, the application wInsight uses 3 frames (navigation, search results - tabular, search results - chart) which need to communicate via the application's session scope. It is not just that we do not want for a single user to be running multiple sessions, but they really do share variable parameters this way.
So far I can only think of trying to build a one true portlet and two empty containers on page load. I would use the portlet to establish the session with the Portlet server and then transfer the session information to the other two empty containers to instantiate their respective portlets. I haven't tried this yet, but will do so soon...
Any help and feedback would be greatly appreciated.

Karen,
You can easiliy create several portlets out of a Struts application. For detailed instructions, refer to the Struts section of the Portal Developer's Guide.
Good luck,
Peter

How to do Multithreading in Oracle PlSql using a Single Session

Hi All,
I have a complex but interesting requirement.
1) I have a table with 90k rows.
2) My PlSql Package picks up all the 90k rows one by one, does some processing/transformation on it
3) if the row satisfies some business rules, then it gets inserted into an application table. If the row is not eligible, then it inserts the row into a Error table.
4) After processing all the 90k records, If my Error Table Count reaches 10% of the input count (90k), then all inserts (i.e. both application table inserts and
error table inserts) must be rolled back.
5) Right now, we are achieving this logic in a single session but there are far many performance issues, because processing has to go through row by row.
Is it possible to implement the above logic as "multi threading within PlSql" whereby i can run Step 2 in 10 parallel slaves and if the total error count of all the 10 slaves exceeds 10% of the input data, then there should be a rollback for all 10 slaves.
+A sample testcase is given below. Issue is: rollback statement in p1 is not taking any effect (because plsql spawns sessions to execute p2 which autocommits itself on graceful exit). But is there any other way by which i can make the rollback to be effective+
create table t1 (a number);
create table j1(b number);
create or replace procedure p1
as
l_cnt number;
i number;
l_job number;
begin
     for i in 1 .. 5 loop
        dbms_job.submit( l_job, 'p2('||i||');' );
    end loop;
    commit;
    loop
        dbms_lock.sleep(30);
        select count(*) into l_cnt from j1;
        exit when (l_cnt = 5);
    end loop;
   rollback;
end;
create or replace procedure p2(i number)
as
begin
insert into t1 values(i);
insert into j1 values(1);
end;
/

Basically your current 'algorithm' can be described as 'slow-by-slow processing' (co Tom Kyte)
Relational databases are about sets not about records.
Consequently your approach must be qualified as evil.
Instead of fixing the problem (and getting rid of slow-by-slow processing), you propose to add even more evil by adding multi-threading to the mix.
The issue you describe is not an issue at all, it is just making clear you are heading for disaster.
An approach that works quite nicely is
- add an extra status column to the table to be processed.
- UPDATE the status column of all records that do not qualify. By UPDATE I mean the UPDATE statement, not record by record processing
- (BULK)-INSERT the remaining records, for which the flag is NULL.
The simple guidelines for application development are:
Only do it in PL/SQL when you can't do it in straight SQL
Only do it in Java when you can't do it in PL/SQL
Only do it in 3GL when you can't do it in Java.
Your 'strategy' is doomed to fail.
Get rid of it.
Before it is too late, and your heart is pumping like mad, because your problems are increasing, and increasing, and increasing, and you have to work 7 x 24 to deal with 'performance problems'
You have already demonstrated your approach doesn't work.
Don't try to make it worse.
Sybrand Bakker
Senior Oracle DBA
Experts: those who do read documentation

Can I download a file in different sessions or should it be in a single session? In other words can I pause the download of a file, shutdown/restart my system and then resume download from where I left off? Or will it start from the very beginning?

Can I download a file in different sessions or should it be in a single session? In other words can I pause the download of a file, shutdown/restart my system and then resume download from where I left off? Or will it start from the very beginning?

If a server supports resuming downloads then the download should continue where it left off.<br />
You can test that by simple starting a large download and wait a minute or so before pausing it.<br />
Then you can close and restart Firefox and see if resuming works.
You can set the pref browser.download.manager.quitBehavior to 2 on the about:config page.<br />
That will make Firefox ask for confirmation if you want to cancel the download if you close Firefox.
See:
* http://kb.mozillazine.org/browser.download.manager.quitBehavior

Max no# of threads in a single session

Hi all,
I have a scenario wherein I have connected to SAP from JAVA using XBP interfaces.
I want to call BAPI_JOB_DEFINITION_GET concurrently in a single session using sync threads. The problem what I am facing here is, I am able to handle 15 to 20 connections but for high volumes of threads(50) the JVM is crashing.
I guess there is some limit set from SAP end.
Could anybody provide any suggestions or advice about, the maximum number of connections and how can I set the parameter to modify the limit.
Thanx in advance
Milind.

This topic should be posted in the Java Programming section, not the xMII section...

Max no# fo connections in a single session

Hi all,
I have a scenario wherein I have connected to SAP from JAVA using XBP itenrfaces.
I want to call BAPI_JOB_DEFINITION_GET concurrently in a single session using sync threads. The problem what I am facing here is, I am able to handle 15 to 20 connections but for high volumes of threads(50) the JVM is crashing.
I guess there is some limit set from SAP end.
Could anybody provide any suggestions or advice about, the maximum number of connections and how can I set the parameter to modify the limit.
Thanx in advance
Milind.

Hi
You will have to do memory settings for the number of threads you are trying to access.
Procedure:
Go to configtool and try to change the heap size.If you can tell the configuration of your OS i can help you in setting the corrcet heap size and JVM parameter.
\usr\sap\SID\JCXX\j2ee\configtool and run configtool.bat
1.Go to instance----
Check the heap size
2.Expand the instance node
Click the dispatcher node----
Check the heap size
Click the server node----
Check the heap size
Change the values.If you have confusion send the present values to me.
Message was edited by:
rajat anand

Message Driven Beans: how to receive and send in a single session?

Hello
How to receive and send JMS messages in a message driven bean using a single session?
Thanks.

Are you referring to writing code within the onMessage method itself to receive JMS messages?
If so, that is not a pattern that is recommended, especially not in the case of a blocking JMS
receieve. If you must write an explicit JMS receive within an EJB component it's best to use
a "check the queue" approach where you give a very small timeout for the receive. That way
if the message is there it will be returned but if not the call will not block.
You'll also need to take the transactional settings of the onMessage method into account.
If your are sending a message and then waiting for a response, those two actions can
not be done within the same global transaction. For that, you'll need to either use
BMT and perform each in its own transaction or just not use global transactions at all,
in which case each send and receive operation will be atomic.
--ken

Single session max throughput on 5555-X

We have some ASA 5555-X firewalls running 9.1(2) with the IDS modules installed that have a pretty basic configuration used to separate multiple internal networks. The firewalls are able to pass over a Gbps of traffic pretty easily as long as it's sourced from multiple services but if we try to do a high speed transfer such as backup to SAN running over a single UDP or TCP session the traffic seems to peg out around 400Mbps. We can verify that the server and SAN are capable of much higher transfer speeds by putting both on the same side of the firewall so I'm convinced the firewall itself is the limiting factor here.
I was wondering if anyone has come across this before and/or has any suggestions for how to boost the speed. I am really trying to avoid something like bridging the networks with multiple interfaces or route exporting VRFs but our DBA's are complaining nonstop about backup times in those environments. There are no Service policy QOS settings set on those interfaces and are NAT exempt so the firewall is not doing anything what I would call special.
Thanks,
Richard Hillius

Hello Richard,
At this point it would be good you do some captures on both interfaces of the ASA in place for this traffic and then see the round trip time just to make sure the ASA is the one generating the slowness on the network.
And agree the ASA can do QoS for specific traffic (so for all traffic that you defined, not just for a single session).
Can you share the following commands:
show interface | include errrors
show cpu usage
I could start providing you comamnds but I think it's better to give you the link :
http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a0080ba9521.shtml
Here is what you need to undertstand about the ASA, let us know the test you performa afterwards.
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.
Any question contact me at [email protected]
Cheers,
Julio Carvajal Segura

Oracle 11g clusterware VIP failover failed

I installed Oracle 11g Clusterware succesfully, without any errors as per link:
http://www.oracle-base.com/articles/11g/OracleDB11gR1RACInstallationOnRHEL5UsingVMwareESXAndNFS.php
After that,I did vip failover test
I rebooted the node-2
Before reboot,
[root@advansrac1 bin]# ./crs_stat -t
Name Type Target State Host
ora....ac1.gsd application ONLINE ONLINE rac1
ora....ac1.ons application ONLINE ONLINE rac1
ora....ac1.vip application ONLINE ONLINE rac1
ora....ac2.gsd application ONLINE ONLINE rac2
ora....ac2.ons application ONLINE ONLINE rac2
ora....ac2.vip application ONLINE ONLINE rac2
After reboot,
Name Type Target State Host
ora....ac1.gsd application ONLINE ONLINE rac1
ora....ac1.ons application ONLINE ONLINE rac1
ora....ac1.vip application ONLINE ONLINE rac1
ora....ac2.gsd application ONLINE ONLINE rac2
ora....ac2.ons application ONLINE ONLINE rac2
ora....ac2.vip application ONLINE UNKNOWN rac1
[root@rac1 bin]# ./crs_stop ora.rac2.vip
Attempting to stop `ora.rac2.vip` on member `advansrac1`
Stop of `ora.rac2.vip` on member `advansrac1` succeeded.
[root@rac1 bin]# ./crs_stat -t
Name Type Target State Host
ora....ac1.gsd application ONLINE ONLINE rac1
ora....ac1.ons application ONLINE ONLINE rac1
ora....ac1.vip application ONLINE ONLINE rac1
ora....ac2.gsd application ONLINE ONLINE rac2
ora....ac2.ons application ONLINE ONLINE rac2
ora....ac2.vip application OFFLINE OFFLINE
[root@rac1 bin]# ./crs_start ora.rac2.vip
Attempting to start `ora.rac2.vip` on member `rac2`
Start of `ora.rac2.vip` on member `rac2` succeeded.
[root@rac1 bin]# ./crs_stat -t
Name Type Target State Host
ora....ac1.gsd application ONLINE ONLINE rac1
ora....ac1.ons application ONLINE ONLINE rac1
ora....ac1.vip application ONLINE ONLINE rac1
ora....ac2.gsd application ONLINE ONLINE rac2
ora....ac2.ons application ONLINE ONLINE rac2
ora....ac2.vip application ONLINE ONLINE rac2
I have only 1.5G on each node
Here the issue is,
1. Actual Result: # During failover why it is showing UNKNOWN state for ora.rac2.vip on member rac1
Expected Result: # During failover,it have to be ONLINE state for ora.rac2.vip on member rac1
2. I have to start ora.rac2.vip manually, when node-2 is up.I want VIP fail over have to happen automatically when node-2 is up to normal online state.
Help me out from this issue

VMware is unsupported but that is likely not your issue.
1. Run cluster verify and report the results
2. Did you create a failover service? How?
3. Post your TNSNAMES.ORA

Query "Stuck" in CXPacket wait with no other waits for that session id in the blocking session id of sys.dm_os_waiting_tasks

So I have a query that is running with a large number of CXPacket waits. There are no other tasks in the sys.dm_os_waiting_tasks that are blocking this session id with a wait other than CXPacket Wait. This is taking place on a SQL Server 2008
R2 machine. My question is there something else to look at? I've gone ahead and posted the output of the entire sys.dm_os_waiting_tasks. Any thoughts?
waiting_task_address   session_id   exec_context_id   wait_duration_ms   wait_type   resource_address   blocking_task_address   blocking_session_id
blocking_exec_context_id   resource_description
0x0000000004E88988   NULL   NULL   13525   FT_IFTS_SCHEDULER_IDLE_WAIT   NULL   NULL   NULL   NULL   NULL
0x0000000004E89288   NULL   NULL   64128606   DISPATCHER_QUEUE_SEMAPHORE   NULL   NULL   NULL   NULL   NULL
0x0000000004ED6748   2   0   19502   XE_TIMER_EVENT   NULL   NULL   NULL   NULL   NULL
0x0000000004450508   3   0   2779501   XE_DISPATCHER_WAIT   NULL   NULL   NULL   NULL   NULL
0x000000000446A748   4   0   838   LAZYWRITER_SLEEP   NULL   NULL   NULL   NULL   NULL
0x000000000448E508   5   0   438   REQUEST_FOR_DEADLOCK_SEARCH   0x000000000B9301F8   NULL   NULL   NULL   NULL
0x0000000004E88508   6   0   1304946379   KSOURCE_WAKEUP   NULL   NULL   NULL   NULL   NULL
0x0000000004484508   7   0   146961   LOGMGR_QUEUE   0x0000000003597248   NULL   NULL   NULL   NULL
0x00000000804942C8   9   0   3366   SQLTRACE_INCREMENTAL_FLUSH_SLEEP   NULL   NULL   NULL   NULL   NULL
0x000000000448E748   10   0   929   SLEEP_TASK   NULL   NULL   NULL   NULL   NULL
0x0000000004450988   11   0   26214727   BROKER_EVENTHANDLER   NULL   NULL   NULL   NULL   NULL
0x0000000004EBC508   12   0   1304959888   ONDEMAND_TASK_QUEUE   0x0000000003575508   NULL   NULL   NULL   NULL
0x0000000004EA2508   13   0   146959   CHECKPOINT_QUEUE   0x0000000003590C70   NULL   NULL   NULL   NULL
0x0000000004EA2748   14   0   1304947282   BROKER_TRANSMITTER   NULL   NULL   NULL   NULL   NULL
0x0000000004484988   16   0   1304947282   BROKER_TRANSMITTER   NULL   NULL   NULL   NULL   NULL
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x0000000255EFEBC8   154   19   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x0000000258D26748   154   17   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x0000000258DB0E08   154   18   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x000000025A392748   154   21   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x0000000258DB2E08   154   20   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x000000025C694508   154   23   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x000000025A675708   154   24   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x000000000446AE08   154   0   19974433   CXPACKET   0x0000000804ECC1D0   0x00000001D3F902C8   154   22   exchangeEvent
id=Port80263100 WaitType=e_waitPortOpen nodeId=4
0x0000000004EBCE08   154   1   18269246   CXPACKET   0x000000080C705200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6220e00 WaitType=e_waitPipeGetRow nodeId=33
0x0000000004485288   154   2   18269246   CXPACKET   0x000000080CD4F200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6220f00 WaitType=e_waitPipeGetRow nodeId=33
0x0000000004EA3B88   154   3   18269246   CXPACKET   0x000000080CCDD200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6221000 WaitType=e_waitPipeGetRow nodeId=33
0x0000000004ED7948   154   4   18269246   CXPACKET   0x000000080CC8B200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6220f80 WaitType=e_waitPipeGetRow nodeId=33
0x000000000448F708   154   5   18269242   CXPACKET   0x000000080CD41200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6220e80 WaitType=e_waitPipeGetRow nodeId=33
0x0000000004451B88   154   6   18269245   CXPACKET   0x000000080CE31200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6221080 WaitType=e_waitPipeGetRow nodeId=33
0x0000000004E89048   154   7   18269246   CXPACKET   0x000000080D12B200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6221100 WaitType=e_waitPipeGetRow nodeId=33
0x000000000446ABC8   154   8   18269243   CXPACKET   0x000000080CE7D200   0x000000000448FB88   154   13   exchangeEvent
id=Pipe2f6221200 WaitType=e_waitPipeGetRow nodeId=33
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258D26748   154   17   18270546   CXPACKET   0x000000025C763020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB0E08   154   18   19974425   CXPACKET   0x00000008064DD020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000255EFEBC8   154   19   18269474   CXPACKET   0x0000000806355020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x0000000258DB2E08   154   20   18270502   CXPACKET   0x0000000805CC1020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322346   CXPACKET   0x0000000806395020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322347   CXPACKET   0x0000000806395020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322347   CXPACKET   0x0000000806395020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322347   CXPACKET   0x0000000806395020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322347   CXPACKET   0x0000000806395020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322347   CXPACKET   0x0000000806395020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322347   CXPACKET   0x0000000806395020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A392748   154   21   18322347   CXPACKET   0x0000000806395020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x00000001D3F902C8   154   22   18270621   CXPACKET   0x000000025CE67020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025C694508   154   23   18270541   CXPACKET   0x000000025C75D020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x0000000004EBCE08   154   1   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x000000000448F708   154   5   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x0000000004485288   154   2   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x0000000004ED7948   154   4   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x0000000004EA3B88   154   3   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x0000000004451B88   154   6   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x0000000004E89048   154   7   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
0x000000025A675708   154   24   18269840   CXPACKET   0x000000025C767020   0x000000000446ABC8   154   8   exchangeEvent
id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17

Hello,
First, I would take a look at what your MAXDOP setting is, that's seems a bit high unless you have around 80 processors - stick to multiples of the number of processors in a single numa node and don't go over half of the numa nodes if this is for an OLTP
system. If it's for a DSS or DW system then having a very high maxdop should be fine.
When dealing with CXPACKET the wait means that it's waiting for all of the parallel threads to complete before it can merge the results and move on. If any single thread has to process more than any other (or waits longer for data) the whole process has
to wait. I would investigate to see if there is a large skew in statistics and one thread is processing much more than another. I'd also try creating an extended events session to grab all of the waitinfo for that session.
Sean Gallardy | Blog |
Twitter

Enable Shadow Copies for Shared Folders in a Failover Cluster (2012 R2)

I cannot find a reference on how to Enable Shadow Copies for Shared Folders in a Failover Cluster
using separate disks for Data and Shadow Copies, using Windows Server 2012 R2. I found an article for Server 2003, but that doesn't solve my issue.
Enable Shadow Copies for Shared Folders in a cluster. Can someone point me to documentation on how to setup properly?
I have a 3 server failover cluster, a single fileserver role with a 2 TB data storage drive and a 200 GB disk for shadow copy drive. The 2 TB is ReFS and being used by Home Directories. The 200 GB is also ReFS, but I didn't have a letter
assigned, but it is associated with the fileserver role.
Any help is appreciated.
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

As mentioned above I spotted Shadow Copy configuration problems in clustered environment on Windows 2012 R2 with latest updates.
Enabling Shadow Copy via Cluster Manager on disk will enable schedule and snapshots but schedule is not-cluster aware (is created locally on node) and "Previous Versions" are visible only locally but not via shared folders (UNC path accesible by
clients)
When I spotted this behavior I tried different way going via Computer Management and cluster resource name but console always hangs for me when using "Configure Shadow Copies". After many minutes configuration window is opened (Hurray!) but any
action there will hang whole console again. Enabling Shadow Copies will fail with "0x80004005: Unspecified
error" for creating scheduled task but "Next Run Time" column still shows "Disabled". Checking disk resource via Cluster Manager shows it is enabled and ?local? scheduled task is created.
Computer management console still shows DISABLED and any action freezes whole console (only when cluster resource name is used).
This fix I found, unfortunately, is not applicable to 2012 R2 OS: https://support.microsoft.com/en-us/kb/2894464
To sum up there is a major bug in MS implementation in Shadow Copies for Shared Folders when clustering is used or it is still not supported in 2012 R2? Doing it outside cluster works as it should (without freezes and Previous Versions are available via
UNC)
There is no documentation about FileServer Clustering on 2012(R2) unfortunately.
Could someone from MS clarify it?
Many thanks
Filip
EDIT:
Ok, one correction:
Scheduled task is not created in "Failover Clustering" hive of Scheduled tasks as user may expect but failover of fileshare to other node will unregister/reregister it on active node only.

RDS 2012 R2 - Allow Some Users Multiple Logon Sessions and Restrict Other Users to a Single Session

In Server 2012 R2 RDS, is there a way to allow some users to log on multiple times, but restrict other users to a single logon? On an OU or AD group basis?
I know there is a GPO setting under Computer Configuration for restricting users to a single logon, but this does not allow me to differentiate on a user basis (only on a per server basis).
Thanks,
James

Hi James,
From my perspective and knowledge, sorry to say but there is no such option\way to provide this permission at same time. If a user specifies a different program to start when the user connects to the RD Session Host server, a new session will be created on
the RD Session Host server for the user, even if the RD Session Host server is configured to restrict users to a single session. A user can specify a program to start on connection on the Programs tab under Options in Remote Desktop Connection.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Plz help!! idempotent methods stateful session beans? (failover)

          plz help!! idempotent methods stateful session beans? (failover)
          Hi there,
          Im trying to failover my shopping cart implemented using stateful ejb, the replication
          is working but the failover is not (Object not found exception....).
          By design is hard to think on an stateful ejb using idempotent methods, but after
          checking the documentation in detail im completely confused, so im starting to
          wonder if i should use idempotent methods or manual retry in case one server is
          down.
          Plz take a loo at these explanations about faiolver in the WLS edocs.
          "....With clustered objects, automatic failover generally occurs only in cases
          where the object is idempotent.....Because of this, replica-aware stubs will not,
          by default, attempt to retry a method that fails after the request is sent but
          before it returns. This behavior can be overridden by marking a service idempotent..."
          BUT
          "By default, a stateful session bean's Home stub provides load balancing and failover
          for its method invocations to any clustered server where the bean is deployed...."
          So is possible to achieve automatic failover (not only load balancing) for stateful
          ejb without having to worry about state-changes or manual retry. (i know the retry
          is requiered if the server crashed just before finishing a transaction but this
          is not what im talking about).
          Any help will be highly appreciated
          Alan


          Ryan,
          Yes, im deploying using In-memory replication and clusterable elements, when try
          to invoke the method (after one of the nodes is down) i recieve an "java.rmi.NoSuchObjectException:
          Bean has been deleted".
          I believe all this could be related to some sort of issue with JNDI Lookup in
          the cluster, but haavent been able to get a clue to make it work....(almost desesperate
          by now)
          Alan
          "ryan upton" <[email protected]> wrote:
          >Alan,
          >
          >If the state isn't maintained during failover I would suspect a
          >configuration error. Have you set the <replication-type> element within
          ><stateful-session-clustering> tag in the bean's deployment descriptor?
          >
          >"Alan" <[email protected]> wrote in message
          >news:40e17cf7$1@mktnews1...
          >>
          >> Ryan,
          >>
          >>
          >> Maybe i didnt explain myself, in the scenario im dealing with I KNOW
          >the
          >method
          >> finished succesfully (example, the user succesfully added an item to
          >a
          >cart).
          >>
          >>
          >> Just after that one of the nodes goes down, and the user decides to
          >add a
          >new
          >> item (new invocation , not a retry of failed one) on the same session.
          >>
          >> This is the case in which failover should work automatically as you
          >say,
          >meaning
          >> the new method invokation should be able to retrieve the session state
          >info from
          >> the replica and switch the primary.....Well, this is the part wich
          >isnt
          >working
          >> :( as i understand it should transparently
          >>
          >> I believe could be a config issue , but have no way to make it work.
          >>
          >> Regards,
          >>
          >> Alan
          >> "ryan upton" <[email protected]> wrote:
          >> >
          >> >"Alan" <[email protected]> wrote in message
          >news:40e06296@mktnews1...
          >> >>
          >> >> Ryan,
          >> >>
          >> >> Thanks for clearing the both conditions a bit more, in this case
          >my
          >> >issue
          >> >has
          >> >> to do with the scenario #1 in which subsequent calls (invocations)
          >> >go to a
          >> >node
          >> >> which isnt avaliable(down), do you have any idea of in what conditions
          >> >the
          >> >"automnatic"
          >> >> failover would fail??? (meaning why the stub would try to dispatch
          >> >a call
          >> >to the
          >> >> same previous node)
          >> >>
          >> >> Thanks for the help again
          >> >>
          >> >
          >> >Subsequent calls won't go to a node that's down. That's the whole
          >> >point
          >> >;-). Failover is always automatic, what you are getting confused
          >on
          >> >is
          >> >automatic method re-execution upon failover which happens if the method
          >> >has
          >> >been marked as idempotent. The logic is this: if I failover to an
          >EJB
          >> >that
          >> >I know is still alive, I can't safely call the same method again.
          > Why?
          >> >Because I don't know how much of the method completed the last time
          >before
          >> >the previous bean's failure. So if the bean can yield multiple results
          >> >from
          >> >multiple invocations I had better play it safe and not re-execute
          >the
          >> >method
          >> >on the bean I failed over to (unless it's idempotent because in that
          >> >case it
          >> >doesn't matter how many times I call it, it always does the same thing).
          >> > In
          >> >scenario #1 and #2 failover is automatic and all new calls are executed
          >> >against the bean the client failed over to, but only idempotent methods
          >> >are
          >> >re-executed.
          >> >
          >> >
          >>
          >
          >

FAILED_OVER for single sessions. No VIP failover

Similar Messages

Maybe you are looking for