2 Replies Latest reply: Oct 7, 2012 5:52 PM by user10657233 RSS

    Cause for TT8112: Operation not permitted. Master Catchup not complete.

    user10657233
      We have two Solaris machines (Host1 and Host2) with TimesTen Release 7.0.3.1.0 installed. We have created a "Transmit Nondurable" replication scheme like below.

      Replication Scheme R1:

      Element: E1
      Type: Datastore
      Master Store: PRIMARY on Host1 Transmit Nondurable
      Subscriber Store: SECONDARY on Host2

      Excluded Tables:
      None
      Excluded Cache Groups:
      None
      Excluded sequences:
      None

      Element: E2
      Type: Datastore
      Master Store: SECONDARY on Host2 Transmit Nondurable
      Subscriber Store: PRIMARY on Host1
      Excluded Tables:
      None
      Excluded Cache Groups:
      None
      Excluded sequences:
      None

      Store: PRIMARY on Host1
      Port: 45678
      Log Fail Threshold: (none)
      Retry Timeout: 60 seconds
      Compress Traffic: Disabled

      Store: SECONDARY on Host2
      Port: 45678
      Log Fail Threshold: (none)
      Retry Timeout: 60 seconds
      Compress Traffic: Disabled

      Both the datastores have LogBuffSize=512000 and LogFileSize=500. We took Host2 down for hardware maintenance with the expectation that Host1 Timesten will handle all the database operations. After few hours, timesten on Host1 started throwing "[TimesTen][TimesTen 7.0.3.1.0 ODBC Driver][TimesTen]TT8112: Operation not permitted. Master Catchup not complete. -- file "table.c", lineno 31044, procedure "sbLRReplKeyLW"" for any insert/delete/update operation. We did not see 100% utilitization of any disks where TimesTen data and logs are stored.

      Can somebody let us know when this error will be thrown by TimesTen? What is the trigger criteria for this error?

      Edited by: user10657233 on Sep 26, 2012 2:00 PM