StationGlobals for threads in cumunicate

Similar Questions

• Why I see Runtime Error R6016-not enough space for thread data?

  All of a sudden when I try to launch Google Chrome, I get "error R6016-not enough space for thread data? ' like Chrome stops. Plenty of hard disk, disk defragmented, no viruses or malware. Never seen this message before.

  I think you're on the right track to reinstall Chrome... but they have a method of choice for the best results and that the information is here:

  http://support.Google.com/chrome/bin/answer.py?hl=en&answer=111899

  Just FYI, running sfc/scannow won't help, but it will waste your time and you will not be able to determine which file is causing the problem because...

  When sfc/scannow runs successfully, you will see a start and complete message in the Event Viewer log system.

  It can take a long time to run and slow down your system.  When it starts and stops correctly you can only see events like this in the case where the system log viewer:

  Event type: Information
  Event source: Windows File Protection
  Event category: no
  Event ID: 64016
  Analysis of file File Protection Windows has been started.

  Event type: Information
  Event source: Windows File Protection
  Event category: no
  Event ID: 64017
  Windows File Protection file analysis completed successfully.

  There is no information about what he did or what he did not.

  Even if sfc/scannow finds something to do, you will not know about it.

  That's why try again more than a waste of time.

• RMAN-06025: no log backup archived for thread 1 with sequence - on double

  I tried to make a duplicate of a database, something I have done before, but this time I have run in to a problem.

  So, make a

  RMAN > list archivelog all;

  Shows that I have log sequence numbers 2600-2862 available.

  I have removed the expired archive logs and made an overlap and have issued the order on «alter system current archivelog» DB

  I did the pfile file and open the destination DB in nomount.

  The backup of the DB and the archivelogs seems to work fine without error.

  RMAN > backup as backupset = compressed database format ' / u04/tmpback/%u' tag "CLONE_TO_PPRD" include current controlfile;

  RMAN > backup as backupset archivelog Tablet all format = ' / u04/tmpback/al_%u' tag "CLONE_TO_PPRD_AL".

  Thus, with the environment on the destination DB (PPRD), opening a new rman to make the duplicate... "' rman target auxiliary sys@source_db /" "

  Then run the command

  target database duplicate to the PPRD until the SNA 2538794790;

  It seems to work fine, until this...

  Instance Oracle to close

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of the command duplicate Db at 30/10/2014 14:46:22

  RMAN-05501: abandonment of duplicate target database

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06053: unable to perform the recovery of the media because of the missing journal

  RMAN-06025: no backup log archived for thread 1 with sequence 2599 and YVERT departure from 2500202517 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2598 and YVERT departure from 2500201335 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2597 and YVERT departure from 2500102904 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2596 and YVERT departure from 2499995595 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2595 and YVERT departure from 2499836289 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2594 and YVERT departure from 2499642775 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2593 and YVERT departure from 2499478641 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2592 and YVERT departure from 2499413468 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2591 and YVERT departure from 2499410632 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2590 and YVERT departure from 2499408867 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2589 and YVERT departure from 2499381186 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2588 and YVERT departure from 2499068021 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2587 and YVERT departure from 2498925555 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2586 and YVERT departure from 2498802786 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2585 and YVERT departure from 2498614939 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2584 and YVERT departure from 2498564861 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2583 and YVERT departure from 2498562153 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2582 and YVERT departure from 2498561088 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2581 and YVERT departure from 2498484636 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2580 and YVERT departure from 2498271487 found to restore

  RMAN-06025: no backup log archived for 1 with sequence 2579 threads and YVERT departure from 2498214991 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2578 and YVERT departure from 2498212309 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2577 and YVERT departure from 2498211201 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2576 and YVERT departure from 2498136750 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2575 and YVERT departure from 2498007880 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2574 and YVERT departure from 2497940390 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2573 and YVERT departure from 2497937659 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2572 and YVERT departure from 2497935694 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2571 and YVERT departure from 2497906173 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2570 and YVERT departure from 2497856983 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2569 and YVERT departure from 2497596547 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2568 and YVERT departure from 2497456509 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2567 and YVERT departure from 2497319931 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2566 and YVERT departure from 2497256972 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2565 and YVERT departure from 2497254201 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2564 and YVERT departure from 2497252909 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2563 and YVERT departure from 2497193527 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2562 and YVERT departure from 2496934735 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2561 and YVERT departure from 2496745593 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2560 and YVERT departure from 2496657121 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2559 and YVERT departure from 2496603411 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2558 and YVERT departure from 2496600720 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2557 and YVERT departure from 2496599649 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2556 and YVERT departure from 2496488543 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2555 and YVERT departure from 2495585865 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2554 and YVERT departure from 2495399778 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2553 and YVERT departure from 2495269888 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2552 and YVERT departure from 2495267113 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2551 and YVERT departure from 2495264943 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2550 and YVERT departure from 2495263264 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2549 and YVERT departure from 2495032426 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2548 and YVERT departure from 2494891192 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2547 and YVERT departure from 2494748475 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2546 and YVERT departure from 2494688135 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2545 and YVERT departure from 2494685342 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2544 and YVERT departure from 2494684167 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2543 and YVERT departure from 2494617350 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2542 and YVERT departure from 2494441823 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2541 and YVERT departure from 2494219188 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2540 and YVERT departure from 2494146694 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2539 and YVERT departure from 2494143651 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2538 and YVERT departure from 2494141374 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2537 and YVERT departure from 2494140316 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2536 and YVERT departure from 2494039070 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2535 and YVERT departure from 2493969002 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2534 and YVERT departure from 2493966234 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2533 and YVERT departure from 2493964141 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2532 and YVERT departure from 2493962603 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2531 and YVERT departure from 2493730362 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2530 and YVERT departure from 2493626024 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2529 and YVERT departure from 2493623327 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2528 and YVERT departure from 2493620995 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2527 and YVERT departure from 2493619424 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2526 and YVERT departure from 2493412146 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2525 and YVERT departure from 2493235154 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2524 and YVERT departure from 2493121677 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2523 and YVERT departure from 2493059844 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2522 and YVERT departure from 2493057083 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2521 and YVERT departure from 2493055871 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2520 and YVERT departure from 2492957915 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2519 and YVERT departure from 2492880955 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2518 and YVERT departure from 2492544076 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2517 and YVERT departure from 2492423758 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2516 and YVERT departure from 2492417400 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2515 and YVERT departure from 2492414719 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2514 and YVERT departure from 2492413908 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2513 and YVERT departure from 2492327128 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2512 and YVERT departure from 2492230125 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2511 and YVERT departure from 2491947217 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2510 and YVERT departure from 2491884830 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2509 and YVERT departure from 2491821845 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2508 and YVERT departure from 2491819116 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2507 and YVERT departure from 2491817468 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2506 and YVERT departure from 2491784652 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2505 and YVERT departure from 2491719981 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2504 and YVERT departure from 2487354643 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2503 and YVERT departure from 2487272304 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2502 and YVERT departure from 2487218716 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2501 and YVERT departure from 2487215968 found to restore

  RMAN-06025: no backup log archived for thread 1 with 2500 sequence and YVERT departure from 2487214915 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2499 and YVERT departure from 2487178867 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2498 and YVERT departure from 2475666929 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2497 and YVERT departure from 2475424798 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2496 and YVERT departure from 2475356185 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2495 and YVERT departure from 2475353406 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2494 and YVERT departure from 2475352071 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2493 and YVERT departure from 2475297238 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2492 and YVERT departure from 2475237220 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2491 and YVERT departure from 2475177867 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2490 and YVERT departure from 2475175065 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2489 and YVERT departure from 2475173911 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2488 and YVERT departure from 2475116250 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2487 and YVERT departure from 2475011369 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2486 and YVERT departure from 2474948383 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2485 and YVERT departure from 2474945180 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2484 and YVERT departure from 2474943701 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2483 and YVERT departure from 2474893025 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2482 and YVERT departure from 2474114073 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2481 and YVERT departure from 2473907191 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2480 and YVERT departure from 2473776113 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2479 and YVERT departure from 2473773241 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2478 and YVERT departure from 2473770145 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2477 and YVERT departure from 2473769454 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2476 and YVERT departure from 2473666106 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2475 and YVERT departure from 2473483998 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2474 and YVERT departure from 2473381579 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2473 and YVERT departure from 2473134334 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2472 and YVERT departure from 2473066760 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2471 and YVERT departure from 2473064023 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2470 and YVERT departure from 2473062119 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2469 and YVERT departure from 2473038503 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2468 and YVERT departure from 2472797901 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2467 and YVERT departure from 2472710532 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2466 and YVERT departure from 2472456854 found to restore

  RMAN-00567: Recovery Manager could not print error messages

  Why is it always get all these old newspapers archive? What should I do to get that continues. I'm sure miss me something small, but it is just eluding me.

  Thank you

  Rob

  Follow these steps:

  RMAN > crosscheck backup;

  RMAN > overlapping copy;

