Unable to archive thread 1 sequence ###

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.

Sun Nov 11 09:41:45 2018
ARC9: Completed archiving thread 1 sequence 59168 (0-0)

ORA-39083: Object type PROCACT_SYSTEM failed to create with error

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

ORA-12012: error on auto execute of job "SYS"."ORA$AT_OS_OPT_SY_16656"

Error

ORA-12012: error on auto execute of job "SYS"."ORA$AT_OS_OPT_SY_16656"
ORA-20001: Statistics Advisor: Invalid task name for the current user
ORA-06512: at "SYS.DBMS_STATS", line 47207
ORA-06512: at "SYS.DBMS_STATS_ADVISOR", line 882
ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 20059
ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 22201
ORA-06512: at "SYS.DBMS_STATS", line 47197

Cause Its an known BUG, Advisory packages were not created properly during database creation.

Solution

Verify advisory packages are exist or not, if you are getting these errors means you will not found these objects.

select name, ctime, how_created
from sys.wri$_adv_tasks
where owner_name = 'SYS'
and name in ('AUTO_STATS_ADVISOR_TASK','INDIVIDUAL_STATS_ADVISOR_TASK');

no rows selected

Create these objects using below command

SQL> EXEC dbms_stats.init_package();

PL/SQL procedure successfully completed.

Resource manager plan is not active or is not managing CPU usage

Error

SQL> EXECUTE dbms_stats.gather_table_stats(ownname=>'ROCFM',tabname=>'SUBSCRIBER',cascade=>true);
BEGIN dbms_stats.gather_table_stats(ownname=>'ROCFM',tabname=>'SUBSCRIBER',cascade=>true); END;

*
ERROR at line 1:
ORA-20000: Unable to gather statistics concurrently: Resource manager plan is not active or is not managing CPU usage
ORA-06512: at "SYS.DBMS_STATS", line 34757

ORA-06512: at line 1


Cause

Resource Manager must be enabled in 12c in order to use any value other than OFF for the CONCURRENT preference (which enables concurrent statistics gathering).

Solution

SQL> alter system set resource_manager_plan = 'DEFAULT_PLAN' ;

System altered.

SQL> EXECUTE dbms_stats.gather_table_stats(ownname=>'ROCFM',tabname=>'SUBSCRIBER',cascade=>true);


PL/SQL procedure successfully completed.


SQL> 

How to Stop Oracle Audit Vault Services

Simple article on stopping Oracle Audit Vault Services.

Follow below  sequence of steps:

/usr/local/dbfw/bin/javafwk stop --> From root
/usr/local/dbfw/bin/dbfwdb stop --> From oracle
/usr/local/dbfw/bin/asmdb stop --> From root

[root@auditvault02 ~]# /usr/local/dbfw/bin/javafwk stop
Stopping Java framework...                                 [  OK  ]
[root@auditvault02 ~]#

[root@auditvault02 ~]# su - oracle
[oracle@auditvault02 ~]$
[oracle@auditvault02 ~]$ /usr/local/dbfw/bin/dbfwdb stop
Shutting down the database
Database shut down
[oracle@auditvault02 ~]$
[oracle@auditvault02 ~]$ lsnrctl stop

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 27-SEP-2018 10:51:53

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
The command completed successfully
[oracle@auditvault02 ~]$
[oracle@auditvault02 ~]$

[root@auditvault02 ~]#
[root@auditvault02 ~]# /usr/local/dbfw/bin/asmdb stop
[root@auditvault02 ~]#

[root@auditvault02 ~]#
[root@auditvault02 ~]# su - grid
[grid@auditvault02 ~]$ lsnrctl stop LISTENER_ASM

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 27-SEP-2018 10:51:34

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1523)))
The command completed successfully
[grid@auditvault02 ~]$


Now follow the reverse to restart up avdf DB and APP services.