![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Resolution: Verify configuration of tibcoadmin_domain.tra file and verify the system environment variables are set correctly. Ensure that TIBCO Rendezvous and TIBCO Repository are in the CLASSPATH, and that a matching version of TIBCO Rendezvous is in the PATH.
Resolution: Retry setting the server state. If this fails, edit the tibcoadmin_domain.tra files to set repo.state to the new desired value and shutdown all Load Balanced servers in the Load Balanced group, then restart the servers.
Resolution: Verify that the directory specified for the property repo.commitHistoryDirectory in the tibcoadmin_domain.tra file exists.
Resolution: Verify that the value specified for the repo.dbtype parameter in the tibcoadmin_domain.tra file is correct, has the correct capitalization and does not include extra spaces or punctuation. Supported values are: "Sql", "Oracle", "Db2", "Sybase"
Resolution: Make sure that the directory specified by the repo.directory parameter does not contain both a file %1.dat and a directory %1.
Resolution: Verify that your tibcoadmin_domain.tra file contains the property java.property.TIBCO_ADMIN_HOME=XX where XX is the directory where TIBCO Administrator is installed (for example, C \:/tibco/administrator/5.1).
Resolution: Add the instance name immediately following tibcr:// for server-based repositories, or provide the path to .dat file for file repositories.
Resolution: May be safely ignored if this server was intended to be a slave. If the server was intended to be a primary server, correct the hostname specified on repo.master parameter in the tibcoadmin_domain.tra file.
Resolution: If TIBCO Hawk monitoring is not required, set the parameter repo.hawkImplant in the tibcoadmin_domain.tra file to false. If TIBCO Hawk monitoring is required, install TIBCO Hawk and add the Hawk jar files as described in the TIBCO Repository Installation and Administration Guide.
Resolution: Either correct or comment out the repo.instanceNames parameter in the tibcoadmin_domain.tra file.
Resolution: Either correct or comment out the repo.instanceNames parameter in the tibcoadmin_domain.tra file.
Resolution: Indicates a configuration problem. Identify which of the servers is correctly configured and change the configuration for the other one. If Load Balancing mode is desired, make sure that all servers in a Load Balanced group have the same server name and that the repo.master parameter in the tibcoadmin_domain.tra file is uncommented and is non-empty for all servers.
Resolution: Indicates a configuration problem. Identify which of the servers is correctly configured and change the configuration for the other one. If Load Balancing mode is desired, make sure that the repo.master parameter in the tibcoadmin_domain.tra file is uncommented and is non-empty for all servers.
Resolution: Only occurs with database backends. Indicates first time running a 4.x server on data created with a 3.x server.
1. Bring up the 3.x server. and export the data using the RepoExport script from a 4.x version.
2. Stop the 3.x server.
4. Start the 4.x server.
5. Recreate the instances and import the saved data using RepositoryImport.
Resolution: Verify that the directory specified by the parameter repo.deploymentDirectory exists and that the server has read access to the directory and all of its files.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |