ORA-65040: operation not allowed from within a pluggable database

cause : sql run from PDB

solution: run it from CDB or root container database

RMAN-01005: recovery catalog is not supported when connected to pluggable database

solution:

connect to right target container database -CDB

rman target sys@abcprodC catalog rman@rmanp

 

Invalids in SYS schema – V$XS_SESSION_ROLE in PDB but not in CDB

-bash-4.2$ sqlplus sys@devc as sysdba

SQL> alter session set container=DEV;

Session altered.

SQL> show con_name;

CON_NAME
——————————
DEV
SQL>
SQL> DROP VIEW SYS.V$XS_SESSION_ROLE; 
DROP VIEW SYS.V$XS_SESSION_ROLE
*
ERROR at line 1:
ORA-02030: can only select from fixed tables/views

If you get above error then do option 2 recommended by development. At this time it is not documented in oracle

SQL> update obj$ set status = 1 where name = ‘V$XS_SESSION_ROLE’ and subname = ‘$DEPRECATED$’; 

1 row updated.

select owner,OBJECT_NAME,OBJECT_TYPE,status from dba_objects where object_name = ‘V$XS_SESSION_ROLE’;

SYS V$XS_SESSION_ROLE VIEW VALID
PUBLIC V$XS_SESSION_ROLE SYNONYM VALID

ORA-00060: deadlock detected while waiting for resource 

ORA-12012: error on auto execute of job “SYS”.”ORA$AT_SA_SPC_SY_5115″
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at “SYS.DBMS_SPACE”, line 2741
ORA-06512: at “SYS.DBMS_HEAT_MAP_INTERNAL”, line 716
ORA-06512: at “SYS.DBMS_HEAT_MAP_INTERNAL”, line 1164
ORA-06512: at “SYS.DBMS_HEAT_MAP”, line 228
ORA-06512: at “SYS.DBMS_SPACE”, line 2747
2018-03-10T10:32:13.788957-06:00

SOLUTION / ACTION PLAN
Your issue looks similar to Doc ID 2321020.1
In 12.2 Auto Space Advisor Job Fails With ORA-60 ( Doc ID 2321020.1 )
Until Bug 24687075 gets fixed, you can disable the space advisory job as

workaround:
SQL> EXEC DBMS_AUTO_TASK_ADMIN.DISABLE(‘AUTO SPACE ADVISOR’,NULL, NULL);

Partition message in alert log

TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P

These are partitions of an internal table that collects AWR statistics – Alert Log Shows Messages Starting “TABLE WRI$_OPTSTAT_* ADDED INTERVAL PARTITION…” ( Doc ID 2018434.1 )

 

Redo warning after 12.2 upgrade

*****************************************************************
An internal routine has requested a dump of selected redo.
This usually happens following a specific internal error, when
analysis of the redo logs will help Oracle Support with the
diagnosis.
It is recommended that you retain all the redo logs generated (by
all the instances) during the past 12 hours, in case additional
redo dumps are required to help with the diagnosis.
*****************************************************************

SRDC – Required Diagnostic Data Collection for Redo Log Corruption ( Doc ID 1671530.1 )

Kindly take a look at – An Internal Routine Has Requested A Dump Of Selected Redo – Message Appears In Alert Log ( Doc ID 2295361.1 )

Solution:

Ignore it if there is no error after this message. Also monitor log if error occurs sometime

ORA-06544: PL/SQL: internal error, arguments

Solution:

Developer require to change SQL or code

ORA-12012: error on auto execute of job “SYS”.”ORA$AT_OS_OPT_SY_37″

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

SOLUTION

Please refer
ORA-12012 Error on auto execute of job “SYS”.”ORA$AT_OS_OPT_SY_<NN> in 12.2 Database ( Doc ID 2127675.1 )

Next Steps:-

Please run dbms_stats.init_package() in the container database to create the tasks correctly:

$ sqlplus / as sysdba

EXEC dbms_stats.init_package();

Once done, please execute below query ..

column name format A35
set linesize 120

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’);

Output of the query will look like this:
NAME CTIME HOW_CREATED
———————————– ———- ——————————
AUTO_STATS_ADVISOR_TASK 14-APR-16 CMD
INDIVIDUAL_STATS_ADVISOR_TASK 14-APR-16 CMD

ORA-28040 : No matching authentication protocol

Cause: This error occurred after 12.2 database upgrade.

Reason: 11g or lower version client try to connect with 12.2 database

solution:

Add below entry on server side of sqlnet.ora on both node. replace 8 with any other number in your environment

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8