Skip to main content
Question

26R1 upgrade fails while creating delivery in ReleaseUpdateStudio

  • September 11, 2026
  • 0 replies
  • 7 views

Forum|alt.badge.img+1

After successfully completing the adoption of 25.2.9 into the Build Place, we started the release update process to 26.1.3. All steps completed successfully until the Order Delivery step.

During this step, the following errors are reported in:

_ERROR_install.log

!!!Error deploying file wadaco/DataCaptureSessionLov.edv at 08-SEP-26 13:52:48

!!!Error occurred while executing Plsql Block

DECLARE

   stmt_ CLOB;

   eol_  VARCHAR2(2) := chr(13)||chr(10);

   real_table_name_ VARCHAR2(127) := Database_SYS.Get_Or_Generate_Rtb_Name('DATA_CAPTURE_SESSION_LOV_TAB');

BEGIN

      stmt_ := 'CREATE OR REPLACE EDITIONING VIEW DATA_CAPTURE_SESSION_LOV_TAB AS'||eol_;

      stmt_ := stmt_ || 'SELECT'||eol_;

      stmt_ := stmt_ || '       capture_session_id,'||eol_;

      stmt_ := stmt_ || '       lov_item_value,'||eol_;

      stmt_ := stmt_ || '       line_no,'||eol_;

      stmt_ := stmt_ || '       lov_item_description,'||eol_;

      stmt_ := stmt_ || '       lov_item_description2,'||eol_;

      stmt_ := stmt_ || '       lov_item_description3,'||eol_;

      stmt_ := stmt_ || '       lov_item_description4,'||eol_;

      stmt_ := stmt_ || '       lov_item_description5,'||eol_;

      stmt_ := stmt_ || '       lov_item_description6,'||eol_;

      stmt_ := stmt_ || '       lov_item_description7,'||eol_;

      stmt_ := stmt_ || '       lov_item_description8,'||eol_;

      stmt_ := stmt_ || '       lov_item_description9,'||eol_;

      stmt_ := stmt_ || '       lov_item_description10,'||eol_;

      stmt_ := stmt_ || '       lov_item_description11,'||eol_;

      stmt_ := stmt_ || '       lov_item_description12,'||eol_;

      stmt_ := stmt_ || '       lov_item_description13,'||eol_;

      stmt_ := stmt_ || '       lov_item_description14,'||eol_;

      stmt_ := stmt_ || '       lov_item_description15,'||eol_;

      stmt_ := stmt_ || '       lov_item_description16,'||eol_;

      stmt_ := stmt_ || '       lov_item_description17,'||eol_;

      stmt_ := stmt_ || '       lov_item_description18,'||eol_;

      stmt_ := stmt_ || '       lov_item_description19,'||eol_;

      stmt_ := stmt_ || '       lov_item_description20,'||eol_;

      stmt_ := stmt_ || '       rowversion,'||eol_;

      stmt_ := stmt_ || '       rowkey,'||eol_;

      stmt_ := stmt_ || '       delete_edition$'||eol_;

      stmt_ := stmt_ || 'FROM ' || real_table_name_ ||eol_;

     

      -- ifs_assert_safe codegen

      EXECUTE IMMEDIATE stmt_;

      -- ifs_assert_safe codegen

      EXECUTE IMMEDIATE 'COMMENT ON TABLE DATA_CAPTURE_SESSION_LOV_TAB

         IS ''LU=DataCaptureSessionLov^PROMPT=Data Capture Session Lov Tab^MODULE=WADACO^''';

      EXECUTE IMMEDIATE 'GRANT SELECT ON DATA_CAPTURE_SESSION_LOV_TAB TO IFSSYS';

END;

ORA-00904: "LOV_ITEM_VALUE": invalid identifier

ORA-06512: at line 37

 

 

!!!Error deploying file apply_install.tem at 08-SEP-26 17:21:21

!!!Error occurred while executing Plsql Block

BEGIN

Database_SYS.Read_User_Objects_Snapshot_('Y', 'Y');

END;

ORA-20105: Database.NEW_INVALIDS:

New invalids after deployment:

 

Schema IFSAPP

WRKTSK\MAINT_MATERIAL_ALLOCATION_RES - View

 

ORA-06512: at "IFSAPP.ERROR_SYS", line 150

ORA-06512: at "IFSAPP.ERROR_SYS", line 368

ORA-06512: at "IFSAPP.DATABASE_SYS", line 1482

ORA-06512: at "IFSAPP.DATABASE_SYS", line 810

ORA-06512: at line 2

We have not made any customizations or modifications to any of the affected sources, views, database objects, or application components.

Because of these errors, the Order Delivery job fails, no delivery package is generated for download, and we are unable to complete the release update process.

At this point, we do not know what options are available to resolve these issues and successfully complete the upgrade from 25.2.9 to 26.1.3.

Could anybody please advise:

  1. Whether these errors are a known issue when upgrading from 25.2.9 to 26.1.3.
  2. Which validation steps we should perform to identify the root cause.

We already opened an support ticket.