Similar Questions

• Problem with the rule while the data is loading files

  Hello
  
  I'm having a problem trying to load data to an application that uses rules files. Load data files were from another application using the DATAEXPORT. I have two files for each entity. One is for the current year and one for next year. The source and target applications are different, so I do all the mapping using rule files.
  
  The data of the current year file contains data for CurrMonth:Dec & CurrYear. The following year data file contains data for Jan: Dec and the next. I made rules for each entity files load data into the application and has made the mapping when creating these rules files using set 12 months.
  
  The problem that I am facing is that I'm able to correctly load the following year in the target application, my rules file is the right month for each column mapping. But for the year underway, I have just 2 columns of data (whereas & CurrMonth = Nov) and so when I'm trying to load the data file using the rules file, it is to map the November and December months like January and February and charging at these months of FY11, which is false.
  
  I don't know how to solve this problem. The current year data file it will always change in terms of months then how can I modify the rules that he recognizes that the months are coming in and where to put the data.
  
  Please let me know your suggestions. Any help will be appreciated.
  
  Thank you!
  ~ Hervé
  
  PS ~ it was the same problem, I was faced with a few months back when I posted this question and I followed the advice in this post, but always faced to the question - DATAEXPORT and rules files
  
  Published by: Gwen on December 20, 2011 08:25

  Adella,
  We have faced a similar issue and we were able to solve it by sticking to these months dimension members (& currmonth: dec) and generate the header
  The export file created when paste us the dimension names in front of months on the export file
  Suppose that your export file is currmonth.txt and she Nov and Dec
  first line of your export file should look like this
  'Version' 'Year' 'Scenario' "XYZ" "123" "ABC" "Account", "Nov", "Dec".
  We have created a batch file to add this to the original export file, it looks like this
  Paste d "\0" Header.txt "D:\Hyperion\products\Essbase\EssbaseServer\app\xyz\123\currmonth.txt" > "D:\Hyperion\products\Essbase\EssbaseServer\app\xyz\121\currmonthchange.txt".

  Header.txt is a text file that it contains ("Version" "Year" "Scénario" "XYZ" "123" "ABC" "count")

  change your rules file so that it generates the header in your source (currmonthchange.txt)

  rulefile--> the properties of data source--> header--> data records source header--> recording containing the names of data filed charge (set 1)

  I hope this will solve your problem

• Netflix in Media Center returns a 'there was a problem of data recovery. "Check the works of your internet connection and try again" error instead of loading Netflix data.

  context: a previous thread with an identical title never responded, the problem just disappeared.  Well its been two weeks since then and the problem came back.

  somethings which may or may not apply: internet TV seems to work better in media center.  All updates have been applied to H.P. of Vista SP2. Netflix works fine in ie8 (such as the internet, of course). Tried to delete all the Internet Options, delete browsing history section of Internet Explorer. I get the same error message with my windows 7 professional media center, but netflix seems to play anyway (no game with vista). I recently installed quicktime alternative 2.72 to see what it was and how it worked, then removed and put back in quicktime.

  Tried / symptoms:

  -Remove all the browsing history (econcepts)
  -Same message on Win7pro but works even when (econcepts)
  -Works on Win7 no problem (omegafiler)
  -Works in ie 8 (econcepts)
  -Works in crome (Martin TX)
  -Consensus is that it started around December 30, 2009 (GeoffG1, johnetX, me)
  -Remove and reinstall silverlight (omegafiler)
  -Remove and replace netflix plugin (omegafiler)<- how="" did="" you="" do="" that="">
  -Netflix says: microsoft problem (Nitestalker)
  -Microsoft is silent (this thread - on vacation?)
  -Same problem on 32-bit and 64-bit VMC (JRSMiamiFL)
  -No applied update (johnetx)<- perhaps="" date="" related="" or="" drm="" date="">
  -Disconnect from netflix, you reconnect again - ultimately the same error (chicagokiwi)
  -Tried to reduce the number of items in the queues to well below the limit of 200 (econcepts)
  -Tried the register / unregister the third wire procedure, no joy (does not break anything else however)
  -Disabled the firewall, no change (econcepts)

  related topics:
  http://social.answers.Microsoft.com/forums/en-us/vistaprograms/thread/0c154c0a-1fcb-4353-8c5e-b394e885256d

  http://social.answers.Microsoft.com/forums/en-us/vistaprograms/thread/aaab24a0-4BB9-42FA-a5ee-46a733d6560f

  http://social.answers.Microsoft.com/forums/en-us/vistamedia/thread/f05f69c7-6456-4117-B302-27c08886ea1e

  Someone else knows Netflix not being is not able to connect?  It started yesterday (30/12/2009) for me.  I looked fine the day before without problem.  The message I get says "there was a problem of data recovery.  Check the works of your internet connection and try again. Ok.  I make it work with both my VMC - one with the service pack and the other without.  My OS updates have been loaded in early December, so I don't see how this could it be.  I searched and found this problem has come up before, but I have not found a solution.  I made NO changes to my HTPC.

  Those who have and solved this problem.

  UPDATE UPDATE UPDATE UPDATE UPDATE UPDATE *.

  2009-01-05 has attempted to start Netflix this morning and you know, it works on both my VMCs.  That's the good news.  So now the real questions are:

  Only 20 people reported it as a problem and only 6 on the green button.  I believe that it affected all the world with Media Center.  So why not discussed much?

  It already happened, causes a stir and silently slips without known cause or cure.  How can we find out what caused this and how to prevent it from happening again in the future?

  *******************************************************************************************

• Netflix in WMC «there was a problem of data recovery...» »

  I installed the latest round of updates (Ultimate) of Windows Vista and it apparently burst Netflix in WMC.  Now, I get the error:

  "There was a problem of data recovery. Make sure your internet connection is working and try again. »

  Internet works on the machine.  I reinstalled Silverlight (v4) and Netflix for WIndows Media Center.

  How to diagnose and repair the problem?

  Thank you!

  Keith...

  Sorry for the delay, but I've been busy (in my free time) trying to get this to work.

  I gave up trying to resuscitate MCE and installed a brand new Windows Vista Ultimate Edition with Service Pack 2.  After apply all WIndows patches and installation of Silverlight, I have the "Netflix" element in MCE.  He invites me to install, what I'm doing.  However, every time I start MCE and go to Netflix, he tells me to do reinstall - no login screen.

  I tried all the "mcupdate" article and then supported your steps above, but no go.

  I did this twice, so it wasn't just a fluke.  Apparently, the part of Netflix to MCE is not detect the plug-in that it installed.

  Any thoughts on what to do then?

  Thank you again...

  Keith...

  Later: I ran "mcupdate" after the steps you suggested, and now Netflix is gone again!

  Later: same problem on my other computer running MCE and Vista.  I don't want to mess up this computer so I left as what.

  Later: opening of a new post on problems become Netflix to work with a clean install.

