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
wdrshttp://www.w3.org/2007/05/powder-s#
schemahttp://schema.org/
n6https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n4https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.openlinksw.com/oplweb/faq/UDA/HowDoIInterpretDatabaseAgentVersionStringsAnswer#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
n2:this
wdrs:describedby
n4:uda-faq.ttl n6:uda-faq.ttl
rdf:type
schema:Answer
schema:answerExplanation
Database Agent Version Strings produce the following information: Finally, version string errors provide useful, diagnostic information. Failure to produce version strings often stems from one of three problems: 1. The agent does not exist on the system. 2. Permissions prohibit the execution of the agent. 3. The agent has library issues. Typically, the agent requires the addition of the database lib sub-directory to LD_LIBRARY_PATH, LIBPATH (AIX), or SHLIB_PATH (HP/UX). Database Agent Version Strings should be compared to Request Broker Version Strings and Client Version Strings to insure compatibility. Compatibility and stability problems arise, when Multi-Tier component versions differ.