Re: adop fails after cloning

Posted by ErmanArslansOracleBlog on
URL: http://erman-arslan-s-oracle-forum.114.s1.nabble.com/adop-fails-after-cloning-tp488p489.html

hi,

Run checkDBPatch script again and please send me the logfile located in programdir.
checkDBpatch_$$.log , $$ should be your pid, just do an ls -lrt on the folder and send me the last log file.

There could be a problem in one of the inserts that checkDB  makes. That insert may load data for adop queries and as insert can not be done appropriately, adop can not see the checkdb script is executed.
This is an assumption, but there are inserts like this in the checkdb script.

InsCmd="INSERT INTO APPLSYS.TXK_TCC_RESULTS (tcc_version,bugfix_xml_version,node_name, database_name,component_name,component_version,component_home,check_date,check_result, check_message) values"
tccversion=$progver
tccexectime=$execdate
tccresult=$TCCresult
xmlversion=$xmlver
server=`grep s_dbhost ${contextfile} | sed 's/^.*s_dbhost[^>.]*>[ ]*\([^<]*\)<.*/\1/g; s/ *$//g'`
dbname=$DBNAME
compver=$DB_VERSION
compname="RDBMS"
comphome=$ORACLE_HOME
chkmesg1=`echo ${MissRlbkFix}| tr "\012" "," `
chkmesg=`echo ${chkmesg1}| sed 's/.$//'`

So, I would start checking "TXK_TCC_RESULTS" table and the variables used in the insert above.
server may be wrong or dbname may be wrong. You name it.. But control this table, compare it with your PROD database at least