Monday, 27 February 2017

ADOP Phase=Preppare ERROR: [ERROR]: Patch file system WebLogic domain edit lock is enabled.

Action:

I run the adop phase=prepare on the run file system.

ERROR:

ERROR:

Verifying existence of context files in database.

Checking if adop can continue with available nodes in the configuration.
    Log: /u02/erptest/fs_ne/EBSapps/log/adop/23/20170227_125158/prepare/erplxtst1
        txkADOPEvalSrvStatus.pl returned SUCCESS

Validating configuration on admin node: [erplxtst1].
    Output: /u02/erptest/fs_ne/EBSapps/log/adop/23/20170227_125158/prepare/validate/remote_execution_result_level1.xml
    [ERROR]     txkADOPValidation failed on Node: "erplxtst1"
    [ERROR]     txkADOPValidation failed or is incomplete on Admin node: erplxtst1
    [ERROR]     Unable to continue processing on other available nodes: erplxtst2
    [UNEXPECTED]Error running "txkADOPValidation" on node(s): erplxtst1.


<?xml version = '1.0' encoding = 'UTF-8'?>
<NODES>
   <Node>
      <Name>erplxtst1</Name>
      <ProcessName>erplxtst1_erplxtst1pool-1-thread-1_erplxtst1_erplxtst1</ProcessName>
      <ResultString>    [WARNING]: There could be issues while validating the ports used for E-Business Suite instance against ports used in /etc/services. Refer the log file for more details.
        [ERROR]: Patch file system WebLogic domain edit lock is enabled.

.end std out.
end err out.
</ResultString>
      <Status>failed</Status>
      <TraceFile>NoTraceFile</TraceFile>
   </Node>
</NODES>

Solutions:

1.    On the PATCH file system:

mv /dev7i/applmgr/fs2/FMW_Home/user_projects/domains/EBS_domain_dev7i/edit.lock edit.lockOLD


2. Source the Run file system environment.

3. Re-run prepare:
 
  adop phase=prepare

  

Sunday, 26 February 2017

Adop Phase=prepare Failed After Creating the Custom Application in EBS R12.2

ERROR:

he adop phase=prepare failed with error.  The unexpected error occurred while executing txkADOPPreparePhaseSynchronize.pl.

In txkADOPPreparePhaseSynchronize log file
=============================
Inside evalADPATCHStatus()...
=============================
message_status: ERROR
Adsplice action did not go through successfully.
*******FATAL ERROR*******
PROGRAM : (//EBSDEV/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)
FUNCTION: main::execADSPLICE [ Level 1 ]
ERRORMSG: Adsplice action did not go through successfully.

Solutions:

Please run the following steps.

1. adop phase=abort,cleanup cleanup_mode=full (as env is currently in prepare failed state after adsplice was run on Run FS).
2. adop phase=fs_clone
3. adop phase=prepare

Wednesday, 8 February 2017

ERROR: After run the EXEC FND_CONC_CLONE.SETUP_CLEAN;

Action: Action: After run the EXEC FND_CONC_CLONE.SETUP_CLEAN;
Running adautoconfig.sh then facing below error.

1. ERROR:
begin
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
ORA-06512: at “APPS.ADX_PRF_PKG”, line 83
ORA-01403: no data found
ORA-06512: at line 7
 
2.Solution:
1. Run adadmin–>Recreate Grants and Synonyms
2. Compile Apps Schema
 
 

Monday, 23 January 2017

Login Page Issue 500 Internal Server Error

ERROR:

I found that error in application log and Database alert log when hitting the login URL.

Error in executing triggers on connect internal
*** 2017-01-21 18:37:11.364
----- Error Stack Dump -----
ORA-00604: error occurred at recursive SQL level 1
ORA-01438: value larger than specified precision allowed for this column
ORA-06512: at line 5


Solutions:

column TRIGGER_BODY format a1000
set pagesize 1000
spool trg.txt

SQL>select OWNER, TRIGGER_NAME,
TRIGGER_TYPE, TRIGGERING_EVENT, STATUS, TRIGGER_BODY
from DBA_TRIGGERS
where trim(triggering_event) = 'LOGON';

Status: Enabled


SQL>alter trigger LOGON_AUDIT_TRIGGER disable;


After disable the trigger Login page is opening.


OS Watcher Installation in RAC

 Step:1 Download and untar the oswbb812.tar under the grid user in RAC on the both nodes. Follow the OS Watcher User's Guide (Doc ID 153...