Question on dbtechstack-cloning

[Sri]

Hi Erman,

We are running adcfgclone as part of cloning but it was failing with connection error.DB-ETCC: Could not connect to database.How come database will be available here.we are trying to relink and configure the oracle home.we didnt begin restore yet


[orapatch@erpdevelopmentdb bin]$ perl adcfgclone.pl dbTechStack

                     Copyright (c) 2002, 2015 Oracle Corporation
                        Redwood Shores, California, USA

                        Oracle E-Business Suite Rapid Clone

                                 Version 12.2

                      adcfgclone Version 120.63.12020000.56

Enter the APPS password :

Running: Context clone...

Log file located at /u05/PATCHDB/12.1.0/appsutil/clone/bin/CloneContext_1031163720.log

Provide the values required for creation of the new Database Context file.

Target System Hostname (virtual or normal) [erpdevelopmentdb] :

Target Instance is RAC (y/n) [n] :

Target System Database SID : PATCHGST

Target System Base Directory : /u05/PATCHDB

Target System utl_file_dir Directory List : /usr/tmp

Number of DATA_TOP's on the Target System [3] : 1

Target System DATA_TOP Directory 1 : /u05/PATCHDB/datafiles

Target System RDBMS ORACLE_HOME Directory [/u05/PATCHDB/12.1.0] :

Do you want to preserve the Display [null] (y/n)  :

Target System Display [erpdevelopmentdb:0.0] :

Do you want the target system to have the same port values as the source system (y/n) [y] ? : n

Target System Port Pool [0-99] : 13

Checking the port pool 13
done: Port Pool 13 is free
Report file located at /u05/PATCHDB/12.1.0/appsutil/temp/portpool.lst
The new database context file has been created :
  /u05/PATCHDB/12.1.0/appsutil/PATCHGST_erpdevelopmentdb.xml
Check Clone Context logfile /u05/PATCHDB/12.1.0/appsutil/clone/bin/CloneContext_1031163720.log for details.

Running Rapid Clone with command:

Running:
perl /u05/PATCHDB/12.1.0/appsutil/clone/bin/adclone.pl java=/u05/PATCHDB/12.1.0/appsutil/clone/bin/../jre mode=apply stage=/u05/PATCHDB/12.1.0/appsutil/clone component=dbTechStack method=CUSTOM dbctxtg=/u05/PATCHDB/12.1.0/appsutil/PATCHGST_erpdevelopmentdb.xml showProgress contextValidated=true


Beginning rdbms home Apply - Tue Oct 31 16:37:53 2017

/u05/PATCHDB/12.1.0/appsutil/clone/bin/../jre/bin/java -Xmx600M -DCONTEXT_VALIDATED=true -Doracle.installer.oui_loc=/u05/PATCHDB/12.1.0/oui -classpath /u05/PATCHDB/12.1.0/appsutil/clone/jlib/xmlparserv2.jar:/u05/PATCHDB/12.1.0/appsutil/clone/jlib/ojdbc6.jar:/u05/PATCHDB/12.1.0/appsutil/clone/jlib/java:/u05/PATCHDB/12.1.0/appsutil/clone/jlib/oui/OraInstaller.jar:/u05/PATCHDB/12.1.0/appsutil/clone/jlib/oui/ewt3.jar:/u05/PATCHDB/12.1.0/appsutil/clone/jlib/oui/share.jar:/u05/PATCHDB/12.1.0/appsutil/clone/jlib/oui/srvm.jar:/u05/PATCHDB/12.1.0/appsutil/clone/jlib/ojmisc.jar   oracle.apps.ad.clone.ApplyDBTechStack -e /u05/PATCHDB/12.1.0/appsutil/PATCHGST_erpdevelopmentdb.xml -stage /u05/PATCHDB/12.1.0/appsutil/clone   -showProgress
APPS Password : Log file located at /u05/PATCHDB/12.1.0/appsutil/log/PATCHGST_erpdevelopmentdb/ApplyDBTechStack_10311637.log
  \      0% completed

