ORA-25191: cannot reference overflow table of an index-organized table

SQL> begin
dbms_stats.gather_table_stats(ownname => ‘EXFSYS’, tabname => ‘RLM$ERRCODE’, estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE, method_opt => ‘FOR ALL COLUMNS SIZE AUTO’, cascade =>TRUE,degree=>12, no_invalidate=>false);
end;

ORA-25191: cannot reference overflow table of an index-organized table

SOLUTION:

SQL> select IOT_NAME from dba_tables where owner=’EXFSYS’ and table_name = ‘SYS_IOT_OVER_70459’;

IOT_NAME

RLM$ERRCODE

 

SQL> begin
dbms_stats.gather_table_stats(ownname => ‘EXFSYS’, tabname => ‘RLM$ERRCODE‘, estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE, method_opt => ‘FOR ALL COLUMNS SIZE AUTO’, cascade =>TRUE,degree=>12, no_invalidate=>false);
end;

PL/SQL procedure successfully completed

 

done…

 

 

 

 

ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

SQL> alter database archivelog;
alter database archivelog
*
ERROR at line 1:
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
Cause:
The database was crashed itself or you issued shutdown abort or startup force commands.
In my case I issued the following command, to take database into mount state.

Solution:

SQL> startup mount force;

SQL> select status from v$instance;
STATUS
————————————
MOUNTED
SQL> alter database open;
Database altered.
SQL> shutdown immediate;
Database closed.

Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 293601280 bytes
Fixed Size 1248600 bytes
Variable Size 88081064 bytes
Database Buffers 197132288 bytes
Redo Buffers 7139328 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.

Done…

ORA-28365: wallet is not open error

In general Oracle Wallet is used to encrypt data inside the database. So, you must first open the Wallet.

If you know the password of this Wallet you can use the following syntax:

alter system set encryption wallet open identified by “<password>”;

 

[https://community.oracle.com/thread/994202?tstart=0]

Done…

ORA-01031: insufficient privileges: error when trying to Debug

The Oracle user or schema account does not have the required Oracle rights to debug an object.

The following privileges are required for the Debugger:

PRIVILEGE

DEBUG CONNECT SESSION
INSERT ANY TABLE
CREATE ANY PROCEDURE
SELECT ANY SEQUENCE
DEBUG ANY PROCEDURE
CREATE SESSION
UPDATE ANY TABLE
SELECT ANY TABLE
EXECUTE ANY PROCEDURE

EXECUTE ON DBMS_DEBUG

 

DBA_REGISTRY_HISTORY

DBA_REGISTRY_HISTORY provides information about upgrades, downgrades, and critical patch updates that have been performed on the database.

Column Datatype NULL Description
ACTION_TIME TIMESTAMP(6) The time the upgrade, downgrade, or patch action was completed
ACTION VARCHAR2(30) The specific action (for example, UPGRADE or DOWNGRADE)
NAMESPACE VARCHAR2(30) The namespace of the components affected (for example, SERVER)
VERSION VARCHAR2(30) The version number of the server (for example, 10.2.0.1.0)
ID NUMBER The identification number of the Critical Patch Update
COMMENTS VARCHAR2(255) Additional comments about the action taken

 
mydb>select action_time, version, ID , BUNDLE_SERIES ,COMMENTS from DBA_REGISTRY_HISTORY;

ACTION_TIME VERSION ID BUNDLE_SERIES COMMENTS

06-APR-12 02.31.18.463300 AM 11.2.0.3 1 PSU PSU 11.2.0.3.1
23-AUG-15 06.50.26.796815 AM 8289601 view invalidation
23-AUG-15 06.57.40.080186 AM 11.2.0.4.0 Upgraded from 11.2.0.3.0
23-AUG-15 07.02.41.964733 AM 11.2.0.4 6 PSU PSU 11.2.0.4.6

 

done…