txkWfClone.sh Poor performance in R12
Hi, everybody should come across, while during a clone, you might have experienced very poor performance while running txkWfClone.sh profile.
Sometimes, it may end up in error
txkWfClone.sh INSTE8_APPLY -1
it is time out message and could not complete the cloning.
It Runs txkWfClone.sql against apps user in the database.
During cloning, execution of txkWfClone is required only for the first autoconfig run. For subsequent Autoconfig runs, it is not required
To resolve this,
Take the backup of the files described.
1). Move the phase of the script txkWfClone.sh to INSTALL_SETUP phase in $FND_TOP/admin/driver/fndtmpl.drv:
###### Required for OWF ######
fnd admin/template txkWfClone.sql INSTE8 /admin/install/ txkWfClone.sql 600
to
fnd admin/template txkWfClone.sh INSTALL /admin/install/ txkWfClone.sh 600
Changing the autoconfig phase of this script from INST8_SETUP to INSTALL_SETUP will prevent it from unwanted execution, resulting in better performance for future autoconfig runs.
The role of txkWfCLone.sh is to create workflow related references in db tier of target system in the cloning process.
During txkWfClone.sh's execution, the comparison between source system and target system URLs is done. Essentially, in a scenario where we are creating an additional middle tier from an existing middle tier/(s) having one common database tier, it will result in redundant operation of changing/creating workflow references for target middle tier.
For comparison, txkWfClone constructs an url for target system using the context variables as follows:
'%s_webentryurlprotocol%'||'://'||'%s_webhost%'||'.'||'%s_domainname%'||':'||'
%s_active_webport%'||'/pls/'||'%s_dbSid%'
Cheers!!!
Sometimes, it may end up in error
txkWfClone.sh INSTE8_APPLY -1
it is time out message and could not complete the cloning.
It Runs txkWfClone.sql against apps user in the database.
During cloning, execution of txkWfClone is required only for the first autoconfig run. For subsequent Autoconfig runs, it is not required
To resolve this,
Take the backup of the files described.
1). Move the phase of the script txkWfClone.sh to INSTALL_SETUP phase in $FND_TOP/admin/driver/fndtmpl.drv:
###### Required for OWF ######
fnd admin/template txkWfClone.sql INSTE8 /admin/install/ txkWfClone.sql 600
to
fnd admin/template txkWfClone.sh INSTALL /admin/install/ txkWfClone.sh 600
Changing the autoconfig phase of this script from INST8_SETUP to INSTALL_SETUP will prevent it from unwanted execution, resulting in better performance for future autoconfig runs.
The role of txkWfCLone.sh is to create workflow related references in db tier of target system in the cloning process.
During txkWfClone.sh's execution, the comparison between source system and target system URLs is done. Essentially, in a scenario where we are creating an additional middle tier from an existing middle tier/(s) having one common database tier, it will result in redundant operation of changing/creating workflow references for target middle tier.
For comparison, txkWfClone constructs an url for target system using the context variables as follows:
'%s_webentryurlprotocol%'||'://'||'%s_webhost%'||'.'||'%s_domainname%'||':'||'
%s_active_webport%'||'/pls/'||'%s_dbSid%'
Cheers!!!
