This document is a basic knowledge base from searchers that I did in Oracle Support to solve problems so it might save you time to search. You might find the error and straightway the fix.
ORA-12638: Credential retrieval failed
Set SQLNET.ORA client
SQLNET.NO_NTLM=FALSE
EM express doesn’t work with Oracle 19c on Windows
Change the ACL manually or reinstall Oracle 19c and not use WVA
ORA-12592: TNS: Bad Packet Accompanied by Alert Log Errors ORA-3137 [12333] / ORA-3131
Line 1037: (10392) [000001 09-JAN-2020 08:27:21:954] nioqrc: Recieve: returning error: 3111
Doc ID Oracle Net: Intermittent 3135/12592/3113 Errors Returned to Client Application (Doc ID 2237258.1)
Solution
Set DISABLE_OOB=ON at the client side sqlnet.ora file.
In other words, disable out of band breaks or OOB in this environment to
stop this bad packet with an urgent flag from being delivered.
SQLNET.ORA at client side. Typically located in ORACLE_HOME/network/admin OR TNS_ADMIN
DISABLE_OOB=ON
Relaunch the client application and test.
ORA-ORA-02372 / ORA-01401 / ORA-12899 / ORA-01461 While Importing Or Loading Data In An AL32UTF8 / UTF8 (Unicode) Or Other Multibyte NLS_CHARACTERSET Database. (Doc ID 1297961.1). ccsscan
Import (both the old imp tool or datapump) give errors like
IMP-00019: row rejected due to ORACLE error 1401
IMP-00003: ORACLE error 1401 encountered
ORA-01401: inserted value too large for column
or
IMP-00058: ORACLE error 1461 encountered
ORA-01461: can bind a LONG value only for insert into a LONG column
or from 10g onwards:
IMP-00019: row rejected due to ORACLE error 12899
IMP-00003: ORACLE error 12899 encountered
ORA-12899: value too large for column “SCHEMA_NAME”.”TABLE_NAME”.”COLUMN_NAME” (actual: <xx>, maximum: <yy>)
or
ORA-02374: conversion error loading table “SCHEMA_NAME”.”TABLE_NAME”
ORA-12899: value too large for column COLUMN_NAME (actual: <xx>, maximum: <yy>)
or
ORA-02375: conversion error loading table “SCHEMA_NAME.TABLE_NAME” partition “PARTITION_NAME”
ORA-12899: value too large for column COLUMN_NAME (actual: <xx>, maximum: <yy>)
ORA-02372: data for row:
or
ORA-31693: Table data object “SCHEMA_NAME”.”TABLE_NAME” failed to load/unload and is being skipped due to error:
ORA-12899: value too large for column “SCHEMA_NAME”.”TABLE_NAME”.”COLUMN_NAME” (actual: <xx>, maximum: <yy>)
The database is down. Please specify the host credentials to access database restart and diagnostics tools.
Enterprise manager shows that database is down but in real it is not.
alter user DBSNMP account unlock;
alter user SYSTEM account unlock;
alter user SYSMAN account unlock;
ERROR at line 1:
ORA-65048: error encountered when processing the current DDL statement in pluggable database PDB1
ORA-00959: tablespace ‘XXXXX does not exist
Alter the user
alter user c##xxxxx identified by xxxxx container=current;
EM 13c: Enterprise Manager 13c Cloud Control Installation with a 12.2 Repository Database Fails with Message: Check if the parameter _allow_insert_with_update_check is set to True (Doc ID 2254373.1)
Error during EM 13c install: need to set _allow_insert_with_update_check=true
Prior to installation of EM 13.2:
1. For for Enterprise Manager 13.2 repository, the compatible initialization parameter should be set to 12.1.0.0 or higher.
Confirm with:
SQL> show parameter compatible
2. Ensure the _allow_insert_with_update_check database initialization parameter is set to be true for the repository database.
If you are using PDB for the Repository Database, set this parameter value in CDB.
SQL>alter system set “_allow_insert_with_update_check” = true;
Problem Description:
Database character set change is erroring out with following error message.
ALTER DATABASE CHARACTER SET AL32UTF8
*
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
Reference: http://www.acehints.com/2016/09/fix-ora-12712-new-character-set-must-be.html
Solution Description: Use INTERNAL_USE option along with the above command. Here is the steps to change the character set.
conn / as sysdba
startup restrict;
ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8;
shutdown immediate;
conn / as sysdba
startup
ORA-60100: dropping temporary tablespace with tablespace ID number (tsn) 3 is blocked due to sort segments
— check any blocks
SELECT b.tablespace, b.segfile#, b.segblk#, b.blocks, a.sid, a.serial#,
a.username, a.osuser, a.status
FROM v$session a,v$sort_usage b
WHERE a.saddr = b.session_addr
ORDER BY b.tablespace, b.segfile#, b.segblk#, b.blocks;
Release / kill the sessions that is doing sort
drop tablespace again
drop tablespace temp;
Alert log message: SR 3-17005473261 – Errors ORA-06512 0 DBMS_SPACE
Bug 24687075 – SPACE ADVISOR TASKS/JOBS HITTING DEADLOCKS WITH GATHER DB STATS JOBS
In 12.2 Auto Space Advisor Job Fails With ORA-60 (Doc ID 2321020.1)
Error Summary:
ORA-00060: deadlock resolved; details in file /u01/app/oracle/diag/rdbms/xx/xx/trace/xx01_j001_16511.trc
ORA-12012: error on auto execute of job “SYS”.”ORA$AT_SA_SPC_SY_12590″
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
ORA-00060: deadlock resolved; details in file
ORA-12012: error on auto execute of job “SYS”.”ORA$AT_SA_SPC_SY_12636″
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
Solution
Failed job can be recovered from next automatic maintenance job running normally. Therefore, if it does not occur frequently, can be ignored safely.
OR
Until the bug is fixed, you can disable the space advisory job as a workaround:
connect / as sysdba
select CLIENT_NAME,STATUS from DBA_AUTOTASK_CLIENT;
EXEC DBMS_AUTO_TASK_ADMIN.DISABLE(‘AUTO SPACE ADVISOR’,NULL,NULL);
select CLIENT_NAME,STATUS from DBA_AUTOTASK_CLIENT;
ADRCI errors
DIA-48447: The input path [diag/rdbms/xx/xx] does not contain any ADR homesChange the file and correct as shown below:
# Format:
# SID:ORACLE_HOME:ADRCI_HOME
Alert log message:
Error Summary:
ORA-12012: error on auto execute of job “SYS”.”ORA$AT_OS_OPT_SY_161″
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
Reference
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/readm/dbca-known-bugs.html#GUID-DBD9265E-2964-42AA-A534-FB4B9F35BB72
2.12.8 Oracle Database Configuration Assistant (DBCA) Known Bugs
2.12.8.1 Bug 25710407
Workaround: Connect to the created database using the SYSDBA privilege and run the following command:
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’);
EXEC dbms_stats.init_package();
Now there are rows in these queries:
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’);
Leonardo Bissoli
