My Oracle Support Banner

Fchksum32 Returns A Different Result After tpexport() / tpimport() Cycles (Doc ID 2626334.1)

Last updated on JANUARY 14, 2021

Applies to:

Oracle Tuxedo - Version 12.2.2 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.2 version, Tuxedo Kernel

ACTUAL BEHAVIOR
---------------
Fchksum32 returns a different result after tpexport()/tpimport() cycles

Typically a single round of tpexport()/tpimport() produces the same checksum, however after few tpimport() calls something gets messed up and checksum differ:

- The buffer content is exactly the same (verified by Fprint32 and manual field checks)
- The buffer memory differs, probably because of padding bytes (verified by memcmp, memory dumps)

As the result Fchksum32() can't be used to ensure buffer content is the same.

EXPECTED BEHAVIOR
-----------------------
Multiple calls of tpexport()/tpimport() should not change buffer checksums.

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!


In this Document
Symptoms
Cause
Solution
References


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