select dbms_crypto.randomnumber from dual;

gives me:

Error at line 1/8: ORA-00904: "DBMS_CRYPTO"."RANDOMNUMBER": invalid identifier

However, after some troubleshooting I tried STANDARD_HASH in a query and it works. Previously I was using it as an assignment.

This does not work:

 v_secret_hash := STANDARD_HASH(p_api_secret, 'SHA256'); 

This works:

SELECT STANDARD_HASH(p_api_secret, 'SHA256') INTO v_secret_hash FROM DUAL;

I tried both assignment and select statement with DBMS_CRYPTO and it does not work. I guess it is not allowed to be used on always free? Perhaps it works for you because you're at Oracle? Also I'm wondering if I should upgrade to Oracle 26ai because I'm currently on 19c. Anyways, if you could ask around and give me some insights or better still if you have anyone who can help give me access I'd appreciate it! ;-)

Have a good day and bless you for taking time to answer my question!

SQL> select standard_hash('qweqwe') from dual;

STANDARD_HASH('QWEQWE')
----------------------------------------
F4542DB9BA30F7958AE42C113DD87AD21FB2EDDB

SQL> select dbms_crypto.randomnumber from dual;

RANDOMNUMBER
------------
  2.3354E+38

SQL> @ver

BANNER_FULL
--------------------------------------------------------------------------
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.29.0.1.0

STANDARD_HASH works for me. Is there a way for anyone at Oracle to give me access to DBMS_CRYPTO?

I tried your sql statement in your response in SQL Commands and it gives me the same error. Tried with SYS.DBMS_CRYPTO also to see if prefixing with schema works. What should one do when Always Free does not work as expected? I know there is no support available, but is there any forum where I can contact someone for help?