Archive for the ‘Oracle Queries’ Category

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

DBMS_AW_EXP: SYS.AW$EXPRESS: OLAP not enabled

November 24th, 2019, posted in Oracle Queries
Share

Customer Recommended Datapump Export (expdp) Raises Warnings Like “DBMS_AW_EXP: SYS.AW$EXPRESS: OLAP not enabled” (Doc ID 1638799.1)

APPLIES TO :
Oracle Database – Enterprise Edition – Version 11.2.0.4 and later
Oracle Database Cloud Schema Service – Version N/A and later
Oracle Database Exadata Express Cloud Service – Version N/A and later
Oracle Database Exadata Cloud Machine – Version N/A and later
Oracle Cloud Infrastructure – Database Service – Version N/A and later
Information in this document applies to any platform.oracle immam dba,oracle, immam dba,dba imam,dba immam

SYMPTOMS :
Expdp on Oracle Standard Edition / Standard Edition 1 produces below warnings

DBMS_AW_EXP: SYS.AW$EXPRESS: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWMD: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWCREATE: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWCREATE10G: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWXML: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWREPORT: OLAP not enabled

CAUSE :
The issue was explained in
Bug 17718899 – EXPDP ON STANDARD EDITION ONE SHOWS MESSAGES “OLAP NOT ENABLED”
closed with status ‘Not a Bug’ with below comment:

OLAP is not available in Standard Edition One (SE1) or Standard Edition (SE) as per the Database Licensing Information document,
it is only available in Enterprise Edition (EE).

This message is intentionally output for DATAPUMP and coded as such in 11.2.0.4 and higher Standard Edition One (SE1) or Standard Edition (SE).

From the Datapump perspective these are warnings and it is safe to ignore them.

NOTE :
The same symptoms can be encountered with the Oracle Enterprise Edition when OLAP is not installed.

SOLUTION :
The OLAP related warnings can be safely ignored for DataPump usage.


REFERENCES :
BUG:17718899 – EXPDP ON STANDARD EDITION ONE SHOWS MESSAGES “OLAP NOT ENABLED”

Share

Autoconfig Error on Appstier Tier: Context Value Management Failed

October 29th, 2019, posted in Oracle Queries
Share

After clone, while running adautocfg.sh getting the following error.

Context Value Management will now update the Context file


Updating Context file...COMPLETED


Attempting upload of Context file and templates to database...Exception 
in thread "main" java.lang.AbstractMethodError: oracle.sql.LnxLibThin.lnxnuc([BILjava/lang/String;)
at oracle.sql.NUMBER.toInt(NUMBER.java:413) 
at oracle.jdbc.dbaccess.DBConversion.NumberBytesToInt(DBConversion.java: 2959) 
at oracle.jdbc.driver.OracleStatement.getIntValue(OracleStatement.java:4583) 
at oracle.jdbc.driver.OracleCallableStatement.getInt(OracleCallableStatement.java:635) 
at oracle.apps.ad.autoconfig.oam.InDbCtxFile.uploadCtx(InDbCtxFile.java: 216) 
at oracle.apps.ad.autoconfig.oam.CtxSynchronizer.uploadToDb(CtxSynchronizer.java:328) 
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBCtx(FileSysDBCtxMerge.java:678) 
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBFiles(FileSysDBCtxMerge.java:222) 
at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1586) 
at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:665) 
Error returned from java. Context Value Management was aborted 
ERROR: Context Value Management Failed. 
Terminate. 


The logfile for this session is located at: 
%APPL_TOP%\admin\%CONTEXT_NAME%\log\\adconfig.log immam_dba,dba immam,imam dba,dba imam,oracle clone issue,oracle database,oracle application,oracle clone issue,ora oracle,Autoconfig Error on Appstier Tier: Context Value Management Failed,Imam_DBA ORACLE

 

Solution :

The reason for this error is that JAVA_TOP/oracle/sql contain the following two files
LnxLibThin.class,
LdxLibThin.class
Need to remove and re-run autoconfig again.

As part of the 11.5.10 Maintenance Pack, these files should have been removed by adpatch
After successfully removed these two files, need to re-run the autoconfig from Applmgr user

Cheers!!!

Share