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.

expdp did not create dumpfile while expdp is successful

A client sent the following information about the dump file of expdp is unavailable, while the datapump log shows expdp completes successfully.

$ expdp exp_user/password@testdbpdb directory=DATA_PUMP_DIR dumpfile=hr.dmp schemas=hr reuse_dumpfiles=yes logfile=exp_hr.log
..
..
.
Master table "EXP_USER"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for EXP_USER.SYS_EXPORT_SCHEMA_01 is:
/home/oracle/hr.dmp
Job "EXP_USER"."SYS_EXPORT_SCHEMA_01" successfully completed at Fri Aug 27 11:53:13 2021 elapsed 0 00:00:57

$ ls -ltr /home/oracle/hr.dmp
ls: cannot access /home/oracle/hr.dmp: No such file or directory

CAUSE and SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.

Failed to Start Listener with TNS-01192 Error

In 19c GI environment, local listeners failed to start up with following errors:

[grid@racnode1 $ srvctl start listener -node racnode1
PRCR-1013 : Failed to start resource ora.LISTENER.lsnr
PRCR-1064 : Failed to start resource ora.LISTENER.lsnr on node racnode1
CRS-5016: Process "/u01/app/19.0.0.0/grid/bin/lsnrctl" spawned by agent "ORAAGENT" for action "start" failed: details at "(:CLSN00010:)" in "/u01/app/grid/diag/crs/racnode1/crs/trace/crsd_oraagent_grid.trc"
CRS-5016: Process "/u01/app/19.0.0.0/grid/bin/lsnrctl" spawned by agent "ORAAGENT" for action "start" failed: details at "(:CLSN00010:)" in "/u01/app/grid/diag/crs/racnode1/crs/trace/crsd_oraagent_grid.trc"
CRS-2674: Start of 'ora.LISTENER.lsnr' on 'racnode1' failed

Further check “crsd_oraagent_grid.trc” with following errors:

Starting /u01/app/19.0.0.0/grid/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 19.0.0.0.0 - Production
System parameter file is /u01/app/19.0.0.0/grid/network/admin/listener.ora
Log messages written to /u01/app/grid/diag/tnslsnr/racnode1/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
TNS-01192: Missing SID_LIST_ value left of equation for SID description in LISTENER.ORA

Listener failed to start. See the error message(s) above...

Subscribe to get access

Read more of this content when you subscribe today.

RMAN-06091: no channel allocated for maintenance

After Oracle databases migrated to different versions, the following errors occur from a couple of RMAN backups, which have been working find in old version databases.

It happens for some Oracle databases applied the latest RU/RUR/BP, etc.

...
..
.
RMAN-03002: failure of crosscheck command at 08/04/2021 13:51:11
RMAN-06091: no channel allocated for maintenance (of an appropriate type)

CAUSE & WORKAROUND

It is a known bug for all database versions until 19c.

Subscribe to get access

Read more of this content when you subscribe today.