Your Doorstep to the Temple of Oracle

Oracle EBS

The domain edit lock is owned by another session in non-exclusive mode – this deployment operation requires exclusive (

Posted by appsdba11i on November 6, 2013

During OBIEE upgrade i faced this issue

$ ./ -oracleInstance /u01/TEST/admin/instances/TEST_obiee -adminHost -adminPort 7001 -adminUsername weblogic

“[Deployer:149163]The domain edit lock is owned by another session in non-exclusive mode – this deployment operation requires exclusive
access to the edit lock and hence cannot proceed.
If you are using “Automatically Aquire Lock and Activate Changes” in the console, then the lock will expire shortly so retry this operation.”


In weblogic console “lock % edit Button is disabled ”


$ ./opmnctl redeploy -oracleInstance /u01/TEST/admin/instances/TEST_obiee -adminHost -adminPort 7001 -adminUsername weblogic

$ ./opmnctl registerinstance -oracleInstance /u01/TEST/admin/instances/TEST_obiee -adminHost -adminPort 7001 -adminUsername weblogic

after completion of both you can run the below command

$ ./ -oracleInstance /u01/TEST/admin/instances/TEST_obiee -adminHost -adminPort 7001 -adminUsername weblogic


Posted in Concurrent Manager | Tagged: , | Leave a Comment »

R12.2 Installation

Posted by appsdba11i on November 6, 2013

Posted in R12 | Leave a Comment »

lsnrctl: symbol lookup error: lsnrctl: undefined symbol: nlgh

Posted by appsdba11i on June 6, 2013


We faced this issue after OS upgrade in DB node

Unable to start listener . its erroing out with below error

bash-3.00$ lsnrctl start $ORACLE_SID
lsnrctl: symbol lookup error: lsnrctl: undefined symbol: nlgh

Searched metalink and find that this need Oracle Library relink.

Bringdown Database & Try relinking

bash-3.00$ cd $ORACLE_HOME/bin
bash-3.00$ relink all

If relink fails with Below error
writing relink log to: /u01/oracle/product/112/install/relink.log
/prod/oracle/product/112/bin/relink: line 146: 30017 Segmentation fault $RUNINSTALLER $ARGS>$LOGFILE 2>&1

then follow this

cd $ORACLE_HOME/rdbms/lib
make -f install

cd $ORACLE_HOME/network/lib
make -f install

This resolved our issue and we are able to start listener .

Posted in core oracle dba | Tagged: , , | Leave a Comment »

How to Kill or Cancel a expdp Job

Posted by appsdba11i on June 4, 2013

We recently got an option to cancel the Running Expdp.
we have killed the OS level process but it doesnt worked.SO i am giving the process which worked for me

we followd this process to cancel Job

Just Check your Running Job from Database (dba_datapump_jobs).

select job_name,owner_name,state from dba_datapump_jobs;

Get the Name of Job and kill the expdp Job

expdp / attach=JOBNAME

SQL> SELECT owner_name, job_name, operation, job_mode, state FROM dba_datapump_jobs; 2

————– ——————- —————– ————- ———

ex:expdp / attach=SYS_EXPORT_SCHEMA_01

bash-3.2$ expdp / attach=SYS_EXPORT_SCHEMA_01
Export: Release – Production on Mon Jan 3 11:25:35 2011
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
UDE-01017: operation generated ORACLE error 1017
ORA-01017: invalid username/password; logon denied
Username: system

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

Operation: EXPORT
Creator Privs: TRUE
Start Time: Monday, 01 June, 2011 16:04:23
Instance: TEST1
Max Parallelism: 1
EXPORT Job Parameters:
Parameter Name Parameter Value:
CLIENT_COMMAND system/******** dumpfile=scott.dmp directory=backup logfile=exp.log schemas=scott
Bytes Processed: 0
Current Parallelism: 1
Job Error Count: 0
Dump File: /u01/oracle/scott.dmp
bytes written: 19,435,520

Worker 1 Status:
Process Name: DW00
Object Schema: SCOTT
Object Name: YHJNSNHSS
Completed Objects: 1
Total Objects: 548
Completed Rows: 110,849,510
Worker Parallelism: 1

Export> KILL_JOB
Are you sure you wish to stop this job ([yes]/no): yes

This will Kill the expdp job


Posted in Issues | Tagged: , , | Leave a Comment »

The processing of JSP page

Posted by appsdba11i on May 5, 2013

Posted in Concurrent Manager | Leave a Comment »

The processing of a JSP page

Posted by appsdba11i on May 5, 2013

When we pass a URL(say AppsLocalLogin.jsp) in the browser, the steps can be summarized as:

A. Browser requests a page ending with .jsp
B. OC4J identifies from URL which application and therefore which .jsp file is targeted
C. OC4J checks to see if there is already a translated page (.class file) previously generated that corresponds to this page.
D. If such a page exists the dates on the .jsp file are compared with the date on the .class file
E. If the .jsp file is newer, the .class file is out of date and the translation if repeated
F. If there is no page already translated, the jsp page will get translated to produce the first .class file

The translated .class files are kept in the “persistence” directory of the OC4J container running the application.

This persistence directory will contain two sub-directories:

For each JSP page you will see 3 files in this directory.
The filename of the file is the same as the JSP name but with a _ prefix.
For a JSP named “myPage.jsp” you should see:


JSP translated files are saved is controlled by a setting in the OC4J “global-web-application” definition for the OC4J instance.


Here is the relevant tag within this file:

Within that, it is the “development” attribute that controls if the .java and .jpa files are kept or deleted after generation.

You would need to edit this file and set this value to true, to have the .java file for the jsp saved.

With regard to performance there is no real impact from changing this to true.
The file is produced one time each time the .jsp file is modified
The file is always produced even if development=”false”; it is just also removed.


Posted in 11i Apps | Leave a Comment »

Performing maintenance on standby database server without bringing down the primary database

Posted by sriwidu on March 15, 2013

We often experience situations where we have to perform maintenance on the server with a standby database.In few cases,it is mandatory to bring down the standby database,but we might not be  in a position to bring down the primary database due to business reasons.Here I am providing to all of you,the steps to perform maintenance on a standby database without shutting down the primary database.


step 1: Note down the current applied log details:

set linesize 100
col name format a15
select name,THREAD#,SEQUENCE#,Applied,to_char(COMPLETION_TIME,’yyyy/mm/dd hh24:mi:ss’)
from V$archived_log where (THREAD#,RECID) in (select THREAD#,max(RECID) from V$archived_log
where APPLIED=’YES’ group by THREAD#);

step 2: Disable standby archive writing:

At Primary

alter system set log_archive_dest_state_1=defer scope = both sid = ‘*’;

step 3: Disable auto recovery

At Standby

alter database recover managed standby database cancel;

shutdown immediate;


Perform all the maintenance tasks.


Step 5: Copy all the archives generated at primary while the standby was shutdown {This step will help in faster recovery}

Step 6: Bounce the archiver processes at primary {This step will ensure proper archive shipping}

Note : We don’t need to kill any processes here or bounce the primary.We can simply perform the following

a) Note down the log_archive_max_processes value

show parameter log_archive_max_processes

b) alter system set log_archive_max_processes=1;

c) Restore the value back by using below command

alter system set log_archive_max_processes=<old value noted in step a>;

Step 7: Startup standby database and configure automatic recovery:

startup nomount

alter database mount standby database;

alter database recover managed standby database disconnect from session;

step 8: Enable standby archive writing:

At Primary

alter system set log_archive_dest_state_1=enable scope = both sid = ‘*’;

step 9: verify if standby is in sync

Posted in core oracle dba | Tagged: , , , | Leave a Comment »

2012 in review

Posted by appsdba11i on January 6, 2013

The stats helper monkeys prepared a 2012 annual report for this blog.

Here’s an excerpt:

4,329 films were submitted to the 2012 Cannes Film Festival. This blog had 30,000 views in 2012. If each view were a film, this blog would power 7 Film Festivals

Click here to see the complete report.

Posted in Concurrent Manager | Leave a Comment »

RC-50014: Fatal: Execution of AutoConfig was failed Raised by

Posted by appsdba11i on October 16, 2012

Autoconfig failed with Below error

Enter value for 1: Enter value for 2: Enter value for 3: Connected.
ERROR at line 1:
ORA-29874: warning in the execution of ODCIINDEXALTER routine
ORA-29960: line 1,
DRG-11422: linguistic initialization failed
DRG-11446: supplied knowledge base file
/u01/oracle/product/112/ctx/data/enlx/droldUS.dat not installed
ORA-06512: at “SYS.DBMS_SQL”, line 1199
ORA-06512: at line 96

Solution :
Run below statements and retried autoconfig
$ cd $JTF_TOP/patch/115/sql/
$ sqlplus apps/apps @jtfiimt.sql JTF JTF NULL NULL

$ cd $JTF_TOP/patch/115/sql/
$ sqlplus apps/apps @jtfiaibu.sql JTF JTF APPS

Posted in Issues | Tagged: , | Leave a Comment »

worker failed during patch 13791619

Posted by appsdba11i on June 8, 2012

worker failed during patch 13791619

Target file: APPREBC.xlf
Start uploading…
oracle.apps.xdo.XDOException: Template APPPBR not found
at oracle.apps.xdo.oa.util.TemplateTranslator.getBaseTemplateInfo(
at oracle.apps.xdo.oa.util.TemplateTranslator.createMLSTemplates(
at oracle.apps.xdo.oa.util.XLIFFLoader.processUpload(
at oracle.apps.xdo.oa.util.XLIFFLoader.process(
at oracle.apps.xdo.oa.util.XLIFFLoader.main(

Cause :

MLS_TERRITORY was set to 00 instead of US.

It can be found with following query

SQL> select mls_territory from XDO_TEMPLATES_B where application_id=200 and template_code=’APPPBR’;


1) Take Backup of XDO_TEMPLATES_B

2) update table XDO_TEMPLATES_B

Set mls_territory=’US’,MLS_LANGUAGE=’en’
where application_id=200
and template_code =’APPPBR’;

3) Please check with below queries and commit after

select mls_territory from XDO_TEMPLATES_B where application_id=200 and template_code=’APPPBR’;

Select * from xdo_templates_b where template_code =’APPPBR’;

4) commit;

5) Then restart the failed worker using adctrl

Ref note : 1076074.1

Posted in patching | Tagged: , | Leave a Comment »