Completed Apply...
Tue Oct 31 16:39:53 2017

Starting database listener for PATCHGST:
Running:
/u05/PATCHDB/12.1.0/appsutil/scripts/PATCHGST_erpdevelopmentdb/addlnctl.sh start PATCHGST
Logfile: /u05/PATCHDB/12.1.0/appsutil/log/PATCHGST_erpdevelopmentdb/addlnctl.txt

You are running addlnctl.sh version 120.4


Starting listener process PATCHGST ...


LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 31-OCT-2017 16:39:53

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Starting /u05/PATCHDB/12.1.0/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 12.1.0.2.0 - Production
System parameter file is /u05/PATCHDB/12.1.0/network/admin/PATCHGST_erpdevelopmentdb/listener.ora
Log messages written to /u05/PATCHDB/12.1.0/admin/PATCHGST_erpdevelopmentdb/diag/tnslsnr/erpdevelopmentdb/patchgst/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=erpdevelopmentdb.ttd.com)(PORT=1534)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=erpdevelopmentdb.ttd.com)(PORT=1534)))
STATUS of the LISTENER
------------------------
Alias                     PATCHGST
Version                   TNSLSNR for Linux: Version 12.1.0.2.0 - Production
Start Date                31-OCT-2017 16:39:53
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u05/PATCHDB/12.1.0/network/admin/PATCHGST_erpdevelopmentdb/listener.ora
Listener Log File         /u05/PATCHDB/12.1.0/admin/PATCHGST_erpdevelopmentdb/diag/tnslsnr/erpdevelopmentdb/patchgst/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=erpdevelopmentdb.ttd.com)(PORT=1534)))
Services Summary...
Service "PATCHGST" has 1 instance(s).
  Instance "PATCHGST", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

addlnctl.sh: exiting with status 0

addlnctl.sh: check the logfile /u05/PATCHDB/12.1.0/appsutil/log/PATCHGST_erpdevelopmentdb/addlnctl.txt for more information ...


Running ETCC to check status of DB technology patches...


 +===============================================================+
 |    Copyright (c) 2005, 2017 Oracle and/or its affiliates.     |
 |                     All rights reserved.                      |
 |             Oracle E-Business Suite Release 12.2              |
 |          Database EBS Technology Codelevel Checker            |
 +===============================================================+

Using context file from command line argument:
/u05/PATCHDB/12.1.0/appsutil/PATCHGST_erpdevelopmentdb.xml

Starting Database EBS Technology Codelevel Checker, Version 120.47
Tue Oct 31 16:39:53 IST 2017
Log file for this session : /u05/PATCHDB/12.1.0/appsutil/etcc/checkDBpatch_28635.log

Bugfix XML file version: 120.0.12020000.37
This file will be used for identifying missing bugfixes.

Mapping XML file version: 120.0.12020000.10
This file will be used for mapping bugfixes to patches.


[WARNING] DB-ETCC: Bugfix XML file (/u05/PATCHDB/12.1.0/appsutil/etcc/txk_R1220_DB_base_bugs.xml) in current directory is more than 30 days old.
 Check if a newer version is available in patch 17537119.

Identifying database release.
Database release set to 12.1.0.2.

Connecting to database.

+-----------------------------------------------------------------------------+
[WARNING] DB-ETCC: Could not connect to database, so unable to check:
  - Whether database is in READ-WRITE mode.
  - Existence of table needed to store DB-ETCC results.
  - Enablement of database In-Memory option.
    If this feature is enabled, additional fixes need to be verified.

Resolve the database connectivity issue, and then rerun DB-ETCC.
+-----------------------------------------------------------------------------+

Checking Bugfix XML file for 12.1.0.2

Obtained list of bugfixes to be applied and the list to be rolled back.
Now checking Database ORACLE_HOME.

