Workflow for NFM-P database management
Stages
Note: It is strongly recommended that you verify the checksum of each file that you download from the NSP download page on the Nokia Support portal. You can compare the SHA-256 checksum value in the Packages.sha256sum on the download page to the output of the RHEL sha256sum command. See the RHEL sha256sum man page for information.
Database properties and status | |
1 |
Display the main database properties; see How do I view the main database properties? . |
2 |
Display the auxiliary database properties; see the following, as required: |
Database operation and security | |
3 |
As a security precaution, configure the number of failed Oracle database user login attempts that the NFM-P allows before a user is locked out; see How do I configure the Oracle database user lockout threshold? . |
4 |
As required, unlock the Oracle database user account after multiple login failures; see How do I unlock the Oracle database user account? . |
5 |
Configure how the NFM-P responds to Oracle database errors; see How do I configure Oracle database error monitoring? . |
6 |
Configure size constraint policies to regulate the number of records retained in the main database; see How do I configure a size constraint policy? . |
7 |
Configure ageout constraint policies to define a configurable ageout time for a specific object type in the main database; see How do I configure an ageout constraint policy? . |
8 |
Manage main database disk usage by configuring policies to manage the file size and number of archive log and core dump files; see How do I create a database file policy to manage database log or core dump files? . |
9 |
Configure the statistics data retention period for the main database; see How do I configure the statistics data retention period for the main database? . |
Backup, restore, and maintenance | |
10 |
Perform an immediate full or partial main database backup; see How do I back up the main database from the client GUI? or How do I back up the main database from a CLI? . |
11 |
Back up an auxiliary database; see How do I back up an auxiliary database? . |
12 |
Schedule a regular main database backup; see How do I schedule main database backups? . |
13 |
Schedule regular auxiliary database backups; see How do I schedule auxiliary database backups?. |
14 |
Restore the main database in a standalone system; see How do I restore a standalone main database?. |
15 |
Restore the main database in a redundant system; see How do I restore the primary main database in a redundant system?. |
16 |
Restore an auxiliary database; see How do I restore an auxiliary database? |
17 |
As required, delete the inactive residential subscriber instances from the main database; see How do I delete the inactive residential subscriber instances?. |
18 |
Test the main database restore function to ensure that main database backups are viable in the event of a failure; see How do I test an NFM-P main database restore? . |
19 |
Export a main database to a file set; see How do I export an NFM-P main database?. |
20 |
Import a main database from a file set; see How do I import an NFM-P main database?. |
21 |
Verify the synchronization of NE and main database information; see How do I check the main database performance? . |
Redundancy functions | |
22 |
Perform a main database switchover; see How do I configure main database switchover behavior? , How do I perform a main database switchover using the NFM-P client GUI? , or How do I perform a main database switchover using a CLI script? . |
23 |
Enable or disable automatic database realignment on a main server; see How do I enable or disable automatic database realignment?. |
24 |
Re-establish redundancy after a database activity switch or similar maintenance activity; see How do I reinstantiate the main database from the client GUI? and How do I reinstantiate the main database from a CLI?. |