We are using TIBCO Administrator File based Domainin a primary and secondary server configuration. Sometimes we haveapplication deployment issues. What are the possible causes?
Article ID: KB0090545
Updated On:
| Products | Versions |
|---|---|
| TIBCO Administrator | - |
| Not Applicable | - |
Description
Resolution:
Occasionally, deployment issues may arise with a TIBCO Administrator File based Domain when using a primary-secondary servers configuration.
Here is a list of the most common possible causes.
- The admin super-user password has recently changed.
- The repo.state is set to READ_ONLY on a secondary server.
- Someone has recently restored the primary server's domain DAT files from a backup. This can lead the secondary server to believe that it does not need to sync up with the primary server.
- The primary and secondary TIBCO Administrator servers use different versions of TIBCO components such as TIBCO TRA.
- There is a time zone or simply time difference between the two servers.
- Temporary RV communication glitches may contribute to the synchronization failure such as dropped RV packets in the network or the RVD daemon is overloaded. If you suspect that your primary and secondary servers are out of sync, the following steps should be carried to sync them.
- On the secondary server machine:
. Stop your tibcoadmin, hawkagent and its associated tibhawkhma processes.
. Make sure that the RVD daemon is stopped and does not get respawned.
. Remove all files under <tibco_home>\administrator\domain\< domain_name>\data\ .
. Copy all .dat files under <tibco_home>\administrator\domain\< domain_name>\data\ from your primary TIBCO Administrator server to your secondary server.
Occasionally, deployment issues may arise with a TIBCO Administrator File based Domain when using a primary-secondary servers configuration.
Here is a list of the most common possible causes.
- The admin super-user password has recently changed.
- The repo.state is set to READ_ONLY on a secondary server.
- Someone has recently restored the primary server's domain DAT files from a backup. This can lead the secondary server to believe that it does not need to sync up with the primary server.
- The primary and secondary TIBCO Administrator servers use different versions of TIBCO components such as TIBCO TRA.
- There is a time zone or simply time difference between the two servers.
- Temporary RV communication glitches may contribute to the synchronization failure such as dropped RV packets in the network or the RVD daemon is overloaded. If you suspect that your primary and secondary servers are out of sync, the following steps should be carried to sync them.
- On the secondary server machine:
. Stop your tibcoadmin, hawkagent and its associated tibhawkhma processes.
. Make sure that the RVD daemon is stopped and does not get respawned.
. Remove all files under <tibco_home>\administrator\domain\< domain_name>\data\ .
. Copy all .dat files under <tibco_home>\administrator\domain\< domain_name>\data\ from your primary TIBCO Administrator server to your secondary server.
. Restart all TIBCO processes on the secondary server.
NOTE: Before making any changes make sure to make a proper backup of your Domain folder under <TRA>/Domain/<DomainName> and <ADMIN>/Domain/<DomainName> folders.
Issue/Introduction
We are using TIBCO Administrator File based Domainin a primary and secondary server configuration. Sometimes we haveapplication deployment issues. What are the possible causes?
Feedback
Yes
No
Powered by
