- Hybrid-DR-Topologie für On-Premise-Oracle Exadata bereitstellen
- Standbyinstanz erstellen
Standbyinstanz erstellen
Erstellen Sie eine Standby-Cloud-Instanz aus der Primärdatenbank.
Archiv-Log erstellen
Prüfen Sie den Logmodus Ihres On-Premise-Oracle Exadata Database Machine. Wenn es sich im Modus NOARCHIVELOG
befindet, ändern Sie es in den Modus ARCHIVELOG
, um ein Archive-Log zu erstellen.
- Zeigen Sie den Logmodus für den On-Premise-Server an.
SQL> select log_mode from v$database;
Die Ausgabe sieht ähnlich aus wie folgt, wenn sich der Logmodus imNOARCHIVELOG
-Modus befindet:LOG_MODE ------------ NOARCHIVELOG
- Fahren Sie die On-Premise-Instanz herunter.
SQL> shutdown immediate;
Die Ausgabe sieht wie folgt aus:Database closed. Database dismounted. ORACLE instance shut down.
- Mounten Sie die On-Premise-Datenbank.
SQL> startup mount;
Die Ausgabe sieht wie folgt aus:ORACLE instance started. Total System Global Area 4966054520 bytes Fixed Size 9144952 bytes Variable Size 922746880 bytes Database Buffers 4026531840 bytes Redo Buffers 7630848 bytes Database mounted.
- Ändern Sie das Datenbankarchivlog, und öffnen Sie die Datenbank.
SQL> alter database archivelog;
SQL> alter database open;
- Ändern Sie den Logmodus in
ARCHIVELOG
.SQL> select log_mode from v$database;
LOG_MODE ------------ ARCHIVELOG
- Zeigen Sie die Archive-Logliste an.
SQL> archive log list;
Die Ausgabe sieht wie folgt aus:Database log mode Archive Mode Automatic archival Enabled Archive destination USE_DB_RECOVERY_FILE_DEST Oldest online log sequence 4 Next log sequence to archive 7 Current log sequence 7
- Archivieren Sie alle Logs.
SQL> archive log all;
ORA-00271:there are no logs that need archiving
Standbydatenbank in OCI instanziieren
Instanziieren Sie die Standby-Oracle Database Exadata Cloud Service-Datenbank.
- Stoppen oder Herunterfahren der Oracle Database Exadata Cloud Service-Datenbank mit dem
srvctl
-Utility.-
$ srvctl stop database -d standby DB_UNIQUE_NAME -o immediate
-
$ srvctl stop database -d DB1_phx3g7 -o immediate
-
- Melden Sie sich bei der Datenbank an.
SQL> startup nomount;
- Führen Sie in der primären On-Premise-Oracle Exadata Database Machine die folgenden Befehlsreihen aus, um das Logging zu erzwingen und die Logdatei zu definieren.
SQL> alter database force logging;
SQL> set linesize 500 pages 0 SQL> col value for a90 SQL> col name for a50 SQL> select name, value from v$parameter where name in ('db_name','db_unique_name','log_archive_config', 'log_archive_dest_1','log_archive_dest_2','log_archive_dest_state_1','log_archive_de st_state_2', 'remote_login_passwordfile', 'log_archive_format','log_archive_max_processes','fal_server','db_file_name_convert' ,'log_file_name_convert', 'standby_file_management');
Die Ausgabe sieht wie folgt aus:db_file_name_convert log_file_name_convert log_archive_dest_1 location=USE_DB_RECOVERY_FILE_DEST valid_for=(ALL_LOGFILES,ALL_ROLES) MAX_FAILURE=1 REOPEN =5 DB_UNIQUE_NAME=db1 ALTERNATE=LOG_ARCHIVE_DEST_2 log_archive_dest_2 location=+DATAC1 valid_for=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db1 ALTERNATE=LOG_ARCHI VE_DEST_1 log_archive_dest_state_1 ENABLE log_archive_dest_state_2 ALTERNATE fal_server log_archive_config log_archive_format %t_%s_%r.dbf log_archive_max_processes 4 standby_file_management MANUAL remote_login_passwordfile EXCLUSIVE db_name db1 db_unique_name db1 14 rows selected.
- Legen Sie die Standby-Dateiverwaltung fest.
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO SID='*';
- Definieren Sie in der primären On-Premise-Oracle Exadata Database Machine die folgenden Parameter für Logarchivierung und Standbyverwaltung.
LOG_ARCHIVE_CONFIG='DG_CONFIG=(PROD1,STAND1)' LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PROD1' LOG_ARCHIVE_DEST_2='SERVICE=STAND1 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STAND1' LOG_ARCHIVE_DEST_STATE_1=ENABLE LOG_ARCHIVE_DEST_STATE_2=ENABLE REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE LOG_ARCHIVE_FORMAT=%t_%s_%r.arc LOG_ARCHIVE_MAX_PROCESSES=8 FAL_SERVER=STAND1 DB_FILE_NAME_CONVERT='STAND1',' PROD1' LOG_FILE_NAME_CONVERT= 'STAND1',' PROD1' STANDBY_FILE_MANAGEMENT=AUTO
Das folgende Beispiel enthält die Parameterwerte:ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB1, DB1_phx3g7)'; ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=DB1'; ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=DB1_phx3g7 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DB1_phx3g7’; ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE; ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER; ALTER SYSTEM SET FAL_SERVER=DB1_phx3g7; ALTER SYSTEM SET FAL_CLIENT=DB1; ALTER SYSTEM SET DB_FILE_NAME_CONVERT='DB1_phx3g7','DB1' scope=spfile; ALTER SYSTEM SET LOG_FILE_NAME_CONVERT='DB1_phx3g7','DB1' scope=spfile; ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO;
- Melden Sie sich in der primären On-Premise-Oracle Exadata Database Machine als
sysdba
an, und führen Sie dann die folgenden Befehlsreihen aus, um das Logging zu erzwingen.$ sqlplus / as sysdba
SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB1, DB1_phx3g7)'; System altered. SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=DB1'; System altered. SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=DB1_phx3g7 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DB1_phx3g7'; System altered. SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE; System altered. SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER; System altered. SQL> ALTER SYSTEM SET REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE;
ERROR at line 1: ORA-02095: specified initialization parameter cannot be modified SQL> ALTER SYSTEM SET FAL_SERVER=DB1_phx3g7; System altered. SQL> ALTER SYSTEM SET FAL_CLIENT=DB1; System altered. SQL> ALTER SYSTEM SET DB_FILE_NAME_CONVERT='DB1_phx3g7','DB1' scope=spfile; System altered. SQL> ALTER SYSTEM SET LOG_FILE_NAME_CONVERT= 'DB1_phx3g7','DB1' scope=spfile; System altered. SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO; System altered.
Erstellen Sie keinpfile
in der primären On-Premise-Oracle Exadata Database Machine. Verwenden Sie stattdessen den von Oracle Database Exadata Cloud Service erstellten StandardwertPfile
. - Melden Sie sich in der Standby-Oracle Database Exadata Cloud Service als
sysdba
an, und starten Sie dann die Instanz, ohne die Datenbank mounten zu müssen.$ sqlplus / as sysdba
SQL> startup nomount;
- Führen Sie in der Standby-Oracle Database Exadata Cloud Service die folgenden Befehlsreihen aus, um Server, Logging und Dateiverwaltung zu definieren.
alter system set fal_server='DB1' scope =spfile; alter system set fal_client='DB1_PHX3G7' scope =spfile; alter system set log_archive_config='DG_CONFIG=(DB1, DB1_phx3g7)' scope =spfile; alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=DB1_PHX3G7' scope =spfile; alter system set log_archive_dest_2='SERVICE=DB1 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DB1' scope =spfile; alter system set log_archive_dest_state_1='ENABLE' scope =spfile; alter system set log_archive_dest_state_2='ENABLE' scope =spfile; alter system set log_archive_format='%t_%s_%r.dbf' scope =spfile; alter system set log_file_name_convert='DB1','DB1_phx3g7' scope =spfile; alter system set db_file_name_convert='DB1','DB1_phx3g7' scope =spfile; alter system set remote_login_passwordfile='exclusive' scope =spfile; alter system set standby_file_management='AUTO' scope =spfile;
- Verwenden Sie in der Standby-Oracle Database Exadata Cloud Service Oracle Recovery Manager (RMAN), um ein Testziel und eine Standby-Datenbank in der Cloud zu definieren, und führen Sie RMAN aus, um die Standby-Datenbank zu erstellen.
rman target sys/Test_Dr_123@DB1 auxiliary sys/Test_Dr_123@DB1_Phx3g7
Die Ausgabe sieht in etwa wie folgt aus:connected to target database: DB1 (DBID=1657313530) connected to auxiliary database: DB1 (not mounted)
RMAN> run
- Melden Sie sich in der Standby-Oracle Database Exadata Cloud Service als
sysdba
an, und trennen Sie dann die Verbindung zur Session.$ sqlplus / as sysdba
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
- Zeigen Sie in der Standby-Oracle Database Exadata Cloud Service die Logs an, um zu prüfen, ob sich das Media Recovery im Transit befindet.
[oracle@exacs82-vm3sv1 DB11]$ pwd /u02/app/oracle/diag/rdbms/db1_phx3g7/DB11
[oracle@exacs82-vm3sv1 trace]$ tail -f alert_DB11.log
Die Ausgabe enthält eine Zeile, die der folgenden ähnelt:PR00 (PID:253670): Media Recovery Waiting for T-1.S-125 (in transit)
- Melden Sie sich in der primären On-Premise-Oracle Exadata Database Machine als
sysdba
bei sqlplus an, und führen Sie dann die folgende Reihe von SQL-Befehlen aus, um die Logdatei zu wechseln.$ sqlplus / as sysdba
SQL> alter system switch logfile; SQL> / SQL> / SQL> /
- Melden Sie sich in der Standby-Oracle Database Exadata Cloud Service als
sysdba
an, und führen Sie dann die folgenden Befehlsreihen aus.SQL> SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference" FROM (SELECT THREAD#,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 124 124 0 2 26 26 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 124 124 0 2 26 26 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 130 128 2 2 27 27 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 130 128 2 2 27 27 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 130 130 0 2 28 28 0
- Melden Sie sich in der Standby-Oracle Database Exadata Cloud Service als
sysdba
an, und führen Sie dann die folgenden Befehlsreihen aus.SQL> alter database recover managed standby database cancel;
SQL> show parameter cluster
NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ cdb_cluster boolean FALSE cdb_cluster_name string cluster_database boolean FALSE cluster_database_instances integer 1 cluster_interconnects string 192.0.2.22:192.0.2.23 SQL> alter system set cluster_database=TRUE scope=spfile; System altered.
SQL> alter system set cluster_database=TRUE scope=spfile;
SQL> show parameter cluster;
NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ cdb_cluster boolean FALSE cdb_cluster_name string cluster_database boolean FALSE cluster_database_instances integer 1 cluster_interconnects string 192.0.2.22:192.0.2.23 SQL> / System altered.
SQL> show parameter pluggable;
NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ enable_pluggable_database boolean FALSE SQL> shutdown; ORA-01109: database not open Database dismounted. ORACLE instance shut down.
- Zeigen Sie in der Standby-Oracle Database Exadata Cloud Service den Status der Ressourcen an, und bestätigen Sie, dass sie alle online sind.
[grid@exacs82-vm3sv1 ~]$ crsctl stat res
Die Ausgabe enthält den Typ, den Zielstatus und den Status für jede Ressource. Beispiel:NAME=ora.ASMNET1LSNR_ASM.lsnr(ora.asmgroup) TYPE=ora.asm_listener.type TARGET=ONLINE , ONLINE STATE=ONLINE on exacs82-vm3sv1, ONLINE on exacs82-vm3sv2 NAME=ora.DATAC1.ACFSVOL01.advm TYPE=ora.volume.type TARGET=ONLINE , ONLINE STATE=ONLINE on exacs82-vm3sv1, ONLINE on exacs82-vm3sv2 NAME=ora.DATAC1.dg(ora.asmgroup) TYPE=ora.diskgroup.type TARGET=ONLINE , ONLINE STATE=ONLINE on exacs82-vm3sv1, ONLINE on exacs82-vm3sv2 NAME=ora.LISTENER.lsnr TYPE=ora.listener.type TARGET=ONLINE , ONLINE STATE=ONLINE on exacs82-vm3sv1, ONLINE on exacs82-vm3sv2 . . .
- Starten und mounten Sie die Datenbank in der Standby-Oracle Database Exadata Cloud Service.
[oracle@exacs82-vm3sv1 ~]$ source DB1.env [oracle@exacs82-vm3sv1 ~]$ srvctl start database -db db1_phx3g7 -startoption mount
- Melden Sie sich auf Knoten 1 des Standby-Oracle Database Exadata Cloud Service als
sysdba
an, mounten Sie die Datenbank inopen_mode
, und beenden Sie dann den Vorgang.oracle@exacs82-vm3sv1
SQL> select open_mode from v$database;
Die Ausgabe sieht in etwa wie folgt aus:OPEN_MODE -------------------- MOUNTED
SQL> exit
- Melden Sie sich auf Knoten 2 des Standby-Oracle Database Exadata Cloud Service als
sysdba
an, mounten Sie die Datenbank inopen_mode
, und beenden Sie dann den Vorgang.oracle@exacs82-vm3sv2
SQL> select open_mode from v$database;
Die Ausgabe sieht in etwa wie folgt aus:OPEN_MODE -------------------- MOUNTED
SQL> exit
- Trennen Sie die Verbindung zur Session.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Die Ausgabe sieht in etwa wie folgt aus: - Führen Sie in der primären On-Premise-Oracle Exadata Database Machine die folgenden SQL-Befehlsreihen für die Logdatei aus.
SQL> alter database force logging;
SQL> /
SQL> /
- Melden Sie sich in der Standby-Oracle Database Exadata Cloud Service als
sysdba
an, und führen Sie dann die folgenden Befehlsreihen aus.SQL> SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference" FROM (SELECT THREAD#,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 161 161 0 2 41 41 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 161 161 0 2 41 41 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 161 161 0 2 41 41 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 163 161 2 2 41 41 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 163 161 2 2 41 41 0
SQL> /
Thread Last Sequence Received Last Sequence Applied Difference ---------- ---------------------- --------------------- ---------- 1 163 163 0 2 42 42 0
- Prüfen Sie in der primären On-Premise-Oracle Exadata Database Machine, ob die Datei
tnsnames.ora
ordnungsgemäß für Folgendes konfiguriert ist:
Prüfen SieDB1 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = exa11-scan1)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = db1.us.osc.oracle.com) (INSTANCE_NAME = db12) ) ) DB1_phx3g7 = (DESCRIPTION = (SDU = 65536) (RECV_BUF_SIZE = 134217728) (SEND_BUF_SIZE = 134217728) (ADDRESS_LIST = (CONNECT_TIMEOUT = 3) (RETRY_COUNT = 3) (ADDRESS = (PROTOCOL = TCP)(HOST = 10.255.195.136)(PORT = 1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = DB1_phx3g7.datasubnetactiv.oscphevcn.oraclevcn.com) (UR = A) ) )
tnsnames
für die On-Premise-Datenbank (db1):[oracle@exa11db01 admin]$ tnsping db1
Prüfen SieUsed parameter files: /u01/app/oracle/product/19.0.0.0/dbhome_1/network/admin/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = exa11-scan1)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = db1.us.osc.oracle.com) (INSTANCE_NAME = db11))) OK (0 msec)
tnsnames
für die Oracle Database Exadata Cloud Service-Instanz (DB1_phx3g7):[oracle@exa11db01 admin]$ tnsping DB1_phx3g7
TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 05-FEB-2021 16:19:15 Copyright (c) 1997, 2020, Oracle. All rights reserved. Used parameter files: /u01/app/oracle/product/19.0.0.0/dbhome_1/network/admin/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (SDU = 65536) (RECV_BUF_SIZE = 134217728) (SEND_BUF_SIZE = 134217728) (ADDRESS_LIST = (CONNECT_TIMEOUT = 3) (RETRY_COUNT = 3) (ADDRESS = (PROTOCOL = TCP)(HOST = 10.255.195.136)(PORT = 1521))) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = DB1_phx3g7.datasubnetactiv.oscphevcn.oraclevcn.com) (UR = A))) OK (40 msec)
- Vergewissern Sie sich in der Standby-Oracle Database Exadata Cloud Service, dass die Datei
tnsnames.ora
für Folgendes ordnungsgemäß konfiguriert ist:
Prüfen Siedb1 = (DESCRIPTION = (SDU=65536) (RECV_BUF_SIZE=134217728) (SEND_BUF_SIZE=134217728) (ADDRESS_LIST = (CONNECT_TIMEOUT=3)(RETRY_COUNT=3) (ADDRESS = (PROTOCOL = TCP)(HOST = 10.136.74.18)(PORT = 1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = db1.us.osc.oracle.com) (UR=A) ) ) DB1_phx3g7 = (DESCRIPTION = (SDU = 65536) (RECV_BUF_SIZE = 134217728) (SEND_BUF_SIZE = 134217728) (ADDRESS_LIST = (CONNECT_TIMEOUT = 3) (RETRY_COUNT = 3) (ADDRESS = (PROTOCOL = TCP)(HOST = 10.255.195.136)(PORT = 1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = DB1_phx3g7.datasubnetactiv.oscphevcn.oraclevcn.com) (INSTANCE_NAME = DB12) (UR = A) ) )
tnsnames
für die On-Premise-Datenbank (db1):[oracle@exacs82-vm3sv2 DB1]$ tnsping db1
Prüfen SieTNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 05-FEB-2021 16:34:59 Copyright (c) 1997, 2020, Oracle. All rights reserved. Used parameter files: /u02/app/oracle/product/19.0.0.0/dbhome_5/network/admin/DB1/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (SDU=65536) (RECV_BUF_SIZE=134217728) (SEND_BUF_SIZE=134217728) (ADDRESS_LIST = (CONNECT_TIMEOUT=3)(RETRY_COUNT=3) (ADDRESS = (PROTOCOL = TCP)(HOST = 10.136.74.18)(PORT = 1521))) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = db1.us.osc.oracle.com) (UR=A))) OK (40 msec)
tnsnames
für die Oracle Database Exadata Cloud Service-Instanz (DB1_phx3g7):[oracle@exacs82-vm3sv2 DB1]$ tnsping DB1_phx3g7
TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 05-FEB-2021 16:35:15 Copyright (c) 1997, 2020, Oracle. All rights reserved. Used parameter files: /u02/app/oracle/product/19.0.0.0/dbhome_5/network/admin/DB1/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (SDU = 65536) (RECV_BUF_SIZE = 134217728) (SEND_BUF_SIZE = 134217728) (ADDRESS_LIST = (CONNECT_TIMEOUT = 3) (RETRY_COUNT = 3) (ADDRESS = (PROTOCOL = TCP)(HOST = 10.255.195.136)(PORT = 1521))) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = DB1_phx3g7.datasubnetactiv.oscphevcn.oraclevcn.com) (INSTANCE_NAME = DB12) (UR = A))) OK (0 msec)