Ravindra's blog: 2021

Sunday 22 August 2021

ora-01153::undefined an incompatible media recovery is active

Information: If you are seeing below error while starting MRP process means currently your MRP process is running. check MRP process status using below sql.

SQL> select process, status, sequence# from v$managed_standby where process in ('MRP0','RFS');

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
MRP0      APPLYING_LOG         18
RFS       IDLE                 18
RFS       IDLE                  0
RFS       IDLE                  0

Note: if you want start it again then cancel it and start it again using below sql

SQL> alter database recover managed standby database cancel;
Database altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
Database altered.

Saturday 7 August 2021

START and STOP data gaurs setup in data guard broker configuration

INFORMATION: Before start below steps start listener on both side

1. Start Source Database normal mode (open mode)

SQL> startup;

ORACLE instance started.

Total System Global Area 1593835520 bytes

Fixed Size 8621184 bytes

Variable Size 1375732608 bytes

Database Buffers 201326592 bytes

Redo Buffers 8155136 bytes

Database mounted.

Database opened.

2. start target database(standby database) in mount mode

SQL> startup mount;

ORACLE instance started.

Total System Global Area 1593835520 bytes

Fixed Size 8621184 bytes

Variable Size 1258292096 bytes

Database Buffers 318767104 bytes

Redo Buffers 8155136 bytes

Database mounted.

3. start MRP process

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Database altered.

4. Validation

- Check MRP process is in running mode

SQL> select process, status, sequence# from v$managed_standby where process like '%MRP%';

PROCESS STATUS SEQUENCE#

--------- ------------ ----------

MRP0 APPLYING_LOG 10

- connect to DGMGRL prompt and check data gaurd configuration

[oracle@DB12C ~]$ dgmgrl sys@DB12C_STB as sysdba

DGMGRL for Linux: Release 12.2.0.1.0 - Production on Sat Aug 7 18:46:44 2021

Welome to DGMGRL, type "help" for information.

Password:

Connected to "DB12C_STB"

Connected as SYSDBA.

DGMGRL> show configuration;

Configuration - my_dg

Protection Mode: MaxPerformance

Members:

db12c - Primary database

db12c_stb - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:

SUCCESS (status updated 12 seconds ago)

Saturday 31 July 2021

OCI Error ORA-00904: "INTCOL#": invalid identifier

Error Details:

ERROR OGG-00663 Oracle GoldenGate Capture for Oracle, ehrint01.prm: OCI Error ORA-00904: "INTCOL#": invalid identifier

(status = 904), SQL <SELECT md_col_name, md_col_num, md_col_segcol, md_col_type, md_col_len, md_col_prec, md_col_scale, md_col_charsetid, md_col_charsetform, md_col_alt_type, md_col_alt_prec, md_col_alt_char_used, md_col_alt_length, md_col_alt_type_owner, property, xopqtypeflags , intcol# FROM TABLE (system.logmnr$col_gg_tabf_public( :sid, :mdh, :object_id, :objv, to_number(:csn) ))>.

Solution:

Apply the patch 17030189 on database and after applied patch execute script prvtlmcs.plb, prvtlmcb.plb, both script location are GG_HOME.

Wednesday 21 July 2021

OGG-02022 Logmining server does not exist on this Oracle database.

error:

2021-07-21 16:33:31 ERROR OGG-02022 Logmining server does not exist on this Oracle database.

2021-07-21 16:33:31 ERROR OGG-01668 PROCESS ABENDING.

Solution

dblogin userid gguser@<service_name> password <***>