

From alert log it was noticed that archive process is leaving some messages as below.
Sun Nov 11 09:41:34 2018 ARC5: Evaluating archive log 20 thread 1 sequence 59168 ARC5: Unable to archive thread 1 sequence 59168 Log actively being archived by another process ARC5: Evaluating archive log 22 thread 1 sequence 59175 ARC5: Unable to archive thread 1 sequence 59175 Log actively being archived by another process
Cause :
It is due to having more than one archiver.
Solution :
If automatic archiving is turned ‘ON’ and LOG_ARCHIVE_MAX_PROCESSES is set to more than one, then all of the archiver processes will try to archive this logfile, however they will not be able to aquire the lock ‘kcrrlt’, to protect multiple arch processes from archiving the same logfile.
The failing process process will write to the trace/alert message that it was unable to archive the logfile.
It doesn’t mean that the log mentioned is not archived; it is successfully archived by some other process. It only means that the log was not archived the first time it was tried.
If you go a bit down you will see that the log had been archived.
Error :
/u01/oradr/db_1/appsutil/clone/bin/../jre/bin/java -Xmx600M -DCONTEXT_VALIDATED=true -Doracle.installer.oui_loc=/u01/oradr/db_1/oui -classpath /u01/oradr/db_1/appsutil/clone/jlib/xmlparserv2.jar:/u01/oradr/db_1/appsutil/clone/jlib/ojdbc5.jar:/u01/oradr/db_1/appsutil/clone/jlib/java:/u01/oradr/db_1/appsutil/clone/jlib/oui/OraInstaller.jar:/u01/oradr/db_1/appsutil/clone/jlib/oui/ewt3.jar:/u01/oradr/db_1/appsutil/clone/jlib/oui/share.jar:/u01/oradr/db_1/appsutil/clone/jlib/oui/srvm.jar:/u01/oradr/db_1/appsutil/clone/jlib/ojmisc.jar oracle.apps.ad.clone.ApplyDBTier -e /u01/oradr/db_1/appsutil/TEST_azuredr.xml -stage /u01/oradr/db_1/appsutil/clone -showProgress APPS Password : Log file located at /u01/oradr/db_1/appsutil/log/TEST_azuredr/ApplyDBTier_03271654.log \ 0% completed RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack ERROR while running Apply… Tue Mar 27 16:55:27 2018 ERROR: Failed to execute /u01/oradr/db_1/appsutil/clone/bin/adclone.pl
Cause :
log file reveled the information
"Perl lib version (5.10.1) doesn't match executable version (v5.10.0) at /usr/lib64/perl5/Config.pm line 50. Compilation failed in require at /u01/oradr/db_1/appsutil/clone/ouicli.pl line 35. BEGIN failed--compilation aborted at /u01/oradr/db_1/appsutil/clone/ouicli.pl line 35."
Solution :
set perl to verion 5.10.0 as below and rerun the clone
export PERL5LIB=/u01/oradr/db_1/perl/lib/5.10.0:/u01/oradr/db_1/perl/lib/site_perl/5.10.0:/u01/oradr/db_1/appsutil/perl export PATH=/u01/oradr/db_1/perl/bin:$PATH
Error
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
>>> Cannot set an SCN larger than the current SCN. If a Streams Capture configuration was imported then the Apply that processes the captured messages needs to be dropp
ed and recreated. See My Oracle Support article number 1380295.1.
ORA-39083: Object type PROCACT_SYSTEM failed to create with error:
ORA-20000: Incompatible version of Workspace Manager Installed
Cause
Version of the Oracle Workspace Manager (OWM) in the source and target are not same.
Solution
Ignore the following errors, if IMPDP is importing all other components and data successfully:
To move the workspaces from the 11.2.0.3 or 11.2.0.4 SOURCE db, the FULL db export must be generated with the parameter “VERSION=12”.
If the SOURCE database is older than 11.2.0.3, e.g. 11.2.0.2 or 11.1.0.7, the database will first need to be upgraded to 11.2.0.3 or 11.2.0.4