Invalidation of Dependent Procedures in Oracle RPC Signature Dependency Mode on Data Type Change

I'm working with Oracle's RPC Signature Dependency Mode and encountered unexpected behavior when changing a procedure's parameter data type within the same class. According to Oracle documentation, such changes shouldn't affect the RPC signature, yet it seems to invalidate dependent procedures. I'm hoping to gain some insights or solutions from the community.

Here's what I've done:

Set the session to signature dependency mode:

ALTER SESSION SET REMOTE_DEPENDENCIES_MODE = 'SIGNATURE';

Created a base procedure with a NUMBER parameter and a dependent procedure that calls this base procedure:

CREATE OR REPLACE PROCEDURE base_procedure (p_input IN NUMBER) ISBEGIN    -- Procedure logicEND;CREATE OR REPLACE PROCEDURE dependent_procedure ISBEGIN    base_procedure(1);  -- Calling the base procedure    -- Additional logicEND;

Changed the base procedure's parameter from NUMBER to FLOAT, expecting no invalidation since they're in the same data type class:

CREATE OR REPLACE PROCEDURE base_procedure (p_input IN FLOAT) ISBEGIN    -- Updated procedure logicEND;

After this change, the dependent procedure was invalidated, which contradicts my understanding of Oracle's documentation on signature dependency mode.

Has anyone experienced similar behavior or can provide clarity on why this invalidation occurs despite the data type change being within the same class? Any insights on how to manage such changes without causing invalidations would be highly appreciated.