ORA-39006 ORA-39113 ORA-06550 PLS-00352 PLS-00201 ORA-39097 When Datapump Impdp Using Network Link

The following errors appear when running impdp operation which uses network link.

$ impdp imp_user/password@dbname directory=IMP_DIR logfile=imp_test.log tables=test  network_link=DB_LINK

Import: Release 12.1.0.2.0 - Production on Fri Aug 27 14:44:25 2021

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 12c EE Extreme Perf Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options
ORA-39006: internal error
ORA-39113: Unable to determine database version
ORA-06550: line 1, column 7:
PLS-00352: Unable to access another database 'DB_LINK'
ORA-06550: line 1, column 7:
PLS-00201: identifier 'SYS@DB_LINK' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

ORA-39097: Data Pump job encountered unexpected error -6550

CAUSE and SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.

ORA-10561: block type ‘TRANSACTION MANAGED DATA BLOCK’

The standby database alert log has the following errors:

Tue Nov 17 11:43:51 2020
 Errors in file /u01/app/oracle/diag/rdbms/stbytestdb/STBYTESTDB/trace/STBYTESTDB_mrp0_7269.trc:
 ORA-00600: internal error code, arguments: [3020], [3], [115047], [115047], [], [], [], [], [], [], [], []
 ORA-10567: Redo is inconsistent with data block (file# 3, block# 115047, file offset is 942465024 bytes)
 ORA-10564: tablespace SYSAUX
 ORA-01110: data file 3: '/u02/oradata/STBYTESTDB/sysaux01.dbf'
 ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 8316
 Tue Nov 17 11:43:51 2020
 MRP0: Background Media Recovery process shutdown (STBYTESTDB)

SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.

Data Guard Standby Automatic Password file Synchronization

It makes DBA life easy by using new feature of Data Guard Standby Automatic Password file Synchronization

For 12cR1 and earlier versions, when setup DataGuard( DG), if there is a change in password file of Primary database , then the password file needs to be copied from Primary database to standby database server. Otherwise the DG will get errors.

Subscribe to get access

Read more of this content when you subscribe today.

ORA-46952: standby database format mismatch for password file

SYMPTOM

After Oracle database has been upgraded from 18c to 19c, the Standby database alert log shows the following ORA-errors.

ORA-46952: standby database format mismatch for password file 
           '/u01/app/oracle/product/19.0.0/dbhome_1/dbs/orapwSTBOEMREP'
MRP0 (PID:6256): Managed Standby Recovery not using Real Time Apply
Recovery interrupted!

Subscribe to get access

Read more of this content when you subscribe today.

How to Configure OMS to Connect to Repository Database with Standby Database

This post demonstrates how to configure database connection string for OMS to connect to repository database, which has a data guard standby database.  The purpose is to make sure OEM is still functioning after database has been switched or failed over to data guard physical standby database.

Subscribe to get access

Read more of this content when you subscribe today.

Restart all OMS

[oracle@oemnode1 ~]$ emctl stop oms -all
[oracle@oemnode1 ~]$ emctl start oms

Switch Over Repository Database to Standby Database

DGMGRL> show configuration;

Configuration - dg_oemrep

Protection Mode: MaxPerformance
Members:
oemrep - Primary database
stboemrep - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 27 seconds ago)
DGMGRL> switchover to stboemrep;
Performing switchover NOW, please wait...
Operation requires a connection to database "stboemrep"
Connecting ...
Connected to "STBOEMREP"
Connected as SYSDBA.
New primary database "stboemrep" is opening...
Operation requires start up of instance "OEMREP" on database "oemrep"
Starting instance "OEMREP"...
Connected to an idle instance.
ORACLE instance started.
Database mounted.
Connected to "OEMREP"
Switchover succeeded, new primary is "stboemrep"
DGMGRL>

Check and Confirm OEM 13c  is Still Working