Session Database Reference (Oracle)

Target Audience

• IT system architect
• Technology consultant
• Implementation project team
• Database system administrator (DBA)
• Support specialist

Getting Started

This SAP product documentation is a complete reference of the schema of SAP CC Session Database, a component of the SAP Convergent Charging software product. SAP CC Session Database is a back-end database of SAP CC Core Server in real-time environment with online charging services (OCS) based on session management.

The database contains data related to a particular business process (session-based charging) handled by the SAP CC Core Server system. This data includes:

• Business processing data: business data tables related to session-based charging operations

Refer to this information when administering the SAP CC system or the database system, installing/upgrading, or updpating/patching SAP CC tables in your database.

Database Schema

The database schema describes the structure, all the tables (entities), the columns (attributes), and the keys (relationships) of SAP CC Session Database.

SQL Scripts

All the necessary SQL scripts are delivered with SAP Convergent Charging to:

• Administer your database and SAP CC tables (creation and deletion scripts)
• Change SAP CC tables in your database (patch scripts)

Delivered SQL scripts are stored in one of the following SAP CC installation folders:

• MS Windows: <DRIVE>:\usr\sap\<SID>\CCD<SAP_INST_NB>\exe\CC_CORE_SERVER\session_sql
or
• UNIX and other operating systems: /usr/sap/<SID>/CCD<SAP_INST_NB>/exe/CC_CORE_SERVER/session_sql

Abbreviations

PK: Primary Key

FK: Foreign Key

UK: Unique Key

IX: Indexed Field

Database Schema

Database Indexes

This database schema defines the necessary database indexes to speed up the retrieval of data stored in the database tables. The initial installation of SAP CC creates these indexes that you manage during technical operations.

Reserved Space in Tablespaces

This database schema defines some reserved spaces to optimize the physical storage of data in your database system. You configure and maintain these spaces.

Database Partitioning

SAP Convergent Charging provides advanced functions to ensure the highest level of performance (high volume of data, very high end-to-end throughput and latency) and high availability. These functions require database partitioning to improve the database performance with large and very large databases.

SAP CC associates a business partitioning mechanism to isolate some data during business operations.

For more information about the business partitioning in SAP Convergent Charging, consult the SAP CC 5.0 Application Help and the database section.

Schemas and Database Partitioning

SAP CC delivers two schemas of Session Database.

Class	Scope
Schema With Database Partitions	Large and high volume of data High performance
Schema Without Partition	Small-sized business environments (includ. production system landscapes) or development system landscapes

The RATING_SESSION database table includes a PARTITION_ID column that refers to the partition ID assigned to a subscriber account in customer master data in SAP CC Core Database. The data objects associated to a subscriber account are stored in the same database partition with the same partition ID.

See the SAP CC 5.0 Application Help for more information about the subscriber accounts and associated objects in customer master data.

SQL Scripts

All the necessary SQL scripts are delivered with SAP Convergent Charging to:

• Administer your database and SAP CC tables (initial creation and deletion scripts).
• Change some SAP CC tables in your database (patch scripts) during the regular software maintenance of SAP CC or during an upgrade project from previous main release of SAP CC.
• Fix some SAP CC tables in your database (correction scripts) during troubleshooting operations with your SAP Support Team.

Two Sets of Scripts

SAP CC delivers two sets of SQL scripts to install a new database system with or without database partitioning. The file naming convention uses the enterprise and standard terms:

Script Set	Script Name Patern
Database With Partitions	<DB_TECHNO_KEY>_enterprise_<DB_SCHEMA_KEY>_create.sql <DB_TECHNO_KEY>_enterprise_<DB_SCHEMA_KEY>_drop.sql patch<SCHEMA_VERSION>to<_NEW_VERSION><DB_TECHNO>_enterprise_<DB_SCHEMA>.sql
Database Without Partition	<DB_TECHNO_KEY>_standard_<DB_SCHEMA_KEY>_create.sql <DB_TECHNO_KEY>_standard_<DB_SCHEMA_KEY>_drop.sql patch<SCHEMA_VERSION>to<_NEW_VERSION><DB_TECHNO>_standard_<DB_SCHEMA>.sql

Delivered SQL scripts are stored in one of the following SAP CC installation folders:

• MS Windows: <DRIVE>:\usr\sap\<SID>\CCD<SAP_INST_NB>\exe\CC_CORE_SERVER\core_sql
or
• UNIX and other operating systems: /usr/sap/<SID>/CCD<SAP_INST_NB>/exe/CC_CORE_SERVER/core_sql

Implementation

To implement this database in your SAP system landscape, consider the following activities:

• Sizing
• Installation
• Technical configuration in SAP CC
• Validations
• Technical operations (administration, software maintenance, purging and archiving, monitoring, and troubleshooting)

Sizing

Refer to the SAP CC 5.0 Tuning Guide and Sizing Guidelines for SAP Convergent Charging for information about the the translation of your business requirements and IT strategy into hardware requirements based on predictions considering:

• Data volume
• Performance
• Robustness
• Scalability
• High availability

The sizes of the hardware and database are influenced by both business aspects and technological aspects.

Installation

Refer to the SAP CC 5.0 Installation Guide for information about the installation preparations, initial installation, and follow-up activities of this database system in your SAP CC system landscape.

Technical Configuration in SAP CC

Refer to the SAP CC System Parameter Reference and SAP CC 5.0 Configuration Guide for more information about the configuration in SAP CC that relates to the databases. See the SQLHELPER_LOGIN system parameter.

Technical Operations

During the project implementation phase or during the productive operation phase, consider the following activities:

• Administration
• Software maintenance
• Purging and archiving
• Monitoring
• Troubleshooting

Software Maintenance

Refer to the information provided by the database supplier for more information about the software maintenance of your database systems.

Monitoring

DBA Cockpit

Install and use DBA Cockpit in SAP Solution Manager to monitor the back-end databases of SAP Convergent Charging. Refer to the SAP CC 5.0 Operations Guide for more information.

SAP CC Activities

You can monitor the performance and health metrics reported by the instances of the running SAP CC Core Server system. These instances are connected to the back-end database system and manage several internal functions. By using CA Introscope for SAP in SAP Solution Manager, you can view the back-end activities that relate to the database commits, rollbacks, and prepared SQL statements.

See the {Database Name} on {Hostname} ({Database Type} DB) metric node in the SAP CC 5.0 Metric Reference and Performance Troubleshooting for more information and user assistance.

Troubleshooting

Communication	From Logs	Performance
You use SAP Solution Manager to detect connection or communication problems. You use the SAP CC Admin+ user interface: admin_sql_connection - To disconnect from or to force the reconnection of the selected instances of the SAP CC system with a selected instance of the database system refresh_sql_connections - To force the update of the connections to the database	You use the logs of the database system. You use the logs and traces recorded in the SAP CC system.	You use SAP Solution Manager.