TSC / CCS / MCS

Test - Integrate - Control

Drop Database

In TSC it’s possible to completely drop the current MIB database without restarting the system! This is quite an advanced feature; you could use it if you find that there is a fairly big error throughout your database that cannot be handled by online patches.

Dropping the MIB completely cannot be done while data is arriving and being processed. If you drop the database, the following happen:
  • the current plugin is disconnected, so that no TM is arriving
  • all current test sequences are suspended, so that TC sending has to stop
  • the current MIB is deallocated
To restart, all you have to do is connect again, and resume the suspended test sequences. On connection the new DB is loaded. Test sequences only resume when you tell them to.

The whole cycle can be done within a few seconds!
In TSC it’s possible to completely drop the current MIB database without restarting the system! This is quite an advanced feature; you could use it if you find that there is a fairly big error throughout your database that cannot be handled by database patches.

Dropping the MIB completely cannot be done while data is arriving and being processed, or while test sequences are actively sending telecommands. These need a database to be loaded. But if we stop the TM shortly, and suspend test sequences, we can carry on with a new database after reconnecting.

If you drop the database, the following happen:
  • the current plugin is disconnected, so that no TM is arriving
  • all current test sequences are suspended, so that TC sending has to stop
  • the current MIB is deallocated
To restart, all you have to do is connect again, and resume the suspended test sequences.

What happens to my current packet and TM parameter subscriptions in test sequences?

If the new database still contains the same TM parameter name, or the same TM packet SPID, then when the test sequence resumes, it will continue to get the (maybe updated) parameters or packets. If the TM parameter or packet definition no longer exist, then the test sequences will not receive their subscribed updates, and possibly waitfor statements will time out - if a timeout was specified.

If you continue to send TC by name, then the new definition will be used. Of course, if test sequences use a TC or TC parameter that no longer exists, they will receive an error.