RC-50409: Topology information required for cloning not found

Summary

Running the preclone steps (adpreclone.pl dbTier) to create a new clone (probably from a previous clone) you get the errors:

RC-50409: Topology information required for cloning not found in the database.

Make sure that AutoConfig was run successfully prior to starting Rapid Clone, and try again

Raised by oracle.apps.ad.tools.AdCreateCtlFile

RC-50208: Exception  in method gen_crctrfclone_sql

RC-50208: Exception  in Constructor AdCreateCtlFile

Raised by oracle.apps.ad.tools.AdCreateCtlFile

This problem typically occurs when you try to create a new clone, from a clone created from a RAC database.

Workaround

Check if the following query returns a row!

SELECT DB_NAME, INSTANCE_NAME, INSTANCE_NUMBER, SID_GUID,

INTERCONNECT_NAME,PORT,

LISTENER_NAME, NAME, NODE_NAME, HOST

FROM applsys.FND_DATABASES, applsys.FND_DATABASE_INSTANCES, applsys.FND_TNS_LISTENERS,

applsys.FND_TNS_LISTENER_PORTS,

applsys.FND_APP_SERVERS, applsys.FND_NODES

WHERE FND_DATABASES.DB_GUID=FND_DATABASE_INSTANCES.DB_GUID AND

FND_DATABASE_INSTANCES.SERVER_GUID=FND_APP_SERVERS.SERVER_GUID AND

FND_TNS_LISTENERS.LISTENER_GUID = FND_TNS_LISTENER_PORTS.LISTENER_GUID AND

FND_TNS_LISTENERS.SERVER_GUID = FND_APP_SERVERS.SERVER_GUID AND

FND_NODES.NODE_ID = FND_APP_SERVERS.NODE_ID;

A. If YES, then update the INTERCONNECT_NAME column with the instance name. An example follows:

UPDATE applsys.FND_DATABASE_INSTANCES

SET INTERCONNECT_NAME = 'mramadhani'; or habiba

COMMIT;

B. If NO rows returned then run again the Autoconfig for the Database Tier.

At the end run again the precloning steps

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

alter system set control_files = '/home/oracle/teadata/cntrl01.dbf','/home/oracle/teadata/cntrl02.dbf','/home/oracle/teadata/cntrl03.dbf'scope=spfile;

/home/oracle/teadata/cntrl01.dbf, /home/oracle/teadata/cntrl02.dbf, /home/oracle/teadata/cntrl03.dbf

Initially when a database is created, by default the database will always be in NOARCHIVELOG mode. In order to put it in ARCHIVELOG mode, you must do the following:

1) You have to shutdown the database

SQL>shutdown immediate;

2) Set the parameter in the pfile (i.e. init.ora).

LOG_ARCHIVE_START=TRUE

3) Create New SPFILE from Modified pfile(init.ora)

SQL> create SPFILE from PFILE;

4) Startup Database in Mount Mode

SQL> startup mount;

5) Change Database log mode from NOARCHIVELOG to ARCHIVELOG

SQL> alter database archivelog;

6) Open DB for normal use

SQL> alter database open;

7) Check the archive log status

Error cloning a clone

A few posts ago I hit an issue with executing the runInstaller. It still surprised me that after hundreds of installs you can still hit new errors. The other day I hit a new error while cloning an EBS environment. While preparing the environment for cloning (executing adpreclone.pl dbTier), the error below appeared:

RC-50409: Topology information required for cloning not found in the database. Make sure that

AutoConfig was run successfully prior to starting Rapid Clone, and try again

Raised by oracle.apps.ad.tools.AdCreateCtlFile

RC-50208: Exception in method gen_crctrfclone_sql

RC-50208: Exception in Constructor AdCreateCtlFile

Raised by oracle.apps.ad.tools.AdCreateCtlFile

This particular environment is a clone of our production environment. After it was built users had performed some work and wanted it cloned to another environment. There are two solutions for this particular error, which can be found in detail in Metalink Note: 376964.1.

The easiest solution is to run autoconfig at the dbTier level. The curious part is that since this environment is a clone of production, autoconfig would would have been executed as part of the post cloning steps (adcfgclone.pl dbTier). I checked my post cloning logs and indeed it completed successfully. I executed autoconfig ($ORACLE_HOME/appsutil/bin/adconfig.sh) on the database tier again and the preclone script finished without error.

SELECT DB_NAME

      , INSTANCE_NAME

     , INSTANCE_NUMBER

     , SID_GUID

     , INTERCONNECT_NAME

     , PORT

     , LISTENER_NAME

      , NAME

      , NODE_NAME

      , HOST

 FROM FND_DATABASES

    , FND_DATABASE_INSTANCES

    , FND_TNS_LISTENERS

    , FND_TNS_LISTENER_PORTS

    , FND_APP_SERVERS

    , FND_NODES 

 where

 FND_DATABASES.DB_GUID=FND_DATABASE_INSTANCES.DB_GUID;

select NAME, SERVER_TYPE, FND_NODES.NODE_NAME from FND_APP_SERVERS,FND_NODES where FND_APP_SERVERS.NODE_ID =FND_NODES.NODE_ID and SERVER_TYPE='DB';

Try this sql as well, let me know if anything fails or looks incorrect:

SELECT DB_NAME

     , INSTANCE_NAME

     , INSTANCE_NUMBER

     , SID_GUID

     , INTERCONNECT_NAME

     , PORT

     , LISTENER_NAME

     , NAME

     , NODE_NAME

     , HOST

FROM FND_DATABASES

   , FND_DATABASE_INSTANCES

   , FND_TNS_LISTENERS

   , FND_TNS_LISTENER_PORTS

   , FND_APP_SERVERS

   , FND_NODES 

where FND_DATABASES.DB_GUID=FND_DATABASE_INSTANCES.DB_GUID and 

FND_DATABASE_INSTANCES.SERVER_GUID=FND_APP_SERVERS.SERVER_GUID and 

FND_TNS_LISTENERS.LISTENER_GUID = FND_TNS_LISTENER_PORTS.LISTENER_GUID

and

FND_TNS_LISTENERS.SERVER_GUID =  FND_APP_SERVERS.SERVER_GUID and 

FND_NODES.NODE_ID = FND_APP_SERVERS.NODE_ID;

Brian,

Do you have the techstack Validation utility installed in this

environment?

See metalink note 277366.1, it is very helpful in verifying that your

configuration is correct.

If you do not have it installed yet, we might be able to troubleshoot

this

the old-fashioned way:

1. Is this the first time you run preclone on this ORACLE_HOME?

2. When did you last invoke Autoconfig against the DB ORACLE_HOME?

3. I think your topology info in the APPS schema is inconsistent.

   Run this sql in the APPS schema to get some basic info:

select NAME, SERVER_TYPE, FND_NODES.NODE_NAME from FND_APP_SERVERS,

FND_NODES where FND_APP_SERVERS.NODE_ID = FND_NODES.NODE_ID and

SERVER_TYPE='DB';