25R2 Upgrade issue

hope you have followed the instructions as given in documentation. if you can share the error log, can give some inputs..

/Wasana

Hi ​@dmcler 

Known issue. Look at this:

https://support.ifs.com/csm?id=kb_article&sys_kb_id=null&table=kb_knowledge&sysparm_article=KB0094562

Hi Wasana,

Thank you for the feedback.

The database is a clone of a used 25R1 database and is not empty. There are over 37,000 ORA-06508 errors like these: 
ORA-04063: package body "IFSAPP.DATABASE_SYS" has errors
ORA-06508: PL/SQL: could not find program unit being called: "IFSAPP.DATABASE_SYS"

Apparently, the database is not EBR compliant or something specific for Windows Server 25R2 still needs to be done with the database.

According to the documentation, an upgrade script (*.upg presumably ?) should be executed:

https://docs.ifs.com/techdocs/25r2/060_development/027_base_server_dev/225_reduced_downtime_delivery/010_ebr_prep/#use_the_provided_utility_framework_method_to_prepare_all_tables_for_ebr

However, the framework preparation from Developer Studio did nothing.So we started with the R2 delivery installation without any further adjustments or preparation to the database.

Hi Kepiosko,
This also concerns invalid objects, but the KB article pertains to SU7. We have 25R1 SU5.

Thanks anyway for the heads-up.

Hi ,

If you dont have any modifications and if its purely standard , you don't have anything to do with EBR  compliance as CORE code is updated accordingly.

Are you taking the delivery continuity as well ? if so you need to update the solution set to enable it. 

Best Regards,
Wasana

No, we don't use delivery continuity.

Since migrating to Oracle Enterprise Edition,

strangely, a fresh installation from the initial- build home hasn't worked (various 500 errors on API calls).

I'm now testing a fresh installation via a update- build home.

25R2 installation  from upgrade  build home on an empty database works,

but updating it with an existing 25r1 database does not (11,000 invalid objects and missing tables are shown in the log).

Next step: After updating the Oracle patches, everything now works perfectly!

Hi ​@dmcler - I’m preparing an on-premise instance for an update from 24R1 SU9 to 25R2 SU4, and am getting some interesting errors.

When the installer.cmd script is executing, it is trying to establish a connection to an Oracle SERVICE_NAME that is not seemingly honoring the jdbc connection string in the ifscloud-values.yaml file (it’s appending _INSTALL to the SERVICE_NAME in the error logs).

You mentioned an Oracle Patch. Was this an Oracle Patch bundle (just finished ours with 19.30 a few days ago)?

Here’s the error message that’s being outputted by the installer.cmd process:
…

INFO:Connection successfull
INFO:Start executing D:/ifsremote/ifsroot/deliveries/ifs-cloud-25.2.4-[REDACTED]-4.0.0-20260411T172908Z-success/InstallationFiles/ifsinstaller/installers/db-deploy-utils/InstallerApply.sql
INFO:Finished executing D:/ifsremote/ifsroot/deliveries/ifs-cloud-25.2.4-[REDACTED]-4.0.0-20260411T172908Z-success/InstallationFiles/ifsinstaller/installers/db-deploy-utils/InstallerApply.sql
INFO:Connection closed
INFO:Trying to connect to the database to deploy D:/ifsremote/ifsroot/deliveries/ifs-cloud-25.2.4-[REDACTED]-4.0.0-20260411T172908Z-success/InstallationFiles/database/_utils/prepare.sql as user SYS
FINE: Database not answering, waiting 5 seconds before retrying 1/3
FINE: Database not answering, waiting 5 seconds before retrying 2/3
ERROR:No connection to the database could be established (1)! Connect string jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=XXX.XXX.XXX.XXX)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=devpdb_INSTALL))) Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
...

Here’s the connection string definition from the ifscloud-values.yaml file (IP address redacted):

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=XXX.XXX.XXX.XXX)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=devpdb)))

Was there anything in particular that needed to be performed against the database instance in question prior to deploying this Release Update, and if so, what was it?

I appreciate your participation on the Community forum, and any responses are greatly appreciated. Thank you, and let me know if there are any details that I could collect that would be helpful at all.

Regards,

Randy

Figured my own problem out, I needed to update the TNSNames and Lister ORA files to included the xxx_INSTALL entry.

Regards,

Randy