Posts Tagged ‘dba imam’

ORA-25153: Temp Tablespace error on adconfig.sh

July 24th, 2022, posted in Oracle, Oracle EBS Application
Share

========================================================================

                                                        If This Error Facing on Adconfig.sh or autoconfig.sh
=======================================================================

Atempting upload of Context file and templates to database...ERROR: InDbCtxFile.uploadCtx() :
Exception : Error executng BEGIN fnd_gsm_util.append_ctx_fragment(:1,:2,:3);
END;: 1; Oracle error -1187: ORA-01187: cannot read from file 515 because it failed verification tests
ORA-01110: data file 515: '/oradata/proddb/data/temp03.dbf' 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 -1187: ORA-01187: cannot read from file 515 because it failed verification tests
ORA-01110: data file 515: '/oradata/proddb/data/temp03.dbf' 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:1688)
at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:763)
FAILED
COMPLETED

=======================================================================================================================================================
                                             Solution Apply
============================================================================================================================================
login as: dgdb
dgdb@192.168.1.80's password:
Last login: Mon May  2 15:54:08 2016 from 192.168.81.61
[dgdb@b6dgdb ~]$ cd /oradb/proddb/PROD/db/tech_st/11.1.0/
[dgdb@b6dgdb 11.1.0]$ . ./T2_b6dgdb.env
[dgdb@b6dgdb 11.1.0]$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Mon May 2 16:46:14 2016

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

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

SQL>
sql> select bytes/1024/1024 from dba_temp_files;
select bytes/1024/1024 from dba_temp_files
*
ERROR at line 1:
ORA-01187: cannot read from file 513 because it failed verification tests
ORA-01110: data file 513: '/oradata/proddb/data/temp01.dbf'

SQL> col name format a50
SQL> run
1* select file#,status,name from v$tempfile

FILE# STATUS  NAME
---------- ------- --------------------------------------------------
1 ONLINE  /oradata/proddb/data/temp01.dbf
2 ONLINE  /oradata/proddb/data/temp02.dbf
3 ONLINE  /oradata/proddb/data/temp03.dbf

SQL> col DESCRIPTION format a40
SQL>
SQL> SELECT * FROM   database_properties WHERE  property_name like '%TABLESPACE'

PROPERTY_NAME                  PROPERTY_VALUE                           DESCRIPTION
------------------------------ ---------------------------------------- ----------------------------------------
DEFAULT_TEMP_TABLESPACE        TEMP                                     ID of default temporary tablespace
DEFAULT_PERMANENT_TABLESPACE   SYSTEM                                   Default Permanent Tablespace ID

CREATE TEMPORARY TABLESPACE temp3 TEMPFILE '/oradata/proddb/data/temp_01' SIZE 1024M TABLESPACE GROUP temp;

alter tablespace temp3 add tempfile  '/oradata/proddb/data/temp_02' SIZE 1024M;

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp3;

SQL> SELECT * FROM dba_tablespace_groups;

GROUP_NAME                     TABLESPACE_NAME
------------------------------ ------------------------------
TEMP                           TEMP1
TEMP                           TEMP2

DROP TABLESPACE temp1 INCLUDING CONTENTS AND DATAFILES;

DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;

sql> select TABLESPACE_NAME,FILE_NAME from dba_temp_files

TABLESPACE_NAME                FILE_NAME
------------------------------ ----------------------------------------
TEMP3                          /oradata/proddb/data/temp_02
TEMP3                          /oradata/proddb/data/temp_01

========================================================================================================================================
                                              Then Run Adconfig.sh
========================================================================================================================================
login as: dgapps
dgapps@192.168.1.81's password:
Last login: Mon May  2 16:24:32 2016 from 192.168.81.61
[dgapps@c6dgapps ~]$ cd /oraapps/prodapps/
oraInventory/ PROD/
[dgapps@c6dgapps ~]$ cd /oraapps/prodapps/PROD/apps/apps_st/appl/
[dgapps@c6dgapps appl]$ cd ad/12.0.0/bin
[dgapps@c6dgapps bin]$
[dgapps@c6dgapps bin]$ sh adconfig.sh
Enter the full path to the Context file:/oraapps/prodapps/PROD/inst/apps/T2_c6dgapps/appl/admin/T2_c6dgapps.xml
Share

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