Skip to main content
Question

Sanity build failed when applying 25R2

  • December 25, 2025
  • 3 replies
  • 42 views
N
Sidekick (Partner)
Forum|alt.badge.img+8

We modified the customization source to comply with NZD.
We will not be using the NZD function, so we plan to offline delivery.
FNDNZD component is inactive.
When applying 25R2 in the Manage Release Update, the following error occurs in the Sanity build.

_ifs_ant_generatedb.log
ERROR:Missing --SAFE_FOR_ONLINE_DEPLOYMENT comment in file '/opt/ifs/build-home/database/XXX/XXX.ins' at line 20. Please review the PL/SQL block and ensure it is properly annotated to support online deployment.
ERROR:Missing --SAFE_FOR_ONLINE_DEPLOYMENT comment in file '/opt/ifs/build-home/database/ZZZ/YYY.ins' at line 21. Please review the PL/SQL block and ensure it is properly annotated to support online deployment.
INFO :Scanning completed for 9028 .ins files with 2 validation error(s).
INFO :Scanning Post SQL files...
INFO :Scanning completed for 103 Post SQL files with 0 validation error(s).
INFO :Scanning .cdb files...
ERROR:File '/opt/ifs/build-home/source/XXX/database/230323_183000_NIfXXX.cdb' with .cdb extension is not supported for online deployment. Please remove or empty the file to proceed.
ERROR:File '/opt/ifs/build-home/source/XXX/database/230323_183000_NIfYYY.cdb' with .cdb extension is not supported for online deployment. Please remove or empty the file to proceed.
INFO :Scanning completed for 4 .cdb files with 2 validation error(s).
 

3 replies

ashen_malaka_ranasinghe
Hero (Employee)
Forum|alt.badge.img+12

Hi ​@NECMIOH,

With 25R2, Delivery Continuity (NZD) ships GA and adds online‑aware tooling/validators to sanity builds and installers. If the feature is enabled, validators will:

  1. enforce --SAFE_FOR_ONLINE_DEPLOYMENT for .ins, and
  2. block .cdb outright.

Offline remains the default path unless NZD is activated, and that Online deliveries follow a strict Apply → Cutover → Cleanup flow.

You can follow the steps below:

  1. Confirm the mode used by your RU/environment: is Delivery Continuity (NZD) enabled there?
  2. If going OFFLINE:
    1. Ensure FNDNZD: false in the exact solution set used by RU (no overrides later in the pipeline).
    2. Recreate/refresh the RU and rerun Sanity. The .cdb should be allowed and the SAFE_FOR_ONLINE_DEPLOYMENT requirement should disappear.
  3. If going ONLINE:
    1. Add --SAFE_FOR_ONLINE_DEPLOYMENT to the two .ins files at the indicated lines, after verifying the blocks are genuinely online‑safe.
    2. Remove/empty the two .cdb files or transition their logic to compliant .ins/Post SQL and, if needed, split changes across Apply/Cutover/Cleanup.
Find me on LinkedIn as Ashen Malaka: https://www.linkedin.com/in/ashen-malaka-ranasinghe/
N
Sidekick (Partner)
Forum|alt.badge.img+8
  • NECMIOH
  • Author
  • Sidekick (Partner)
  • December 25, 2025

Because it is offline delivery, FNDNZD: false is set, but the error you reported occurs.
 

 

S
Hero (Customer)
Forum|alt.badge.img+12
  • SimonTestard
  • Hero (Customer)
  • December 30, 2025

The Validation for NZD should not prevent you from building in Sanity, those are supposed to only be informational to let you know that if built, the delivery won’t be able to delivered Online (which is not a problem if you’re not a Continuity Delivery customer anyways).

 

In short, it says “error” but it is more of a warning as such.

 

In the logs, does the deploy_db folder get created ? If it does, do you have any errors in there ?

 

 

 

 

Terms & ConditionsCookie settingsAccessibility statement