Unable to change the password for fnd_user sysadmin in EBS

 Issue:

After Clone while changing the APPS user password using FNDCPASS command getting the following error messages in log file.

FNDCPASS apps/apps 0 Y system/manager USER sysadmin sysadmin

Working...

Unable to change the password for fnd_user sysadmin.

Cause:

Signon Password policy is enabled in ERP application, so it will not allow to repeat the username in passwords.

Solution:

It should not contain the username in passwords. ie. sysadmin/sysadmin123

FNDCPASS apps/apps 0 Y system/manager USER sysadmin admin123

ORA-00230: operation disallowed: snapshot control file enqueue unavailable

Issue: 

While running the RMAN backup command getting the following error,

cannot make a snapshot control file

released channel: c1

released channel: c2

released channel: c3

released channel: c4

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on c1 channel at 02/28/2020 20:15:58

ORA-00230: operation disallowed: snapshot control file enqueue unavailable

RMAN>  Recovery Manager complete.

(or)

RMAN backup log file shows below while running

waiting for snapshot control file enqueue

waiting for snapshot control file enqueue

waiting for snapshot control file enqueue

waiting for snapshot control file enqueue

waiting for snapshot control file enqueue

Solution:

Check any other RMAN backup process running in server level and kill the os process

$ ps -ef|grep rman

$ kill -9 pid

after killing the OS process also getting same snapshot error. Please follow the below,

Execute the following query to determine which job is causing the wait:

SELECT s.SID, USERNAME AS "User", PROGRAM, MODULE,

       ACTION, LOGON_TIME "Logon", l.*

FROM V$SESSION s, V$ENQUEUE_LOCK l

WHERE l.SID = s.SID

AND l.TYPE = 'CF'

AND l.ID1 = 0

AND l.ID2 = 2;

You should see output similar to the following (the output in this example has been truncated):

SID User Program              Module                    Action           Logon

--- ---- -------------------- ------------------------- ---------------- ---------

  785 SYS  rman@exad (TNS V1-V3) backup full datafile: ch5  0000007 STARTED  24-OCT-16

SQL> select sid,serial#,username,osuser,machine,event,program,sql_id,blocking_session,logon_time from gv$session where status like 'ACTIVE' and SID='785';

ALTER SYSTEM KILL SESSION '785,37463' IMMEDIATE;

Warning!!! Due to high volume of data, got out of memory exception.

 Error:

When submitting the Account Analysis Report, XLAAARPT (navigation: Reports::Request::Standard), the report errors on every run with the following error message in the log file:

***Warning!!! Due to high volume of data, got out of memory exception...***

****Please retry with scalable option or modify the Data template to run in scalable mode...****

Solution:

Increase the Memory for the Concurrent Program

1. Go to "System Administrator" responsibility.

2. Navigate to Concurrent - > Program - > Define.

3. Search for the report (example Account Analysis Report), "XLAAARPT" shortname in Concurrent Process window.

4. Set the Options field to -Xmx2048M (make sure you DONT MISS OUT the "-" before the X).

5. Save.

6. Bounce the Concurrent Manager for the effects to take place.

adcfgclone.pl dbconfig RC-20200: fatal: could not find unzip

 While cloning database Tier

Error :

RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

Please make sure you have UnZip 5.X in your path and try again…

ERROR while running Apply…

ERROR: Failed to execute /clone/oracle/product/11.2.0/appsutil/clone/bin/adclone.pl

Please check logfile.

Solution 1

Which unzip should point to $ORACLE_HOME/bin/unzip

Take the backup of existing unzip from $ORACLE_HOME/bin

cd $ORACLE_HOME/bin

mv unzip unzip_bkp

cp /usr/bin/unzip to $ORACLE_HOME/bin

Make sure the unzip utility under /usr/bin should be of version 5.X and not 6

Solution 2:

Download the unzip file from below link 

https://oss.oracle.com/el4/unzip/unzip.html

Take the backup of existing unzip from $ORACLE_HOME/bin

Untar donwloaded file into the $ORACLE_HOME/bin/

Retest the issue.

Find Toad Connections in Oracle Database

select p.spid, s.sid,s.process cli_process,s.last_call_et/3600 last_call_et ,

s.status,s.action,s.module,s.program

from gv$session s, gv$process p

where

p.addr=s.paddr

and s.MODULE like ('%TOAD%')

Order by last_call_et;

ADOP Cutover Failed

Before starting the ADOP patch cycle,

Run File system: FS1

Patch File System: Fs2

Issue:

Prepare : Completed

Apply : Completed

Finalize: Completed

Cutover: Failed --> After file system switch over completed and while starting Middle Tier it is failed.

set pagesize 200;

set linesize 160;

col PREPARE_STATUS format a15

col APPLY_STATUS format a15

col CUTOVER_STATUS format a15

col ABORT_STATUS format a15

col STATUS format a15

select NODE_NAME,ADOP_SESSION_ID, PREPARE_STATUS , APPLY_STATUS  ,CUTOVER_STATUS , CLEANUP_STATUS , ABORT_STATUS , STATUS 

from AD_ADOP_SESSIONS

order by ADOP_SESSION_ID;

ADOP_SESSION_ID P A C C A S

--------------- - - - - - -

12 Y Y 6 N X F

12 Y Y 5 N X F 

Cutover Statuses:

cutover_status='Y' 'COMPLETED'

cutover_status not in ('N','Y','X') and status='F' 'FAILED'

cutover_status='0' 'CUTOVER STARTED'

cutover_status='1' 'SERVICES SHUTDOWN COMPLETED'

cutover_status='3' 'DB CUTOVER COMPLETED'

cutover_status='D' 'FLIP SNAPSHOTS COMPLETED'

cutover_status='4' 'FS CUTOVER COMPLETED'

cutover_status='5' 'ADMIN STARTUP COMPLETED'  --> Issue occured here

cutover_status='6' 'SERVICES STARTUP COMPLETED'

cutover_status='N' 'NOT STARTED'

cutover_status='X' 'NOT APPLICABLE'

So Cutover Failed, But File system is already switched i.e patch edition (FS2) become run edition and run edition (FS1) become patch.

Run File System: FS2

Patch File System: FS1

Solution:

1. Source the Run edition Env file (FS2 is Run edition here)

2. Shutdown the application services and start only admin server.

3. Run the cutover again, this cutover will not bringdown and brought up any services and also will not flip filesystem again,  It will complete quickly.

adop phase=cutover mtrestart=no

4. Restart tha application services on all nodes.