Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Related Documentation
- C Series
- Modifying the SSR Database Schema in an Active Cluster (SRC CLI)
- SSR Database Schema
- Configuring the Fields in the Subscriber Sessions Table (SRC CLI)
- Mapping SAE Plug-In Attributes to Fields in the Subscriber Sessions Table (SRC CLI)
- Creating the SSR Database (SRC CLI)
- Deleting the SSR Database (SRC CLI)
Making Modifications to the SSR Database Schema Overview
Whenever you have modified, added, or deleted fields from the subscriber sessions table, you apply the new database schema by destroying and re-creating the SSR database.
 | Note: This is a destructive process, and must be performed during a schedule maintenance window. Destroying the database causes all data in the database to be lost. |
Because the configuration of the database is stored in Juniper Networks database, modifications to the database schema can be made from any node in the SSR cluster. However, destroying and recreating the database can be performed only from a client node (with or without a management server).
| Note: Changes to the SSR database schema requires you to restart all SRC components. |
Related Documentation
- C Series
- Modifying the SSR Database Schema in an Active Cluster (SRC CLI)
- SSR Database Schema
- Configuring the Fields in the Subscriber Sessions Table (SRC CLI)
- Mapping SAE Plug-In Attributes to Fields in the Subscriber Sessions Table (SRC CLI)
- Creating the SSR Database (SRC CLI)
- Deleting the SSR Database (SRC CLI)
