This HTML5 document contains 4 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n2http://data.openlinksw.com/oplweb/faq/UDA/HowDoIInterpretRequestBrokerVersionStringsAnswer#
wdrshttp://www.w3.org/2007/05/powder-s#
schemahttp://schema.org/
n4https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n5https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
n2:this
wdrs:describedby
n4:uda-faq.ttl n5:uda-faq.ttl
rdf:type
schema:Answer
schema:answerExplanation
Request Broker Version Strings produce the following information: Version Information - Is the Broker current? Is the Broker version associated with specific limitations, formal bugzillas, or other known problems? Platform of Compilation - Compare the platform of compilation information with the output of uname -a on the affected server. Is the Broker compatible with that operating system? Finally, version string errors provide useful, diagnostic information. Failure to produce version strings often stems from one of three problems: 1. The Broker does not exist on the system. 2. Permissions prohibit the execution of the Broker version string. 3. The Broker has file dependency issues. Users may need to adjust PATH or other environment variables to pick up needed libraries. Request Version Strings should be compared to Database Agent Version Strings and Client Version Strings to insure compatibility. Compatibility and stability problems arise, when Multi-Tier component versions differ.