cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

New users cannot make calls due to discrepancies between TimesTen Data Authority Server (TTDAS) instances

745
Views
0
Helpful
0
Comments

Core Issue

Broken replication between two TTDAS instances can result in discrepancies between the databases. These are some of the symptoms in this situation:

  • This is a sample of replication errors taken from TTMON log file: 

    Wed Nov 02 13:29:50 2005 CRITICAL SqlError: Error message is [Error occurred in file: PreparedStatement.cpp line:156 user Info:Error in exec statement rc:SQL_ERROR

    Errmsg#:1 sqlstate:S1000 nativeErrorCode:994 MsgText:[TimesTen][TimesTen 5.0.30 ODBC Driver][TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3037, procedure "sb_xactBeginQ()"

    Errmsg#:2 sqlstate:08001 nativeErrorCode:798 MsgText:[TimesTen][TimesTen 5.0.30 ODBC Driver][TimesTen]TT0798: Daemon reports error -102 -- file "db.c", lineno 12127, procedure "sbDbAppExit()"

    Wed Nov 02 13:29:50 2005 CRITICAL DAAPIX_Error::handleErrors() - DAAPIX Data System error; err level <_70>; native err <_798>

    Wed Nov 02 13:29:50 2005 CRITICAL DAAPIX_Error::handleErrors() - TT DB Config/Fatal Error - transition to DISABLED: should shutdown

    Wed Nov 02 13:29:50 2005 CRITICAL <_101>:<_70>:<_798>: : executeX() encountered Database error

    Wed Nov 02 13:29:50 2005 INFO Name: dsServerX731StatusDisabled, dsOAMTrapsPath: /xxx/xxx/TTMON_POPNAME_1

    Wed Nov 02 13:29:50 2005 INFO Name: dsDAAPIXBasicTrapsDBFatalError, dsDAAPIXBasicTrapsMessage: DAAPIX_Error::handleErrors() - DAAPIX Data System error; err level <_70>; native err <_798>

    , dsOAMTrapsPath: /xxx/xxx/TTMON_POPNAME_1

    Wed Nov 02 13:29:50 2005 ERROR DAAPIX_Exception caught in dsTTMON_CompactTask; code = <_101>, reason = <_101>:<_70>:<_798>: : executeX() encountered Database error

    Wed Nov 02 13:29:50 2005 CRITICAL xcheck failed: (rc==SQL_SUCCESS), file Connection.cpp, line 38

  • The ttmon.log might show replication lag that is other than zero, as shown:

    ++++++ REPLICATION STATISTICS ++++++

    Daemon Status: UP

    Replication State: START

    Replication Lag: 162

  • The sonic D.HARD.POP1.DE queue shows an increasing number of hard state messages. For example, adding a new subscriber.

Resolution

Interface issues can cause connectivity and replication issues between TT databases. To determine interface issues, issue the netstat -ni command on UNIX Command Line Interface (CLI).

An interface with an increasing number of errors under the "Ierrs" column can result in connectivity and replications issues. This is an example:

dsuser$ netstat -ni

Name  Mtu  Net/Dest  Address  Ipkts  Ierrs Opkts  Oerrs Collis Queue
lo0  8232 127.0.0.0  127.0.0.1  502922895 0  502922895 0  0  0 

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards