Parameter: ORACLE_COMMIT_WRITE
Definition
Description and Use
This parameter is only relevant for Oracle databases. For the other databases, no specific commit option is available.
The default commit options used for an Oracle database are: IMMEDIATE and WAIT.
As far as SAP CC is concerned, the used options are BATCH and WAIT.
High throughputs generate frequent commits on the database, which may impact the latency of SAP CC responses. To lighten the disks load and reduce global latency, it is possible to configure the Oracle commit mechanism so that it writes the related redo logs using a batch mode after the transaction has been committed (NOWAIT). This modification only concerns update requests impacting the COUNTER and/or RATING_SESSION tables and performed within the following stateful operations:
- activate
- charge
- updateRate
- session-based charging
Caution
When using the NOWAIT value, updates of counters or sessions may be lost in case of database failure. When such a situation occurs, counter values and sessions are nevertheless always present in the memory of the SAP CC instances, and will be correctly replicated in the database next time the corresponding session or counter will be updated. If these SAP CC instances consecutively fail or shutdown, this data can be definitively lost. At high throughput, such as loss may represent few seconds of traffic.
Syntax and Constraints
The possible values are:
- BATCH_WAIT: the BATCH,WAIT commit option is used. There is no risk of any data loss.
- BATCH_NOWAIT: the BATCH,NOWAIT commit option is used. Removes waiting time on Oracle Log Writer process but introduces a risk of data loss in case of database failure followed by one or more CC rater instance failure.
- IMMEDIATE_NOWAIT: the IMMEDIATE,NOWAIT commit option is used. Removes waiting time on Oracle Log Writer process but introduces a risk of data loss in case of database host failure followed by one or more CC rater instance failure.
See Also
Commit option used within internal stateful operations performed on the Session Database
Technical Details
For more information, consult this section.
| Name | ORACLE_COMMIT_WRITE
|
|||||
| Category | Parameter | |||||
| Type | String | |||||
| Access (RO/RW) |
RW(+): Dynamic Read / Static and Dynamic Write An immediate change is possible but is temporary. When it is relevant, change the permanent settings used by the SAP CC Core Server system when it restarts. Use the Admin+ user interface to change the runtime values or the permanent values of this system parameter in an instance of the SAP CC Core Server system or in multiple instances. |
|||||
| Groups | ||||||
| Instance Type |
This system parameter is only available in the following type of instances in a running SAP CC Core Server system:
|
|||||
| Default Value (Factory Settings) |
The predefined default value is:
You can use a default value to reset the runtime value or the restart value (persistent) in the Admin+ user interface. Note A default value is part of the factory settings of the SAP CC Core Server systems. It differs from the original value set during the installation or after the Customizing activities. In Admin+, you can reset a parameter value to this default value, but it is not recommended:
reset command.
|
|||||