Oracle Database Admin/Oracle Database

Oracle Active Data Guard 19c- ADG 구성

다소곳한 직장인 DBA 일생 기록 2025. 3. 31. 14:03

ADG 테스트를 위한 간단한 Single to Single ADG(Active Data Guard) 구성

 

 

 

0. ADG 구성 환경 

  Primary DB Standby DB
hostname choki july
IP 192.168.71.101 192.168.71.102
instance_name(SID) CHOKI RCHOKI
데이터파일 /oracle/oracle_base/oradata
/oracle/oradata
/oracle/oradata_chki
아카이브로그 /arch /arch

 

 

1. [Primary] Logging 설정

  • Force logging, supplemental Logging 설정 수행
col name for a10
col force_logging for a15
col log_mode for a14
select name, force_logging, supplemental_log_data_min, log_mode 
from v$database;
NAME       FORCE_LOGGING   SUPPLEMENTAL_LOG_DATA_MI LOG_MODE
---------- --------------- ------------------------ --------------
CHOKI      YES             YES                      ARCHIVELOG
-- Force Logging 변경
alter database force logging;
-- Supplemental Log 설정
alter database add supplemental log data ;
-- 아카이브 설정 확인
select log_mode from v$database;

 

 

2. [Primary] Standby용 Redolog 생성

  • 역활 전환 시(switchover) 사용함.
-- RAC redologfile 확인
set lines 200 pages 1000
col member for a70
col status for a15
select thread#, l.group#, member, l.archived, l.status, (bytes/1024/1024) MB
from v$log l, v$logfile f
where f.group# = l.group#
order by 1, 2
;

   THREAD#     GROUP# MEMBER                                                                 ARCHIVED  STATUS                  MB
---------- ---------- ---------------------------------------------------------------------- --------- --------------- ----------
         1          1 /oracle/oracle_base/oradata/CHOKI/onlinelog/o1_mf_1_mo8pznhk_.log      YES       INACTIVE               100
         1          2 /oracle/oracle_base/oradata/CHOKI/onlinelog/o1_mf_2_mo8pzod6_.log      NO        CURRENT                100
         1          3 /oracle/oracle_base/oradata/CHOKI/onlinelog/o1_mf_3_mo8pzpjl_.log      YES       INACTIVE               100



-- standby용 redologfile 확인
set lines 200 pages 1000
col member for a60
select thread#, l.group#, member, archived, l.status, (bytes/1024/1024) MB
from v$standby_log l, v$logfile f
where f.group# = l.group#
order by 1, 2
;

ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 31 ('/oracle/oracle_base/oradata/CHOKI/onlinelog/redostd01.log') SIZE 100m;
ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 32 ('/oracle/oracle_base/oradata/CHOKI/onlinelog/redostd02.log') SIZE 100m;
ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 33 ('/oracle/oracle_base/oradata/CHOKI/onlinelog/redostd03.log') SIZE 100m;
ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 34 ('/oracle/oracle_base/oradata/CHOKI/onlinelog/redostd04.log') SIZE 100m;

 

 

3. [Standby] adump 디렉토리 생성

  • Primary와 동일하게 audit_file_dest 생성 필요.
  • Standby DB nomount 기동 시 audit_file_dest 경로가 있어야 에러 없이 기동됨.
-- [Primary] 파라미터 경로 확인
SQL> show parameter audit
audit_file_dest : /oracle/oracle_base/admin/CHOKI/adump

-- [standby]에서 디렉토리 생성 /oracle/admin/$ORACLE_UNIQUE_NAME/adump
su - oracle
mkdir -p /oracle/oracle_base/admin/RCHOKI/adump

 

 

4. [Primary] DB 설정파일 복사

  • wallet 파일, 패스워드 파일, init파라미터파일 등을 standby로 전송 
  • (*주의*) 패스워드 파일인 경우 선 COPY / 후 RENAME
scp initCHOKI.ora oracle@192.168.71.102:/oracle/app/product/19c/dbs/
scp orapwCHOKI oracle@192.168.71.102:/oracle/app/product/19c/dbs/


mv orapwCHOKI orapwRCHOKI
cp initCHOKI.ora initRCHOKI.ora

 

 

5. [Standby] 정적 리스너 생성

  • rman duplicate 및 데이터 sync 동기화를 위한 redo/archive 전송을 위한 리스너 생성
cd $ORACLE_HOME/network/admin

vi listener.ora
-- 아래의 내용 추가 
------------------------------------------------------------------------
LISTENER_ADG =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.71.102)(PORT = 1525))
    )
  )

SID_LIST_LISTENER_ADG =
  (SID_LIST =
    (SID_DESC =
      (ORACLE_HOME=/oracle/app/product/19c)
      (SID_NAME=RCHOKI)
    )
  )
------------------------------------------------------------------------

-- 리스너 기동 
lsnrctl start LISTENER_ADG

 

 

6. [Standby] tnsnames.ora 수정

cd $ORACLE_HOME/network/admin

vi tnsnames.ora
-- 아래 내용 추가 
---------------------------------------------------------------------- 
CHOKI =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.71.101)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = CHOKI)
    )
  )
----------------------------------------------------------------------

-- tnsping 테스트 
tnsping CHOKI
-- 접속 테스트
sqlplus system/oracle@CHOKI

 

 

7. [Primary] tnsnames.ora 수정 

cd $ORACLE_HOME/network/admin

vi tnsnames.ora
-- 아래 내용 추가 
----------------------------------------------------------------------
RCHOKI =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.71.102)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = CHOKI)
    )
  )
----------------------------------------------------------------------

-- tnsping
tnsping RCHOKI

 

 

8. [Primary] ADG 파라미터 설정

 

  • 파라미터 내용

log_archive_config : redo전송 및 수신을 허용할 DB목록
log_archive_dest_2 : 2
 - LGWR : redo전송 시 lgwr 프로세스 사용, redolog 기록시점에 바로 전송됨. 
- ASYNC : 비동기방식으로 redolog 전송
standby_file_management : Standby DB 데이터 파일을 자동으로 관리할지 여부를 제어
fal_server : FAL(fetch archive log) 아카이브로그를 요청할 대상
fal_client : FAL(fetch archive log) 아카이브 요청을 보내는 자기자신 DB명

 

