Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2269491.1
Update Date:2017-06-12
Keywords:
Solution Type  Problem Resolution Sure

Solution  2269491.1 :   LSMSSEC Slave Threads Stopped  

Related Items 
    

  • Oracle Communications EAGLE (Software)
    •  
Related Categories 
    

  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec OS ELAP LSMS
    •  






In this Document


Symptoms


Changes


Cause


Solution



Created from <SR 3-14895122771>


Applies to:  

Oracle Communications EAGLE (Software) - Version LSMS 12.0 and later
Tekelec



Symptoms


LSMSEC Slave threads stopped



Changes


 


Cause


The log file "dbreplMon.log" show:



Sat May 13 18:01:00 2017 All tests passed on STANDBY
Sat May 13 18:02:06 2017 All tests passed on STANDBY
Sat May 13 18:03:12 2017 All tests passed on STANDBY
Sat May 13 18:04:18 2017 All tests passed on STANDBY
Sat May 13 18:05:25 2017 All tests passed on STANDBY
Sat May 13 18:06:29 2017 Error: Slave threads are not running!
Sat May 13 18:06:29 2017 Error: Replication not checked...
Sat May 13 18:06:29 2017 Error: EVENT: LSMS_EVENT_DB_ERR ACTION: SET MSG: Slave threads stopped


It is observed the Secondary bin logs are out of sync.


Solution


Perform the following steps to restart node on Secondary server:-


    

  1. Pre-activity

      

    1. Verify current status LSMSPRI and LSMSSEC:
      

      hastatus
      

      2. 

    2. Sanity check for Primary and Standby server:

        

      1. syscheck
        2. 

      2. sentry status
        3. 

      3. logs;date
        4. 

      4. ls -ltr */*Tran*<mmdd>
        5. 

      

      3. 

    3. Verify and disable lsms backup:
      

      ps -ef |grep lsmsbkp
      

      4. 

    4. Update the "/etc/cron.d/lsmsbkp.cron" to comment out the 'lsmsbkp' line
      5. 

    

    2. 

  2. Stop Provisiong on LSMSPRI:
    

      

    1. Login to lsmspri server.
      2. 

    2. Stop all npac agents. (eg. lsms stop WestCoast)
      3. 

    3. Stop all EMS agents. (eg. eagle stop <clli>)
      4. 

    

    3. 

  3. Perform the Restart Node on LSMSSEC.

      

    1. Login to lsmssec server.
      2. 

    2. start screen session.
      3. 

    3. su - lsmsmgr
      4. 

    4. restart node (ei. Maintenance-> Stop/Start Node)
      The Start Node process may take hours to complete depending on database size. It copies the database from the Active server to Standby.
      5. 

    5. Wait till start node completed before moving to next step.
      6. 

    

    4. 

  4. Post-activity:

      

    1. Login to lsmspri server.
      2. 

    2. Start all EMS agents. (eg. eagle start <clli>)
      3. 

    3. Start all npac agents. (eg. lsms start WestCoast)
      4. 

    4. Enable lsms backup. (update the "/etc/cron.d/lsmsbkp.cron" to un-comment the 'lsmsbkp' line)
      5. 

    5. Sanity check for Primary and Standby server:

        

      1. syscheck
        2. 

      2. sentry status
        3. 

      3. logs;date
        4. 

      4. ls -ltr */*Tran*<mmdd>
        5. 

      

      6. 

    

    5. 




Attachments

This solution has no attachment


















       

Copyright © 2018 Oracle, Inc.  All rights reserved.

 Feedback