• Failed to load movies Netflix in Media Center message appears to indicate there was a problem of data recovery. Check the works of your internet connection and try again.

  Original title: cannot load Netflix movies in Media Center

  Netflix photo click on the message appears indicating a problem of data recovery.  Check the works of your internet connection and try again.

  Hi Barbarasimonetti,

  (1) since when are you facing this problem?

  (2) remember to make changes?

  (3) what is the complete error message you receive?

  Method 1: You can follow the steps described in the article below

  Known issues and limitations of Netflix on Windows Media Center for Windows Vista

  http://support.Microsoft.com/kb/972496

  Method 2: If a Protection of resources Windows (WRP) file is missing or is damaged, Windows may not behave as expected. Auditor of file system (CFS) scan to fix all of the corrupted system files. To do this, follow the steps mentioned in the link below:

  How to use the System File Checker tool to fix the system files missing or corrupted on Windows Vista or Windows 7

  http://support.Microsoft.com/kb/929833

  Thank you, and in what concerns:

  Ajay K

  Microsoft Answers Support Engineer
  ***************************************************************************

• Problem with the rules after upgrade of the VM in foglight cartridge

  Hello

  There is a small problem with the rules after that I updated the VM cartridge level.

  In the default rules, I changed a few settings so that they will act as I need.

  However, each time I upgrade VM cartridge my rules are off and marked as backup.

  The question is: is there a way to upgrade the cartridge and keep my active rules after upgrading?

  Best regards

  Victor

  This is the normal behavior according to this KB article

  https://support.quest.com/SolutionDetail.aspx?ID=SOL105872&PR=Foglight

  105872 knowledge article

   
  • return

  • Title

    Backup rules fill in the dashboard management rule after Foglight upgraded

  • Description

    After that an upgrade of Foglight was conducted, several backup rules are created for rules that have been published before the upgrade. For example:

    Cluster VMW IO network
    Cluster VMW IO network (backup)

  • Resolution

    During the upgrade procedure, the FMS has detected that some of the original rules have been changed in some way. It copies the rules previously upgraded in backups, before trying to merge the contents of the update rule in the former.

    Assuming that the FMS works as expected, the rules of backup can be deleted. However, it is best to confirm this in the respect of the rules first before making deletions.

    When editing rules, particularly rules OOTB (out of the box), it is recommended to copy the original rule, disable the original rule and edit the copied rule. This should reduce the risk of the problem described in this Article.

  Golan

• Adobe, we are tired of you. expecially if you stole the money. I'm still waiting to solve the problem of the double charge.

  Adobe, we are tired of you. expecially if you stole the money. I'm still waiting to solve the problem of the double charge.

  Hello

  Sorry for the inconvenience.

  We see that you have an adobe account with e-mail and with the forums.

  Also I see that you are charged twice per month.

  I would kindly ask you do support adobe touch for the same.

  Contact the customer service

  * Be sure to stay connected with your Adobe ID before accessing the link above *.

  Let us know if this helps!

• Backup planning app: dimensions, data, rules...

  Hi all, I am interested how can I easily save my planning application:
  -structure: dimensions, Member
  -data
  -rule files
  -Maybe something else (an opportunity then as well easy, fully restore my planning application)
  (use EMP 11.1.1.2)
  Thanks in advance

  Hello

  I wrote a blog on LCM earlier that can help you, you can have a reading of it here .

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• problems of ultra maxx charges with a power cord

  Sometimes my Maxx will begin charging when I plug, sometimes it requires a reboot before it will start to load. I tried a new power cord from Verizon and the results are the same. I got the phone because he is out, and the problem started a couple of weeks. Someone can offer some advice or should I go to? Any suggestion would be appreciated.

  By a new power cord do you mean just the cord or adapter as well? If only the power cord that I suggest that you try using a different card first thus.

  Also make sure you have the USB plug inserted at bottom. You don't want to lift or turn it on, but push to make sure that it is firmly in place.

  If this continues to happen that I would propose a factory data reset. Who will rule on software issues. If the FDR works advertising repair/replacement would be the next logical step. HTH

• Problem creating new channels charger after an election when ReplicationGroupAdmin or DbPing used

  This question relates to 5.0.84.  I have found no messages forward precisely the same problem here.

  My application uses I HA with replication on 4 nodes.  We tested different failure scenarios in which us network-isolate the master node.  We see survivors 3 replicas of an election, a master is determined, food chains are established and the overall replication group resumes its features.   We also tested the scenarios in which the master of the now 3-node replication-reduced group is isolated from the network in the same way.    The results generally worked, but were less reliable when the Group transitions from 3 to 2 knots.   We thought the quorum (replacement of likely to be elected group size) setting was the proper way to address this issue and had good results by manually setting the substitution of group likely to be elected to down size.

  We have set up a StateChangeListener and in its stateChange() method try to automate adjustment of the size of likely to be elected group override by calling DbPing getNodeState() (alternating) methods and ReplicationGroupAdmin for interview each of 4 nodes possible to see who was available and no INDIVIDUAL State.    However, it seems that DbPing or ReplicationGroupAdmin employment within our application to any node causes the implementation of feeder channels after an election of a new master failed (regardless of the number of survivors is likely to be elected nodes).    It seems rather ironic, or that the introduction be DbPing or ReplicationGroupAdmin in our application code introduces a principle of Heisenberg uncertainty effect in which tent to observe the number of active nodes causes the behavior of replication group, or more precisely - creating channel charger - for change.    Is there a prohibition against using DbPing, ReplicationGroupAdmin or getNodeState() in an application node methods likely to be elected?   Do same using these objects/methods in a cause of app monitor a change in behavior among the nodes to be elected after an election?    We seem to be observing such behavior.

  Thank you

  Ted

  Here's the log of je.info.0, of NŒUD01.  Initially, the NŒUD02 is the master.   17:57:55, we network-isolate NŒUD02.  We see an election is called, node01 wins and starts trying to establish the feeders but can't.

  130903 17:55:56:752 INFO [NŒUD01] began to ServiceDispatcher. HostPort = ap01.domain.acme .net: 13000

  current group 130903 size INFO [NŒUD01] 17:55:56:867: 4

  INFO [node01] existing 17:55:56:868 130903 node01 mark for a current master node.

  17:55:56:913 INFO [node01] node node01 130903 began

  17:55:56:914 130903 INFO [node01] committed election; choice #1

  130903 17:55:56:926 INFO [node01] Started election thread kills Sep 03 17:55:56 CDT 2013

  130903 changed NŒUD02 master INFO [node01] 17:56:29:308

  17:56:29:310 130903 INFO [node01] election is completed. Elapsed time: 32396ms

  17:56:29:310 INFO [NŒUD01] exit election after 5 attempts 130903

  130903 wire INFO [node01] election of 17:56:29:311 came out. Group master: node02 (64)

  130903 17:56:29:310 INFO [node01] Replica loop started with master: node02 (64)

  Departure from 130903 17:56:29:343 INFO [node01] Replica-power handshake

  Handshake 130903 17:56:29:536 INFO [node01] Replica-charger NŒUD02 completed.

  130903 17:56:29:553 INFO [node01] Replica-charger NŒUD02 syncup began. Replica range: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:56:29:650 INFO [node01] Rollback to matchpoint 843 393-0 x 33/0x2d38 status not = no active txns, nothing to restore

  17:56:29:651 130903 NŒUD02 start INFO [node01] VLSN Replica-feeder stream: 843 394

  130903 17:56:29:652 INFO [node01] Replica-charger NŒUD02 syncup completed. Elapsed time: 102ms

  Replica of INFORMATION [node01] 130903 17:56:29:658 initialization is complete. Replica VLSN: VLSN validation master Heartbeat 843 393: 843 393 delta VLSN: 0

  17:56:29:662 INFO [NŒUD01] 130903 joined group as a replica.  Join consistencyPolicy = PointConsistencyPolicy targetVLSN = 843, 393 first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:56:29:667 Replay INFO [node01] started thread. Message queue size: 1000

  130903 17:56:29:666 INFO [node01] refreshed 0 monitors.

  130903 17:56:30:939 WARNING [node01] likely to be elected changed size override group: 3

  130903 inactive channel INFO [NŒUD01] 17:57:54:860: node02 (64) forced close. Timeout: 7000ms.

  17:57:55:406 130903 INFO [NŒUD01] exit inner loop of the replica.

  130903 replica of the INFO [NŒUD01] 17:57:55:407 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:57:56:049 130903 INFO [node01] committed election; choice #2

  130903 17:57:56:050 INFO [node01] pending election. Waiting...

  130903 17:57:56:057 INFO [node01] Started election thread kills Sep 03 17:57:56 CDT 2013

  17:58:08:115 INFO [node01] 130903 master changed to node01

  17:58:08:116 130903 INFO [node01] election is completed. Elapsed time: 12067ms

  17:58:08:121 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:08:122 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:08:122 INFO [NŒUD01] exit election after 2 attempts 130903

  130903 wire INFO [node01] election of 17:58:08:123 came out. Group master: node01 (61)

  17:58:09:124 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:09:130 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:10:128 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:10:137 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:11:132 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  ...      The same message repeated ad nauseam...

  Here's the log of je.info.0 of NŒUD02 for the same period of time.   NŒUD02 begins as master, but this host becomes isolated from the network and its supply channels stops at 17:57:55:

  130903 17:56:26:861 INFO [NŒUD02] file chose lowest used for cleaning. fileChosen: 0x2f totalUtilization: 50 bestFileUtilization: 0 lnSizeCorrectionFactor: isProbe 0.55577517: false

  17:56:26:912 130903 INFO [NŒUD02] CleanerRun 1 ends on the probe file 0x2f = false invokedFromDaemon = true finished = true fileDeleted = false nEntriesRead = 1 nINsObsolete = 0 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nBINDeltasObsolete = 0 nBINDeltasCleaned = 0 nBINDeltasDead = 0 nBINDeltasMigrated = 0 nLNsObsolete = 0 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0 logSummary = < CleanerLogSummary endFileNumAtLastAdjustment = '0 x 33' initialAdjustments = '5' recentLNSizesAndCounts = "Horn : 1274201 / 3219 - is: 1494628 / 3219 Cor: 535 / 6-is: 965 / 11 Cor: 788 / 8-East: 1190 / Cor 13: 789 / 8-is: 1289/14 Horn: 714 / 2-is: 1310 / 9 Horn: 37694 / 611 - is: 178596 / 619 Horn: 168637 / 3961 - is: 1164331 / 3961 Cor: 62 / 1-is: 2286 / 21 Cor: 22130 / 1446 - is: 417561 / 1451 Horn: 2429020 / 9915 - is: 3837944 / 9915 "> inSummary = < totalINCount INSummary = '0' totalINSize = '0' totalBINDeltaCount = '0' totalBINDeltaSize = '0' obsoleteINCount = '0' obsoleteINSize = '0' obsoleteBINDeltaCount = '0' obsoleteBINDeltaSize = '0' / >» estFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > recalcFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > lnSizeCorrection = 0.55577517 newLnSizeCorrection = 0.55577517 estimatedUtilization = 0 correctedUtilization = 0 recalcUtilization = 0

  130903 17:56:26:973 INFO [NŒUD02] began to ServiceDispatcher. HostPort = ap02.domain.acme .net: 13000

  [17:56:26:992 130903 INFO [NŒUD02] Unknown Service request: Acceptor registered services:]

  current group 130903 size INFO [NŒUD02] 17:56:27:108: 4

  INFO [NŒUD02] existing 17:56:27:108 130903 NŒUD02 mark for a current master node.

  17:56:27:186 INFO [NŒUD02] node NŒUD02 130903 began

  17:56:27:186 130903 INFO [NŒUD02] committed election; choice #1

  130903 17:56:27:206 INFO [NŒUD02] Started election thread kills Sep 03 17:56:27 CDT 2013

  130903 17:56:29:290 INFO [NŒUD02] winning proposal: Proposal(00000140e6787717:0000000000000000000000000a000253:00000001) value: value: 10.0.2.83 13000. $ $$$ $$ NŒUD02$ $$ 64

  17:56:29:299 INFO [NŒUD02] master changed from NŒUD02 130903

  17:56:29:301 130903 INFO [NŒUD02] completed election. Elapsed time: 2114ms

  Manager of Feeder INFO [NŒUD02] 17:56:29:302 130903 accepts applications.

  17:56:29:309 130903 INFO [NŒUD02] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  Group INFO [NŒUD02] Joining 130903 17:56:29:312 as master

  130903 17:56:29:317 INFO [NŒUD02] refreshed 0 monitors.

  130903 wire INFO [NŒUD02] election of 17:56:29:318 came out. Group master: node02 (64)

  17:56:29:374 130903 Feeder INFO [NŒUD02] has accepted the java.nio.channels.SocketChannel connection [connected local=/10.0.2.83:13000 remote=/10.0.2.82:60052]

  Departure of handshake 17:56:29:477 INFO [NŒUD02] replica Feeder 130903

  Handshake 130903 17:56:29:539 INFO [NŒUD02] Feeder-replica completed node01.

  Syncup 17:56:29:542 130903 INFO [NŒUD02] Feeder-replica node01 began. Range of charger: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  17:56:29:654 130903 node01 start INFO [NŒUD02] replica Feeder to VLSN stream: 843 394

  130903 17:56:29:656 INFO [NŒUD02] Feeder-replica node01 syncup completed. Elapsed time: 113ms

  130903 17:56:29:660 Feeder INFO [NŒUD02] release thread for the replica node01 started at master VLSN 843 394 to 843 393 VLSN delta = - 1 = socket (node01 (61)) java.nio.channels.SocketChannel [remote=/10.0.2.82:60052 connected local=/10.0.2.83:13000]

  17:56:30:321 130903 Feeder INFO [NŒUD02] has accepted the java.nio.channels.SocketChannel connection [connected local=/10.0.2.83:13000 remote=/10.0.2.63:47920]

  Departure of handshake 17:56:30:326 INFO [NŒUD02] replica Feeder 130903

  Handshake 130903 17:56:30:349 INFO [NŒUD02] Feeder-replica completed node04.

  130903 17:56:30:350 INFO [NŒUD02] Feeder-replica node04 syncup began. Range of charger: first = 843, 326 last = 843, 395 sync = 843, txnEnd 395 = 843, 395

  17:56:30:363 130903 node04 start INFO [NŒUD02] replica Feeder to VLSN stream: 843 394

  130903 17:56:30:364 INFO [NŒUD02] Feeder-replica node04 syncup completed. Elapsed time: 14ms

  17:56:30:383 130903 Feeder INFO [NŒUD02] out of thread for the replica node04 started to master VLSN 843 394 to 843 395 delta VLSN = 1 socket = (node04 (62)) java.nio.channels.SocketChannel [remote=/10.0.2.63:47920 connected local=/10.0.2.83:13000]

  130903 17:56:31:678 likely to be elected [NŒUD02] WARNING group size changed override: 3

  17:57:21:200 130903 Feeder INFO [NŒUD02] has accepted the java.nio.channels.SocketChannel connection [connected local=/10.0.2.83:13000 remote=/10.0.2.84:38224]

  Departure of handshake 17:57:21:206 INFO [NŒUD02] replica Feeder 130903

  Handshake 130903 17:57:21:272 INFO [NŒUD02] Feeder-replica completed node03.

  130903 17:57:21:273 INFO [NŒUD02] Feeder-replica node03 syncup began. Range of charger: first = 843, 326 last = 843, 399 sync = 843, 399 = 843, 399 txnEnd

  17:57:21:389 130903 node03 start INFO [NŒUD02] replica Feeder to VLSN stream: 843 394

  130903 17:57:21:390 INFO [NŒUD02] Feeder-replica node03 syncup completed. Elapsed time: 117ms

  17:57:21:392 130903 Feeder INFO [NŒUD02] out of thread for the replica node03 started to master VLSN 843 394 to 843 399 delta VLSN = 5 socket = (node03 (63)) java.nio.channels.SocketChannel [remote=/10.0.2.84:38224 connected local=/10.0.2.83:13000]

  130903 inactive channel INFO [NŒUD02] 17:57:55:115: node01 (61) forced close. Timeout: 7000ms.

  130903 inactive channel INFO [NŒUD02] 17:57:55:115: node04 (62) forced close. Timeout: 7000ms.

  130903 17:57:55:116 INFO [NŒUD02] closing feeder for replica node01 reason: null write time: 2ms Avg write time: 98us

  130903 inactive channel INFO [NŒUD02] 17:57:55:125: node03 (63) forced close. Timeout: 7000ms.

  130903 17:57:55:126 INFO [NŒUD02] closing feeder for replica node04 reason: null write time: 3ms Avg write time: 147us

  130903 17:57:55:127 INFO [NŒUD02] closing feeder for replica node03 reason: null write time: 1ms Avg write time: 90us

  17:57:55:409 130903 Feeder INFO [NŒUD02] out to stop node01 replica. VLSN charger: 843 402 currentTxnEndVLSN: 843 401

  Out of the 17:57:55:410 130903 Feeder INFO [NŒUD02] judgment of the node03 replica. VLSN charger: 843 402 currentTxnEndVLSN: 843 401

  Out of the 17:57:55:411 130903 Feeder INFO [NŒUD02] judgment of the node04 replica. VLSN charger: 843 402 currentTxnEndVLSN: 843 401

  17:58:49:456 INFO [NŒUD02] master changed to node01 130903

  17:58:50:227 130903 Master INFO [NŒUD02] change: managing change. The ID of the master node: master group to node02 id (64): node01 (61)

  Block latch commit 17:58:50:228 130903 Releasing INFO [NŒUD02]

  130903 Feeder INFO [NŒUD02] 17:58:50:229 Manager is out. VLSN CurrentTxnEnd: 843 401

  17:58:50:230 INFO [NŒUD02] RepNode thread 130903 main stop.

  Shutdown 17:58:50:233 130903 INFO [NŒUD02] RepNode exception:

  (I 5.0.84) NŒUD02 (64): / data / NŒUD02 com.sleepycat.je.rep.stream.MasterStatus$ MasterSyncException: master the change. The ID of the master node: master group to node02 id (64): node01 (61) MASTER_TO_REPLICA_TRANSITION: this node was a master and must reset the internal State to become a replica. The application must close and reopen all the environment handles. The environment is not valid and must be closed.node02 (64) [MASTER]

  No feeders.

  GlobalCBVLSN = 843, 393

  Group info [RepGroup] 8e8b97b5-f9bc-4b9e-bb6e-56edfbe79674

  Version of the representation: 2

  Change version: 4

  Node for the max rep ID: 64

  Node: NŒUD02 ap02.domain.acme .net: 13000 (belongs) changeVersion:4 LocalCBVLSN:843, 393 to: kills Sep 03 17:56:31 CDT 2013

  Node: node03 ap03.domain.acme .net: 13000 (belongs) changeVersion:3 LocalCBVLSN:843, 393 to: kills Sep 03 17:57:21 CDT 2013

  Node: node01 ap01.domain.acme .net: 13000 (belongs) changeVersion:1 LocalCBVLSN:843, 393 to: kills Sep 03 17:56:29 CDT 2013

  Node: node04 ap04.domain.acme .net: 13000 (belongs) changeVersion:2 LocalCBVLSN:843, 393 to: kills Sep 03 17:56:30 CDT 2013

  vlsnRange = first = 843, 326 last = 843, 401 sync = 843, txnEnd 401 = 843, 401

  lastReplayedTxn = null lastReplayedVLSN = 843, 393 numActiveReplayTxns = 0

  130903 17:58:50:234 INFO [NŒUD02] stop the node node02 (64)

  INFO [NŒUD02] elections stop 130903 17:58:50:235 triggered

  INFO [NŒUD02] elections stop 130903 17:58:50:238 finished

  130903 17:58:50:239 RepNode INFO [NŒUD02] main thread: MASTER node02 (64) was released.

  17:58:50:240 130903 INFO [NŒUD02] ServiceDispatcher stop starting. [HostPort = ap02.domain.acme .net: 13000 registered services:]

  Stop INFO [NŒUD02] ServiceDispatcher 17:58:50:243 130903 done. HostPort = ap02.domain.acme .net: 13000

  Stop 17:58:50:243 INFO [NŒUD02] node02 130903 (64) finished.

  Here's the log of node03.  We see node01 wins the election, but

  17:57:20:961 130903 INFO [node03] CleanerRun 1 ends on the probe file 0x2f = false invokedFromDaemon = true finished = true fileDeleted = false nEntriesRead = 1 nINsObsolete = 0 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nBINDeltasObsolete = 0 nBINDeltasCleaned = 0 nBINDeltasDead = 0 nBINDeltasMigrated = 0 nLNsObsolete = 0 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0 logSummary = < CleanerLogSummary endFileNumAtLastAdjustment = '0 x 32' initialAdjustments = '5' recentLNSizesAndCounts = "Horn : 1274201 / 3219 - is: 1494628 / 3219 Cor: 535 / 6-is: 965 / 11 Cor: 788 / 8-East: 1190 / Cor 13: 789 / 8-is: 1289/14 Horn: 714 / 2-is: 1310 / 9 Horn: 37694 / 611 - is: 178596 / 619 Horn: 168637 / 3961 - is: 1164331 / 3961 Cor: 62 / 1-is: 2286 / 21 Cor: 22130 / 1446 - is: 417561 / 1451 Horn: 2429020 / 9915 - is: 3837944 / 9915 "> inSummary = < totalINCount INSummary = '0' totalINSize = '0' totalBINDeltaCount = '0' totalBINDeltaSize = '0' obsoleteINCount = '0' obsoleteINSize = '0' obsoleteBINDeltaCount = '0' obsoleteBINDeltaSize = '0' / >» estFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > recalcFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > lnSizeCorrection = 0.55577517 newLnSizeCorrection = 0.55577517 estimatedUtilization = 0 correctedUtilization = 0 recalcUtilization = 0

  130903 17:57:20:991 INFO [node03] began to ServiceDispatcher. HostPort = ap03.domain.acme .net: 13000

  current group 130903 size INFO [node03] 17:57:21:111: 4

  INFO [node03] existing 17:57:21:112 130903 node03 mark for a current master node.

  17:57:21:155 130903 INFO [node03] master changed from NŒUD02

  17:57:21:182 INFO [node03] node node03 130903 began

  130903 17:57:21:183 INFO [node03] Replica loop started with master: node02 (64)

  Departure from 17:57:21:205 130903 INFO [node03] Replica-power handshake

  Handshake 130903 17:57:21:269 INFO [node03] Replica-charger NŒUD02 completed.

  Syncup of NŒUD02 17:57:21:282 130903 INFO [node03] Replica-power began. Replica range: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:57:21:385 INFO [node03] Rollback to matchpoint 843 393-0 x 32/0x55da status not = no active txns, nothing to restore

  17:57:21:386 130903 NŒUD02 start INFO [node03] Replica-feeder VLSN stream: 843 394

  130903 17:57:21:387 INFO [node03] Replica-charger NŒUD02 syncup completed. Elapsed time: 105ms

  Replica of the INFO [node03] 130903 17:57:21:391 initialization is complete. Replica VLSN: VLSN validation master Heartbeat 843 393: 843 399 delta VLSN: 6

  130903 17:57:21:396 Replay INFO [node03] thread started. Message queue size: 1000

  17:57:21:417 INFO [node03] 130903 joined group as a replica.  Join consistencyPolicy = PointConsistencyPolicy targetVLSN = 843, 399 first = 843, 326 last = 843, 399 sync = 843, 399 = 843, 399 txnEnd

  130903 17:57:21:421 INFO [node03] refreshed 0 monitors.

  130903 inactive channel INFO [node03] 17:57:55:069: node02 (64) forced close. Timeout: 7000ms.

  17:57:55:406 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:57:55:407 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:57:56:059 130903 INFO [node03] committed election; choice #1

  130903 17:57:56:068 INFO [node03] Started election thread kills Sep 03 17:57:56 CDT 2013

  130903 17:58:08:101 INFO [node03] winning proposal: Proposal(00000140e679d235:0000000000000000000000000a000254:00000001) value: value: 10.0.2.82 13000. $ $$$ $$ NŒUD01$ $$ 61

  17:58:08:108 130903 INFO [node03] master changed to node01

  17:58:08:112 130903 INFO [node03] completed election. Elapsed time: 12053ms

  130903 17:58:08:113 INFO [node03] Replica loop started with master: node01 (61)

  17:58:08:124 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:08:125 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:08:126 INFO [node03] try again #: 0/10 retries loop replica after 1000ms.

  130903 17:58:09:127 INFO [node03] Replica loop started with master: node01 (61)

  17:58:09:131 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:09:131 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:09:132 INFO [node03] try again #: 1/10 retries loop replica after 1000ms.

  130903 17:58:10:133 INFO [node03] Replica loop started with master: node01 (61)

  17:58:10:138 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:10:138 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:10:139 INFO [node03] try again #: 2/10 retries loop replica after 1000ms.

  130903 17:58:11:139 INFO [node03] Replica loop started with master: node01 (61)

  17:58:11:142 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:11:142 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:11:143 INFO [node03] try again #: 3/10 retries loop replica after 1000ms.

  130903 17:58:12:144 INFO [node03] Replica loop started with master: node01 (61)

  17:58:12:146 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:12:147 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:12:147 INFO [node03] try again #: 4/10 retries loop replica after 1000ms.

  130903 17:58:13:148 INFO [node03] Replica loop started with master: node01 (61)

  17:58:13:162 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:13:222 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:13:222 INFO [node03] try again #: 5/10 retries loop replica after 1000ms.

  130903 17:58:14:223 INFO [node03] Replica loop started with master: node01 (61)

  17:58:14:225 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:14:226 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:14:226 INFO [node03] try again #: 6/10 retries loop replica after 1000ms.

  130903 17:58:15:227 INFO [node03] Replica loop started with master: node01 (61)

  17:58:15:229 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:15:230 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:15:230 INFO [node03] try again #: 7/10 retries loop replica after 1000ms.

  130903 17:58:16:231 INFO [node03] Replica loop started with master: node01 (61)

  17:58:16:233 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:16:234 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:16:234 INFO [node03] try again #: 8/10 retries loop replica after 1000ms.

  130903 17:58:17:235 INFO [node03] Replica loop started with master: node01 (61)

  17:58:17:237 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:17:238 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:17:238 INFO [node03] try again #: 9/10 retries loop replica after 1000ms.

  130903 wire INFO [node03] election of 17:58:18:112 came out. Group master: node01 (61)

  130903 17:58:18:239 INFO [node03] Replica loop started with master: node01 (61)

  17:58:18:280 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:18:280 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:58:18:281 130903 INFO [node03] could not recover from exception: failed after attempts: 10 with retry interval: 1000ms., despite 10 attempts.

  com.sleepycat.je.rep.impl.node.Replica$ ConnectRetryException: failed after attempts: 10 with retry interval: 1000ms.

  at com.sleepycat.je.rep.impl.node.Replica.createReplicaFeederChannel(Replica.java:777)

  at com.sleepycat.je.rep.impl.node.Replica.initReplicaLoop(Replica.java:578)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoopInternal(Replica.java:392)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoop(Replica.java:328)

  at com.sleepycat.je.rep.impl.node.RepNode.run(RepNode.java:1402)

  17:58:18:282 130903 INFO [node03] committed election; choice #2

  130903 17:58:18:282 INFO [node03] in the current election. Waiting...

  .... Attempts and the ConnectRetryException repeat ad nauseam...

  We see a similar trend in the node04 newspaper.  We observe on 17:58:08:101 node01 became master, but we are unable to establish a connection to power supply to:

  130903 17:55:48:149 INFO [node04] began to ServiceDispatcher. HostPort = ap04.domain.acme .net: 13000

  current group 130903 size INFO [node04] 17:55:48:230: 4

  130903 17:55:48:231 INFO [node04 Existing node04 mark for a current master node.

  17:55:48:258 INFO [node04] node node04 130903 began

  17:55:48:259 130903 INFO [node04] committed election; choice #1

  130903 17:55:48:266 INFO [node04] Started election thread kills Sep 03 17:55:48 PDT 17:56:29:300 2013130903 Master INFO [node04] changed to NŒUD02

  17:56:29:301 130903 INFO [node04] completed election. Elapsed time: 41043ms

  130903 17:56:29:301 INFO [node04] Replica loop started with master: NŒUD02 (64) 130903 17:56:29:303 INFO [node04] out election after 5 retries130903 17:56:29:304 wire INFO [node04] election came out. Group master: NŒUD02 (6

  4)

  17:56:29:309 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:56:29:310 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:56:29:310 INFO [node04] try again #: 0/10 retries loop replica after 10

  00ms.130903 17:56:30:310 INFO [node04] Replica loop started with master: node02 (64)

  Departure from 17:56:30:324 130903 INFO [node04] Replica-power handshake

  Handshake 130903 17:56:30:348 INFO [node04] Replica-charger NŒUD02 completed.

  Syncup of NŒUD02 17:56:30:352 130903 INFO [node04] Replica-power began. Replica range: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:56:30:361 INFO [node04] Rollback to matchpoint 843 393-0 x 34 / 0 x 1628

  status = no active txns, nothing to restore

  17:56:30:362 130903 NŒUD02 start INFO [node04] Replica-feeder VLSN stream: 843 394

  130903 17:56:30:362 INFO [node04] Replica-charger NŒUD02 syncup completed. Elapsed time: 10 ms

  Replica of the INFO [node04] 130903 17:56:30:382 initialization is complete. Replica VLSN: VLSN validation master 843 393: 843 395 delta VLSN: 2 Heartbeat

  130903 17:56:30:386 Replay INFO [node04] thread started. Message queue size: 1000

  17:56:30:397 INFO [node04] 130903 joined group as a replica.  Join consistencyPolicy = PointConsistencyPolicy targetVLSN = 843 395 first = 843, 326 last = 843, 395 sync = 843, txnEnd 395 = 843, 395

  130903 17:56:30:401 INFO [node04] refreshed 0 monitors.

  130903 17:56:30:922 WARNING [node04] likely to be elected changed size override group: 3

  130903 inactive channel INFO [node04] 17:57:55:223: node02 (64) forced close. Timeout: 7000ms.

  17:57:55:398 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:57:55:399 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:57:55:401 130903 INFO [node04] committed election; choice #2

  130903 17:57:55:401 INFO [node04] in the current election. Waiting...

  130903 17:57:55:406 INFO [node04] Started election thread kills Sep 03 17:57:55 CDT 2013

  17:58:08:101 130903 INFO [node04] master changed to node01

  17:58:08:102 130903 INFO [node04] completed election. Elapsed time: 12701ms

  17:58:08:102 INFO [node04] 130903 exit election after 2 attempts

  130903 17:58:08:102 INFO [node04] Replica loop started with master: node01 (61)

  130903 wire INFO [node04] election of 17:58:08:103 came out. Group master: node01 (61)

  17:58:08:110 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:08:110 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:08:111 INFO [node04] try again #: 0/10 retries loop replica after 1000ms.

  130903 17:58:09:111 INFO [node04] Replica loop started with master: node01 (61)

  17:58:09:114 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:09:114 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:09:114 INFO [node04] try again #: 1/10 retries loop replica after 1000ms.

  130903 17:58:10:115 INFO [node04] Replica loop started with master: node01 (61)

  17:58:10:117 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:10:118 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:10:118 INFO [node04] try again #: 2/10 retries loop replica after 1000ms.

  130903 17:58:11:118 INFO [node04] Replica loop started with master: node01 (61)

  17:58:11:121 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:11:121 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:11:122 INFO [node04] try again #: 3/10 retries loop replica after 1000ms.

  130903 17:58:12:122 INFO [node04] Replica loop started with master: node01 (61)

  17:58:12:125 INFO [node04] 130903 exit inner loop of the replica.

  130903 17:58:12:125 INFO [node04] try again #: 4/10 retries loop replica after 1000ms.

  130903 17:58:13:126 INFO [node04] Replica loop started with master: node01 (61)

  17:58:13:129 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:13:129 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:13:129 INFO [node04] try again #: 5/10 retries loop replica after 1000ms.

  130903 17:58:14:130 INFO [node04] Replica loop started with master: node01 (61)

  17:58:14:132 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:14:133 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:14:133 INFO [node04] try again #: 6/10 retries loop replica after 1000ms.

  130903 17:58:15:133 INFO [node04] Replica loop started with master: node01 (61)

  17:58:15:136 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:15:136 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:15:137 INFO [node04] try again #: 7/10 retries loop replica after 1000ms.

  130903 17:58:16:137 INFO [node04] Replica loop started with master: node01 (61)

  17:58:16:140 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:16:140 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:16:140 INFO [node04] try again #: 8/10 retries loop replica after 1000ms.

  130903 17:58:17:141 INFO [node04] Replica loop started with master: node01 (61)

  17:58:17:143 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:17:144 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:17:144 INFO [node04] try again #: 9/10 retries loop replica after 1000ms.

  130903 17:58:18:145 INFO [node04] Replica loop started with master: node01 (61)

  17:58:18:147 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:18:148 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:58:18:148 130903 INFO [node04] could not recover from exception: failed after attempts: 10 with retry interval: 1000ms., despite 10 attempts.

  com.sleepycat.je.rep.impl.node.Replica$ ConnectRetryException: failed after attempts: 10 with retry interval: 1000ms.

  at com.sleepycat.je.rep.impl.node.Replica.createReplicaFeederChannel(Replica.java:777)

  at com.sleepycat.je.rep.impl.node.Replica.initReplicaLoop(Replica.java:578)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoopInternal(Replica.java:392)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoop(Replica.java:328)

  at com.sleepycat.je.rep.impl.node.RepNode.run(RepNode.java:1402)

  17:58:18:149 130903 INFO [node04] committed election; choice #3

  130903 17:58:18:149 INFO [node04] in the current election. Waiting...

  130903 17:58:18:150 INFO [node04] Started election thread kills Sep 03 17:58:18 CDT 2013

  .... Attempts and the ConnectRetryException repeat ad nauseam...

  The problem is that you touch a model not supported by violating the contract of the StateChangeListener by launching an expensive operation in the middle of the stateChange method. Of http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/StateChangeListener.html#stateChange (com.sleepycat.je.rep.StateChangeEvent), we caution:

  void stateChange(StateChangeEvent stateChangeEvent) throws RuntimeException
  

  ....

  This method should do the minimum amount of work, queuing any intensive operations of resource for processing by another thread before returning to appellant, so that it does not unduly delay the other cleaning operations performed by the internal thread that calls this method.

  In other words, we really mean the work done by stateChange shouldn't make any IO or network communication, and if he does, he should leave this thread back, and do the expensive work in another thread.

  It seems rather ironic, or that the introduction be DbPing or ReplicationGroupAdmin in our application code introduces a principle of Heisenberg uncertainty effect in which tent to observe the number of active nodes causes the behavior of replication group, or more precisely - creating channel charger - for change.    Is there a prohibition against using DbPing, ReplicationGroupAdmin or getNodeState() in an application node methods likely to be elected?   Do same using these objects/methods in a cause of app monitor a change in behavior among the nodes to be elected after an election?    We seem to be observing such behavior.

  While an application can certainly use DbPing or ReplicationGroupAdmin, the problem is that the state change listener runs in the critical path the replication group state changes. You talked about monitors and another model of watch and manage the replication group membership is to use http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/monitor/Monitor.html. This class and the MonitorStateChangeListener partner, run outside the ReplicatedEnvironment and could be another means of implementation of the application logic.

  So in summary, you should use com.sleepycat.je.rep.monitor.monitor * to implement your logic, or have the implementation of StateChangeListener cause another thread to perform work asynchronously, so that stateChange() can quickly return.

  Please let me know if it helps.

  Thank you

  Bogdan

• Problem loading data for Planning Server through ODI

  Hi all
  
  I am facing problem while loading data for Planning Server through ODI.
  I created the interface with flat as a source of data as file below
  
  Location data load Cube name POV cost per seat
  Ctbn_PnL of Tidel Equifax, Budget, Working_2010, FY10, Wk1, Local 333
  Ctbn_PnL of Tidel Equifax, Budget, Working_2010, FY10, Wk2, Local 444
  Ctbn_PnL of Tidel Equifax, Budget, Working_2010, FY10, Wk3, 555 Local
  Ctbn_PnL of Tidel Equifax, Budget, Working_2010, FY10, Wk4, Local 666
  Budget, Working_2010, FY10, Wk5, Tidel Equifax, Local 777 Ctbn_PnL
  Ctbn_PnL of Tidel Equifax, Budget, Working_2010, FY10, Wk6, Local 888
  Budget, Working_2010, FY10, Wk1, PADI Ctbn_PnL Equifax, Local 222
  Budget, Working_2010, FY10, Wk2, PADI Ctbn_PnL Equifax, Local 111
  Budget, Working_2010, FY10, Wk3, PADI Ctbn_PnL Equifax, room 345
  Budget, Working_2010, FY10, Wk4, PADI Ctbn_PnL Equifax, Local 346
  Budget, Working_2010, FY10, Wk5, PADI Ctbn_PnL Equifax, Local 347
  Budget, Working_2010, FY10, Wk6, PADI Ctbn_PnL Equifax, Local 349
  
  And the target as an application of Planinng. Interface has been properly executed, but are not filled with data in the form of Plannning or Essbase.
  I obtained the information in the log file after running the interface:
  
  2010-05-20 18:45:38, 409 [DwgCmdExecutionThread:null:5] INFO: Oracle Data Integrator adapter for Hyperion Planning - free 9.3.1.1
  2010-05-20 18:45:38, 409 INFO [DwgCmdExecutionThread:null:5]: connection for application [PnL_ODI] [chnveltss03]: [11333] using [admin] username.
  2010-05-20 18:45:39, 800 [DwgCmdExecutionThread:null:5] INFO: successfully connected to the planning application.
  2010-05-20 18:45:39, 800 INFO [DwgCmdExecutionThread:null:5]: loading for the charge of planning options
  Name of the dimension: location like Parent child: false
  Order By entry charge: forgery
  Update the database: true
  2010-05-20 18:45:39, 815 INFO [DwgCmdExecutionThread:null:5]: beginning of the loading process.
  2010-05-20 18:45:39, 815 DEBUG [DwgCmdExecutionThread:null:5]: number of columns in the result set of source does not match the number of columns planning targets.
  2010-05-20 18:45:39, 831 [DwgCmdExecutionThread:null:5] INFO: type of load is a [member of the load dimension].
  2010-05-20 18:45:39, 831 [DwgCmdExecutionThread:null:5] ERROR: file [[Tidel, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 831 [DwgCmdExecutionThread:null:5] ERROR: file [[Tidel, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 847 [DwgCmdExecutionThread:null:5] ERROR: file [[Tidel, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 847 [DwgCmdExecutionThread:null:5] ERROR: file [[Tidel, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 847 [DwgCmdExecutionThread:null:5] ERROR: file [[Tidel, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 847 [DwgCmdExecutionThread:null:5] ERROR: file [[Tidel, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 847 [DwgCmdExecutionThread:null:5] ERROR: file [[Padi, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 862 ERROR [DwgCmdExecutionThread:null:5]: file [[Padi, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 862 ERROR [DwgCmdExecutionThread:null:5]: file [[Padi, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 862 ERROR [DwgCmdExecutionThread:null:5]: file [[Padi, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 862 ERROR [DwgCmdExecutionThread:null:5]: file [[Padi, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 862 ERROR [DwgCmdExecutionThread:null:5]: file [[Padi, null, null, null, null, null, null, null, null, null, null, null, Ctbn_PnL, Budget, null, "Equifax, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 878 [DwgCmdExecutionThread:null:5] ERROR: Record [[null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null]] has been rejected by Planning Server.
  2010-05-20 18:45:39, 878 [DwgCmdExecutionThread:null:5] INFO: planing cube refresh initiated.
  2010-05-20 18:45:44, 284 INFO [DwgCmdExecutionThread:null:5]: planning of the cube refresh operation completed successfully.
  2010-05-20 18:45:44, 284 INFO [DwgCmdExecutionThread:null:5]: load the process is complete.
  
  
  Please help me in this grace,
  Srinivas

  You are right. The table that you have described is in the format 'Generation' (the highest to the lowest level of the hierarchy). The KM of planning requires data to load in format "Parent/child". You must create multiple interfaces (one for each pair of generation) or use a view to make the transformation.

  While a view seems to be the easier choice, note that ODI will not be able to perform any analysis of lineage of data on the integration process.

  Hope this helps,
  Matt

• Problem of Business rule

  Hello
  
  We are facing a particular problem. Our form of data are created in such a way that once saved the business rule attached to this form runs. IE run save option.
  but it does not work
  
  Simo

  Simon,

  1. I've seen on 11.1.1.1 and 64 bit, when we tried to save it saves but running the attached matching rule.

  2 oracle too had confirmed that his problem from version 11.1.1.1.

  3. it happens that after restarting services planning.

  4. the work around is to open the business in your service console Regional rule and he re-record.

  Sandeep Reddy, Enti
  HCC
  http://hyperionconsutlancy.com/

• Generation of mapping error when you use a data rule

  I hope someone can point me in the right direction on this one. I looked everywhere but could not find a similar problem anywhere.
  
  It is customer 10.2.0.1.31 OWB and 10.2.0.1.0 repository in a 10g database SE. I have a table on which I defined a data policy, which is deployed in the database as well as its corresponding error table. The rule I used is the integrated IS_DATE, and it is applied to a VARCHAR2 field that will store a date in a specific format. I set the table as an operator in a map and set data IS_DATE rule action to PASS to the ERROR. When I try to deploy the mapping I get the following errors in the log:
  
  WARNING-ORA-06550: line 244, column 4:
  PL/SQL: ORA-00907: lack the right parenthesis
  
  WARNING-ORA-06550: line 221, column 3:
  PL/SQL: SQL statement ignored
  
  WARNING-ORA-06550: line 3112, 132 column:
  PLS-00103: encountered the symbol "DD" when expecting one of the following conditions:
  
  . ( ) , * @ % & | = - + <>/ mod rest isn't
  rem range = >... < a superscript (*) > <>or! = or ~ = > = < = <>
  and as between LIKE2_ LIKE4_ LIKEC_ | Member of type multiset
  SUBMULTISET_
  The symbol "." was replaced by "DD" continue.
  
  
  When I look at the generated code, there are lines like this:
  
  not (wb_to_date ("table". ""»(, mois dd, RRRR, Mon dd, RRRR RRRR-MM-JJ, MM/DD/RRRR, AAAA-MM-JJ, AAAA/MM/JJ) column is not null "
  
  Why OWB is not to put single quotes around the rule of data data formats integrated? Is there something fundamental that miss me in my warehouse model?

  Hello

  It's bug 5195315, which seems to be fixed in a patch 10.2. If you can pick up the latest patch 10.2 worth 3 years of corrections of a value pick.

  See you soon
  David

• connection problem of data with the support of mobistar (Belgium)

  WiFi works. Data connection isn't.

  The signal 'H' or 'E' is highlighted. I tried with the parameters of android and iphone Mobistar Belgium Web site and with all types of authentication. But it is impossible to connect.

  I will try with a sim card from another carrier and let you know.

  In the meantime, does anyone know if there are any specific APN settings for mobistar.be?

  Hi yellowtrolley,

  Thank you for reporting this issue. Please try the following to the APN settings I found on this site nd make sure your specific device supports the following frequencies:

  • GSM 900/1800 (2G GSM) net
  • W CDMA 2100 (3 G UMTS)

  The APN settings:

  • username: mobistar
  • password: mobistar
  • Name of the APN: web.pro.be

  You can also try this page if you need more specific parameters.

  Please let us know if this solves your problem, or if you have other questions about your Firefox OS device.

  Thank you!! =)

  -Ralph

• Problems sending data between the computer and the emulator.

  I can't send anything to the Calculator Emulator. Does not appear in the Send button calculator. In the emulator, it seems that send key as soon as I connect with the calculator and can send data to it. There is command of testicles that EU can do to make sure that a machine works, for example, the USB driver?

  In fact, including updates, firmware:

  application version: 20140702v6031

  operating system version: V 0.032.6030

  version of the program: 201472 (6031)

  most: the calculator, I received yesterday, day 1. and I doesn't seem to work well. There is a channel for guaranteed support, you can contact?

  Recognizing

  Davi

  Friends:

  Thank you very much. The problem has been resolved. As soon as I saw the kit, 3 updates were made and the machine works normally.

  Thank you

  Davi