/
FATAL-5203: Sanity check: cannot allocate
FATAL-5203: Sanity check: cannot allocate
This article explains how to resolve issue when APPLY crashes with FATAL-5203 error
Problem Details
Problem Statement
APPLY fails with error
Applicable Error Code
FATAL-5203: Sanity check: cannot allocate -234524800 bytes.
Affected Versions
Version Independent , noticed in 2.8
Affected Platforms
Platform independent
Problem Description
APPLY Crashes with a sanity check error
Solution
This could be a problem with the size of the PLOG. A full PLOG may not have been received. This can occur if there is a network issue or possibly a problem with a share disk or NFS mount.
Resend the PLOG over. Details on how to do this can be found here:
https://dbvisit.atlassian.net/wiki/display/ugd7/Resending+a+PLOG
Chris Lawless May 08, 2015 09:02
, multiple selections available,
Related content
APPLY process starts hunderds of plogs back
APPLY process starts hunderds of plogs back
More like this
Receive a Fatal> Fatal-5259: Error. What Is the Solution?
Receive a Fatal> Fatal-5259: Error. What Is the Solution?
More like this
How to debug problematic SQL query in target database when apply process crashes without tracefile
How to debug problematic SQL query in target database when apply process crashes without tracefile
More like this
Apply process crashes with: FATAL-4106: Internal error (signalled by Perl interpreter): Can't call method "prepare"
Apply process crashes with: FATAL-4106: Internal error (signalled by Perl interpreter): Can't call method "prepare"
More like this
FATAL-6020, ERR-9032: Invalid command
FATAL-6020, ERR-9032: Invalid command
More like this
Apply does not replicate the changes
Apply does not replicate the changes
More like this