My Oracle Support Banner

Persistent Store Configuration & Operational Considerations for JMS, SAF & WebLogic tlogs in OSM (Doc ID 2469767.1)

Last updated on DECEMBER 04, 2018

Applies to:

Oracle Communications Order and Service Management - Version 7.3.1.0.0 and later
Information in this document applies to any platform.

Purpose

Using file store for persistence of JMS messages and JTA transaction logs (tlogs) can lead to unusable or corrupted backups and DR/GR synchronization, as well as increased maintenance (monitoring for size, and outages for compaction). Avoiding this maintenance leads to performance issues. 

 

 

Scope

This applies to OSM 7.3.1.0 and higher

Note: The recommendation herein apply to older OSM releases as well, but for those releases, JDBC persistence is only available for JMS/SAF and not for tlogs.  So the older releases will continue to have the same sync issues with tlog files, but will be protected for the more numerous message handling scenario.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Cause
 Workaround
 Solution
 Rationale
 Performance
 Comparison

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.