Posts Tagged ‘dba immam’

EXP-00111

January 12th, 2020, posted in Oracle
Share

ERROR :
EXP-00111: Table WORKER resides in an Encrypted Tablespace sujeet and will not be exported


Cause :
Encrypted Tablespace feature is not supported by classic export


Action :
Use DATAPUMP Utility to export this table.

Share

NID-00135: There are number active threads.

December 29th, 2019, posted in Oracle Queries
Share

NID-00135: There are number active threads.

SQL> select name,open_mode from v$database;

NAME      OPEN_MODE
--------- --------------------
PROD      MOUNTED

[oracle@oracle sujeet$ nid TARGET=SYS/sys123 DBNAME=PROD SETNAME=YES

DBNEWID: Release 11.1.0.7.0 - Production on Thu Apr 26 18:04:18 2018

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Connected to database ACSEBSP (DBID=2199446376)

Connected to server version 11.1.0

NID-00135: There are 1 active threads


Change of database name failed during validation - database is intact.
DBNEWID - Completed with validation errors.

Solution :

Action:  Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.

 

SQL> alter database open;
Database altered.


SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup mount
ORACLE instance started.



[oracle@oracle sujeet$ nid TARGET=SYS/sys123 DBNAME=PROD SETNAME=YES
Share

apps-fnd-01564 oracle error 1653 in summit others

December 22nd, 2019, posted in Oracle Queries
Share

CAUSE :

Typically occurs when writing a new record to oracle database, but there is not enough space to write it. The data file in oracle tablespace called APPS_TS_TX_DATA should be set to AUTOEXTEND. If it is not, Oracle will not auto-increase the size of the datafile, and will raise the above error.

apps-fnd-01564 oracle error 1653 in summit others,apps-fnd-01564,oracle error,imam dba,dba imam,immam dba,dba immam,

SOLUTION :

If all the reports end in COMPLETE – NORMAL, means its work.

If not than follow below steps.

Run a Concurrent Manager Recovery :

1. Please stop Concurrent managers by adcmctl.sh.

2. If not stopped, please abort managers by adcmctl.sh.

adcmctl.sh abort apps/****

3. Please kill if a process remains.

4. relink all (ADADMIN)

5. Please retry Concurrent Manager Recovery.

Navigate :
Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery.

OR

SOLUTION :

WARNING: This procedure should be performed by your ORACLE Database Administrator.
The SYSTEM user should have required privileges to perform this task.

Enable Autoextend on the APPS_TS_TX_DATA tablespace by executing the following Oracle PL/SQL command:

SQL > ALTER DATABASE DATAFILE '/u01/ORACLE/ORADATA/APPS_TS_TX_DATA.ORA' AUTOEXTEND ON NEXT 3072K

 

Share

ORA-19588: archived log RECID 1003 STAMP 2001986 is no longer valid

December 10th, 2019, posted in Oracle Queries
Share
Error in RMAN backup logORA-19588: archived log RECID 1003 STAMP 2001986 is no longer valid,oracle error,imam dba,dba imam,immam dba,dba immam,rman error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on d1 channel at 03/04/2018 23:16:26
ORA-19588: archived log RECID 1003 STAMP 2001986 is no longer valid

Recovery Manager complete.

 

SOLUTION :

This is not an error but a warning. The reason for this is archive logfile which this process is trying to take backup,
is already been backed up by another process and file is deletedThis error is mostly because of 2 reasons :
1. Either 2 backups like one full backup and one archive log backup are running in parallel.
And if the archivelog backup job tried to take backup of the archives, which were backed up and deleted by the full back
job running at the same time, then this warning will come.So never schedule two backups at the same time

2. Another reason might be because of few invalid or deleted records in control file.

 

To clean up invalid records, crosscheck the archive log:

RMAN> CROSSCHECK ARCHIVELOG ALL;

RMAN> DELETE EXPIRED ARCHIVELOG ALL;

It is recommended to use delete input option while backing up archivelog.

RMAN> backup archivelog until time 'sysdate -1' delete input;

If we want to take backup of all archivelogs, then:
——————————————————————

RMAN> backup archivelog all delete input ;
Share

ORA-28014: Cannot Drop Administrative Users

December 2nd, 2019, posted in Oracle Queries
Share

ORA-28014: cannot drop administrative users

 

The below error is encountered when I was trying to drop schema from 12C database :atabase, dba imam, dba immam, Imam Dba, ORA-28014: Cannot Drop Administrative Users, Oracle, Oracle DBA, oracle quries

SQL> drop user BKP CASCADE;
drop user BKP CASCADE
*
ERROR at line 1:
ORA-28014: cannot drop administrative users

Solution :
SQL> alter session set "_oracle_script"=true;

Session altered.

SQL> drop user BKP CASCADE;
User dropped.
Share