The opatch utility is version 12.1.0.1.10.
DB-ETCC is compatible with this opatch version.

Found patch records in the inventory.

Checking Mapping XML file for 12.1.0.2

  Missing Bugfix: 22660003  ->  Patch 25967939
  Missing Bugfix: 24589081  ->  Patch 26043804
  Missing Bugfix: 25099339  ->  Patch 26043804
  Missing Bugfix: 25643931  ->  Patch 25643931
  Missing Bugfix: 25919622  ->  Patch 26043804

Generating Patch Recommendation Summary.

===============================================================================
PATCH RECOMMENDATION SUMMARY
===============================================================================
The default patch recommendations to install these missing bugfixes are:
-------------------------------------------------------------------------------
Oracle Database Release 12.1.0.2 - InMemory status unknown (No PSU applied)
-------------------------------------------------------------------------------
  Patch 25967939
    - Filename: p25967939_121020_Linux-x86-64.zip

  Patch 26043804
    - Filename: p26043804_121020_Linux-x86-64.zip

  Patch 25643931
    - Filename: p25643931_121020_Linux-x86-64.zip


+-----------------------------------------------------------------------------+
[WARNING] DB-ETCC: Could not connect to database, so unable to check:
  - Whether database is in READ-WRITE mode.
  - Existence of table needed to store DB-ETCC results.
  - Enablement of database In-Memory option.
    If this feature is enabled, additional fixes need to be verified.

Resolve the database connectivity issue, and then rerun DB-ETCC.
+-----------------------------------------------------------------------------+

[WARNING] Database not available. DB-ETCC results cannot be stored.

Finished checking fixes for Oracle Database: Tue Oct 31 16:40:03 IST 2017

Log file for this session: /u05/PATCHDB/12.1.0/appsutil/etcc/checkDBpatch_28635.log

===============================================================================
[orapatch@erpdevelopmentdb bin]$

Thank you

[ErmanArslansOracleBlog]

you are using "dbTechStack" argument.
It is for Cloning the Technology Stacks Only.

Why are you using this argument? What is your purpose?

Did you have a look at "Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)" with your purpose in mind?

[ErmanArslansOracleBlog]

This is weird. It should not be there.
Normally, after starting the listener, it should be completed.
In adcfgclone Version 120.63.12020000.37 , it is just like that.. No db connections are made.
But yours is  adcfgclone Version 120.63.12020000.56 , a higher version.. I think this enhancement is a little wrong ...

Anyways, ignore it. (if your db techstack is properly built/configured at this point)
Continue your cloning.
After you start up the db, run etcc check manually.

[ErmanArslansOracleBlog]

As I said, it seems to be warning.. It doesn't affect the script's return.

Do this ->

run dbtechstack again.
and just after you get the prompt use "echo $?" command.
If you get "0", then continue..

[Sri]

Perfect erman,thank you very much for your inputs.you saved lot of our time. it returned 0 and we could see the configuration was completed [orapatch@erpdevelopmentdb bin]$ echo $? 0 [orapatch@erpdevelopmentdb bin]$

[Sreedar Raju]

Hello:
I ran into this issue, and thought sharing the solution will help others.
I opened the script and debugged the issue, and it turns out this is really simple.
DBCC checkDBpatch.sh checks the CONTEXT_FILE for the instance name.
If the instance name is in lowercase in the CONTEXT File and the actual instance name is uppercase, as in TESTDB, DBCC will take the values from CONTEXT FILE and connect to an idle database.

So Fixing the instnace name's CASE correctly fixed the issue of DBCC complaining about unable to connect to database on the database while using checkDBpatch.sh.

Hope this helps.
Regards,
Sreedar

[Sreedar Raju]

Here is the no BS straight solution:
Fix the instance name s_instName in the $CONTEXT_FILE in the DB tier - with the same case as the environment variable $ORACLE_SID

Regards,
Sreedar