Hide Navigation Pane
Show Navigation Pane
Download
SHA1
Modifying the SSR Database Schema in an Active Cluster (SRC CLI)
The default database schema is sufficient for most carrier environments. However, if you need to modify the default schema, you need to modify the fields in the subscriber sessions table, re-create the database, and apply the new schema. See SSR Database Schema for a description of the default database schema and which fields can be modified.
 | Caution: The following procedure requires you to re-create the SSR database. This is a destructive process that deletes all information in the database. This procedure should be performed only during a maintenance window. Review this procedure in full before proceeding. In addition, because the steps required to re-create the SSR database can be performed only from a client node, we recommend that you perform this procedure from a client node. |
 | Note: This procedure assumes that you are working with an active cluster and that the SSR database is in production mode. If you are unsure what mode the database is in, see Viewing the SSR Database Mode (SRC CLI). |
| Note: Changes to the SSR database schema requires you to restart all SRC components. |
To modify the SSR database schema in an active cluster:
- Modify the fields in the subscriber sessions table.
See Configuring the Fields in the Subscriber Sessions Table (SRC CLI).
- Commit the configuration.
See Committing a Configuration and Exiting Configuration Mode.
- Place the database into maintenance mode.
See Placing the SSR Database into Maintenance Mode (SRC CLI).
- Delete the existing database.
- Create the database with the modified fields.
- Verify the cluster configuration changes by viewing the status of the database.
- Restart all SSR client components in the cluster.
See Enabling SRC Components.
- Place the new database into production mode.
See Placing the SSR Database into Production Mode (SRC CLI).