alter system set log_archive_dest_state_2='DEFER' sid='*';
alter system set log_archive_config='dg_config=(CHOKI,RCHOKI)' scope=both sid='*';
alter system set log_archive_dest_1='location=/arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES)' scope=both sid='*';
alter system set log_archive_dest_2='SERVICE=RCHOKI LGWR ASYNC VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=RCHOKI REOPEN' scope=both sid='*';
alter system set standby_file_management='auto' scope=both sid='*';
alter system set fal_server='RCHOKI' scope=both sid='*';
alter system set fal_client='CHOKI' scope=both sid='*';

 

 

9. [Standby] 파라미터 설정

  • pfile 내용 수정
cd $ORACLE_HOME/dbs

vi initRCHOKI.ora
-- 내용수정 및 추가 
------------------------------------------------
*.db_recovery_file_dest=/arch
*.db_recovery_file_dest_size=50G
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=RCHOKI'
*.log_archive_dest_2='SERVICE=CHOKI LGWR ASYNC VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=CHOKI REOPEN'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable' 
*.standby_file_management='auto'
*.DB_FILE_NAME_CONVERT='/oracle/oracle_base/oradata/CHOKI/datafile','/oracle/oradata_chki','/oracle/oradata/CHOKI','/oracle/oradata_chki'
*.LOG_FILE_NAME_CONVERT='/oracle/oracle_base/oradata/CHOKI/onlinelog','/oracle/oradata_chki'
*.fal_server='CHOKI'
*.fal_client='RCHOKI'
*.log_archive_config='dg_config=(RCHOKI,CHOKI)'
*.db_unique_name='RCHOKI'

 

  • DB nomount 기동
sqlplus / as sysdba
startup nomount pfile='/oracle/app/product/19c/dbs/initRCHOKI.ora'

 

 

 

10. [Primary/Standby] RMAN duplication

 

  • rman을 이용한 데이터 초기 복제 수행
-- standby 
rman target sys/oracle@CHOKI  auxiliary sys/oracle@RCHOKI
-- primary
rman target sys/oracle  auxiliary sys/oracle@RCHOKI

run {
allocate channel prmy1 type disk rate 100M  ;
allocate channel prmy2 type disk rate 100M  ;
allocate channel prmy3 type disk rate 100M  ;
allocate channel prmy4 type disk rate 100M  ;
allocate auxiliary channel stby1 type disk      ;
allocate auxiliary channel stby2 type disk      ;
allocate auxiliary channel stby3 type disk      ;
allocate auxiliary channel stby4 type disk      ;
duplicate target database for standby from active database;
RELEASE CHANNEL prmy1;
RELEASE CHANNEL prmy2;
RELEASE CHANNEL prmy3;
RELEASE CHANNEL prmy4;
}
EXIT;

 

 

 

 

11.  [Primary/Standby]  ADG SYNC 및 Archivelog 전송

  • Rman 복제 이후 Redolog 전송하여 적용
-- (Primary) 아카이브 전송 활성화
alter system set log_archive_dest_state_2='ENABLE' sid='*' scope=both;

 

  • [Standby] start redo apply (한 노드씩 수행) Arch, redo 적용 mrp 프로세스 기동
SELECT DATABASE_ROLE, OPEN_MODE, PROTECTION_MODE, PROTECTION_LEVEL 
FROM V$DATABASE;

DATABASE_ROLE    OPEN_MODE            PROTECTION_MODE      PROTECTION_LEVEL
---------------- -------------------- -------------------- --------------------
PHYSICAL STANDBY MOUNTED              MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE


alter database recover managed standby database disconnect from session;

SQL> alter database recover managed standby database disconnect from session;

Database altered.

SELECT PROCESS, STATUS, THREAD#, SEQUENCE#
FROM V$MANAGED_STANDBY
WHERE PROCESS IN ('RFS', 'MRP0');


PROCESS   STATUS          THREAD#  SEQUENCE#
--------- ------------ ---------- ----------
RFS       IDLE                  1          0
RFS       IDLE                  1         36
RFS       IDLE                  0          0
MRP0      APPLYING_LOG          1         36	----> mrp 확인

-- ADG apply lag 조회
col value for a20
SELECT SOURCE_DBID,SOURCE_DB_UNIQUE_NAME,TIME_COMPUTED,  name, value, unit
FROM V$DATAGUARD_STATS ;


SOURCE_DBID SOURCE_DB_UNIQUE_NAME            TIME_COMPUTED                  NAME                             VALUE                UNIT
----------- -------------------------------- ------------------------------ -------------------------------- -------------------- ------------------------------
 1926381892 CHOKI                            06/03/2025 17:13:04            transport lag                    +00 00:00:00         day(2) to second(0) interval
 1926381892 CHOKI                            06/03/2025 17:13:04            apply lag                        +00 00:00:00         day(2) to second(0) interval
 1926381892 CHOKI                            06/03/2025 17:13:04            apply finish time                                     day(2) to second(3) interval
          0                                  06/03/2025 17:13:04            estimated startup time           22                   second

 

 

12. ADG 기동

  • MOUNT 모드에서 READ-ONLY WITH APPLY 모드로 변경 
-- Cancel apply process Archive, redo 적용중지
alter database recover managed standby database cancel;

-- real-time READ ONLY로 redo apply
alter database open;


-- mrp 프로세스 기동 실시간 apply 로 변경 
alter database recover managed standby database using current logfile disconnect from session ;


-- READ ONLY WITH APPLY 로 변경 확인
SELECT DATABASE_ROLE, OPEN_MODE, PROTECTION_MODE, PROTECTION_LEVEL
FROM V$DATABASE;

DATABASE_ROLE    OPEN_MODE            PROTECTION_MODE      PROTECTION_LEVEL
---------------- -------------------- -------------------- --------------------
PHYSICAL STANDBY READ ONLY WITH APPLY MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE

 

 

{참조}  alertlog 내용

  • rman duplicate 로그
더보기
더보기

RMAN> run {
allocate channel prmy1 type disk rate 100M  ;
allocate channel prmy2 type disk rate 100M  ;
allocate channel prmy3 type disk rate 100M  ;
allocate channel prmy4 type disk rate 100M  ;
allocate auxiliary channel stby1 type disk      ;
allocate auxiliary channel stby2 type disk      ;
allocate auxiliary channel stby3 type disk      ;
allocate auxiliary channel stby4 type disk      ;
duplicate target database for standby from active database;
RELEASE CHANNEL prmy1;
RELEASE CHANNEL prmy2;
RELEASE CHANNEL prmy3;
RELEASE CHANNEL prmy4;
}
EXIT;2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15>
using target database control file instead of recovery catalog
allocated channel: prmy1
channel prmy1: SID=406 device type=DISK

