In this Document

Symptoms
Cause
Solution

Applies to:
Oracle Applications Manager - Version: 11.5.10.0 to 11.5.10.2 - Release: 11.5.10 to 11.5.10
Information in this document applies to any platform.
***Checked for relevance on 19-Feb-2011***

Symptoms
The following error occurs when running adcfgclone.pl dbTier:

From the ApplyDBTier_<timestamp>.log file:

RC-40201: Unable to connect to Database <db sid>.
StackTrace:
java.lang.Exception: Cannot connect to database using DBUtil
at
oracle.apps.ad.clone.ApplyDatabase.checkDBConnection(ApplyDatabase.java:339
8)
at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:524)
at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:328)
at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:304)
at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:154)
at java.lang.reflect.Constructor.newInstance(Native Method)
at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:68)
at java.lang.Thread.run(Thread.java:479)

Creating the control file for <instance name> database

SQL*Plus: Release 10.2.0.2.0 - Production on Tue Apr 17 11:52:01 2007
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
ERROR:
ORA-01031: insufficient privileges
ORA-01031: insufficient privileges
ERROR:
ORA-01031: insufficient privileges
ORA-01031: insufficient privileges
SP2-0640: Not connected
SP2-0640: Not connected

Also in the log file is the following line showing that ownership is being set to 'root' even
though that is not the correct database owner.

setting ownership: root:root

The context file for the new target db tier shows:
<dbuser oa_var="s_dbuser" osd="unix">root</dbuser>
<dbgroup oa_var="s_dbgroup" osd="unix">root</dbgroup>
The issue can be reproduced by running adcfgclone.pl dbTier.

Cause
The issue is caused by an incorrect /tmp/adpairsfile.lst. The parameters s_dbuser and
s_dbgroup reference the 'root' user instead of the true database user. This file should be
created fresh during a clone but in some cases where a previous clone failed on the server this
file could exist prior to the current clone session.

Solution
To implement the solution, please execute the following steps:
1. Rename the /tmp/adpairsfile.lst and the newly created database context file in
$ORACLE_HOME/appsutil.
2. Re-run adcfgclone.pl dbTier

Related