Troubleshooting guide
6 — 5620 SAM database management
6-12 Alcatel-Lucent 5620 Service Aware Manager
5620 SAM
System Administrator Guide
4 Configure the Scheduled Backup Directory parameter in the Backup Setting panel.
The value that you specify is the database station directory in which to save the
backup file sets. Each file set is stored in a subdirectory named backupsetn, where
n is a sequential number; the highest possible value is the Number to Keep
parameter value.
5 Close the Database Manager form.
6 After each scheduled database backup completes, move the database backup file
set to another station for safekeeping.
Procedure 6-9 To configure the allowed number of Oracle database
login attempts
As a security precaution, you can configure the allowed number of Oracle database user
login attempts before the user account is locked because of failed attempts. See
Procedure 6-10 for information about how to reset the Oracle database user account.
1 Log in to the 5620 SAM database station as the Oracle management user.
2 Open a console window.
3 Enter the following:
bash$ path/install/config/samdb/SAMDb_security.sh ↵
where path is the 5620 SAM database installation location, typically /opt/5620sam/samdb
The following prompt is displayed:
Enter the password for the "sys" user (terminal echo is off):
4 Enter the Oracle SYS user password and press ↵.
Caution — Before the 5620 SAM performs a database backup, it
deletes the contents of the specified backup directory. Ensure that the
backup directory that you specify in this step does not contain files that
you need to retain.
Note 1 — The Scheduled Backup Directory must be a directory on the
local file system.
Note 2 — The Oracle management user requires read and write
permissions on the Scheduled Backup Directory.
Note 1 — In a redundant deployment, you must perform this procedure
on the primary database station. After you perform the procedure, the
primary database automatically copies the configuration change to the
standby database.
Note 2 — The configuration changes that you make in this procedure
are not affected by subsequent database upgrades.
Release 12.0 R6 | November 2014 | 3HE 08861 AAAF TQZZA Edition 01