Some time ago we migrated from oracle 11 to 19c. Out of 5 of our schemas, 2 of them, when adding new objects to the schema (packages, synonyms, views, etc.), create them as non-editonable in default, which makes it impossible to update the objects of these two applications.
Editions in this database instance are disabled for all of our 5 schemas. Only two schemas have this problem, the other 3 create new objects as editionable as standard (even SYS and SYSTEM don't have this problem). The base is in the default "ora $ base" edition. In our applications, editions are to be turned off. What we missed for these two schemas, and how can it be fixed without re-importing (production database, and it's been a long time since the migration). I assume this is not an editions problem, there must be something else that caused these two schemas to have such problem.
?

create or replace noneditionable procedure p as
begin
  dbms_output.put_line ( 'First version' );
end p;
/

exec p ();

First version

create or replace noneditionable procedure p as
begin
  dbms_output.put_line ( 'Second version' );
end p;
/

exec p ();

Second version

create or replace editionable procedure p as
begin
  dbms_output.put_line ( 'Editionable version' );
end p;
/

ORA-38824: A CREATE OR REPLACE command may not change the EDITIONABLE property of an existing object.

exec p ();

Second version

alter procedure p 
  editionable;

create or replace editionable procedure p as
begin
  dbms_output.put_line ( 'Editionable version' );
end p;
/

exec p ();

Editionable version

select editions_enabled 
from   dba_users
where  username = user;

EDITIONS_ENABLED   
N