• Media, recovery waiting for thread 1 sequence (in transit)

  I have rebuilt our standby database using rman double since it lacked many newspapers of archiving.
  
  After the double, the eve is now almost in sync with the primary. The Marbles that ship through, but are not implemented in a timely. How long should wait to a journal of the Archives of the primary to be applied to the waiting?
  
  I need to know this so that a good script can be configured to check the primary and standby. For the moment, that they are never exactly synchronized - sequence always one behind the primary number.
  
  Why is Eve does not have in a timely fashion?
  
  From the journal of alerts:
  
  Media, recovery waiting for thread 1 sequence 11278 (in transit)
  
  The journal seems to be "in transit" for a long time
  
  PRIMARY:
  SQL > select max (sequence #) the journal of v current_seq $;
  
  CURRENT_SEQ
  -----------
  11278
  
  
  SB:
  SQL > select MAX (SEQUENCE #), APPLIED from V$ ARCHIVED_LOG in case of APPLICATION = 'YES' GROUP APPLIED;
  
  MAX(SEQUENCE#) APP
  -------------- ---
  YES 11277
  
  
  JOURNAL ALERTS:
  RFS [2]: Archived Log: ' / backup/prod/log_1_11277_704816194.dbf'
  Primary database is in MAXIMUM PERFORMANCE mode
  Mon Nov 1 15:22:01 2010
  Recovery Media Log /backup/prod/log_1_11272_704816194.dbf
  Mon 1 Nov 15:26:49 2010
  Recovery Media Log /backup/prod/log_1_11273_704816194.dbf
  Mon Nov 1 15:29:54 2010
  Recovery Media Log /backup/prod/log_1_11274_704816194.dbf
  Mon Nov 1 15:34:18 2010
  Recovery Media Log /backup/prod/log_1_11275_704816194.dbf
  Mon Nov 1 15:36:42 2010
  Recovery Media Log /backup/prod/log_1_11276_704816194.dbf
  Mon Nov 1 15:39:43 2010
  Recovery Media Log /backup/prod/log_1_11277_704816194.dbf
  Mon Nov 1 15:42:34 2010
  Media, recovery waiting for thread 1 sequence 11278 (in transit)
  
  I should add that I understand that for the primary and standby to be interrupted by a newspaper is not a concern (they ask). It's just that I wanted a check that compare the two script and at the time where they are never equal - when I understand them to be, and that newspapers should apply almost immediately.
  
  Published by: Dan on November 1, 2010 16:36

  How long should wait to a journal of the Archives of the primary to be applied to the waiting?

  also depends on the speed of the network.
  Make sure that the archives are shipped instead of sleep.

  PRIMARY:
  SQL > select max (sequence #) the journal of v current_seq $;
  CURRENT_SEQ

  11278 (it's not connect archivelog)... :)

  SB:
  SQL > select MAX (SEQUENCE #), APPLIED from V$ ARCHIVED_LOG in case of APPLICATION = 'YES' GROUP APPLIED;
  MAX(SEQUENCE#) APP

  YES 11277

  Hi check MRP starts or not?
  database principal that you must not check the current sequence, generated check last sequence... not common sequence.

  current sequence is redo log, which has not yet been archived

  I think that everything is perfect here... no problems.

  Hope you understand, I would like to know if it is not explicit, thank you.

• Editing screen, but still wait for thread to return

  I have an app that makes updates to the user interface through a reference to a bitmapfield a new thread, and that thread is updating the user interface.

  The problem I have is that I want the main thread "wait" wire under update charts, before continuing with the "game".

  so... for example...

  // update the main bitmapfield  pt = new PlayerThread(bfField,square);
  pt.start(); 
  
  // wait for the thread to finish updating the ui while (pt.isAlive()){}
  

  Now, I * KNOW * it is not the right way to do this, because the UI is not updated, because the user interface is in a loop waiting for the thread ends, which defeats the purpose of having the thread in the background in the first place.

  What is the 'proper' waiting to do this? I completely missed the point to put on?

  It works fine if I do not "wait" for the thread, but this means that the user can press the buttons, or interact with the game when they aren't supposed to.

  I thought that there must be a way to define a 'isthreading = true' var and disable keys by adding an if statement to my keydown, but how can I make my app "waiting" for the thread, I created to be finished, but not really break the UI itself?

  I hope that was clear...

  You need a reporting mechanism indicating the UI thread "I'm done" or "the data is ready. Never loop in a UI thread - this will cause finally the event queue to overflow, which ask you dumped as "refractory".

  A typical mechanism is to implement a listener and a data event. The "interested" party registers a listener with the background thread, the background thread fires the event data when appropriate.

  If there is only a single listener, then it can be implemented with fewer resources by using a callback mechanism.

  Search for references to the model of the observer:

  http://en.Wikipedia.org/wiki/Observer_pattern

• Notifications by e-mail for threads

  In the past, when I look at my personal e-mail notification for the threads that I am involved, I could easily delete older entries because they were classified and labeled at the age of the last activity, say "2 months" for example.

  Today I see that the dates and they do not seem to be sorted according to the last activity. This makes it more work to move and throw the old idle sons.

  Is it possible to recover the old vision?

  
  
  If you found this information useful, please consider awarding points to 'Correct' or 'Useful' responses Thank you!!
  
  AWo
  

  VCP/vExpert 2009

  This is good feedback, and Yes, it would be wise to order them by last activity.  The only problem I have is a priority, because it is a nice feature to have, and I have my team of dev busy with other tasks.

  -Robert

• Eve redo particular journal for thread group

  Hi master,
  
  I actually play experience to create the database physical standbyt on the same machine as my primary database.
  
  I have my past according to "data guard admin guide". even if the article for the newspaper group waiting for redo ading, it says you need to add the newspaper group pending roll forward to 'wire '...
  
  What is this thread? and how can I foind thread that I have to give the next group of redo log?
  
  How to find the current thread?
  
  What happens if I add "thread"clause in my statement:-".
  
  ALTER DATABASE ADD LOGFILE ENSURES WIRE 5
  2 > ('/ oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500 M;
  
  Thanks and greetings
  VD

  Vikrant,

  First a question: you have a RAC instance? If so, the same paragraph does not apply to you and I don't know why you are questioning it.

  Second

  "The THREAD clause is required only if you want to add one or more standby redo log.
  groups of files to a specific primary database thread. If you do not include the WIRE
  clause and the configuration uses Real Application Clusters (RAC), Data Guard will be
  automatically assign standby redo log threads file groups when running because they are
  required by the various RAC instances. »

  This means that you don't have to specify the thread for CARS, it will affect one according to the current thread.

  Your conclusion is incorrect.
  Where did you read the word "current"?
  Oracle will probably simply ensure that each instance has enough sleep redolog groups, it takes 1 day before redolog group-by-Group + 1 extra.

  --
  Sybrand Bakker
  Senior Oracle DBA

• Rich Text Editor for threads - please fix the bugs!

  Hello

  I don't know if I'm alone in this experience, but the Rich Text Editor is terribly buggy - at least on Firefox

  I'm trying to change in a "What you see is what you get"-style to ensure that information is presented in a good way.

  When I post the message is often completely f...

  At least, it would be great to have an option to see a preview of the post (or is that and I'm just blind to find?).

  It would really help that my comment between two texts cited is not add in the framework of the first text mentioned... (just an example of what has happened in the last 24 hours...). When I want to help or chat, I'm really annoyed to waste time with such things - but also with poorly formatted information, which makes it more difficult to understand.

  Best regards

  Bernd

  work on VM Ubuntu with the latest update of Firefox, VMware authorized Scripts.

  Like what is said above the rich text editor has quite a few bugs.  Believe me, they know pretty much all we have brought up a lot of times what they was using the text editor that works quite well and has very few bugs.  You can also set your value by default when you post then change, text gross, then on the side right of the screen, there's a link saying "set default editor", which will start you clear each time.  Even thought it might not be as fantasy, it does the job without the headaches of your post showing completely messed up 75% of the time

  • Kyle

• StationGlobals in Batch Mode - even for all the lots?

  Hello

  I am trying to create a simple Testplan in BatchModel with 4 TestSockets.

  In the testplan is a loop, a loop around a SationGlobal.Dut for 10 times

  Question: Is this StationGlobal copied for all 4 testsockets and is also 4 times in the backgrouodn or the same stationglobals for all testsockets?

  Should I use a table 1 d for the loop variable and use as Index MyIndex from the SocketNumber?

  THX

  Solved.

  Changed the StationGlobal in a table with size = number of TestSockets.

  In the testplan write and read of the StationGlobal for help:

  StationGlobal.MyGlobal [RunState.TestSockets.MyIndex]

• Error in the new thread should terminate execution

  Hello

  I have a labview VI (continuous while loop), getting initialized in the subsequence of Initialize section of the main sequence and running in the new thread. An error in the execution of this loop will stop execution of VI, pass the error to Teststand and out the thread. I need to put an end to the execution of the main sequence, when the error event in the new thread (passing initialization). Is it possible to do? I'm getting the popup of error Standard Teststand, when the error event, but when I choose to cancel/Abort, the execution of the main sequence doesn't stop and continues. What is the right way to handle errors for threads running in parallel?

  Thank you best regards &,.

  Juvin Ronny

  Some approaches.

  1) wait on the new thread periodically with a wait with a timeout step zero and "timeout causes error" box unchecked. If the thread is finished and has an error, the step of waiting spread the main thread of the error.

  (2) call the Execution.Terminate () or Execution.Abort () of cleaning up your sequence newthread.

  Hope this helps,

  -Doug

• Nut thread inspection

  Hi all

  I have an application in which I want to inspect a hole size M6 for Threading.

  It's a simple "go/no go" system to check if the thread is present or not. No need to thread quality, pitch, etc.

  Is this possible in Labview using a USB camera or something? If Yes, can someone give me an idea?

  Thank you. I appreciate your help.

  Yes its possible!

  Requires software OR following

  Vision acquisition module (SAV)

  Vision development module

  IMAQ dx Module

  Learn more about NI VISION

  https://decibel.NI.com/content/docs/doc-46492

• Problem with the archive log when you use RMAN for backup and restore (11g 2)

  Hello world
  Please help me solve this problem.
  I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
  -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
  

  
  D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}

  Repeat 7 times (Monday-> Saturday). And I got these files:

  [oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1


  And
  RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

  My configuration of rman:
  RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

  - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16

RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2

RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16

Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16

searching for all files in the recovery area
cataloging files...
no files cataloged

using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16


  -Fourth, the problem here, I got the database;
.. .every oky until this line...
starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82      2.16M      DISK        00:00:00     20-JAN-16     
        BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

  List of Archived Logs in backup set 82
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1154833    20-JAN-16 1177422    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83      3.88M      DISK        00:00:00     20-JAN-16     
        BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

  List of Archived Logs in backup set 83
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1162729    20-JAN-16 1188784    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84      10.68M     DISK        00:00:01     20-JAN-16     
        BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

  List of Archived Logs in backup set 84
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    2       1177422    20-JAN-16 1201833    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88      1.81M      DISK        00:00:01     20-JAN-16     
        BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

  List of Archived Logs in backup set 88
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    3       1201833    20-JAN-16 1204844    20-JAN-16
  1    4       1204844    20-JAN-16 1204893    20-JAN-16
  1    5       1204893    20-JAN-16 1204958    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92      143.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

  List of Archived Logs in backup set 92
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       1204958    20-JAN-16 1205034    20-JAN-16
  1    7       1205034    20-JAN-16 1205253    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96      80.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

  List of Archived Logs in backup set 96
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       1205253    20-JAN-16 1205354    20-JAN-16
  1    9       1205354    20-JAN-16 1205433    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100     18.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

  List of Archived Logs in backup set 100
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    10      1205433    20-JAN-16 1205519    20-JAN-16
  1    11      1205519    20-JAN-16 1205559    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104     128.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

  List of Archived Logs in backup set 104
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    12      1205559    20-JAN-16 1205624    20-JAN-16
  1    13      1205624    20-JAN-16 1205739    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108     8.00K      DISK        00:00:00     20-JAN-16     
        BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

  List of Archived Logs in backup set 108
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    14      1205739    20-JAN-16 1205796    20-JAN-16
  1    15      1205796    20-JAN-16 1205840    20-JAN-16

  
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

  Sorry for a long post.


  > 1 and from the 1205841 SNA sequence

  The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

  The message

  channel ORA_DISK_1: restoring archives Journal

  Archives journal thread = 1 sequence = 15

  channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

  channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

  indicates that he has restored the sequence up to 15

  You can check the log file alert database instance for messages on the fact of recovery.

  He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

  Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

  Hemant K Collette

• I would like to know the role of each thread on the coherence

  Help me.
  I would like to know the role of each thread on coherence.
  There are too many kinds of discussions.
  
  Example ~.
  --------------------------------------------------------------------------------------------------------------------------------------------------
  GC GC RUNNABLE slave slave
  RMI TCP TCP RMI-1972 accept accept 1972 RUNNABLE
  Track subscriber Health Center track subscriber RUNNABLE Health Center
  LT = 0:P = 342534:O = 0:port = LT 55170 = 0:P = 342534:O = 0:port = RUNNABLE 55170
  Attach the loop to wait API API wait loop tie RUNNABLE
  PacketListener1 PacketListener1 EXECUTABLE
  PacketListener1P PacketListener1P EXECUTABLE
  PacketListenerN PacketListenerN EXECUTABLE
  Cluster | Member(ID=1, timestamp=2013-04-05 10:45:44.655, Address=192.168.240.157:8088, MachineId=50044, location=site:,machine:TMTEST-PC,process:5316, Role=CoherenceServer) Cluster. Member(ID=1, timestamp=2013-04-05 10:45:44.655, Address=192.168.240.157:8088, MachineId=50044, location=site:,machine:TMTEST-PC,process:5316, Role=CoherenceServer) EXECUTABLE
  RT = 0:P = 342534:O = 0:TCPTransportConnection [addr = 192.168.240.157, = 55178, local port = 55170] RT = 0:P = 342534:O = 0:TCPTransportConnection [addr = 192.168.240.157, = 55178, local port = 55170] RUNNABLE
  Thread finalizer finalizer thread RUNNABLE
  WT = 10 WT = 10 RUNNABLE
  Main TIMED_WAITING main
  IpMonitor IpMonitor TIMED_WAITING
  Invocation: management: EventDispatcher Invocation: management: EventDispatcher TIMED_WAITING
  Invocation: Invocation: management of the TIMED_WAITING
  DistributedCache DistributedCache TIMED_WAITING
  JMX server connection timeout JMX server connection timeout 52 TIMED_WAITING 52
  RMI Scheduler (0) RMI Scheduler (0) pending
  WAITING for Thread-6 wire-6
  stop the server to JMX on stop stop JMX server during the stop pending
  Logger@9228429 3.7.1.7 Logger@9228429 3.7.1.7 pending
  PacketReceiver PacketReceiver pending
  PacketPublisher PacketPublisher pending
  PacketSpeaker PacketSpeaker pending
  WT = 7 WT = WAITING 7
  WT = 9 = WAIT 9 WT
  -----------------------------------------------------------------------------------------------------------------------------------------------

  Briefly

  PacketListener1 PacketListener1P PacketListenerN - listen to threads of e/s for TCMP transport protocol
  Cluster. Member (Id = 1, Timestamp is 10:45:44.655 2013-04-05, address = 192.168.240.157:8088, MachineId = 50044, location = site:, machine: TMTEST-PC, process: 5316, role = CoherenceServer) -main thread for the cluster service (discovery, node joing / exit, etc)
  IpMonitor - monitor IP, is involved in the detection of death system
  Invocation: management: EventDispatcher -thread expedition event for JMX service distributed in coherence
  Invocation: management -main thread for JMX services distributed in coherence
  DistributedCache - main thread for the cache service DistributedCache
  Logger@9228429 3.7.1.7 - wire consistency async logging
  PacketReceiver - wire incoming network packets
  PacketPublisher - wire, sending packages via TCMP
  PacketSpeaker - wire, sending packages via TCMP (discharges of some PacketPublisher work for the better use of Basic)

• Execution of sequential operations to parallel groups of Threads

  I have the following scenario, which must be changed as soon as possible:
  1. a group of sequential threads runs (contains 3-wire)
  2. a sequential group of other threads is running (contains 2-wire)
  3. a group of parallel threads is running (contains 9 wires such as producers and consumers of threads applied properly)
  
  Why I created this scenario?
  To run a particular thread first (point-1: containing 3-wire), after their treatment is done I needed to run another 2-wire (point-2: containing 2 wires). If and only if 1 and 2 points are covered, I required to deal with-3 points.
  
  Initially, I required to run all threads for parallel operations, but I left this idea that parallel threads are run simultaneously.
  
  For the situation described above everything works smoothly until there was a problem.
  
  Why do I need to change the above scenario?
  Sometimes, I get an Exception that can be handled well in the case of parallel threads. While the same Exception if I get in the sequential threads that becomes unmanageable. Since then, all other sequential treatments of threads comes under condition of waiting until the end of the first.
  
  
  So, I need to take advantage of the parallel threads, but I chose this path to be easy which became difficult to handle the situation for the application.
  So, I need to create such a scenario, in which I need to run different parallel threads for a fixed order. For example:
  Order-1 = process the first 3 parallel threads
  Order-2e = process 2 parallel threads
  Order-3e = process the next 9 parallel threads
  
  Also, the above case is somewhat limited, although I need a generic solution for this. As if in the future, I want to add more than 2-wire command-1 or if I remove still some discussions for any order must be execution of the sequence of groups as you want.
  Is it possible in java through which we can make a group of parallel threads that can be executed to order we can specify?
  
  I have the code snippet following, if you can help me to change:
  
  Level-1
  
  [] Thread = Thread [list1.size (new)];
  int j = 0;
  {for (List1.Size ())}
  Object delegator1 = new Object("Level-1");
  Thread th = new Thread (delegator1);
  discussions [j] = th;
  Th.Start ();
  
  j ++ ;
  }
  for (thread Threading: thread) {}
  thread. Join();
  }
  
  Level-2
  
  son = new Thread [list2.size ()];
  j = 0;
  {for (List2.Size ())}
  Object delegator2 = new Object("Level-2");
  Thread th = new Thread (delegator2);
  discussions [j] = th;
  Th.Start ();
  
  j ++ ;
  }
  for (thread Threading: thread) {}
  thread. Join();
  }
  
  Level 3 & 4-> producer-consumer applied using wait-notify works very well.
  
  {for(list3.) Size())}
  Object delegator3 = new Object ("level 3 & 4")
  Thread th = new Thread (delegator3);
  Th.Start ();
  }
  
  I want these different levels to run at the same time but if first level finishes off the second level must eventually runs.
  
  Published by: 990484 on February 26, 2013 09:45

  If you just want to wait for a set of threads end, for example, use a CountDownLatch in the main thread, initialized to the number of threads. The main thread waits then each thread to complete and to warn the latch.

  Repeat for the next series.

• Success for the RESTORATION but failed on RECOVER - need help

  I was able to run the command 'restore database' and it went successfully.
  But when I run 'recover data', it will stop with error
  
  RMAN-08187: WARNING: media recovery until all SNA 1155620136
  Archive log file name=/oracle/oradsk3/archivelogs/1_94646_700099109.dbf thread = 1 sequence = 94647
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command recover at 19/11/2012 05:55:32
  ORA-00283: cool cancelled due to errors
  RMAN-11003: failure in parsing / execution of the SQL statement: alter database recover logfile ' / oracle/oradsk3/archivelogs/1_94646_700099109.dbf'
  ORA-00283: cool cancelled due to errors
  ORA-01112: media recovery not started
  RMAN-06054: unknown request media recovery log archived for thread 1 with sequence 94647 and from the 1155620136 SNA
  
  
  Even though I have this error correctly I can start my database without problem. But on our ERP application, she meet errors such as below
  Error: SQLState QP99P: database error 376 (error 1376) (rcdset.readkastset () in the subject...
  Fatal error: error 1376 (database error 376) on select
  
  What should be corrected for this problem?
  On the other hand, im a newbie to the oracle database. Hope someone could help me with that.
  
  Here are the commands I've done:
  controls:
  1) rman-> enter
  (2) connect target /-> enter
  (3) delete expired backup; -> enter # this will remove all the expired backup set on the controlfile
  (4) catalog starts by ' / oracle/RMAN; -> enter # this will be added all the files in the directory
  (5) overview of restore of database; -> enter # this will test restore backup sets on the database, no real restoration, the test only.
  (6) validate restore them database;
  (7) food that all archivelog validate;
  (8) judgment;
  (9) startup nomount;
  (10) mount the database;
  (11) incarnation of the list;
  (12) to restore the database incarnation 1; -Replace the old incarnation.
  (13) restore database;
  (14) to recover the database;
  (15) Alter database open resetlogs;

  the value of newname for datafile ' / oracle/dbs/Ora11g/MISSING00126 ' to ' / oracle/oradsk3/ERPLN/system01.dbf';

  Are you sure that FILE_ID 126 was system01.dbf?

  until the sequence = 94646;

  should be the SEQUENCE until = 94647 (i.e. the last archivelog to apply more 1)

  recover the database;

  All until the clause should be in the same braces as RESTORE and RECOVER

  Hemant K Collette