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

Last updated on SEPTEMBER 19, 2023

Applies to:

Symptoms

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.

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

Changes

Cause

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