Troubleshooting guide

14 — As required maintenance tasks
Alcatel-Lucent 5620 Service Aware Manager 14-43
5620 SAM
System Administrator Guide
6 Close the console window when the reinstantiation is complete.
7 Open a 5620 SAM GUI client to verify that the 5620 SAM main servers and
databases are functional. The server and database status is displayed in the status
bar at the bottom of the GUI.
14.10 Clearing inactive residential subscriber instances from the
5620 SAM database
Alcatel-Lucent recommends that you periodically remove the inactive residential
subscriber instance records from the 5620 SAM database. A residential subscriber
instance becomes inactive when the associated subscriber is deleted from an NE. The
inactive instances accumulate rapidly, for example, in a Wi-Fi offload deployment.
Procedure 14-18 To delete the inactive residential subscriber
instances
Perform this procedure to configure and execute a script that removes the inactive
residential subscriber instance records from the 5620 SAM database.
If required, disable the GUI client timeout
1 Choose Administration→Security→5620 SAM User Security from the 5620 SAM
main menu. The 5620 SAM User Security — Security Management (Edit) form
opens.
2 Set the Client Timeout (minutes) parameter to 0, which specifies no timeout.
Setting the parameter to 0 ensures that the 5620 SAM GUI client session does not
close because of user inactivity while the script execution is in progress.
3 Save your changes and close the form.
Configure a script bundle
4 Choose Tools→Scripts from the 5620 SAM main menu. The Scripts form opens.
5 Choose Script Bundle (Scripting) from the drop-down menu and click Search. A list
of script bundles is displayed.
6 If a subscriber instance deletion script bundle is listed, go to step 12.
7 Click Browse Examples. The Browse Examples of Scripts form opens.
Note — Before you execute the script, Alcatel-Lucent recommends
that you disable the GUI client timeout so that you can use the client
GUI to monitor the script execution. Otherwise, if the execution takes
longer then the GUI client timeout, you can monitor the script
execution using the 5620 SAM user activity log.
Release 12.0 R6 | November 2014 | 3HE 08861 AAAF TQZZA Edition 01