Archive for the ‘Oracle Queries’ Category

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

September 7th, 2018, posted in Oracle Queries
Share

When we are taking archive log backup with delete then got an error.

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

archived log file name=/pac/lci9t1/arch/redo_1_16470_842608348.arc thread=1 sequence=16470

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

archived log file name=/pac/lci9t1/arch/redo_1_16471_842608348.arc thread=1 sequence=16471

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

SOLUTION:

Cause: The archive logs seems that it is not yet applied in the standby database.

                        Select sequence# , applied from v$archived_log;

Action: Check the standby database and apply the logs manually and the start the deletion process.

              I can delete the archive logs by force using the below command.

      RMAN > delete noprompt force archivelog all;

But I don’t want to delete the archives which are not applied in standby  so i’m changing the configuration

RMAN> show all;

Old configuration:

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

Change as Below:

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

new RMAN configuration parameters:

CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

new RMAN configuration parameters are successfully stored

RMAN-08591: WARNING: invalid archived log deletion policy


Now check the configuration
RMAN> show all;

CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

Now I am able to delete those archivelogs now.

RMAN> delete noprompt archivelog all;

RMAN> crosscheck archivelog all;

Once I deleted those logs, I changed the rman configuration by the default one.

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY CLEAR;

RMAN> Show all;
Share

Oracle EBS Query To Check FND Languages Installed in Oracle

June 26th, 2018, posted in Oracle Queries
Share

 

clear columns
set lines 180
set pages 50
col LANGUAGE_CODE for a15
col NLS_LANGUAGE for a20
col ISO_LANGUAGE for a15
col INSTALLED_FLAG for a15
SELECT LANGUAGE_CODE,NLS_LANGUAGE, ISO_LANGUAGE,INSTALLED_FLAG 
FROM APPS.FND_LANGUAGES 
WHERE INSTALLED_FLAG IN ('B','I');
Share

ORA-00704 Bootstrap Process Failure

June 24th, 2018, posted in Oracle Queries
Share

ORA-00704 bootstrap process failure

After Upgrading ORACLE_HOME (from 10.2.0.1 to 10.2.0.4), I was started my database by using startup command, then got below error.

 

ORA-01092 oracle instance terminated. Disconnection force.

After I saw my alert log and got ORA-00704 error,

Alert Log :

 

Errors in file /oracle/product/db/10.2.0/dbhome/admin/test/udump/test_ora_11338.trc:

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Wed Jun 19 11:43:30 2013

Error 704 happened during db open, shutting down database

USER: terminating instance due to error 704

Instance terminated by USER, pid = 11338

ORA-1092 signalled during: ALTER DATABASE OPEN....


Solution:

I missed to run catupgrd.sql script after upgrade, so got above errors while starting the database.

 

Go to ORACLE_HOME/rdbms/admin

sqlplus / as sysdba

sql>startup upgrade

sql>@catupgrd.sql 

sql>@utlrp.sql

sql>shut immediate

sql>startup
Share

Other Ways To Take Trace in Oracle Application

June 16th, 2018, posted in Oracle Queries
Share

Problem sys@standby> startup mount; ORACLE instance started. Total System Global Area 835104768 bytes Fixed Size 2217952 bytes Variable Size 490735648 bytes Database Buffers 335544320 bytes Redo Buffers 6606848 bytes Database mounted. sys@standby> alter database recover managed standby database using current logfile disconnect; alter database recover managed standby database using current logfile disconnect * ERROR at line 1: ORA-01153: an incompatible media recovery is active Cause This indicates a currently running media recovery process. Action sys@standby> alter database recover managed standby database cancel; sys@standby> alter database recover managed standby database using current logfile disconnect; Note When shutting down physical standby database, firstly turn off media recovery process. Otherwise the next time when starting up redo apply again, you will encounter error ORA-01153.

Other Ways To Take Trace in Oracle Application :

 

 

SQL> ALTER SESSION SET sql_trace=TRUE;
SQL> ALTER SESSION SET sql_trace=FALSE;

SQL> EXEC DBMS_SESSION.set_sql_trace(sql_trace => TRUE);
SQL> EXEC DBMS_SESSION.set_sql_trace(sql_trace => FALSE);

SQL> ALTER SESSION SET EVENTS '10046 trace name context forever, level 8';
SQL> ALTER SESSION SET EVENTS '10046 trace name context off';

SQL> EXEC DBMS_SYSTEM.set_sql_trace_in_session(sid=>123, serial#=>1234, sql_trace=>TRUE);
SQL> EXEC DBMS_SYSTEM.set_sql_trace_in_session(sid=>123, serial#=>1234, sql_trace=>FALSE);

SQL> EXEC DBMS_SYSTEM.set_ev(si=>123, se=>1234, ev=>10046, le=>8, nm=>' ');


Share

Workflow : Workflow Component wfcmp

June 9th, 2018, posted in Oracle Queries
Share

Oracle Applicaition,Oracle Database,Oracle DBA,Oracle Applicaition DBA,Oracle Database DBA,Applicaition DBA,Database DBA,Oracle EBS Applicaition DBA,Oracle EBS Database DBA,Oracle,Oracle Applicaition,Oracle Database,Workflow : Workflow Component wfcmp,Oracle Applicaition Workflow,Oracle Database Workflow,oracle ebs logo,oracle ebs logo,oracle e business suite logo,

Query :


select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS
from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc
where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
order by COMPONENT_STATUS , STARTUP_MODE , COMPONENT_NAME;
Share