search

oracle / oracle-database-operator

The Oracle Database Operator for Kubernetes (a.k.a. OraOperator) helps developers, DBAs, DevOps and GitOps teams reduce the time and complexity of deploying and managing Oracle Databases. It eliminates the dependency on a human operator or administrator for the majority of database operations.
Universal Permissive License v1.0
141 stars 45 forks source link

19.0.3 standby database wont recover, with error "LOG_FILE_NAME_CONVERT is not defined" #155

Open kimattree opened 3 days ago

kimattree commented 3 days ago

I have a hot/standby configuration running oracleDB 19.0.3 EE, Dataguard enabled, I'm testing the solution and as part of that, I delete/kill the standby database and allow it to restart/recover, however, I'm getting this error on restart, and the DB never reaches healthy state:

ORACLE EDITION: ENTERPRISE
LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 29-NOV-2024 11:35:49
Copyright (c) 1991, 2019, Oracle.  All rights reserved.
Starting /opt/oracle/product/19c/dbhome_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 19.0.0.0.0 - Production
System parameter file is /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/oracledb-secondary-lqwi3/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=0.0.0.0)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date                29-NOV-2024 11:35:49
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Listener Log File         /opt/oracle/diag/tnslsnr/oracledb-secondary-lqwi3/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=0.0.0.0)(PORT=1521)))
Services Summary...
Service "DATAGUARD" has 1 instance(s).
  Instance "ORCL2", status UNKNOWN, has 1 handler(s) for this service...
Service "ORCL2" has 1 instance(s).
  Instance "ORCL2", status UNKNOWN, has 1 handler(s) for this service...
Service "ORCL2_DGMGRL" has 1 instance(s).
  Instance "ORCL2", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
SQL*Plus: Release 19.0.0.0.0 - Production on Fri Nov 29 11:35:49 2024
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle.  All rights reserved.
Connected to an idle instance.
SQL> ORACLE instance started.
Total System Global Area 2.0133E+10 bytes
Fixed Size         16224352 bytes
Variable Size        2483027968 bytes
Database Buffers     1.7583E+10 bytes
Redo Buffers           50880512 bytes
Database mounted.
Database opened.
SQL> Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
The Oracle base remains unchanged with value /opt/oracle
#####################################
########### E R R O R ###############
DATABASE SETUP WAS NOT SUCCESSFUL!
Please check output for further info!
########### E R R O R ###############
#####################################
The following output is now a tail of the alert.log:
===========================================================
2024-11-29T11:36:12.433392+00:00
PDB$SEED(2):Opening pdb with no Resource Manager plan active
Physical standby database opened for read only access.
Completed: ALTER DATABASE OPEN
2024-11-29T11:36:12.549190+00:00
db_recovery_file_dest_size of 51200 MB is 2.29% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2024-11-29T11:36:26.273214+00:00
Starting background process RSM0
2024-11-29T11:36:26.283925+00:00
RSM0 started with pid=77, OS id=263
2024-11-29T11:36:30.353536+00:00
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT  NODELAY
2024-11-29T11:36:30.354749+00:00
Attempt to start background Managed Standby Recovery process (ORCL2)
Starting background process MRP0
2024-11-29T11:36:30.364717+00:00
MRP0 started with pid=78, OS id=265
2024-11-29T11:36:30.365543+00:00
Background Managed Standby Recovery process started (ORCL2)
2024-11-29T11:36:35.385096+00:00
 Started logmerger process
2024-11-29T11:36:35.392757+00:00
IM on ADG: Start of Empty Journal
IM on ADG: End of Empty Journal
PR00 (PID:267): Managed Standby Recovery starting Real Time Apply
max_pdb is 3
2024-11-29T11:36:35.525681+00:00
Parallel Media Recovery started with 12 slaves
2024-11-29T11:36:35.547070+00:00
stopping change tracking
2024-11-29T11:36:35.560511+00:00
TT02 (PID:293): LOG_FILE_NAME_CONVERT is not defined, stop clearing ORLs                 <--------------------------------------------------------------------------------------
2024-11-29T11:36:35.600564+00:00
Recovery of Online Redo Log: Thread 1 Group 4 Seq 21 Reading mem 0
  Mem# 0: /opt/oracle/oradata/ORCL2/onlinelog/o1_mf_4_mngf5fkz_.log
2024-11-29T11:36:36.370932+00:00
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT  NODELAY
kimattree commented 3 days ago

deleting all the data on the PV and allowing the secondary to recreate from scratch resolves the issue...