Skip to main content

Drop of components in a service update SU

  • September 18, 2026
  • 3 replies
  • 54 views
Do Gooder (Customer)
Forum|alt.badge.img+1

We have just upgraded our IFS instance from 25.2.3 to 25.2.9. No problem with the upgrade, but to our big surprise, we saw that several IFS core components were dropped with this lift. Is that really ok? A service update should only contain high priority bug corrections.

This is an extract from the _obsoletes.log found in the database_apply folder after the upgrade:

Drop of component AT
Remove internal component "AT - Automated Tests"

Drop of component DEMO
Remove internal component "DEMO - Demo Installation"

Drop of component DEMOCD
Remove internal component "DEMOCD - Demo CD"

Drop of component FNDADS

Drop of component FNDINT
Remove internal component "FNDINT - Foundation1 Internal"

Drop of component GETUTL
Remove internal component "GETUTL - Global Extension Utility"

Drop of component RCMINT

Drop of component SEROBJ

If I diff the prifs component, and the folder source/prifs/database, for the source and target version of IFS, I can see that drp scripts are added for all of these components, which causes them to be dropped.

As I wrote initially, this did not cause any harm since it seems to be internal IFS components, but I would still say that this is not an ok action in a service update.

What is your opinion?

 

Cheers

 

    3 replies

    Jonas Feigl
    Superhero (Employee)
    Forum|alt.badge.img+20
    • Jonas Feigl
    • Superhero (Employee)
    • September 18, 2026

    Hi ​@mabose, Components that are part of the Release Update you are on will indeed not be made obsolete in a Service Update.

    The components that have had .drp scripts added in this SU aren’t actually IFS Cloud 25R2 components. Instead these are components that have existed in IFSAPP10 and before that, in upgraded databases, could have some minor remnants (like dangling entries in MODULE_TAB etc.) that did not get cleaned up. This is just a cleanup for upgraded environments that should have no impact on IFS Cloud installations otherwise - as you have already confirmed.

     

    Do Gooder (Customer)
    Forum|alt.badge.img+1
    • mabose
    • Author
    • Do Gooder (Customer)
    • September 18, 2026

    Thank you, Jonas, for your quick response.

     

    True, these components are obsolete rubbish, I am very well aware of that. And I have no problem that you drop them. But still, my opinion is that this is nothing you handle in an Service Update. The SUs are only supposed to contain P1 and P2 bug corrections, and cleaning up Apps8, 9 and 10 components cannot hardly be of that dignity.

    But let’s not make a mountain out of a molehill. I am not looking for a bug fix or something. Rather I am just asking you to really consider what you include in an SU to make our lifts as simple as possible

    Thanks

    Jonas Feigl
    Superhero (Employee)
    Forum|alt.badge.img+20
    • Jonas Feigl
    • Superhero (Employee)
    • September 18, 2026

    Some of these components had left obsolete tables and views in the database which were causing EBR and NZD compliance errors (which was what triggered this clean up). As such they were classified as P2 as they were otherwise blocking online installations in 25R2.

      Terms & ConditionsAccessibility statement