My Oracle Support Banner

Transaction Log "bs" Entry When "sb" Is Expected (Doc ID 2455475.1)

Last updated on OCTOBER 17, 2018

Applies to:

Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.

Symptoms

Referring to documentation on Store Transaction Log Format,  the section about the 'co' records has an 'sb' field:

 

 

The problem is that "bs=" in the "se" records, rather than "sb=" is being seen.

Here is an example:

This query finds none:

index=email_core sourcetype=email_transaction_store "<se " sb=*

And this query finds many:

index=email_core sourcetype=email_transaction_store "<se " bs=*

Example:

<se ts="2018-10-03T08:33:16.293-07:00" sn="imapd" pi="18058" si="5886248" ma="user/john.doe/Drafts" mc="0" sf="UC" bs="231" td="1118"/>

It is expected that what is documented should be consistent with what is being shown in the transaction log file.

 

Cause

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

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


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