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

Adcfgclone error Oracle error -25153: ORA-25153: Temporary Tablespace is Empty has been detected in

October 27th, 2019, posted in Oracle EBS Application, Oracle Queries
Share
 | 50% completed ERROR: InDbCtxFile.uploadCtx() : Exception : Error executng BEGIN fnd_gsm_util.append_ctx_fragment(:1,:2,:3); END;: 1; Oracle error -25153: ORA-25153: Temporary Tablespace is Empty has been detected in FND_GSM_UTIL.APPEND_CTX_FRAGMENT.
oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Error executng BEGIN fnd_gsm_util.append_ctx_fragment(:1,:2,:3); END;: 1; Oracle error -25153: ORA-25153: Temporary Tablespace is Empty has been detected in FND_GSM_UTIL.APPEND_CTX_FRAGMENT.
at oracle.apps.ad.autoconfig.oam.InDbCtxFile.uploadCtx(InDbCtxFile.java:220)
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:1680)
at oracle.apps.ad.clone.ApplyApplTop.runCVM(ApplyApplTop.java:510)
at oracle.apps.ad.clone.ApplyApplTop.runAutoConfig(ApplyApplTop.java:552)
at oracle.apps.ad.clone.ApplyApplTop.doConf(ApplyApplTop.java:339)
at oracle.apps.ad.clone.ApplyApplTop.doApply(ApplyApplTop.java:382)
at oracle.apps.ad.clone.ApplyApplTop.(ApplyApplTop.java:267)
at oracle.apps.ad.clone.ApplyAppsTier.(ApplyAppsTier.java:105)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:67)
at java.lang.Thread.run(Thread.java:595)

 

 

Solution:

Add Tempfile to the temporary tablespace. It will resolve the issue !!

Share

ORA-25153: Temporary Tablespace Is Empty Has Been Detected

October 20th, 2019, posted in Oracle Queries
Share

The Following Error was detected while doing Cloning of DB Tier.

The Actual Fact Was:

The server was heavily loaded, so the control file creation terminated unsuccessfully. So manually created the control file and opened the database.

After this, I began run adconfig.sh

 

$cd $ORACLE_HOME/appsutil/bin
$ ./adconfig.sh
[oracle@prod bin]$ ./adconfig.sh
Enter the full path to the Context file: /oracle/PROD/db/tech_st/11.1.0/appsutil/UPGRDE_prod.xml
Enter the APPS user password:
The log file for this session is located at: /oracle/PROD/db/tech_st/11.1.0/appsutil/log/UPGRDE_prod/11081336/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.
Using ORACLE_HOME location : /oracle/PROD/db/tech_st/11.1.0
Classpath : :/oracle/PROD/db/tech_st/11.1.0/jdbc/lib/o jdbc5.jar:/oracle/PROD/db/tech_st/11.1.0/appsutil/java/xmlparserv2.jar:/oracle/PROD/db/tech_st/11.1.0/appsutil/java:/oracle/PROD/db/tech_st/11.1.0/jlib/netcfg.jar:/oracle/PROD/db/tech_st/11.1.0/jlib/ldapjclnt11.jar

Using Context file : /oracle/PROD/db/tech_st/11.1.0/appsutil/UPGRDE_prod.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...ERROR: InD bCtxFile.uploadCtx() : Exception : Error executng BEGIN fnd_gsm_util.append_ctx_ fragment(:1,:2,:3); END;: 1; Oracle error -25153: ORA-25153: Temporary Tablespac e is Empty has been detected in FND_GSM_UTIL.APPEND_CTX_FRAGMENT.
oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Error executng BEGIN fnd_gsm _util.append_ctx_fragment(:1,:2,:3); END;: 1; Oracle error -25153: ORA-25153: Temporary Tablespace is Empty has been detected in FND_GSM_UTIL.APPEND_CTX_FRAGMENT.
at oracle.apps.ad.autoconfig.oam.InDbCtxFile.uploadCtx(InDbCtxFile.java: 249)
at oracle.apps.ad.autoconfig.oam.CtxSynchronizer.uploadToDb(CtxSynchroni zer.java:328)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBCtx(File SysDBCtxMerge.java:678)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBFiles(Fi leSysDBCtxMerge.java:222)
at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:16 88)
at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:763)
FAILED

So after creating the controlfile, i did not created a tempfile. So,

 

sqlplus "/as sysdba"

SQL*Plus: Release 11.1.0.6.0 - Production on Mon Nov 8 13:45:51 2010

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


Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select * from v$tempfile;
no rows selected

SQL> alter tablespace TEMP1 add tempfile '/oracle/PROD/db/apps_st/data/TEMP01.dbf' size 500M autoextend on;
Tablespace altered.

SQL> select * from v$tempfile;
FILE# CREATION_CHANGE# CREATION_TIME TS# RFILE# STATUS
---------- ---------------- ------------------ ---------- ---------- -------
ENABLED BYTES BLOCKS CREATE_BYTES BLOCK_SIZE
---------- ---------- ---------- ------------ ----------
NAME
--------------------------------------------------------------------------------
1 5.9652E+12 08-NOV-10 284 1 ONLINE
READ WRITE 524288000 64000 524288000 8192
/oracle/PROD/db/apps_st/data/TEMP01.dbfimmam_dba,dba immam,imam dba,dba imam,oracle clone issue,oracle database,oracle application,oracle clone issue,ora oracle

 

 

After this, again run adconfig.sh on DB Tier :

 

[oracle@prod bin]$ ./adconfig.sh
Enter the full path to the Context file: /oracle/PROD/db/tech_st/11.1.0/appsutil/UPGRDE_prod.xml
Enter the APPS user password:
The log file for this session is located at: /oracle/PROD/db/tech_st/11.1.0/appsutil/log/UPGRDE_prod/11081348/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.
Using ORACLE_HOME location : /oracle/PROD/db/tech_st/11.1.0
Classpath : :/oracle/PROD/db/tech_st/11.1.0/jdbc/lib/ojdbc5.jar:/oracle/PROD/db/tech_st/11.1.0/appsutil/java/xmlparserv2.jar:/oracle/PROD/db/tech_st/11.1.0/appsutil/java:/oracle/PROD/db/tech_st/11.1.0/jlib/netcfg.jar:/oracle/PROD/db/tech_st/11.1.0/jlib/ldapjclnt11.jar

Using Context file : /oracle/PROD/db/tech_st/11.1.0/appsutil/UPGRDE_prod.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db111
Updating rdbms type in Context file to 32 bits
Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.
[oracle@prod bin]$

 

Cheers… Hope this helps…

Share