Hi all,
Upgrading a remote deployment from 24R1 to 25R2 SU7 (25.2.7), Oracle 19c, standard IFS-CLOUD-MANUFACTURING solution set, no customizations.
dbinstaller runs through the full cycle (kill/prepare/apply/import/cutover/cleanup) and reports success, but PROJECTION_CONFIG_ENTITY_API package body is left invalid:
Line 292: PLS-00323: subprogram or cursor 'VALIDATE_ENTITY_LUS_INSTALLED' is declared in a package specification and must be defined in the package body
Line 312: PLS-00323: subprogram or cursor 'VALIDATE_PROJ_CONFIG_ENTITIES_' is declared in a package specification and must be defined in the package bodySpec is VALID, so it looks like the shipped body just doesn't implement these two functions. This breaks PROJECTION_CONFIG_API downstream (ORA-04063/ORA-06508), which means every projection load fails with HTTP 500 - blank screen after login, both on Azure AD and local accounts.
Tried:
- UTL_RECOMP.RECOMP_SERIAL - no change, 164 invalid objects before and after
- Full dbinstaller re-run from scratch - same result, invalid count actually went up slightly (164 → 168)
- Manual
ALTER PACKAGE ... COMPILE BODY- identical PLS-00323 errors, so it's not a compile-order thing
Found KB0094562 which covers a similar-sounding issue (new invalids after deployment, functionality introduced in 25R1 SU7 meant to land in 25R2 SU3) but that one's about different packages (CLOUD_EVENT_RECEIVER_UTIL_API, FND_CDC_UTIL_API, FND_SEED_UTIL_API) and a different source version (25R1 SU7+ → 25R2, not 24R1 → 25R2 SU7).
Anyone run into this specific one? Is there a known fix/patch script for PROJECTION_CONFIG_ENTITY_API, or should I be looking at a corrupted delivery download instead? This is currently a hard blocker, app is completely inaccessible on this env.
Thanks for any pointers.