allocated channel: prmy2
channel prmy2: SID=779 device type=DISK

allocated channel: prmy3
channel prmy3: SID=1164 device type=DISK

allocated channel: prmy4
channel prmy4: SID=19 device type=DISK

allocated channel: stby1
channel stby1: SID=771 device type=DISK

allocated channel: stby2
channel stby2: SID=1153 device type=DISK

allocated channel: stby3
channel stby3: SID=13 device type=DISK

allocated channel: stby4
channel stby4: SID=392 device type=DISK

Starting Duplicate Db at 03-JUN-25

contents of Memory Script:
{
   backup as copy reuse
   passwordfile auxiliary format  '/oracle/app/product/19c/dbs/orapwRCHOKI'   ;
}
executing Memory Script

Starting backup at 03-JUN-25
Finished backup at 03-JUN-25

contents of Memory Script:
{
   sql clone "create spfile from memory";
   shutdown clone immediate;
   startup clone nomount;
   restore clone from service  'CHOKI' standby controlfile;
}
executing Memory Script

sql statement: create spfile from memory

Oracle instance shut down

connected to auxiliary database (not started)
Oracle instance started

Total System Global Area    2147481656 bytes

Fixed Size                     8898616 bytes
Variable Size                486539264 bytes
Database Buffers            1644167168 bytes
Redo Buffers                   7876608 bytes
allocated channel: stby1
channel stby1: SID=391 device type=DISK
allocated channel: stby2
channel stby2: SID=771 device type=DISK
allocated channel: stby3
channel stby3: SID=1144 device type=DISK
allocated channel: stby4
channel stby4: SID=10 device type=DISK

Starting restore at 03-JUN-25

channel stby1: starting datafile backup set restore
channel stby1: using network backup set from service CHOKI
channel stby1: restoring control file
channel stby1: restore complete, elapsed time: 00:00:02
output file name=/oracle/oradata/controlfile/o1_mf_mo8pznbg_.ctl
Finished restore at 03-JUN-25

contents of Memory Script:
{
   sql clone 'alter database mount standby database';
}
executing Memory Script

sql statement: alter database mount standby database

contents of Memory Script:
{
   set newname for tempfile  1 to
 "/oracle/oradata_chki/o1_mf_temp_mo8q0gr6_.tmp";
   switch clone tempfile all;
   set newname for datafile  1 to
 "/oracle/oradata_chki/o1_mf_system_mo8pzwcz_.dbf";
   set newname for datafile  2 to
 "/oracle/oradata_chki/o1_mf_sysaux_mo8q05dj_.dbf";
   set newname for datafile  3 to
 "/oracle/oradata_chki/o1_mf_undotbs1_mo8q0ds8_.dbf";
   set newname for datafile  4 to
 "/oracle/oradata_chki/o1_mf_users_mo8q0shn_.dbf";
   set newname for datafile  5 to
 "/oracle/oradata_chki/ogg01.dbf";
   restore
   from  nonsparse   from service
 'CHOKI'   clone database
   ;
   sql 'alter system archive log current';
}
executing Memory Script

executing command: SET NEWNAME

renamed tempfile 1 to /oracle/oradata_chki/o1_mf_temp_mo8q0gr6_.tmp in control file

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 03-JUN-25

channel stby1: starting datafile backup set restore
channel stby1: using network backup set from service CHOKI
channel stby1: specifying datafile(s) to restore from backup set
channel stby1: restoring datafile 00001 to /oracle/oradata_chki/o1_mf_system_mo8pzwcz_.dbf
channel stby2: starting datafile backup set restore
channel stby2: using network backup set from service CHOKI
channel stby2: specifying datafile(s) to restore from backup set
channel stby2: restoring datafile 00002 to /oracle/oradata_chki/o1_mf_sysaux_mo8q05dj_.dbf
channel stby3: starting datafile backup set restore
channel stby3: using network backup set from service CHOKI
channel stby3: specifying datafile(s) to restore from backup set
channel stby3: restoring datafile 00003 to /oracle/oradata_chki/o1_mf_undotbs1_mo8q0ds8_.dbf
channel stby4: starting datafile backup set restore
channel stby4: using network backup set from service CHOKI
channel stby4: specifying datafile(s) to restore from backup set
channel stby4: restoring datafile 00004 to /oracle/oradata_chki/o1_mf_users_mo8q0shn_.dbf
channel stby4: restore complete, elapsed time: 00:00:15
channel stby4: starting datafile backup set restore
channel stby4: using network backup set from service CHOKI
channel stby4: specifying datafile(s) to restore from backup set
channel stby4: restoring datafile 00005 to /oracle/oradata_chki/ogg01.dbf
channel stby4: restore complete, elapsed time: 00:00:08
channel stby1: restore complete, elapsed time: 00:01:02
channel stby2: restore complete, elapsed time: 00:01:02
channel stby3: restore complete, elapsed time: 00:01:02
Finished restore at 03-JUN-25

sql statement: alter system archive log current

contents of Memory Script:
{
   switch clone datafile all;
}
executing Memory Script

datafile 1 switched to datafile copy
input datafile copy RECID=1 STAMP=1202833725 file name=/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_system_n3x8zhly_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=2 STAMP=1202833725 file name=/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_sysaux_n3x8zln8_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=3 STAMP=1202833725 file name=/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_undotbs1_n3x8zm27_.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=4 STAMP=1202833725 file name=/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_users_n3x8zl4q_.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=5 STAMP=1202833725 file name=/oracle/oradata_chki/ogg01.dbf
Finished Duplicate Db at 03-JUN-25

released channel: prmy1

released channel: prmy2

released channel: prmy3

released channel: prmy4
released channel: stby1
released channel: stby2
released channel: stby3
released channel: stby4

 

 

  • rman duplicate standbyDB alertlog
더보기
더보기


2025-06-03T16:27:04.362798+09:00
Stopping background process MMON
2025-06-03T16:27:06.827268+09:00
License high water mark = 7
2025-06-03T16:27:06.860659+09:00
Dispatchers and shared servers shutdown

