In the previous post,
we saw about how to setup a database link connecting two different ADB-S
accessible over the public endpoint using wallet in place. In this blogpost we
will see about how to establish database link connecting two different ADB-S
accessible over the public endpoint without wallet in place.
On the target ADB details page, under Network,
click Edit in the Mutual TLS (mTLS) authentication field &
change the value to allow TLS Authentication by deselecting Require mutual
TLS (mTLS) authentication and click update, the ADB lifecycle state changes
to updating and post that mutual TLS (mTLS) authentication field changes
to show Not required.
2 from v$pdbs, json_table( cloud_identity,'$.OUTBOUND_IP_ADDRESS[*]'
3 columns( outbound_ips varchar2(20) path '$') ) jt;
----------------
150.136.133.92
2 dbms_cloud.create_credential(
3 credential_name =>'DB_LINK_CRED',
4 username =>'DEMO_USER',
5 password=>'Good2go1!1234' );
6 end;
7 /
2 dbms_cloud_admin.create_database_link(
3 db_link_name => 'DB_LINK_TEST',
4 hostname => 'adb.us-ashburn-1.oraclecloud.com',
5 port => 1522,
6 service_name => 'g26be7c92912cdb_atp21c_low.adb.oraclecloud.com',
7 credential_name =>'DB_LINK_CRED',
8 directory_name => null );
9 end;
10 /
-
X
------------------------------------------------------------------------
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.23.0.1.0
------------------------------------------------------------------------
Oracle Database 21c Enterprise Edition Release 21.0.0.0.0 - Production
Version 21.3.0.0.0
No comments:
Post a Comment