Don't think this is ORDS specific but encountered whilst trying to resolve an issue with ORDS on serverC.
Examples below are from serverB - which has no issues except with sqlcl when not using wallet.
dns/load-balancer / ORDS 24.2 / APEX latest / ADB latest - all fine
sql /nolog
set cloudconfig /home/oracle/Wallets/Wallet_APEX23B.zip
connect ORDS_PUBLIC_USER2/***@apex23b_medium
show connection
- all fine
sql ORDS_PUBLIC_USER2@jdbc:oracle:thin:@(description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)…
FAILS with
Error Message = Listener refused the connection with the following error:
ORA-12506, TNS:listener rejected connection based on service ACL filtering
(CONNECTION_ID=qIjV+JyzSNa1Kj4/OxqXzQ==)
99% sure this used to work
Get same error on ServerC which runs ORDS 25.1
In both cases recently reset ORDS_PUBLIC_USER2 via ords --config /etc/ords/config config secret db.password
sqlcl running on same compute instance as custom ORDS
get same error trying to connect as ADMIN
Has something changed in last ~ 6 months to force sqlcl to use wallet or am I missing something else?
NB ADB itself accepts sql developer ADMIN connection from home PC via wallet, so don't believe it is DB ACL related.
update: quick chat with mad robot and this syntax is successful
sql -cloudconfig /home/oracle/Wallets/Wallet_APEX23B.zip ORDS_PUBLIC_USER2/***@apex23b_medium