Data Pump shutdown on PDB: 0 in progress
alter database close
ORA-1507 signalled during: alter database close...
alter database dismount
ORA-1507 signalled during: alter database dismount...
.... (PID:10574): Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
2025-06-03T16:27:07.971259+09:00

IM on ADG: Start of Empty Journal

IM on ADG: End of Empty Journal
JIT: pid 10574 requesting stop
.... (PID:10574): Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
2025-06-03T16:27:07.975230+09:00
Stopping background process VKTM
2025-06-03T16:27:08.001825+09:00
JIT: pid 10574 requesting stop
2025-06-03T16:27:23.570295+09:00
Instance shutdown complete (OS id: 10574)
2025-06-03T16:27:26.043900+09:00
Starting ORACLE instance (normal) (OS id: 10625)
2025-06-03T16:27:26.049474+09:00
****************************************************
 Sys-V shared memory will be used for creating SGA
 ****************************************************
2025-06-03T16:27:26.049987+09:00
**********************************************************************
2025-06-03T16:27:26.050056+09:00
Dump of system resources acquired for SHARED GLOBAL AREA (SGA)

2025-06-03T16:27:26.050220+09:00
 Per process system memlock (soft) limit = 128G
2025-06-03T16:27:26.050258+09:00
 Expected per process system memlock (soft) limit to lock
 instance MAX SHARED GLOBAL AREA (SGA) into memory: 2050M
2025-06-03T16:27:26.050378+09:00
 Available system pagesizes:
  4K, 2048K
2025-06-03T16:27:26.050521+09:00
 Supported system pagesize(s):
2025-06-03T16:27:26.050584+09:00
  PAGESIZE  AVAILABLE_PAGES  EXPECTED_PAGES  ALLOCATED_PAGES  ERROR(s)
2025-06-03T16:27:26.050642+09:00
        4K       Configured               4          524292        NONE
2025-06-03T16:27:26.050778+09:00
     2048K                0            1025               0        NONE
2025-06-03T16:27:26.050852+09:00
RECOMMENDATION:
2025-06-03T16:27:26.050900+09:00
 1. For optimal performance, configure system with expected number
 of pages for every supported system pagesize prior to the next
 instance restart operation.
2025-06-03T16:27:26.052999+09:00
**********************************************************************
2025-06-03T16:27:29.179087+09:00
PGA_AGGREGATE_TARGET specified is high
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_o                                                                              ra_10625.trc  (incident=40007):
ORA-00700: soft internal error, arguments: [pga physmem limit], [10737418                                                                              24], [779238195], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/oracle_base/diag/rdbms/choki/RCHOKI/incident                                                                              /incdir_40007/RCHOKI_ora_10625_i40007.trc
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
2025-06-03T16:27:29.674512+09:00
Initial number of CPU is 4
Number of processor cores in the system is 4
Number of processor sockets in the system is 1
_ksb_restart_policy_times={0,60,120,240}
Capability Type : Network
capabilities requested : 7 detected : 0 Simulated : 0
Capability Type : Runtime Environment
capabilities requested : 400000FF detected : 40000000 Simulated : 0
Capability Type : Engineered Systems
capabilities requested : 7 detected : 0 Simulated : 0
Capability Type : Database Test
capabilities requested : 3 detected : 0 Simulated : 0
Autotune of undo retention is turned on.
IMODE=BR
ILAT =167
LICENSE_MAX_USERS = 0
SYS auditing is enabled
NOTE: remote asm mode is local (mode 0x1; from cluster type)
NOTE: Using default ASM root directory ASM
NOTE: remote asm mode is local (mode 0x1; from cluster type)
NOTE: Cluster configuration type = NONE [2]
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0.
ORACLE_HOME:    /oracle/app/product/19c
System name:    Linux
Node name:      july
Release:        5.4.17-2102.201.3.el7uek.x86_64
Version:        #2 SMP Fri Apr 23 09:05:55 PDT 2021
Machine:        x86_64
Using parameter settings in server-side spfile /oracle/app/product/19c/db                                                                              s/spfileRCHOKI.ora
System parameters with non-default values:
  processes                = 1000
  cpu_count                = 4
  cpu_min_count            = "4"
  _ksb_restart_policy_times= "0"
  _ksb_restart_policy_times= "60"
  _ksb_restart_policy_times= "120"
  _ksb_restart_policy_times= "240"
  nls_language             = "AMERICAN"
  nls_territory            = "AMERICA"
  sga_target               = 2G
  control_files            = "/oracle/oradata/controlfile/o1_mf_mo8pznbg_                                                                              .ctl"
  db_file_name_convert     = "/oracle/oracle_base/oradata/CHOKI/datafile"
  db_file_name_convert     = "/oracle/oradata_chki"
  db_file_name_convert     = "/oracle/oradata/CHOKI"
  db_file_name_convert     = "/oracle/oradata_chki"
  log_file_name_convert    = "/oracle/oracle_base/oradata/CHOKI/onlinelog                                                                              /"
  log_file_name_convert    = "/oracle/oradata_chki"
  db_block_size            = 8192
  compatible               = "19.0.0"
  log_archive_dest_1       = "LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FO                                                                              R=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=RCHOKI"
  log_archive_dest_2       = "SERVICE=CHOKI LGWR ASYNC VALID_FOR=(ONLINE_                                                                              LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=CHOKI REOPEN"
  log_archive_dest_state_1 = "enable"
  log_archive_dest_state_2 = "enable"
  log_buffer               = 7360K
  db_create_file_dest      = "/oracle/oracle_base/oradata"
  db_recovery_file_dest    = "/arch"
  db_recovery_file_dest_size= 50G
  standby_file_management  = "auto"
  enable_goldengate_replication= TRUE
  undo_tablespace          = "UNDOTBS1"
  _compression_compatibility= "19.0.0"
  remote_login_passwordfile= "EXCLUSIVE"
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=CHOKIXDB)"
  connection_brokers       = "((TYPE=DEDICATED)(BROKERS=1))"
  connection_brokers       = "((TYPE=EMON)(BROKERS=1))"
  local_listener           = "(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.                                                                              71.102)(PORT = 1521)),(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.71.102)(                                                                              PORT = 1525))"
  plsql_warnings           = "DISABLE:ALL"
  result_cache_max_size    = 10496K
  _key_vector_create_pushdown_threshold= 20000
  core_dump_dest           = "/oracle/oracle_base/diag/rdbms/choki/RCHOKI                                                                              /cdump"
  audit_file_dest          = "/oracle/oracle_base/admin/RCHOKI/adump"
  audit_trail              = "DB"
  db_name                  = "CHOKI"
  open_cursors             = 300
  optimizer_mode           = "ALL_ROWS"
  _optimizer_mode_force    = TRUE
  _always_anti_join        = "CHOOSE"
  _b_tree_bitmap_plans     = TRUE
  _optimizer_extended_cursor_sharing= "UDO"
  _optimizer_extended_cursor_sharing_rel= "SIMPLE"
  _optimizer_cost_model    = "CHOOSE"
  _optimizer_system_stats_usage= TRUE
  _new_sort_cost_estimate  = TRUE
  _complex_view_merging    = TRUE
  _unnest_subquery         = TRUE
  _eliminate_common_subexpr= TRUE
  _pred_move_around        = TRUE
  _optimizer_cost_based_transformation= "LINEAR"
  _push_join_predicate     = TRUE
  _push_join_union_view    = TRUE
  _push_join_union_view2   = TRUE
  _fast_full_scan_enabled  = TRUE
  _optim_enhance_nnull_detection= TRUE
  _parallel_broadcast_enabled= TRUE
  _always_semi_join        = "CHOOSE"
  _ordered_nested_loop     = TRUE
  _optimizer_max_permutations= 2000
  _nlj_batching_enabled    = 1
  query_rewrite_enabled    = "TRUE"
  _left_nested_loops_random= TRUE
  _improved_row_length_enabled= TRUE
  _index_join_enabled      = TRUE
  _improved_outerjoin_card = TRUE
  _use_column_stats_for_function= TRUE
  _subquery_pruning_mv_enabled= FALSE
  _or_expand_nvl_predicate = TRUE
  _table_scan_cost_plus_one= TRUE
  _new_initial_join_orders = TRUE
  _optim_peek_user_binds   = TRUE
  pga_aggregate_target     = 1G
  _gs_anti_semi_join_allowed= TRUE
  _union_rewrite_for_gs    = "YES_GSET_MVS"
  _generalized_pruning_enabled= TRUE
  _ds_xt_split_count       = 1
  _optimizer_join_order_control= 3
  _bloom_serial_filter     = "ON"
  _sql_model_unfold_forloops= "RUN_TIME"
  _optimizer_better_inlist_costing= "ALL"
  _optimizer_or_expansion  = "DEPTH"
  _optimizer_native_full_outer_join= "FORCE"
  _pivot_implementation_method= "CHOOSE"
  _optimizer_extended_stats_usage_control= 192
  _optimizer_use_cbqt_star_transformation= TRUE
  _optimizer_try_st_before_jppd= TRUE
  _px_groupby_pushdown     = "FORCE"
  _px_wif_dfo_declumping   = "CHOOSE"
  _px_partial_rollup_pushdown= "ADAPTIVE"
  _optimizer_proc_rate_level= "BASIC"
  _optimizer_cluster_by_rowid_control= 129
  _optimizer_cbqt_or_expansion= "ON"
  _mv_access_compute_fresh_data= "ON"
  _optimizer_ads_use_partial_results= TRUE
  _px_dist_agg_partial_rollup_pushdown= "ADAPTIVE"
  _xt_sampling_scan_granules= "ON"
  _optimizer_control_shard_qry_processing= 65528
  _px_shared_hash_join     = FALSE
  diagnostic_dest          = "/oracle/oracle_base"
  _diag_adr_trace_dest     = "/oracle/oracle_base/diag/rdbms/choki/RCHOKI                                                                              /trace"
2025-06-03T16:27:29.988361+09:00
============================================================
NOTE: PatchLevel of this instance 0
============================================================
2025-06-03T16:27:30.910281+09:00
Starting background process PMON
2025-06-03T16:27:30.920474+09:00
PMON started with pid=2, OS id=10634
Starting background process CLMN
2025-06-03T16:27:30.928653+09:00
CLMN started with pid=3, OS id=10636
Starting background process PSP0
2025-06-03T16:27:30.937598+09:00
PSP0 started with pid=4, OS id=10638
Starting background process VKTM
2025-06-03T16:27:31.978127+09:00
VKTM started with pid=5, OS id=10641 at elevated (RT) priority
2025-06-03T16:27:31.978214+09:00
Starting background process GEN0
2025-06-03T16:27:31.979260+09:00
VKTM running at (1)millisec precision with DBRM quantum (100)ms
2025-06-03T16:27:31.984791+09:00
GEN0 started with pid=6, OS id=10645
Starting background process MMAN
2025-06-03T16:27:31.991595+09:00
MMAN started with pid=7, OS id=10647
Starting background process GEN1
2025-06-03T16:27:32.014283+09:00
GEN1 started with pid=9, OS id=10651_10652
Starting background process DIAG
2025-06-03T16:27:32.025707+09:00
DIAG started with pid=11, OS id=10654
Starting background process OFSD
2025-06-03T16:27:32.027192+09:00
Dumping diagnostic data in directory=[cdmp_20250603162732], requested by                                                                               (instance=1, osid=10625), summary=[incident=40007].
2025-06-03T16:27:32.040709+09:00
OFSD started with pid=12, OS id=10656_10657
Starting background process DBRM
2025-06-03T16:27:32.041651+09:00
Oracle running with ofslib:'Oracle File Server Library' version=2
2025-06-03T16:27:32.051795+09:00
DBRM started with pid=14, OS id=10659
Starting background process VKRM
2025-06-03T16:27:32.062410+09:00
VKRM started with pid=15, OS id=10661
Starting background process SVCB
2025-06-03T16:27:32.069005+09:00
SVCB started with pid=16, OS id=10663
Starting background process PMAN
2025-06-03T16:27:32.076069+09:00
PMAN started with pid=17, OS id=10665
Starting background process DIA0
2025-06-03T16:27:32.086014+09:00
DIA0 started with pid=18, OS id=10667
Starting background process DBW0
2025-06-03T16:27:32.096014+09:00
DBW0 started with pid=19, OS id=10669
Starting background process LGWR
2025-06-03T16:27:32.104133+09:00
LGWR started with pid=20, OS id=10671
Starting background process CKPT
2025-06-03T16:27:32.112450+09:00
CKPT started with pid=21, OS id=10673
Starting background process SMON
2025-06-03T16:27:32.120989+09:00
LGWR slave LG00 created with pid=22, OS pid=10675
2025-06-03T16:27:32.129706+09:00
SMON started with pid=23, OS id=10677
LGWR slave LG01 created with pid=24, OS pid=10679
Starting background process SMCO
2025-06-03T16:27:32.151099+09:00
SMCO started with pid=25, OS id=10681
Starting background process RECO
2025-06-03T16:27:32.160485+09:00
RECO started with pid=26, OS id=10683
Starting background process LREG
2025-06-03T16:27:32.180226+09:00
LREG started with pid=28, OS id=10687
Starting background process PXMN
2025-06-03T16:27:32.205290+09:00
PXMN started with pid=30, OS id=10691
Starting background process FENC
2025-06-03T16:27:32.216592+09:00
FENC started with pid=31, OS id=10693
Starting background process MMON
2025-06-03T16:27:32.226939+09:00
MMON started with pid=32, OS id=10695
Starting background process MMNL
2025-06-03T16:27:32.237040+09:00
MMNL started with pid=33, OS id=10697
2025-06-03T16:27:32.237096+09:00
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(P                                                                              ROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Starting background process TMON
2025-06-03T16:27:32.270530+09:00
TMON started with pid=35, OS id=10703
ORACLE_BASE from environment = /oracle/oracle_base
2025-06-03T16:27:35.097840+09:00
PGA_AGGREGATE_LIMIT specified is high
2025-06-03T16:27:35.098009+09:00
WARNING: pga_aggregate_limit value is too high for the
amount of physical memory on the system
  PGA_AGGREGATE_LIMIT is 3000 MB
  PGA_AGGREGATE_TARGET is 1024 MB.
  physical memory size is 3926 MB
  limit based on physical memory and SGA usage is 1486 MB
  SGA_TARGET is 2048 MB
Using default pga_aggregate_limit of 3000 MB
2025-06-03T16:27:37.142600+09:00
Conversion to standby controlfile pending for restored file
No controlfile conversion
2025-06-03T16:27:38.087878+09:00
RFS connections have been disallowed
alter database mount standby database
2025-06-03T16:27:42.259340+09:00
Converting controlfile to standby
If db_file_name_convert or log_file_name_convert parameters
are not used, then RMAN intervention is required to fix the
file names in the converted control file. Refer to RMAN
documentation for how to fix all file names.
Clearing standby activation ID 1926380356 (0x72d23b44)
The primary database controlfile was created using the
'MAXLOGFILES 40' clause.
There is space for up to 37 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 104857600;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 104857600;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 104857600;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 104857600;
WARNING: OMF is enabled on this database. Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames.
.... (PID:10708): RT: Role transition work is not done
**********************************************************************
WARNING: The LOG_ARCHIVE_CONFIG parameter has NOT been defined but
remote Data Guard destinations have been configured.  Oracle strongly
recommends that this parameter is set when using Data Guard as
described in the Data Guard manuals.
**********************************************************************
.... (PID:10708): Redo network throttle feature is disabled at mount time
2025-06-03T16:27:42.429263+09:00
Successful mount of redo thread 1, with mount id 1942063418
2025-06-03T16:27:42.429624+09:00
.... (PID:10708): Database role set to PHYSICAL STANDBY [kcvfdb.c:9076]
Physical Standby Database mounted.
.... (PID:10708): STARTING ARCH PROCESSES
Starting background process ARC0
2025-06-03T16:27:42.452301+09:00
ARC0 started with pid=42, OS id=10732
.... (PID:10708): ARC0: Archival started
.... (PID:10708): STARTING ARCH PROCESSES COMPLETE
2025-06-03T16:27:42.462693+09:00
ARC0 (PID:10732): Becoming a 'no FAL' ARCH
2025-06-03T16:27:42.462863+09:00
In-memory operation on ADG is currently only supported on Engineered syst                                                                              ems and PaaS.
inmemory_adg_enabled is turned off automatically.
Please contact our support team for EXADATA solutions
Lost write protection disabled
.... (PID:10708): Using STANDBY_ARCHIVE_DEST parameter default value as U                                                                              SE_DB_RECOVERY_FILE_DEST [krsd.c:18157]
2025-06-03T16:27:42.473691+09:00
TT00 (PID:10734): Gap Manager starting
2025-06-03T16:27:42.491720+09:00
TMON (PID:10703): STARTING ARCH PROCESSES
Starting background process ARC1
2025-06-03T16:27:42.500051+09:00
ARC1 started with pid=45, OS id=10738
Starting background process ARC2
2025-06-03T16:27:42.511482+09:00
ARC2 started with pid=46, OS id=10740
Starting background process ARC3
2025-06-03T16:27:42.522579+09:00
ARC3 started with pid=47, OS id=10742
TMON (PID:10703): ARC1: Archival started
TMON (PID:10703): ARC2: Archival started
Create Relation IPS_PACKAGE_UNPACK_HISTORY
TMON (PID:10703): ARC3: Archival started
TMON (PID:10703): STARTING ARCH PROCESSES COMPLETE
2025-06-03T16:27:42.689901+09:00
Archiving previously deferred ORLs (RCHOKI)
Completed: alter database mount standby database
2025-06-03T16:27:44.243604+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle/oradata_chkio1_mf_1_mo8pznhk_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.243738+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle/oradata_chkio1_mf_1_mo8pznhk_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.244270+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oracle/oradata_chkio1_mf_2_mo8pzod6_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.244429+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oracle/oradata_chkio1_mf_2_mo8pzod6_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.244864+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.244974+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.247112+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 31 of thread 1
ORA-00312: online log 31 thread 1: '/oracle/oradata_chkiredostd01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.247290+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 31 of thread 1
ORA-00312: online log 31 thread 1: '/oracle/oradata_chkiredostd01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.247694+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 32 of thread 1
ORA-00312: online log 32 thread 1: '/oracle/oradata_chkiredostd02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.247803+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 32 of thread 1
ORA-00312: online log 32 thread 1: '/oracle/oradata_chkiredostd02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.248318+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 33 of thread 1
ORA-00312: online log 33 thread 1: '/oracle/oradata_chkiredostd03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.253649+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 33 of thread 1
ORA-00312: online log 33 thread 1: '/oracle/oradata_chkiredostd03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.254164+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 34 of thread 1
ORA-00312: online log 34 thread 1: '/oracle/oradata_chkiredostd04.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.254285+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_l                                                                              gwr_10671.trc:
ORA-00313: open failed for members of log group 34 of thread 1
ORA-00312: online log 34 thread 1: '/oracle/oradata_chkiredostd04.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.634116+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00312: online log 1 thread 1: '/oracle/oradata_chkio1_mf_1_mo8pznhk_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.803992+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle/oradata_chkio1_mf_1_mo8pznhk_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:44.866950+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle/oradata_chkio1_mf_1_mo8pznhk_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:51.634834+09:00
Full restore complete of datafile 4 /oracle/oracle_base/oradata/CHOKI/dat                                                                              afile/o1_mf_users_n3x8zl4q_.dbf.  Elapsed time: 0:00:01
  checkpoint is 1481009
  last deallocation scn is 849724
2025-06-03T16:27:54.469345+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00312: online log 2 thread 1: '/oracle/oradata_chkio1_mf_2_mo8pzod6_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:54.587490+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oracle/oradata_chkio1_mf_2_mo8pzod6_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:54.637827+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oracle/oradata_chkio1_mf_2_mo8pzod6_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:58.165246+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:58.229675+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:27:58.283359+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_m                                                                              z00_10746.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.                                                                              log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:02.009836+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00312: online log 31 thread 1: '/oracle/oradata_chkiredostd01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:02.097801+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00313: open failed for members of log group 31 of thread 1
ORA-00312: online log 31 thread 1: '/oracle/oradata_chkiredostd01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:02.146561+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00313: open failed for members of log group 31 of thread 1
ORA-00312: online log 31 thread 1: '/oracle/oradata_chkiredostd01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:04.737305+09:00
Full restore complete of datafile 5 /oracle/oradata_chki/ogg01.dbf.  Elapsed time: 0:00:04
  checkpoint is 1481036
  last deallocation scn is 3
2025-06-03T16:28:05.672421+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00312: online log 32 thread 1: '/oracle/oradata_chkiredostd02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:05.738102+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00313: open failed for members of log group 32 of thread 1
ORA-00312: online log 32 thread 1: '/oracle/oradata_chkiredostd02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:05.785088+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00313: open failed for members of log group 32 of thread 1
ORA-00312: online log 32 thread 1: '/oracle/oradata_chkiredostd02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:09.821295+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00312: online log 33 thread 1: '/oracle/oradata_chkiredostd03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:09.872117+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00313: open failed for members of log group 33 of thread 1
ORA-00312: online log 33 thread 1: '/oracle/oradata_chkiredostd03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:09.921124+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.trc:
ORA-00313: open failed for members of log group 33 of thread 1
ORA-00312: online log 33 thread 1: '/oracle/oradata_chkiredostd03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:14.191280+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.                                                                    trc:
ORA-00312: online log 34 thread 1: '/oracle/oradata_chkiredostd04.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:14.245317+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.                                                                    trc:
ORA-00313: open failed for members of log group 34 of thread 1
ORA-00312: online log 34 thread 1: '/oracle/oradata_chkiredostd04.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:14.295228+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10746.                                                                    trc:
ORA-00313: open failed for members of log group 34 of thread 1
ORA-00312: online log 34 thread 1: '/oracle/oradata_chkiredostd04.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:18.066602+09:00
Checker run found 14 new persistent data failures
2025-06-03T16:28:36.105835+09:00
Full restore complete of datafile 3 /oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_undotbs1_n3x8zm27_.dbf.  Elapsed time: 0:00:45
  checkpoint is 1481008
  last deallocation scn is 1476594
  Undo Optimization current scn is 1477582
2025-06-03T16:28:36.993090+09:00
Full restore complete of datafile 2 /oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_sysaux_n3x8zln8_.dbf.  Elapsed time: 0:00:46
  checkpoint is 1481006
  last deallocation scn is 1471240
2025-06-03T16:28:37.204190+09:00
Full restore complete of datafile 1 /oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_system_n3x8zhly_.dbf.  Elapsed time: 0:00:53
  checkpoint is 1481005
  last deallocation scn is 693121
  Undo Optimization current scn is 1477582
2025-06-03T16:28:45.924820+09:00
Switch of datafile 1 complete to datafile copy
  checkpoint is 1481005
Switch of datafile 2 complete to datafile copy
  checkpoint is 1481006
Switch of datafile 3 complete to datafile copy
  checkpoint is 1481008
Switch of datafile 4 complete to datafile copy
  checkpoint is 1481009
Switch of datafile 5 complete to datafile copy
  checkpoint is 1481036
setnotrustfnames set to : 0
alter database clear logfile group 1
Clearing online log 1 of thread 1 sequence number 31
2025-06-03T16:28:46.020796+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle/oradata_chkio1_mf_1_mo8pznhk_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:46.020877+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle/oradata_chkio1_mf_1_mo8pznhk_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:48.800873+09:00
Completed: alter database clear logfile group 1
alter database clear logfile group 2
2025-06-03T16:28:48.803327+09:00
Clearing online log 2 of thread 1 sequence number 32
2025-06-03T16:28:48.803636+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oracle/oradata_chkio1_mf_2_mo8pzod6_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:48.803826+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oracle/oradata_chkio1_mf_2_mo8pzod6_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:48.849393+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:49.327992+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:49.376075+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:50.935663+09:00
Completed: alter database clear logfile group 2
alter database clear logfile group 3
2025-06-03T16:28:50.938667+09:00
Clearing online log 3 of thread 1 sequence number 33
2025-06-03T16:28:50.939083+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:50.939232+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/oradata_chkio1_mf_3_mo8pzpjl_.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:53.059786+09:00
Completed: alter database clear logfile group 3
alter database clear logfile group 31
2025-06-03T16:28:53.062270+09:00
Clearing online log 31 of thread 1 sequence number 0
2025-06-03T16:28:53.062602+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 31 of thread 1
ORA-00312: online log 31 thread 1: '/oracle/oradata_chkiredostd01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:53.062737+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 31 of thread 1
ORA-00312: online log 31 thread 1: '/oracle/oradata_chkiredostd01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:54.859797+09:00
Completed: alter database clear logfile group 31
alter database clear logfile group 32
2025-06-03T16:28:54.862303+09:00
Clearing online log 32 of thread 1 sequence number 0
2025-06-03T16:28:54.862594+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 32 of thread 1
ORA-00312: online log 32 thread 1: '/oracle/oradata_chkiredostd02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:54.862708+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 32 of thread 1
ORA-00312: online log 32 thread 1: '/oracle/oradata_chkiredostd02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:56.812477+09:00
Completed: alter database clear logfile group 32
alter database clear logfile group 33
2025-06-03T16:28:56.814855+09:00
Clearing online log 33 of thread 1 sequence number 0
2025-06-03T16:28:56.815199+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 33 of thread 1
ORA-00312: online log 33 thread 1: '/oracle/oradata_chkiredostd03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:56.815278+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 33 of thread 1
ORA-00312: online log 33 thread 1: '/oracle/oradata_chkiredostd03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:58.503797+09:00
Completed: alter database clear logfile group 33
alter database clear logfile group 34
2025-06-03T16:28:58.506534+09:00
Clearing online log 34 of thread 1 sequence number 0
2025-06-03T16:28:58.506884+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 34 of thread 1
ORA-00312: online log 34 thread 1: '/oracle/oradata_chkiredostd04.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:28:58.506955+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_ora_10708.trc:
ORA-00313: open failed for members of log group 34 of thread 1
ORA-00312: online log 34 thread 1: '/oracle/oradata_chkiredostd04.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2025-06-03T16:29:00.269996+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-01110: data file 1: '/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_system_n3x8zhly_.dbf'
2025-06-03T16:29:00.337394+09:00
Completed: alter database clear logfile group 34
2025-06-03T16:29:00.339480+09:00
RFS connections are allowed
2025-06-03T16:29:00.456326+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-01110: data file 2: '/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_sysaux_n3x8zln8_.dbf'
2025-06-03T16:29:00.534978+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-01110: data file 3: '/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_undotbs1_n3x8zm27_.dbf'
2025-06-03T16:29:00.619757+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-01110: data file 4: '/oracle/oracle_base/oradata/CHOKI/datafile/o1_mf_users_n3x8zl4q_.dbf'
2025-06-03T16:29:00.796101+09:00
Errors in file /oracle/oracle_base/diag/rdbms/choki/RCHOKI/trace/RCHOKI_mz00_10809.trc:
ORA-01110: data file 5: '/oracle/oradata_chki/ogg01.dbf'
Checker run found 1 new persistent data failures

 

  •  ADG SYNC 및 Archivelog 전송 시 standbyDB alertlog
더보기
더보기

-- alter database recover managed standby database disconnect from session 명령어 수행 후
-- redolog 적용 확인
2025-06-03T17:10:35.947767+09:00
alter database recover managed standby database disconnect from session
2025-06-03T17:10:35.970504+09:00
Attempt to start background Managed Standby Recovery process (RCHOKI)
Starting background process MRP0
2025-06-03T17:10:35.979509+09:00
MRP0 started with pid=39, OS id=13688
2025-06-03T17:10:35.980353+09:00
Background Managed Standby Recovery process started (RCHOKI)
2025-06-03T17:10:41.068355+09:00
 Started logmerger process
2025-06-03T17:10:41.094528+09:00
PR00 (PID:13693): Managed Standby Recovery starting Real Time Apply
2025-06-03T17:10:41.150130+09:00
Parallel Media Recovery started with 4 slaves
2025-06-03T17:10:41.161496+09:00
stopping change tracking
2025-06-03T17:10:41.177509+09:00
TT02 (PID:13704): Waiting for all non-current ORLs to be archived
2025-06-03T17:10:41.177567+09:00
TT02 (PID:13704): All non-current ORLs have been archived
2025-06-03T17:10:41.267895+09:00
Completed: alter database recover managed standby database disconnect from session
2025-06-03T17:10:41.357813+09:00
PR00 (PID:13693): Media Recovery Log /arch/RCHOKI/archivelog/2025_06_03/o1_mf_1_35_n3xcgbf0_.arc
PR00 (PID:13693): Media Recovery Waiting for T-1.S-36 (in transit)
2025-06-03T17:10:41.544717+09:00
Recovery of Online Redo Log: Thread 1 Group 31 Seq 36 Reading mem 0
  Mem# 0: /oracle/oradata_chki/redostd01.log -------->> redolog Recovery 수행 


----->> Primary에서 Log Switch 발생 시 Standby 에 redolog 전송 확인
2025-06-03T17:15:21.580639+09:00
 rfs (PID:13976): Primary database is in MAXIMUM PERFORMANCE mode
 rfs (PID:13976): Re-archiving LNO:31 T-1.S-36
2025-06-03T17:15:21.592698+09:00
ARC2 (PID:13286): Archived Log entry 2 added for T-1.S-36 ID 0x72d23b44 LAD:1
2025-06-03T17:15:21.631293+09:00
 rfs (PID:13976): Selected LNO:31 for T-1.S-37 dbid 1926381892 branch 1187134212
2025-06-03T17:15:21.645449+09:00
PR00 (PID:13693): Media Recovery Waiting for T-1.S-37 (in transit)
2025-06-03T17:15:21.645875+09:00
Recovery of Online Redo Log: Thread 1 Group 31 Seq 37 Reading mem 0
  Mem# 0: /oracle/oradata_chki/redostd01.log
----->> Primary에서 Log Switch 발생 시 Standby 에 redolog 전송 확인
2025-06-03T17:16:22.522771+09:00
 rfs (PID:13976): Selected LNO:32 for T-1.S-38 dbid 1926381892 branch 1187134212
2025-06-03T17:16:22.546781+09:00
ARC1 (PID:13284): Archived Log entry 3 added for T-1.S-37 ID 0x72d23b44 LAD:1
2025-06-03T17:16:22.630116+09:00
PR00 (PID:13693): Media Recovery Waiting for T-1.S-38 (in transit)
2025-06-03T17:16:22.630446+09:00
Recovery of Online Redo Log: Thread 1 Group 32 Seq 38 Reading mem 0
  Mem# 0: /oracle/oradata_chki/redostd02.log

반응형