OpenLink Shop Glossary Terms

Common Glossary Terms

Availability -- Presents the offer availability, i.e., whether or not it is in stock.
Available from -- The offer is available for purchase from the identified company.
Benefit -- Benefit associated with the offered product.
CPUs -- The maximum number of Logical Processors which the license will utilize.
Description -- Detailed description of an Offer.
Duration -- The duration of the product (license) on Offer, measured from issue date.
Linked Data URI -- Hyperlink-based Offer Identifier.
Max Purchase -- The maximum number of times a single customer is allowed to purchase a given Offer. This is typically used to restrict access to free Offers.
Offer Code -- A unique identifier for an Offer.
Offer Valid Until -- Date until which the Offer is valid.
Operating System -- The Operating System(s) to which the Software Application License is scoped.
Operating System Family -- The Operating System Family(ies) to which the Software Application License may be scoped.
Operating System Type -- The Types (Workstation or Server) of Operating System to which the Software Application License may be scoped.
Order -- Add the Offer into your shopping cart.
Product -- Software Application License.
Retail Price -- Retail Price of an Offer.
Seats -- The number of systems (e.g., Enterprise Edition Request Broker hosts, Express or Lite Edition Driver hosts, Virtuoso Server hosts) on which the product (license) may be deployed.
Special Price -- Special Price of an Offer.
Summary -- Short summary description of an Offer.

UDA Glossary Terms

ADO.NET Provider -- A Software Application that provides a data access channel between an ADO.NET compliant applications and a backend database management system, using the native protocols of the target DBMS or Driver vendor.
Agent -- A Software Application. May be a Bridge Agent or a Database Agent.
Bridge Agent -- A Software Application. Provides connections to a DBMS-agnostic Data Access Mechanism (e.g., ODBC, JDBC). Enterprise Edition only.
Broker Operating System -- The Operating System on which the Enterprise Edition Request Broker, Database Agents, and/or Bridge Agents will run; where the Enterprise Edition product (license) will be deployed.
Broker Operating System Type -- The Types (Workstation or Server) of Operating System on which the Enterpris Edition product (license) may be deployed.
Data Access Protocol Scope -- Specific data access protocol(s) (ODBC, JDBC, ADO.NET, OLEDB, and/or XMLA) supported by data access driver (Express or Lite Edition) and/or license (Enterprise Edition).
Database Agent -- A Software Application. Provides connections to a specific DBMS (e.g., Oracle 11g, Microsoft SQL Server, MySQL 5.x). Enterprise Edition only.
Database Engine -- Specific version(s) of a Database Management System (DBMS) supported by an ODBC driver, JDBC driver, ADO.NET provider, OLEDB provider, XMLA provider, or License File.
DBMS Family -- Database Management System (DBMS) Family.
Generic Client -- A Software Application. An ADO.NET Provider, JDBC Driver, or ODBC Driver which connects a client application using such Data Access Mechanism to a Request Broker and associated Agents. Enterprise Edition only.
JDBC Driver -- A Software Application. A Software Application that provides a data access channel between a JDBC compliant applications and a backend database management system, using the native protocols of the target DBMS or Driver vendor.
Maximum Concurrent Client Machines — The maximum number of client hosts (physical or virtual, metered by IP address) which may simultaneously open ODBC, JDBC, ADO.NET, OLEDB, and/or XMLA database sessions through a Request Broker and/or Database or Bridge Agent under the given license. Only applicable to Enterprise Edition.
Maximum Database Sessions -- Maximum concurrent database sessions which may be opened under the given license. Opening a new session increments the count; closing an active session decrements the count. For Express or Lite Edition Drivers, this is per licensed host. For Enterprise Edition, this pool is shared by all client connections going through a given Request Broker.
Maximum Logical Processors -- The maximum number of Logical Processors which the operating system reports as present in the machine (physical or virtual) on which the product (license) is deployed, i.e., the Express Edition Driver Host, Lite Edition Driver Host, or Enterprise Edition Request Broker Host.
ODBC Driver -- A Software Application. A Software Application that provides a data access channel between an ODBC compliant applications and a backend database management system, using the native protocols of the target DBMS or Driver vendor.
OLEDB Provider -- A Software Application. A Software Application that provides a data access channel between an OLEDB compliant applications and a backend database management system, using the native protocols of the target DBMS or Driver vendor.
Request Broker or simply Broker -- A Software Application. Receives connection requests from Generic Clients, and apportions these to Agents according to Rules defined by its administrator. Enterprise Edition only.
XMLA Provider -- A Software Application. A Software Application that provides a data access channel between an XMLA compliant applications and a backend database management system, using the HTTP protocol.

Virtuoso Glossary Terms

Client Application Connectivity Protocol Restrictions -- Client application connectivity protocol restriction which specifies the criteria of how a license allows an application to connect to a server.
Client Application Restrictions -- Client application restriction which specifies the criteria of how a license allows an application to connect to a server.
Client Connection Restrictions -- Client connection restriction which specifies the criteria of how a license allows a client to connect to a server.
"Cluster" Module -- Enables Virtuoso Shared-Nothing Cluster functionality. Not required for Virtuoso Replication Clusters .
Clustering -- Indicates whether the additional "Cluster" Module is enabled for the Software Application License.
Column Store -- Indicates whether the additional "Column Store" Module is enabled for the Software Application License.
"Column Store" Module -- Enables Column Store functionality.
Connections -- Client interface portals, formerly known as Database Server Threads . A configurable number are dedicated to handling HTTP-based client requests; the remainder are available for any other data access mechanism (ODBC, JDBC, OLEDB, ADO.NET, XMLA, etc.).
CPU Affinity -- A programming mechanism by which an Application binds to one or more CPU Cores (Logical and/or Physical), irrespective of total available.
CPUs -- The maximum number of Logical Processors which the Software Application will utilize. On Windows and Linux (and soon on Solaris, AIX, and HP-UX), this is managed by CPU Affinity, so the license may be used on machines which report any number of processors, but the software will only utilize the number specified by the license.
- Note: Mac OS X does not support CPU Affinity, so your license must enable utilization of at least as many Logical Processors as are reported present in your Mac.
Database Server Threads -- See Connections .
Operating System -- The Operating Systems for which the Software Application License may be scoped.
Virtuoso Cluster -- A collection of Virtuoso Server Instances configured to operate together, either as a Virtuoso Replication Cluster or a Virtuoso Shared-Nothing Cluster . A Virtuoso Cluster may be housed on a single machine, or distributed over multiple machines, which may themselves be geographically dispersed.
Virtuoso Cluster Node (VCN) -- A Virtuoso Server Quorum that's a member of a Virtuoso Shared-Nothing Cluster . Requires that the "Cluster" Module be licensed.
Virtuoso Host Cluster (VHC) -- A collection of machines, each hosting one or more Virtuoso Server Instances that are members of a Virtuoso Cluster .
Virtuoso Host Cluster Node (VHCN) -- A machine hosting one or more Virtuoso Server Instances that are members of a Virtuoso Cluster .
Virtuoso Replication Cluster -- A collection of Virtuoso Server Instances and/or Virtuoso Shared-Nothing Clusters , each working individually, which are configured into any supported replication topology (e.g., star, chain, bidirectional). Requires that the "Cluster" Module be licensed if the Virtuoso Replication Cluster is comprised in part or in whole of Virtuoso Shared-Nothing Clusters .
Virtuoso Server Instance (VSI) -- One instantiation of the Virtuoso Server executable, minimally comprising an INI file, a DB file, and a TRX file.
Virtuoso Server Quorum (VSQ) -- A collection of one or more mutually-mirroring Virtuoso Server Instances configured to operate as and appear to the world as one Instance, typically comprising a Virtuoso Cluster Node , as part of a Virtuoso Shared-Nothing Cluster . Requires that the "Cluster" Module be licensed.
Virtuoso Shared-Nothing Cluster -- A collection of Virtuoso Cluster Nodes , working in parallel, controlled by a single "Master" Node. Optimal performance typically requires network, if not physical, proximity. Requires that the "Cluster" Module be licensed.

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

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

Namespace Prefixes

Prefix	IRI
n438	https://data.openlinksw.com/oplweb/faq/uda/5fa0003e20f9d6aa8a1d723e3a2eae25#
n423	https://data.openlinksw.com/oplweb/faq/uda/3ac9df2bf203c263a115b4d33a3fa5ab#
n242	https://data.openlinksw.com/oplweb/faq/uda/fd15dc5522ecb10698877e6d65af8b5f#
n433	https://data.openlinksw.com/oplweb/faq/uda/f057c4d1c0619cbc7380aecb971d87c0#
n360	https://data.openlinksw.com/oplweb/faq/uda/6afa46515e9b1e80f62b7133b3ddc1bc#
n422	https://data.openlinksw.com/oplweb/faq/uda/1143b82cd51c240f7ff544643cc5de08#
n185	https://data.openlinksw.com/oplweb/faq/uda/b491d1efc5d74b461c2b4ddeae46c2e5#
n408	https://data.openlinksw.com/oplweb/faq/uda/91ef0d91b319873ba4a59d09d880fb71#
n432	https://data.openlinksw.com/oplweb/faq/uda/f5018efc504a6e6487b16e5720a55be5#
n195	https://data.openlinksw.com/oplweb/faq/uda/11fe68ccd8923c1bae8f894cdeea1b0e#
n146	https://data.openlinksw.com/oplweb/faq/uda/ce015f9da074523402636e384231a509#
n233	https://data.openlinksw.com/oplweb/faq/uda/be215bedea2a72b38eaec14984d8b5db#
n262	https://data.openlinksw.com/oplweb/faq/uda/3097b0a7ebbefbf27bfa86e6003f425b#
n187	https://data.openlinksw.com/oplweb/faq/uda/33b75a2b0baa25e8c221da41ecd5c3a6#
n83	https://data.openlinksw.com/oplweb/faq/uda/0ec1505188e677dc2826b428666b4f96#
n327	https://data.openlinksw.com/oplweb/faq/uda/9eadb9e6f2241ea13e1de56d49bca680#
n356	https://data.openlinksw.com/oplweb/faq/uda/4b4088961623493896bf55a50ecd3fc5#
n82	https://data.openlinksw.com/oplweb/faq/uda/0f45c06ee60bd7848f03bde779551d3d#
n133	https://data.openlinksw.com/oplweb/faq/uda/bc1d2373ad7831b581e22da9ccecfd6d#
n42	https://data.openlinksw.com/oplweb/faq/uda/9920e6efeed3c4f19d1fd3408ce4f1f3#
n269	https://data.openlinksw.com/oplweb/faq/uda/b738b85dec3626c6de26d798072ae92e#
n170	https://data.openlinksw.com/oplweb/faq/uda/605f77eb6332d9280245870f3487ca77#
n106	https://data.openlinksw.com/oplweb/faq/uda/ca79417110f57017a7d8067fa411e632#
n156	https://data.openlinksw.com/oplweb/faq/uda/4fbc44dc12e6ca71745063c71f6a612e#
n450	https://data.openlinksw.com/oplweb/faq/uda/4a363e387a75cebfdc5d9c66596df97e#
n70	https://data.openlinksw.com/oplweb/faq/uda/7dc7628eb68b46968d18cfe1999c374b#
n517	http://data.openlinksw.com/oplweb/glossary-term/NewSQL#
n177	https://data.openlinksw.com/oplweb/faq/uda/8f09d2f368d46f182b40a521e6dce5f8#
n366	https://data.openlinksw.com/oplweb/faq/uda/0b8015e04061d62985320efee5dd3217#
n470	http://data.openlinksw.com/oplweb/faq/Virtuoso/517696a8604089bedb7562b999e57ae538eca3ce#
n239	https://data.openlinksw.com/oplweb/faq/uda/cc93cca2bcc88311768c02ecf6982580#
n378	https://data.openlinksw.com/oplweb/faq/uda/dfe30d17eabf8314616dc633936585e3#
n97	https://data.openlinksw.com/oplweb/faq/uda/3e2fb94c8088c70c2366a9c6f6d71f06#
n236	https://data.openlinksw.com/oplweb/faq/uda/66cb63ba49f4f52c1de0724d0e26784c#
n219	https://data.openlinksw.com/oplweb/faq/uda/03f4d8c10d5ac33101491cc22d627bd7#
n406	https://data.openlinksw.com/oplweb/faq/uda/229ff1ec10646329b09f4367f120c444#
n100	https://data.openlinksw.com/oplweb/faq/uda/1b69f179230d3fd78d568a9b4cc1641f#
n211	https://data.openlinksw.com/oplweb/faq/uda/03dc6ca6667e67faec8738350dbf58dc#
n95	https://data.openlinksw.com/oplweb/faq/uda/d7fff7f36af3c56d45301385bba3220b#
n88	https://data.openlinksw.com/oplweb/faq/uda/bf4afb1dee3133c7f1b5ef05fb317d06#
n331	https://data.openlinksw.com/oplweb/faq/uda/af4220861c2ad4a55cd79e5b6c8c88fb#
n27	https://data.openlinksw.com/oplweb/faq/uda/297334bc185bb8b256d3e24e9f0a8f1c#
n350	https://data.openlinksw.com/oplweb/faq/uda/89931263651c298995f0ba441fa4e0dd#
n420	https://data.openlinksw.com/oplweb/faq/uda/7f32c5193b1e7668417d61259c3cb3b0#
n188	https://data.openlinksw.com/oplweb/faq/uda/a60932be3ab8727a83d60086303369ee#
n131	https://data.openlinksw.com/oplweb/faq/uda/ca917627575e86988ccc39d5d994b448#
n243	https://data.openlinksw.com/oplweb/faq/uda/309521b969592d1866cc5092cdd373a7#
n225	https://data.openlinksw.com/oplweb/faq/uda/eb99bb662716d243892d08fda5a84b59#
n388	https://data.openlinksw.com/oplweb/faq/uda/9133614d6c9589276a8624e6c5e94689#
n305	https://data.openlinksw.com/oplweb/faq/uda/9f500574e90e32a94b38c7995a0ce3a9#
n10	https://data.openlinksw.com/oplweb/faq/uda/85cf5ad955bcff74ae813c84646515d8#
n268	https://data.openlinksw.com/oplweb/faq/uda/6e13d19f112e6f1c89108ab84fa6d58c#
n394	https://data.openlinksw.com/oplweb/faq/uda/8a58d66f2a7d9ce39ceda49a5bbe9bee#
n396	https://data.openlinksw.com/oplweb/faq/uda/c5d39d5477023b67fa888f6050f806ee#
n374	http://data.openlinksw.com/oplweb/faq/b592b5827f38981ebc07ac8a43058282272949e0#
n455	https://data.openlinksw.com/oplweb/faq/uda/bb759a6d035f73be1c8f05d55cdd2416#
n293	https://data.openlinksw.com/oplweb/faq/uda/4ec0bb49449774dce7ba165cdbd0be85#
n280	https://data.openlinksw.com/oplweb/faq/uda/ad2b538c5dfd8e850ca8892c1eeabd1e#
n460	http://data.openlinksw.com/oplweb/glossary-term/DefClusterModule#
n137	https://data.openlinksw.com/oplweb/faq/uda/79143cc781817296c95f9e9ae9471b30#
n485	http://data.openlinksw.com/oplweb/faq/bb11d63e98a39882309774190fa07c195b72b22b#
n115	https://data.openlinksw.com/oplweb/faq/uda/a0cb070e6170586796dd5a2bf67cc3c5#
n506	https://aws.amazon.com/marketplace/pp/
n240	https://data.openlinksw.com/oplweb/faq/uda/0e7e44bf07d423b6ee3b2a8600265691#
n66	https://data.openlinksw.com/oplweb/faq/uda/40bde81ef0e725d6ab6825acb352d062#
n481	http://data.openlinksw.com/oplweb/faq/15bdd998980350282d8fbc337d49e67e5132a171#
n140	https://data.openlinksw.com/oplweb/faq/uda/6239ee5fb153df73f2472e9742513964#
n35	https://data.openlinksw.com/oplweb/faq/uda/358ef3b0149d10d9d0978da2cd6eacd1#
n253	https://data.openlinksw.com/oplweb/faq/uda/f74f1a598f4677c317a62b78cc898e7e#
n22	https://data.openlinksw.com/oplweb/faq/uda/1c06328291cea2f58d51dadd2ef9fb37#
n285	https://data.openlinksw.com/oplweb/faq/uda/74e4fdfc3a7b0d3562238f35c24702a2#
n191	https://data.openlinksw.com/oplweb/faq/uda/2a323e6a20ae56952613a912c9b43006#
n214	https://data.openlinksw.com/oplweb/faq/uda/c669c8a3857d3689c8f3444d4c2dfe11#
n5	https://data.openlinksw.com/oplweb/faq/uda/b7537ec7be197d9ea1d8e5456eaad247#
n334	https://data.openlinksw.com/oplweb/faq/uda/93297dc13f38c349f5c01a5b39c97788#
n251	https://data.openlinksw.com/oplweb/faq/uda/1e78cfb7b229689f3ad0632d8b20800e#
n43	https://data.openlinksw.com/oplweb/faq/uda/088ce23cb1920e34e05fd41a80c22290#
n241	https://data.openlinksw.com/oplweb/faq/uda/f4d5aef46c38be9e2724ec9f04f8b709#
n96	https://data.openlinksw.com/oplweb/faq/uda/1e6257163d35e22c0af7e998b05a1096#
n87	https://data.openlinksw.com/oplweb/faq/uda/05ab7f2a1658a0a22f1c5fc702ea1bcc#
n250	https://data.openlinksw.com/oplweb/faq/uda/3278b42021ab7933540424c7edc68686#
n322	https://data.openlinksw.com/oplweb/faq/uda/0822a66134ab4b884bc6bf34d5a3640d#
n215	https://data.openlinksw.com/oplweb/faq/uda/ddd6e80d1a493ce43730d773a987eb9f#
n444	https://data.openlinksw.com/oplweb/faq/uda/0d61e98059c773218dc54108ef7df63e#
n370	https://data.openlinksw.com/oplweb/faq/uda/0f752946ad071043f183000c98bf56ba#
n101	https://data.openlinksw.com/oplweb/faq/uda/b7b9c059aa406b464f9abe09b952e8e4#
n377	https://data.openlinksw.com/oplweb/faq/uda/ce214c105c50696f84439acefac15ab0#
n419	https://data.openlinksw.com/oplweb/faq/uda/5810fc87a87720532f07d8fd3e30ff39#
n78	https://data.openlinksw.com/oplweb/faq/uda/87002fdba34772bfbeb835662185f3f0#
n28	https://data.openlinksw.com/oplweb/faq/uda/96ae0b3156114faa82b37bf263971eda#
n134	https://data.openlinksw.com/oplweb/faq/uda/4488f021e73791d99d34ce7698715751#
n303	https://data.openlinksw.com/oplweb/faq/uda/83794586559aa06f11524e35f34d2893#
n59	https://data.openlinksw.com/oplweb/faq/uda/14ec56d13962391d5c9ea1e9b98b3402#
n326	https://data.openlinksw.com/oplweb/faq/uda/c1803b32c1fd3f6d1916d7ad4b04a307#
n12	https://data.openlinksw.com/oplweb/faq/uda/2c250661142499c78005dc54caa2e00b#
n363	https://data.openlinksw.com/oplweb/faq/uda/21fe38fc34251416292646dfc9e40138#
n182	https://data.openlinksw.com/oplweb/faq/uda/75922b2f6ac7f90405d6ae343c95df77#
n258	https://data.openlinksw.com/oplweb/faq/uda/6a4e3e3cd628e6adab93c9c5227fbf95#
n412	https://data.openlinksw.com/oplweb/faq/uda/8ab8587ce14ed34ca95967319adf52cc#
n193	https://data.openlinksw.com/oplweb/faq/uda/4365153032355323cc0f24460c54de4e#
n314	https://data.openlinksw.com/oplweb/faq/uda/cc0dad6f9d677a2f70b8ee2cff6405ab#
n486	http://data.openlinksw.com/oplweb/faq/c8c6d2e0c6179b5379182b2827fac6a0b5d7871c#
n487	http://data.openlinksw.com/oplweb/faq/Virtuoso/38223c3529264d6d8c355047bc6173be111a2b29#
n47	https://data.openlinksw.com/oplweb/faq/Virtuoso#
n509	https://www.openlinksw.com/partners/
n235	https://data.openlinksw.com/oplweb/faq/uda/ce99494ddd422a18309931ed8b5e1a47#
n238	https://data.openlinksw.com/oplweb/faq/uda/b7a02a4824244817041fcb0c88ea3780#
n54	https://data.openlinksw.com/oplweb/faq/uda/0ef5c805305fdbc3732c39ab05c3224a#
n123	https://data.openlinksw.com/oplweb/faq/uda/bf2fe0ccee7f05647955db52df23cfa8#
n514	https://virtuoso.openlinksw.com/
n417	https://data.openlinksw.com/oplweb/faq/uda/25fe09bcb7947b98729a96f91f6675ad#
n503	http://data.openlinksw.com/oplweb/glossary-term/ODBCSystemDSN#
n315	https://data.openlinksw.com/oplweb/faq/uda/4800f0c006673eddf65ab433dbd52ad3#
n300	https://data.openlinksw.com/oplweb/faq/uda/965961f86d3a60b86df569a00e58e07e#
n153	https://data.openlinksw.com/oplweb/faq/uda/8576c5e1e078c702a09eba6cac6ebfc7#
n244	https://data.openlinksw.com/oplweb/faq/uda/311d34c7beffc994075829e6e22f43b2#
n174	https://data.openlinksw.com/oplweb/faq/uda/ac4ac8a4b390bdfc18afd2c6035ae956#
n317	https://data.openlinksw.com/oplweb/faq/uda/d08213be52d2610af2c9c67d87f053cf#
n218	https://data.openlinksw.com/oplweb/faq/uda/2d4eab3d2e144f1dc97eac9f443b8259#
n282	https://data.openlinksw.com/oplweb/faq/uda/0da2b9e2e2419f2d64dfb541d8d2e248#
n79	https://data.openlinksw.com/oplweb/faq/uda/bd90c45a86ab9969cbc2da878868776c#
n287	https://data.openlinksw.com/oplweb/faq/uda/64a223ddddbd49c64f6131150042c4c3#
n102	https://data.openlinksw.com/oplweb/faq/uda/5f0f783aac1b96df719176f7871c73d8#
n201	https://data.openlinksw.com/oplweb/faq/uda/596d4eade80add38bc25fc0c805bbdcd#
n39	https://data.openlinksw.com/oplweb/faq/uda/a8b91e687d7a5223fe241884f3a542f1#
n120	https://data.openlinksw.com/oplweb/faq/uda/ba03d7ac3a3bf3f4f51b9792b27e54b3#
n461	http://data.openlinksw.com/oplweb/glossary-term/clustering#
n451	https://data.openlinksw.com/oplweb/faq/uda/e75f3146b2a552316b2501cf9721ab89#
n276	https://data.openlinksw.com/oplweb/faq/uda/748ee12b4728c60601c60b986d7b7db4#
n8	https://data.openlinksw.com/oplweb/faq/uda#
n469	http://data.openlinksw.com/oplweb/faq/9e8311fdc6d314540be6679eea7caf7b0b512aaf#
n343	https://data.openlinksw.com/oplweb/faq/uda/b3fbe03ed3dcd487c187d3d49892f7c3#
n511	https://hub.docker.com/u/
n210	https://data.openlinksw.com/oplweb/faq/uda/d26bd7561ccc6e9b512993b14a80dff8#
n23	https://data.openlinksw.com/oplweb/faq/uda/c5f36bee1ca5b5cb6690459fd4f6a539#
n127	https://data.openlinksw.com/oplweb/faq/uda/217361b21158c53fe111076023248cdb#
n204	https://data.openlinksw.com/oplweb/faq/uda/714171c86e2b8a43e5f3ed2c6d26921d#
n130	https://data.openlinksw.com/oplweb/faq/uda/539e86859b34ffd517123470338feb48#
n192	https://data.openlinksw.com/oplweb/faq/uda/6f72d7ea7863e36a62dda2a1d4480028#
n362	https://data.openlinksw.com/oplweb/faq/uda/786541eaa8c5bfec7df3e342f39a5557#
n254	https://data.openlinksw.com/oplweb/faq/uda/36034fef68c7b3c77045c5132574bf49#
n387	https://data.openlinksw.com/oplweb/faq/uda/6f54cd042594ca1b0fab60046794866e#
n173	https://data.openlinksw.com/oplweb/faq/uda/70cf9b17387ce56c909be92519224b30#
n90	https://data.openlinksw.com/oplweb/faq/uda/ee54e66dce783b00749e900bb41ae0ae#
n436	https://data.openlinksw.com/oplweb/faq/uda/39b67142ab7112ff1b41af6c21ee468d#
n468	http://data.openlinksw.com/oplweb/faq/Virtuoso/a902b6ad755dbd97b7e967c9c2ed9cc56e4edbd5#
n500	http://data.openlinksw.com/oplweb/glossary-term/ODBCAdministrator#
n329	https://data.openlinksw.com/oplweb/faq/uda/75b056489b6b5995a174265937f809eb#
n181	https://data.openlinksw.com/oplweb/faq/uda/d307472b9a726b215326f70b31e131eb#
n340	https://data.openlinksw.com/oplweb/faq/uda/dfe745d746d7faa2b4e3c32040eabd01#
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
n56	https://data.openlinksw.com/oplweb/faq/uda/4dfd89d9b29480f056ff0e0fa71faf7d#
n279	https://data.openlinksw.com/oplweb/faq/uda/329a854c9251df19b7e4c026df9d893d#
n168	https://data.openlinksw.com/oplweb/faq/uda/9c6549a81045716836cc46af67440d3a#
n116	https://data.openlinksw.com/oplweb/faq/uda/519f944c9d52624c301a5c7ff349d285#
n252	https://data.openlinksw.com/oplweb/faq/uda/d489073e3970bf7fa5fe00a1683a55f0#
n464	http://data.openlinksw.com/oplweb/glossary-term/DefVirtuosoReplicationCluster#
n330	https://data.openlinksw.com/oplweb/faq/uda/f07cd970ae1b34c4ea81fa47e2d9d6ea#
wdrs	http://www.w3.org/2007/05/powder-s#
n337	https://data.openlinksw.com/oplweb/faq/uda/8078d03c2648ef8aaea13bb79e9b26d6#
n40	https://data.openlinksw.com/oplweb/faq/uda/321dd64c32802e1d2a9883d410753fb4#
n62	https://data.openlinksw.com/oplweb/faq/uda/85c80fb94ea93dfed2cb2379291eca7b#
n230	https://data.openlinksw.com/oplweb/faq/uda/8918d4433ff6ee32e63285c87537d70d#
n457	https://data.openlinksw.com/oplweb/faq/uda/0cb430654006e7f2c5d11f05923a76b0#
n439	https://data.openlinksw.com/oplweb/faq/uda/b289e5afa49d292b9c60554af06b3d9a#
n368	https://data.openlinksw.com/oplweb/faq/uda/3fbc48fd3d725dbba406e719ae86b490#
n319	https://data.openlinksw.com/oplweb/faq/uda/3de8eb583af3d3bdd95a5f267dcba99e#
n467	http://data.openlinksw.com/oplweb/glossary-term/DefVirtuosoClusterNode#
n475	http://data.openlinksw.com/oplweb/faq/3814155d8288b302be6a9665bbe0f5d5a143f78a#
n138	https://data.openlinksw.com/oplweb/faq/uda/fee14645d110ef3a795fdd18abb849f5#
n373	https://data.openlinksw.com/oplweb/faq/uda/d3265bddd9decd627c475fcf1fee2ccf#
n128	https://data.openlinksw.com/oplweb/faq/uda/43977745152a29417c6154acf3b9e2f4#
oploffer	http://www.openlinksw.com/ontology/offers#
n361	https://data.openlinksw.com/oplweb/faq/uda/af1bea9cb08b0540963f9576eefb9de4#
n7	https://data.openlinksw.com/oplweb/faq/uda/62f712109dc5e043be8844e6ce6f134c#
n73	https://data.openlinksw.com/oplweb/faq/uda/5c9ab22b3753c351d9d02e2b9dbce117#
n507	http://media-cache-ec0.pinimg.com/originals/75/11/a8/
n476	http://data.openlinksw.com/oplweb/faq/8302e09bef19a81914254ab1e4f16d101348ec34#
n508	https://www.openlinksw.com/contact/
n178	https://data.openlinksw.com/oplweb/faq/uda/bf23721b2f74bc54dbcb257517f60e8e#
n257	https://data.openlinksw.com/oplweb/faq/uda/96cc8c3f023a3d74c5d47b5da5618a89#
n431	https://data.openlinksw.com/oplweb/faq/uda/7078660d9bbcd04c54b19ce476f7ca3f#
n367	https://data.openlinksw.com/oplweb/faq/uda/c1dde4591ef4b20f879936eb67b7e29d#
n117	https://data.openlinksw.com/oplweb/faq/uda/4a7a6b8ff64f19e0d87cf5dba2cc98c5#
n132	https://data.openlinksw.com/oplweb/faq/uda/3e22242c66d66ef5571bd1b26bf3ecc6#
n135	https://data.openlinksw.com/oplweb/faq/uda/bf30da0a3d268b7db1abe408ed3eb4ba#
n310	https://data.openlinksw.com/oplweb/faq/uda/d27dae26630ca881cf0902b2b0c3f2fb#
n190	https://data.openlinksw.com/oplweb/faq/uda/b005453cdb2956faf162f0a3841c42ed#
n401	https://data.openlinksw.com/oplweb/faq/uda/4c5e4de81c5d334dac94b47a4c8931ba#
n74	https://data.openlinksw.com/oplweb/faq/uda/b66c5b2901da13ac83f462a4e5ac031d#
n259	https://data.openlinksw.com/oplweb/faq/uda/128a3afe7810f8e2105a96daa9933a51#
n426	https://data.openlinksw.com/oplweb/faq/uda/17a9d35013eeff92d1d579bed441870b#
n379	https://data.openlinksw.com/oplweb/faq/uda/12adf01d799c7e9243241bbfdd60a99d#
n165	https://data.openlinksw.com/oplweb/faq/uda/da45c549e231034c80993c486bff6017#
n288	https://data.openlinksw.com/oplweb/faq/uda/13d55bd737a06c24b002e28c94d65c92#
n397	https://data.openlinksw.com/oplweb/faq/uda/adf36a3ed26b1b9af4941ec5f608a782#
n155	https://data.openlinksw.com/oplweb/faq/uda/60c51324fa030c54ebf41a96ad3bfc7d#
n65	https://data.openlinksw.com/oplweb/faq/uda/69f3ae847fe07578d9f9d60d13694a74#
n498	http://data.openlinksw.com/oplweb/glossary-term/ODBCDriverManager#
n411	https://data.openlinksw.com/oplweb/faq/uda/4502546805f253390522c23a8e701499#
n496	http://data.openlinksw.com/oplweb/glossary-term/JDBCDSN#
n501	http://data.openlinksw.com/oplweb/glossary-term/JDBC#
n45	https://data.openlinksw.com/oplweb/faq/uda/5a98e4e4156d8b133d0d5892c3cf01d0#
n109	https://data.openlinksw.com/oplweb/faq/uda/850abf1af5c9faa0a9a0d245d3cf7c29#
n60	http://data.openlinksw.com/oplweb/glossary-term/SPARQLFederatedQuery#
n448	https://data.openlinksw.com/oplweb/faq/uda/92fdefd87faadecee3dfb572d8625883#
n92	https://data.openlinksw.com/oplweb/faq/uda/c5ca594ac76677f9f20cfe0036c4a1d8#
n425	https://data.openlinksw.com/oplweb/faq/uda/6791448f31a25b30db56314e3cbfd419#
n298	https://data.openlinksw.com/oplweb/faq/uda/43fa9b30dceabf7929e780b0d7eaac22#
n49	https://data.openlinksw.com/oplweb/faq/uda/84afe5021b17577fbfd4d40796bac9fa#
n380	https://data.openlinksw.com/oplweb/faq/uda/929491f84f138b43a48796a102f002ba#
n237	https://data.openlinksw.com/oplweb/faq/uda/1db423a0ee13f6a92e4ab56d031ccbf8#
n353	https://data.openlinksw.com/oplweb/faq/uda/97a0c2e0a411cd85e417a27b32ade136#
n512	http://data.openlinksw.com/oplweb/product_family/virtuoso#
n41	https://data.openlinksw.com/oplweb/faq/uda/2e364ac44af29999fe8aa77ef1979c13#
n463	http://data.openlinksw.com/oplweb/glossary-term/DefVirtuosoSharedNothingCluster#
n171	https://data.openlinksw.com/oplweb/faq/uda/6fb5475816ba10feeced59ecf1590edb#
n163	https://data.openlinksw.com/oplweb/faq/uda/c83be52a5ccc0c8106dfa19dda116a26#
n518	http://data.openlinksw.com/oplweb/glossary-term/NoSQL#
n19	https://data.openlinksw.com/oplweb/faq/uda/faa6e025511baf9e82aa383e11063f9f#
n175	https://data.openlinksw.com/oplweb/faq/uda/bce5d83fe401388fb40c57de942b83af#
n375	https://data.openlinksw.com/oplweb/faq/uda/afebb8ca474c46274159d57017481f74#
n55	https://data.openlinksw.com/oplweb/faq/uda/767b2bb141982259ee145c8093586aba#
n427	https://data.openlinksw.com/oplweb/faq/uda/b877accbcdcd6ebe6fdee106e39428ae#
n255	https://data.openlinksw.com/oplweb/faq/uda/a4321997ca2de9f5cd76d5a01e566c5a#
n349	https://data.openlinksw.com/oplweb/faq/uda/b980b1723c06344315d5c951d4cabb76#
n291	https://data.openlinksw.com/oplweb/faq/uda/0c9f9d9705112fa8a94096bf60e68d88#
n369	https://data.openlinksw.com/oplweb/faq/uda/b9559ed7b9425f8fa3bcb071a69a1111#
n184	https://data.openlinksw.com/oplweb/faq/uda/29453ccb90b70d265071b325f1d883f2#
n21	https://data.openlinksw.com/oplweb/faq/uda/571d0b4129f9d5965394440495bb4325#
n249	https://data.openlinksw.com/oplweb/faq/uda/3792ac4cdfe6d5a357ab087809bb5899#
n223	https://data.openlinksw.com/oplweb/faq/uda/821a2c802e94ef6ccdfa4945ac103dae#
n36	https://data.openlinksw.com/oplweb/faq/uda/6a628311df195fa0087c45f443a4ad70#
n122	https://data.openlinksw.com/oplweb/faq/uda/1d6aea4807c72628f6cf6e1b0cc45a0c#
n25	https://data.openlinksw.com/oplweb/faq/uda/6e417c825778a8ad6a13eb6b37099bae#
n272	https://data.openlinksw.com/oplweb/faq/uda/9031925ec18e443e345c9c4c28d70a73#
n316	https://data.openlinksw.com/oplweb/faq/uda/fad46931192c069fcd661fa91b50b25c#
n510	https://shop.openlinksw.com/license_generator/virtuoso/
n199	https://data.openlinksw.com/oplweb/faq/uda/bc58b7864020848dffd512390108f6fd#
n227	https://data.openlinksw.com/oplweb/faq/uda/9ec8c912f6ffdd8dc893598e678069c5#
n435	https://data.openlinksw.com/oplweb/faq/uda/184abc89c51c4a7cefe0f5a48829232f#
n162	https://data.openlinksw.com/oplweb/faq/uda/fcf4ff253153174592cfea932627b636#
n81	https://data.openlinksw.com/oplweb/faq/uda/5dc4c465185240b0c5159eef211524e5#
n344	https://data.openlinksw.com/oplweb/faq/uda/ffa2d890e0528dd84dff86794aded18e#
n143	https://data.openlinksw.com/oplweb/faq/uda/d7b5fba4e7e99d5938aee20d3da6110a#
n364	https://data.openlinksw.com/oplweb/faq/uda/133f0eab045bc0dc3d2748e203f7849e#
n302	https://data.openlinksw.com/oplweb/faq/uda/d4a9ae0ba933a83ce65b9ea484efa97c#
n6	https://data.openlinksw.com/oplweb/faq/uda/194b43540b62cbd8b7c9e11b788339e1#
n147	https://data.openlinksw.com/oplweb/faq/uda/fa49a1e1caec125671747a50b1439f83#
n270	https://data.openlinksw.com/oplweb/faq/uda/efcfc546417714610216a4d28665224e#
n144	https://data.openlinksw.com/oplweb/faq/uda/fe6ab789dbd7c8718befa0a9720fbfb8#
n405	https://data.openlinksw.com/oplweb/faq/uda/73eafa8e4247182159b9c77c9cabbaf9#
n159	https://data.openlinksw.com/oplweb/faq/uda/3ebb6c7dbd7572397d0940487dd3442c#
n33	https://data.openlinksw.com/oplweb/faq/uda/6ca1fe583af7da4c8dd4e072bb0093b8#
n136	https://data.openlinksw.com/oplweb/faq/uda/3ae82ac8ed828bbd86b6680efbe22638#
xsdh	http://www.w3.org/2001/XMLSchema#
n68	https://data.openlinksw.com/oplweb/faq/uda/2641e9de3134432d4ed5911899ca2f81#
n145	https://data.openlinksw.com/oplweb/faq/uda/46f54d9543c85e10d2458f1e0a22d847#
n142	https://data.openlinksw.com/oplweb/faq/uda/7bb4ff0611fd29c092ce6f71a5637c4b#
n479	http://data.openlinksw.com/oplweb/faq/e4274073d9207ca4c9e1474c178231dcdb8bd811#
n400	https://data.openlinksw.com/oplweb/faq/uda/9e04b3e1284ad78de65b0e41076b7722#
n157	https://data.openlinksw.com/oplweb/faq/uda/a34eed5079f095e9c16ea4f9c9d7a204#
n430	https://data.openlinksw.com/oplweb/faq/uda/073604e899a28f9db0f60e2f2f4e9806#
n86	https://data.openlinksw.com/oplweb/faq/uda/5cd1927893e3683258922d78cad2651e#
n473	https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
n336	https://data.openlinksw.com/oplweb/faq/uda/e33f897d5e0e407ccab26c7124028d36#
n515	http://data.openlinksw.com/oplweb/glossary-term/R2RML#
n167	https://data.openlinksw.com/oplweb/faq/uda/735b19005792e8f7e8d9a9f4b7430e3a#
n381	https://data.openlinksw.com/oplweb/faq/uda/4638afda97f59939b7a848d860bee017#
n217	https://data.openlinksw.com/oplweb/faq/uda/1cccd803c9e8d9f7628e0d5cd2ae4b6b#
n458	https://data.openlinksw.com/oplweb/faq/uda/e06d0b64d819a59fba7c3480296f8cf7#
n312	https://data.openlinksw.com/oplweb/faq/uda/55bcd8f576d520f1beeb95456d0693c6#
n44	https://data.openlinksw.com/oplweb/faq/uda/6d80896885c1dfa2c7a9021ec79c3915#
n281	https://data.openlinksw.com/oplweb/faq/uda/012b14dfc8ea8f4e6fd5c081e92ef991#
n71	https://data.openlinksw.com/oplweb/faq/uda/3fe0da0ddd8369f12aa4a47cb7aa5dd1#
n166	https://data.openlinksw.com/oplweb/faq/uda/bb2d183f40ea68b4e067b28f7004273d#
n172	https://data.openlinksw.com/oplweb/faq/uda/eedb2a9f6484a359df0e5eb8bb729183#
n226	https://data.openlinksw.com/oplweb/faq/uda/eb1f1ab9830f8c90f248d9eef39983d3#
n308	https://data.openlinksw.com/oplweb/faq/uda/a5fef46475e2eee4de53a667c9c2ac18#
n24	https://data.openlinksw.com/oplweb/faq/uda/568fb96f6505bd450bf2390789e03ea8#
n256	https://data.openlinksw.com/oplweb/faq/uda/dcbf2e178a96d437ecb5ad11663d9967#
n224	https://data.openlinksw.com/oplweb/faq/uda/2e8535ffdaa924f620845543357a59ee#
n478	http://data.openlinksw.com/oplweb/glossary-term/ABAC#
n37	https://data.openlinksw.com/oplweb/faq/uda/30e10f688f3c137266046b581a8ded57#
n409	https://data.openlinksw.com/oplweb/faq/uda/6601a7d52df9d908585756ed08343b85#
n124	https://data.openlinksw.com/oplweb/faq/uda/0d19e5e2bdc3ad7f33a50f793b2f0eca#
n345	https://data.openlinksw.com/oplweb/faq/uda/57e827231ea744fd144247c01b235ed7#
n385	https://data.openlinksw.com/oplweb/faq/uda/07d34d6977eb5989fe3c8619e335730d#
n307	https://data.openlinksw.com/oplweb/faq/uda/1e386dfbaf8c89addfa8d279abb4fefa#
skos	http://www.w3.org/2004/02/skos/core#
n462	http://data.openlinksw.com/oplweb/glossary-term/DefVirtuosoCluster#
n169	https://data.openlinksw.com/oplweb/faq/uda/63c66aaa1008020a280aa8f3400fb57a#
n454	https://data.openlinksw.com/oplweb/faq/uda/c44ec04b2a0844b4399f0d16f8c58e4e#
n129	https://data.openlinksw.com/oplweb/faq/uda/9b0bc0ed732de0fdea23259468a6c902#
n418	https://data.openlinksw.com/oplweb/faq/uda/adcb5921993e4ba30f6b4c95827f9a65#
n351	https://data.openlinksw.com/oplweb/faq/uda/cbbe04db5b1c8cbd2941b8b7d5b8bb7b#
n26	https://data.openlinksw.com/oplweb/faq/uda/73e3770f8e82f5ce65cd60a9f6d15a2e#
n263	https://data.openlinksw.com/oplweb/faq/uda/2356ad39cfce80d02792d2926b9b893c#
n284	https://data.openlinksw.com/oplweb/faq/uda/cde56546df652026589c29e6acd556a9#
n189	https://data.openlinksw.com/oplweb/faq/uda/a51e1caa941030cc086608066cd3583b#
n295	https://data.openlinksw.com/oplweb/faq/uda/0c9fee5c5749bb1a60929499eb802ed1#
n483	https://uda.openlinksw.com/images/
n443	https://data.openlinksw.com/oplweb/faq/uda/573a587fcc26df9552a5c9f066510daf#
n216	https://data.openlinksw.com/oplweb/faq/uda/8fc898dcdd2c12542e76dfeab9892f71#
n151	https://data.openlinksw.com/oplweb/faq/uda/0cb253bb099c6bfaca805e52944499b5#
n493	http://data.openlinksw.com/oplweb/faq/Virtuoso/2417d14acdf01e5ed2993eb5014ac5ee314aae67#
n516	http://data.openlinksw.com/oplweb/glossary-term/SQLDBMS#
n321	https://data.openlinksw.com/oplweb/faq/uda/f40384310bde702752f940dd52229422#
n341	https://data.openlinksw.com/oplweb/faq/uda/c4dbe39cef87efd1f775dc001a230eda#
n347	https://data.openlinksw.com/oplweb/faq/uda/02b5d6c455a5d959f76562772fb29e92#
n50	https://data.openlinksw.com/oplweb/faq/uda/d174ab0a053dfb8b8f34fb64ab25ec0a#
n53	https://data.openlinksw.com/oplweb/faq/uda/4c0dcd2ec06142a1542d98d7ba336f0f#
n14	https://data.openlinksw.com/oplweb/faq/uda/1229e829d5f8ff146c949959a53ccd35#
n313	https://data.openlinksw.com/oplweb/faq/uda/fe3b38b09c06da50245104518e4262fb#
n414	https://data.openlinksw.com/oplweb/faq/uda/7f055740ac0d5c59c4cf0e5087a76207#
n229	https://data.openlinksw.com/oplweb/faq/uda/d50dd985bedd7b9eb835d238ea8eb438#
n58	https://data.openlinksw.com/oplweb/faq/uda/f7c48e313636aeef8231af2107559682#
n289	https://data.openlinksw.com/oplweb/faq/uda/8a5dfed45da3d68448eaba6ba37a9b73#
n261	https://data.openlinksw.com/oplweb/faq/uda/5f1658a904d4d369329b22ccde2335de#
n333	https://data.openlinksw.com/oplweb/faq/uda/a90a897237b5016700b292a5b8783107#
n48	https://data.openlinksw.com/oplweb/faq/uda/d38ec6fdf033631a79b75def272ae25c#
n9	https://data.openlinksw.com/oplweb/faq/uda/4c5c62109597dab2ae1a4350eca7f199#
n324	https://data.openlinksw.com/oplweb/faq/uda/5876ed0ca7b5069ea63045f58ffc98da#
n277	https://data.openlinksw.com/oplweb/faq/uda/c9eeb9aa406feaf47536267ab81054af#
n194	https://data.openlinksw.com/oplweb/faq/uda/b3fbd08b04702e476ed14cf6db8b07eb#
n323	https://data.openlinksw.com/oplweb/faq/uda/ac813037b0034bfe6e84a2dff275d700#
n161	https://data.openlinksw.com/oplweb/faq/uda/a19cfe284c593246619a3db89193ee04#
n51	https://data.openlinksw.com/oplweb/faq/uda/9cb19bd7365d102902c96ee3ef1a01f3#
n76	https://data.openlinksw.com/oplweb/faq/uda/4dbd121c381bec9f221d9544f5f952be#
n64	https://data.openlinksw.com/oplweb/faq/uda/b48a43c87481a9f0c6a0b645241d41f8#
n30	https://data.openlinksw.com/oplweb/faq/uda/1421e23ba66fbbdcd68e22a00874dc05#
n376	https://data.openlinksw.com/oplweb/faq/uda/95c940df8b2209d375f08a6503898249#
n275	https://data.openlinksw.com/oplweb/faq/uda/94cef9bc6f25a6ad66b3907b9e025ade#
n125	https://data.openlinksw.com/oplweb/faq/uda/426b1ae6be25430034496bfbafcd86b0#
n393	https://data.openlinksw.com/oplweb/faq/uda/34ef18e3c018ab010478f8c2f32d47ca#
n221	https://data.openlinksw.com/oplweb/faq/uda/03408b593efd098f843b028612d4f1a9#
n52	https://data.openlinksw.com/oplweb/faq/uda/f09b832503799bab6bcd86acb5a85d86#
n320	https://data.openlinksw.com/oplweb/faq/uda/70f9e577eae00ed55077439d36c14234#
n202	https://data.openlinksw.com/oplweb/faq/uda/a5504e04338a16d84a86f6379a1ec6cb#
n403	https://data.openlinksw.com/oplweb/faq/uda/adb9894e02249adc367c06c2570f90d4#
n495	http://data.openlinksw.com/oplweb/glossary-term/JDBCDriver#
n407	https://data.openlinksw.com/oplweb/faq/uda/10e95f9b0da105306abbff35bf94b0bd#
n112	https://data.openlinksw.com/oplweb/faq/uda/5e7357d75134bae76d1fbd88627e6e0b#
n15	https://data.openlinksw.com/oplweb/faq/uda/6a7dcd8d88430314524f1d39efb3bbe7#
n292	https://data.openlinksw.com/oplweb/faq/uda/54225165d7689e8d4251764dd3cbc113#
n466	http://www.openlinksw.com/#
n286	https://data.openlinksw.com/oplweb/faq/uda/d899de50cac91a76139f3286031e1e7f#
n339	https://data.openlinksw.com/oplweb/faq/uda/ad54daedc09914e2f1d6519cc712e91d#
n31	https://data.openlinksw.com/oplweb/faq/uda/332b99734ada0f5af0700cc6bfde7842#
n77	https://data.openlinksw.com/oplweb/faq/uda/0c1e756466dca71af2421c0fa3e17ce9#
n447	https://data.openlinksw.com/oplweb/faq/uda/52ba99f53d4a58d5264e8f3287e65e6b#
n482	http://data.openlinksw.com/oplweb/faq/b8fa3f7f159861b5daf86e817e77f1fa758b1e48#
n304	https://data.openlinksw.com/oplweb/faq/uda/9e62f9cb9cc51ed22a8c008a05e62d15#
n93	http://data.openlinksw.com/oplweb/glossary-term/LinkedData#
n328	https://data.openlinksw.com/oplweb/faq/uda/a8a21d115209d9d2d75d1f9c66744841#
n474	http://data.openlinksw.com/oplweb/faq/57862938e6033f426c6fd1e104935ffccc53175c#
n267	https://data.openlinksw.com/oplweb/faq/uda/76c77835702593e6a254c0701376d1d4#
n499	http://data.openlinksw.com/oplweb/glossary-term/ODBCDriver#
n465	http://data.openlinksw.com/oplweb/glossary-term/DefVirtuosoServerInstance#
n85	https://data.openlinksw.com/oplweb/faq/uda/9df625f1df511c44160cd4d710b8f2b0#
n398	https://data.openlinksw.com/oplweb/faq/uda/9e3b1796252c22bc989caf3454bfd191#
n309	https://data.openlinksw.com/oplweb/faq/uda/05e6f0053b2d31b9ab60b4bb5363e0c7#
n34	https://data.openlinksw.com/oplweb/faq/uda/26f6ef3d75bce6b6180687dcf712015c#
n11	https://data.openlinksw.com/oplweb/faq/uda/0ba91843a5d56af44f426c1d27ae5255#
n332	https://data.openlinksw.com/oplweb/faq/uda/f08f0021cf3c8e4ffd8ba5645bd405bf#
n209	https://data.openlinksw.com/oplweb/faq/uda/93a3053781d3fcb96eec86e9dac40427#
n413	https://data.openlinksw.com/oplweb/faq/uda/a555aeb93471ed7d2161400c25335ade#
n297	https://data.openlinksw.com/oplweb/faq/uda/58457defc1fc98887cd243d28ba266eb#
n176	https://data.openlinksw.com/oplweb/faq/uda/cb3524fdf67b67a3caddd46e8ac01766#
n150	https://data.openlinksw.com/oplweb/faq/uda/0bdce49f64f9f911a85f6a0e39492b31#
n391	https://data.openlinksw.com/oplweb/faq/uda/397cf4e7d3720084388a24945330b888#
n428	https://data.openlinksw.com/oplweb/faq/uda/4586eafb74f87463c7f419e9417dedc2#
n489	https://www.openlinksw.com/DAV/oplweb3/images/
n154	https://data.openlinksw.com/oplweb/faq/uda/aae584285f5f8a59654bae271f888203#
n231	https://data.openlinksw.com/oplweb/faq/uda/19f5e04b153f5ff5da6e9852f6fbd551#
n352	https://data.openlinksw.com/oplweb/faq/uda/6c2aae2de5887e4f1338c242891d3dcb#
n179	https://data.openlinksw.com/oplweb/faq/uda/f3259642731cea781cdcb5063192c01d#
n404	https://data.openlinksw.com/oplweb/faq/uda/5e9ccb4a93fc378ca659571990187a3a#
n69	https://data.openlinksw.com/oplweb/faq/uda/943b57c05e7efe50f1d7abb8a80251f3#
n416	https://data.openlinksw.com/oplweb/faq/uda/8b2d723d006843900f0a0e74da650515#
n152	https://data.openlinksw.com/oplweb/faq/uda/be7baf0247edffdc0345a472ccbc09a7#
n271	https://data.openlinksw.com/oplweb/faq/uda/250cef00371189fedec561d4707a307f#
n410	http://data.openlinksw.com/oplweb/faq/fcea26896e300068cad0f64b88ff48098e7e6661#
n63	http://data.openlinksw.com/oplweb/glossary-term/SPARQL#
n440	https://data.openlinksw.com/oplweb/faq/uda/fe7882ebb9a013c1a3d7c83afd1b6c70#
n186	https://data.openlinksw.com/oplweb/faq/uda/daec62fd2f78a16d71cc9da954a60fef#
n148	https://data.openlinksw.com/oplweb/faq/uda/dc3fd53f48c3d50fa99cf20ac95414b4#
n89	https://data.openlinksw.com/oplweb/faq/uda/ada3f3d5578b010c442ef3aa52a9f579#
n32	https://data.openlinksw.com/oplweb/faq/uda/a8f3c40f7de03c83f429c00de5bc15c6#
n342	https://data.openlinksw.com/oplweb/faq/uda/de1079d68dbe5680c1a0a3610d98ac8c#
n205	https://data.openlinksw.com/oplweb/faq/uda/0bf9b60433a5c006e2146b6ea46df215#
n220	https://data.openlinksw.com/oplweb/faq/uda/70608716ee2a80fd08b0c0daa6b06684#
n480	http://data.openlinksw.com/oplweb/faq/88cc4b84ca5510ea918347b5bfafd5a978a6e6af#
n197	https://data.openlinksw.com/oplweb/faq/uda/1c9887c63c7e71f73d86b1f387f789f7#
n67	https://data.openlinksw.com/oplweb/faq/uda/e930da24b2982e9e4cbff0e75a76bd70#
n200	https://data.openlinksw.com/oplweb/faq/uda/91999158511939b620f55cf7baf97049#
n114	https://data.openlinksw.com/oplweb/faq/uda/5f43b45a026aa3893c1d1f9341007fd5#
n415	https://data.openlinksw.com/oplweb/faq/uda/fbcbe251d833a76b313f9314d465021f#
n121	https://data.openlinksw.com/oplweb/faq/uda/a3718f6c9c5c93c11df58d86846e28d2#
n266	https://data.openlinksw.com/oplweb/faq/uda/b7c235e33e254ad8a118d36ea1bd3d7c#
n38	https://data.openlinksw.com/oplweb/faq/uda/84a4c222fd91765ff730093f6f342638#
n346	https://data.openlinksw.com/oplweb/faq/uda/122d43ab9797ea8e11c78d6a48a12892#
n160	https://data.openlinksw.com/oplweb/faq/uda/b8dcc133da90149948a999a99826f197#
n459	https://data.openlinksw.com/oplweb/faq/uda/5772eec5dcccee5e4a76551f1e29d3df#
n477	http://data.openlinksw.com/oplweb/faq/3449e417f57f74422bbbedf31ff35725b975ddd3#
n141	https://data.openlinksw.com/oplweb/faq/uda/73faec21a8a11ba558b9021399a26b22#
n296	https://data.openlinksw.com/oplweb/faq/uda/49037f693bb17765c7f4755765235fd4#
n273	https://data.openlinksw.com/oplweb/faq/uda/2d1b22cffaae99e25347367c11629b84#
n232	https://data.openlinksw.com/oplweb/faq/uda/deaa99caabd3d4df4e31f296d6c8c8a6#
n105	https://data.openlinksw.com/oplweb/faq/uda/8d8183f7e083e7756e62199a92999ea4#
n452	https://data.openlinksw.com/oplweb/faq/uda/a3f12cb57ea59fe435d3d666c39ab3d7#
n504	http://data.openlinksw.com/oplweb/glossary-term/ODBCFileDSN#
schema	http://schema.org/
n20	https://data.openlinksw.com/oplweb/faq/uda/0cd82c5ebd4d8b61dfd043b76f7b7315#
n441	https://data.openlinksw.com/oplweb/faq/uda/d269e2a3218fe6e7e0e3461334c59e41#
n283	https://data.openlinksw.com/oplweb/faq/uda/910a3346e9906969cab30d1414db5269#
n57	https://data.openlinksw.com/oplweb/faq/uda/110cf3336352171a43d37c0667858319#
n301	https://data.openlinksw.com/oplweb/faq/uda/295fadab7c321968ff184d5b6c5c4d65#
n491	http://data.openlinksw.com/oplweb/faq/Virtuoso/1a606985c34713e64c4c04446c2dca2e634089f5#
n365	https://data.openlinksw.com/oplweb/faq/uda/20b9d578c4218623dc489ea64d206ec4#
n434	https://data.openlinksw.com/oplweb/faq/uda/2b8b8075c37d0770650a9d5187290d4a#
n80	https://data.openlinksw.com/oplweb/faq/uda/3641f1e13b29933d748ff7e8e5bdd27a#
n424	https://data.openlinksw.com/oplweb/faq/uda/7c4f4ece76199b17b55d6a7d44e26d48#
n17	https://virtuoso.openlinksw.com/#
n228	https://data.openlinksw.com/oplweb/faq/uda/3944e25b7e346df69e5a93d60b3e34a2#
n359	https://data.openlinksw.com/oplweb/faq/uda/c2e670978c20c16cc1a65c64fd9f43ae#
n207	https://data.openlinksw.com/oplweb/faq/uda/13d56aab65e7332538ab0bdcf0c49c33#
n29	https://data.openlinksw.com/oplweb/faq/uda/9849a7bee2b0b1303a7af3edd19bf916#
n108	https://data.openlinksw.com/oplweb/faq/uda/a009ae8b221d09a426119ba939181ff4#
n456	https://data.openlinksw.com/oplweb/faq/uda/d3686337d3468de1ce8b667a91fc6b84#
n98	https://data.openlinksw.com/oplweb/faq/uda/4c8fe8c6b7feb7af2154a88da87de493#
n519	http://data.openlinksw.com/oplweb/glossary-term/SPARQLQueryLanguage#
n311	https://data.openlinksw.com/oplweb/faq/uda/9d87afd09334f2533e1a82e3cae80ed2#
n505	http://data.openlinksw.com/oplweb/glossary-term/ODBCUserDSN#
n183	https://data.openlinksw.com/oplweb/faq/uda/f817f817dca49eccaa0e79132965da4a#
n392	https://data.openlinksw.com/oplweb/faq/uda/37ed3e76494b86d60a7d3e731769b2b3#
n104	https://data.openlinksw.com/oplweb/faq/uda/b1602cb158f5f5f7d1903a21e35cda53#
n110	https://data.openlinksw.com/oplweb/faq/uda/59016c088156804b7e1d4cbf11a96405#
n492	http://data.openlinksw.com/oplweb/faq/Virtuoso/3c99389b877fba9266377eded245983f2320976c#
n399	https://data.openlinksw.com/oplweb/faq/uda/80c9b7a041f513126ec77edf43c9c4ca#
n395	https://data.openlinksw.com/oplweb/faq/uda/7bc5173ec4a062364713c65babc8d014#
n208	https://data.openlinksw.com/oplweb/faq/uda/b4cf264e8e5c7485cf7aecc7192016d9#
n383	https://data.openlinksw.com/oplweb/faq/uda/fda897f78a04f1cdf73406a2a7fba424#
n75	https://data.openlinksw.com/oplweb/faq/uda/4ad2dbbeb1030bde0b22a23c95566b03#
n325	https://data.openlinksw.com/oplweb/faq/uda/a2ca2332ccfc7cecb116aad20793096f#
n72	https://data.openlinksw.com/oplweb/faq/uda/569a9ff38c874336585e6274b927ad31#
n513	http://data.openlinksw.com/oplweb/glossary-term/ConceptualDataVirtualization#
n371	https://data.openlinksw.com/oplweb/faq/uda/b09b3bf6bb68edb00cca4e79e0e5e5e4#
n446	https://data.openlinksw.com/oplweb/faq/uda/edccd291a365f754e3d81ea3f056a436#
n245	https://data.openlinksw.com/oplweb/faq/uda/a283a40631a35269d56e974b9d0da0b5#
n264	https://data.openlinksw.com/oplweb/faq/uda/89cefa2522572e1bf45abc18de296bad#
n382	https://data.openlinksw.com/oplweb/faq/uda/761e969e946b8c547a563df4aa138026#
n84	https://data.openlinksw.com/oplweb/faq/uda/08f53bb9e7980f5295a2f9210dad94b7#
n502	http://data.openlinksw.com/oplweb/glossary-term/ODBC#
n180	https://data.openlinksw.com/oplweb/faq/uda/7ef644aca2d996bc59bdec4c823e2823#
n111	https://data.openlinksw.com/oplweb/faq/uda/39ff7a15a191b20dd71ab20779db3fe1#
n338	https://data.openlinksw.com/oplweb/faq/uda/ba34cb5b99651db696ac76d393b492ab#
n164	https://data.openlinksw.com/oplweb/faq/uda/3ff69612908912c3759f097a7f4f005c#
n290	https://data.openlinksw.com/oplweb/faq/uda/f4f42f911118a92e4cead29163e619b9#
n453	https://data.openlinksw.com/oplweb/faq/uda/5cb5e8d14f36ca40629baa3b5b17d627#
n234	https://data.openlinksw.com/oplweb/faq/uda/b2603469a2123966eb2bbe20ca6cff57#
n246	https://data.openlinksw.com/oplweb/faq/uda/8f829b9509e90a80eadfc791ac328323#
n61	https://data.openlinksw.com/oplweb/faq/uda/9a512d9cf8df83959e1ea701086097e6#
n484	http://data.openlinksw.com/oplweb/faq/845a52272bdff0593a02b558b2fbaae2c113d808#
n421	https://data.openlinksw.com/oplweb/faq/uda/0554269f01a00ab41881f01bc466cd2b#
n198	https://data.openlinksw.com/oplweb/faq/uda/e2dbcba6532fb3e1960bb14acb072a68#
n158	https://data.openlinksw.com/oplweb/faq/uda/9920af2a127e308715fd0e080de379ec#
n358	https://data.openlinksw.com/oplweb/faq/uda/2a750567b4c7a5b275f99fb10910d5b6#
n429	https://data.openlinksw.com/oplweb/faq/uda/7fabdfba11b42bd236c93030284b4cfe#
n247	https://data.openlinksw.com/oplweb/faq/uda/aa0fccf917140134a523696c3aa3fc22#
n488	https://azuremarketplace.microsoft.com/en-us/marketplace/apps/
n126	https://data.openlinksw.com/oplweb/faq/uda/17490f7bf2636defb114887241cad59d#
n497	http://data.openlinksw.com/oplweb/glossary-term/JDBCDriverManager#
n107	https://data.openlinksw.com/oplweb/faq/uda/72e05ccd1f32beb0da792551640a18b7#
n445	https://data.openlinksw.com/oplweb/faq/uda/4b6f6db93592353afce7c43848d4714c#
n113	https://data.openlinksw.com/oplweb/faq/uda/76ade409724174c687d14c530d82eb0b#
n46	https://data.openlinksw.com/oplweb/faq/uda/e5e4d76c1cd19e7609fcb0b8b5f147eb#
n91	https://data.openlinksw.com/oplweb/faq/uda/2a26d2d6af39f533738576fd36675eed#
n306	https://data.openlinksw.com/oplweb/faq/uda/381db88949e1724e4acbf9bd3bb17f8f#
n2	https://data.openlinksw.com/oplweb/faq/uda/0e6acb73d51c7ba83ef1205c61fce9c7#
n196	https://data.openlinksw.com/oplweb/faq/uda/3341e16f3aa8d08863e23611019476a4#
n274	https://data.openlinksw.com/oplweb/faq/uda/d417c161574cd98a1f47ca60a84a86ff#
n471	http://data.openlinksw.com/oplweb/glossary-term/DataVirtualization#
n149	https://data.openlinksw.com/oplweb/faq/uda/d423c86a53ad56933525d6951d31e07e#
n384	https://data.openlinksw.com/oplweb/faq/uda/f28c3626d6ca9244d600e0780a55c5be#
n203	https://data.openlinksw.com/oplweb/faq/uda/506bf9480e6c26456fd4ef925c39aad4#
n212	https://data.openlinksw.com/oplweb/faq/uda/9e6ed9cc51658ccf3036bebf5745776d#
n357	https://data.openlinksw.com/oplweb/faq/uda/5235550bc48edea570bbce0533bf7b54#
n99	https://data.openlinksw.com/oplweb/faq/uda/e2970f1e9c6bef22debee151b9f4ae54#
n335	https://data.openlinksw.com/oplweb/faq/uda/259f42b57a708585349f19f4199a50bc#
n389	https://data.openlinksw.com/oplweb/faq/uda/354a00e8d6b41ab064749c56a78e3d14#
n103	https://data.openlinksw.com/oplweb/faq/uda/5242acba5623f74db44399e0af97a9c8#
n13	https://data.openlinksw.com/oplweb/faq/uda/65b24b128b297a4efc86e12fb0c72280#
n402	https://data.openlinksw.com/oplweb/faq/uda/3b2b91d3888e4ac61b393e69e15efbad#
n390	https://data.openlinksw.com/oplweb/faq/uda/23aabe54f385449a8bced23b163b7c20#
n386	https://data.openlinksw.com/oplweb/faq/uda/5835fee3aa470a7de9bcefe6a6a32ff7#
n355	https://data.openlinksw.com/oplweb/faq/uda/a6ddf7a3d8d1b077677faa6ba55e85e0#
n265	https://data.openlinksw.com/oplweb/faq/uda/7075245435eafe9baced5dc72945e20e#
n318	https://data.openlinksw.com/oplweb/faq/uda/1dc6ba56179c486ef36844f03c424404#
n260	https://data.openlinksw.com/oplweb/faq/uda/020ed5ce2b1b9dadf2a16dea8d49cc5f#
n119	https://data.openlinksw.com/oplweb/faq/uda/45a69c34c2b5f12eb0ea2a64c0c16d54#
n18	http://virtuoso.openlinksw.com/images/
n94	https://data.openlinksw.com/oplweb/faq/uda/675594cf4bd109d6b64d3bc08ab9af27#
n118	https://data.openlinksw.com/oplweb/faq/uda/8f1f82361438663a79fe99d20d4b142b#
n299	https://data.openlinksw.com/oplweb/faq/uda/bb429a9e1313719c620154ee1e9f6d27#
n4	https://data.openlinksw.com/oplweb/faq/uda/18680fc9030647594f0a952b9452e499#
n442	https://data.openlinksw.com/oplweb/faq/uda/1d3c9b4967105d716f3d3004f19af594#
n348	https://data.openlinksw.com/oplweb/faq/uda/936c4cb264356149b7885db13b7efb4b#
n139	https://data.openlinksw.com/oplweb/faq/uda/6fe4abfca2864ade79ac9c39f133e962#
n372	https://data.openlinksw.com/oplweb/faq/uda/9aebf97b7a684d0d49dde800bedc9c4f#
n206	https://data.openlinksw.com/oplweb/faq/uda/3e238966014e1a593847b263d0d9ab18#
n213	https://data.openlinksw.com/oplweb/faq/uda/27ba2368b825826b1f6b6ea74ccf411b#
n449	https://data.openlinksw.com/oplweb/faq/uda/154e137de4f9ca69b48979a17a2e30ea#
n222	https://data.openlinksw.com/oplweb/faq/uda/899d6d63a25b063873879a9a8e30e81f#
n294	https://data.openlinksw.com/oplweb/faq/uda/54410a90377512b60d9541a828340eda#
n278	https://data.openlinksw.com/oplweb/faq/uda/3a03151b4b545fd02348eb26128ad0a4#
n16	https://data.openlinksw.com/oplweb/faq/uda/2e7974c825db3bdf70eea0af7d7727e7#
n248	https://data.openlinksw.com/oplweb/faq/uda/c8dca3f06e40c656a740c8f98e07b046#
n437	https://data.openlinksw.com/oplweb/faq/uda/6b2dee5f5f4d0ac8cef0cddb87ec2f04#
n354	https://data.openlinksw.com/oplweb/faq/uda/c25d5459d8e831834440e2266681eb3b#

Statements

Subject Item: n119:this
schema:name: Answer to question: Where Can I Obtain ODBC Driver (or Connectors)?
schema:category: UDA JDBC ODBC
schema:text: ODBC Driver (or Connectors) are provided by Driver Vendors who may be the original Database Management System (DBMS) vendors or 3rd party specialists like OpenLink Software.
rdf:type: schema:Answer

Subject Item: n115:this
schema:name: Where Can I Obtain ODBC Driver (or Connectors)?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n119:this

Subject Item: n46:this
schema:name: What to do if ASNPRINT does not read my license file? -- Answer
schema:category: ODBC JDBC UDA
schema:text: ASNPRINT.exe can read OpenLink's 4.x, 5.x and 6.x license formats but cannot read the older OpenLink 1.x and 3.x license format.
rdf:type: schema:Answer

Subject Item: n49:this
schema:name: Can I Install New Software On Top Of Existing Software? -- Answer
schema:category: ODBC JDBC UDA
schema:text: Users can install new software on top of existing software. However, this is not the preferred course of action, in many circumstances. Users should install new software to new directories if they are attempting to compare software performance or troubleshoot problems.
rdf:type: schema:Answer

Subject Item: n35:this
schema:name: Can I mix and match client and server components from different OpenLink versions? -- Answer
schema:category: ODBC JDBC UDA
schema:text: OpenLink Software does not support mixed-version installations. Mismatched client and server software may not hinder a user's ability to connect and query. However, version incompatibility issues will arise over time. In fact, users who mix OpenLink 3.x and OpenLink 4.x software can expect specific problems with stability, transactions, and threading. These problems may only be resolved by upgrading the older component.
rdf:type: schema:Answer

Subject Item: n36:this
schema:name: Can I run 32 Bit software on a 64 Bit operating system? -- Answer
schema:category: ODBC JDBC UDA
schema:text: OpenLink's 32Bit software runs on 64Bit operating systems. However, OpenLink's 32Bit software is designed for use with 32Bit databases. Connectivity is possible to 64Bit databases that ship with 32bit libraries. However, OpenLink does not recommend this configuration.
rdf:type: schema:Answer

Subject Item: n39:this
schema:name: Can I run 64Bit software on a 32Bit operating system? -- Answer
schema:category: ODBC JDBC UDA
schema:text: OpenLink Software does not recommend this configuration.
rdf:type: schema:Answer

Subject Item: n41:this
schema:name: Can I run multiple versions at the same time? -- Answer
schema:category: ODBC JDBC UDA
schema:text: Users like to run multiple driver versions for comparative purposes. Single-Tier users simply install their new drivers to a new directory. Multi-Tier drivers should install their new drivers to different directories, as well. In addition, Multi-Tier users must insure that their Request Brokers use separate TCP/IP Listen ports.
rdf:type: schema:Answer

Subject Item: n133:this
schema:name: Can OpenLink provide ftp access to the downloads files? -- Answer
schema:category: UDA JDBC ODBC
schema:text: OpenLink has two ftp sites. They are: UK FTP: ftp://ftp.openlinksw.co.uk/ and US FTP: ftp://www.openlinksw.com/ . Please note that the products are labeled according to their internal code, therefore please check with your support consultant before downloading to ensure you have the right product.
rdf:type: schema:Answer

Subject Item: n137:this
schema:name: Can OpenLink provide installation files on CD? -- Answer
schema:category: UDA JDBC ODBC
schema:text: OpenLink does not have ready-made installation CDs. However, OpenLink has the facilities to create CDs on request for customers and partners. Please contact your account manager who will consider your request.
rdf:type: schema:Answer

Subject Item: n77:this
schema:name: Can users install on top of existing OpenLink software installations? -- Answer
schema:category: UDA JDBC ODBC
schema:text: Users may install new driver installations atop old driver installations. Users may install different UDA products -i.e., the Single-Tier and Multi-Tier suite on top of one another and maintain the functionality of both.
rdf:type: schema:Answer

Subject Item: n129:this
schema:name: Can users manually extract and install the software? -- Answer
schema:category: UDA JDBC ODBC
schema:text: Windows users must use WinZip or a similar utility to extract OpenLink components from .zip files. Unix users must use install.sh whenever possible. Manual extraction is not supported. However, users may use gunzip and tar to extract components, if all attempts to use install.sh fail.
rdf:type: schema:Answer

Subject Item: n124:this
schema:name: I cannot download software to the appropriate machine. What do I do? -- Answer
schema:category: UDA JDBC ODBC
schema:text: Network or security policies may restrict a user's ability to download software onto a machine.
rdf:type: schema:Answer

Subject Item: n118:this
schema:name: What can I do if I cant solve the problem? -- Answer
schema:category: UDA JDBC ODBC
schema:text: If you are experiencing any problem, it is recommended that you report this using the OpenLink support site at http://www.openlinksw.com
rdf:type: schema:Answer

Subject Item: n112:this
schema:name: I cant set my OpenLink variables. What do I do? -- Answer
schema:category: UDA JDBC ODBC
schema:text: If a Unix user cannot set their environment variables with openlink.sh or openlink.csh, please type sh or cshat the command line. This should allow you to run openlink.sh or openlink.csh respectively. If the problem persists, a manual setting will need to be completed. Users should edit openlink.sh or openlink.csh with a text file editor. Please take care when editing this file as the variables contained within this file might affect the way the OpenLink installation works. Take note of the variables within the file, close it and set the variables on the command line.
rdf:type: schema:Answer

Subject Item: n109:this
schema:name: My Request Broker shuts itself down. What do I do? -- Answer
schema:category: UDA JDBC ODBC
schema:text: Users may experience intermittent Request Broker shutdowns. This problem stems from the use of one license on multiple machines, and it produces "Duplicate Serial Number" errors. Users who encounter this problem must request an additional temporary or permanent license keys from their account manager or shut down a request broker to resolve this problem.
rdf:type: schema:Answer

Subject Item: n14:this
schema:name: I cant start my Admin Assistant. What do I do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The Multi-Tier Administrative Assistant is a service. It is powered by the www_sv agent that appears in the /bin/w3config sub-directory of Multi-Tier server components installations. Unlike the Request Broker, the Administrative Assistant does not require manual startup. Instead, the Request Broker spawns the agent during its own startup routine.
rdf:type: schema:Answer

Subject Item: n15:this
schema:name: I cant start my Request Broker. What do I do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Request Brokers are listening services. OpenLink's 4.x and newer Brokers listen on the TCP port that is passed to the Listen parameter. The Listen parameter appears in the Protocol TCP section of the Session Rules Book. OpenLink's 3.x and 1.x Brokers listen on PortLow. PortLow appears in the Protocol TCP section of the Session Rules Book. OpenLink's Request Brokers also use UDP port 60001 to broadcast license information.
rdf:type: schema:Answer

Subject Item: n19:this
schema:name: I cant shutdown my Admin Assistant. What do I do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The Multi-Tier Administrative Assistant is a service. It is powered by the www_sv agent that appears in the /bin/w3config sub-directory of Multi-Tier server components installations. Unlike the Request Broker, the Administrative Assistant does not require manual shutdown. Instead, the Request Broker kills the agent during its own shutdown routine.
rdf:type: schema:Answer

Subject Item: n21:this
schema:name: I cant shutdown my Request Broker. What do I do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Take the following actions, if you cannot shutdown your Request Broker: Login to the machine that contains your Multi-Tier server components installation. Use a text editor to open the oplrqb.ini file that appears in the /bin sub-directory of the OpenLink installation and so on ..
rdf:type: schema:Answer

Subject Item: n96:this
schema:name: Components are missing after installation. What do I do? -- Answer
schema:category: UDA JDBC ODBC
schema:text: Occasionally, Unix database agent installation files do not contain database agents. Instead, they contain object code and re-link scripts, which allow users to compile their own agents. This is normal due to the actual database not been available on our internal servers. Nevertheless, users can confirm this with OpenLink Product Support staff. If requesting a database agent or components from the OpenLink Support staff, please have the following information, where available, ready.
rdf:type: schema:Answer

Subject Item: n5:this
schema:name: I think I have OpenLink Software. How can I tell? -- Answer
schema:category: ODBC UDA JDBC
schema:text: It is possible your machine might contain a copy of the OpenLink Software Universal Data Access drivers or you might require one or more additional components -e.g., clients or agents-to match pre-existing software.
rdf:type: schema:Answer

Subject Item: n7:this
schema:name: Do I need to configure my environment to support my JDBC connections? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Insure that the CLASSPATH environment variable is set on the machine that contains your JDBC client application. CLASSPATH appears in the Windows System Utility (Control Panel). Windows users need to navigate to the portion of the utility that displays their User and System settings. Unix users may use echo to display their CLASSPATH setting. For example: bash$ echo $CLASSPATH /home/openlink/v51/mt/jdk1.4 CLASSPATH must pass the full path to an OpenLink JDBC opljdbc.jar, opljdbc2.jar, opljdbc3.jar or megathin.jar, megathin2.jar file depending on your JDK.
rdf:type: schema:Answer

Subject Item: n12:this
schema:name: Do I need to configure my environment to support ODBC-ODBC Bridge connectivity? -- Answer
schema:category: ODBC UDA JDBC
schema:text: You need to insure that your 3rd party drivers connect to the target database. You need to insure that openlink.sh or openlink.csh is run on Unix machines that contain OpenLink Software. openlink.sh should be run in a Bourne or Bash shell. openlink.csh should be run in C shell.
rdf:type: schema:Answer

Subject Item: n182:this
schema:name: Do I need? -- Answer
schema:category: JDBC UDA ODBC
schema:text: If you are unsure of whether you require our Universal Data Access drivers, please review the questions posed below: Do you need to query a database with a 3rd party application? Is your application ODBC- or JDBC- compliant? Does your network environment support the TCP/IP or SPX protocol? OpenLink's Data Access Drivers provide ODBC and JDBC connectivity between compliant applications and databases. Moreover, OpenLink's drivers use the TCP/IP network protocol to achieve this connection. Consequently, if your response is YES to the aforementioned questions, you need these drivers. If you are still unsure, please consult your Database Administrators, System Administrators, or other knowledgeable staff. Users who respond NO to one or more questions must clarify their needs with either a Support Consultant or their Account Manager. We offer other solutions which might be what you require.
rdf:type: schema:Answer

Subject Item: n187:this
schema:name: Do users need to employ special configuration to operate in a firewalled environment? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Single-Tier users should not need to open ports to accommodate the Single-Tier driver. However, ports may need to be opened to facilitate connections between the database native client and the database to which it connects. Multi-Tier users need to take the following action, if a firewall surrounds the machine that contains the Multi-Tier server components
rdf:type: schema:Answer

Subject Item: n174:this
schema:name: Do you have 16Bit drivers? -- Answer
schema:category: UDA JDBC ODBC
schema:text: OpenLink produced 16Bit 1.x builds. These builds are not available to the general public.
rdf:type: schema:Answer

Subject Item: n144:this
schema:name: Does OpenLink Load Share for Active-Active Clusters? -- Answer
schema:category: UDA JDBC ODBC
schema:text: Our Multi-Tier drivers may be deployed in a load balancing architecture.
rdf:type: schema:Answer

Subject Item: n202:this
schema:name: Does OpenLink produce custom software for evaluators? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink can build custom software for users, provided OpenLink has access to the requisite databases, operating system, and development tools. (OpenLink can purchase these tools or use tools provided by the user.) Note: Custom builds come at a cost so please contact your OpenLink Account Manager to discuss any arrangements you have.
rdf:type: schema:Answer

Subject Item: n198:this
schema:name: Does OpenLink provide data migration facilities? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink's UDA drivers can be used in conjunction with 3rd-party data migration facilities. However, OpenLink's Virtuoso Server provides Snapshot Replication and a Virtual Database Repository. Virtuoso Snapshot Replication is similar to MS SQLServer's Data Transformation Services (DTS) Wizard. Virtuoso's Virtual Database Repository provides one with an interface and functionality similar to MS SQLServer's Linked Servers or Oracle's Heterogeneous Services.
rdf:type: schema:Answer

Subject Item: n122:this
schema:name: Does OpenLink function in Fail-over Cluster environments? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Yes. OpenLink functions in Fail-over Cluster environments. Multi-Tier users must install one set of OpenLink server components (Request Broker & Database Agent) on each node. The fail-over Broker may be instantiated by shell scripts, cron, or some other startup procedure, when the active node goes down. Some environments may support multiple, running Request Brokers, so long as each Request Broker can bind to a unique IP address.
rdf:type: schema:Answer

Subject Item: n29:this
schema:name: Does OpenLink work with Oracle Heterogeneous Services? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Our UDA drivers work in conjunction with Oracle's Heterogeneous Services.
rdf:type: schema:Answer

Subject Item: n141:this
schema:name: Does OpenLink work with SQLServer Linked Servers? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink's 5.x+ drivers support ODBC API calls made by MS SQLServer's Linked Servers. We also provide an alternative OLE DB provider for use with this and similar products.
rdf:type: schema:Answer

Subject Item: n146:this
schema:name: Does OpenLink work with the DTS Wizard? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink's 5.x+ drivers support ODBC API calls made by MS SQLServer's DTS Wizard. We also provide an alternative ODBC provider for ADO.NET and OLE.DB for use with this and similar products.
rdf:type: schema:Answer

Subject Item: n149:this
schema:name: Can you explain OpenLink installation file naming conventions? -- Answer
schema:category: UDA JDBC ODBC
schema:text: OpenLink's installation archives follow an eight character naming convention. The first two characters represent the operating system, on which the product was compiled. The third and fourth characters represent the component type, i.e., client, database agent, request broker, Single-Tier driver. The remaining characters specify for which database a product is meant to connect. Generic components will contain a series of `x's or `z's in this field.
rdf:type: schema:Answer

Subject Item: n153:this
schema:name: Heavy load causes my ODBC connections to fail. What do I do? -- Answer
schema:category: UDA JDBC ODBC
schema:text: Use the following guidelines to troubleshoot heavy problems: 1. Patch databases and operating systems regularly. 2. Contact database and o/s vendors to see if patches are associated with problems. 3. Insure Unix kernel tuning parameters match parameters specified by database and o/s documentation. 4. Insure your machine has adequate memory and processor resources. 5. Comparison test Multi-Tier drivers when Single-Tier drivers appear to expose limitations in a database native client. 6. Re-link Multi-Tier database agents against databases, especially patched databases. 7. Insure PortHigh is set in the [Protocol TCP] section of the Multi-Tier Session Rules Book. This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation. 8. Multi-Tier users perform the following test: -- login to the machine that contains the OpenLink server components. -- Run oplshut -s on the command-line. -- Compare the output to the Windows Task Manager or Unix ps -ef. -- Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps. Multi-Tier users experiment with database agent reuse. Users should do comparison test with the following values: -- ifsame process, upto 5 -- ifsame application, upto 5 -- ifsame database, upto 5
rdf:type: schema:Answer

Subject Item: n163:this
schema:name: How can I bench-test OpenLink drivers? -- Answer
schema:category: JDBC UDA ODBC
schema:text: You can download OpenLink ODBC Bench to run TPC-A like and TPC-C like bench tests against OpenLink and non-OpenLink ODBC drivers. OpenLink Software also provide a OpenLink JDBC Bench to run TPC-A like bench tests against OpenLink and non-OpenLink JDBC drivers. Please feel free to contribute your results to the OpenLink Product Support team
rdf:type: schema:Answer

Subject Item: n158:this
schema:name: How can I detect bottlenecks caused by OpenLink drivers? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Download ODBC Scan to detect bottlenecks caused by OpenLink drivers.
rdf:type: schema:Answer

Subject Item: n169:this
schema:name: How can I determine which ports the Multi-Tier Request Broker uses? -- Answer
schema:category: JDBC UDA ODBC
schema:text: The Request Broker port appears in the Session Rules Book. This is the oplrqb.ini file that appears in the /bin sub-directory of the user's server components installation. Users need to open this file with a text editor and locate the following section: [Protocol TCP] PingWatchdog = No PingInterval = 600 Listen = 5000 PortLow = 5000 PortHigh = 5099 IPAddress = 127.0.0.1 OpenLink's 4.x and 5.x Brokers listen on the port passed by the Listen parameter. OpenLink's 1.x and 3.x Brokers listen on the initial port as specified by the PortLow parameter.
rdf:type: schema:Answer

Subject Item: n165:this
schema:name: How can I assess my data access needs? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Use the following series of questions to help you resolve your data access needs: Do you need to: -- Category 1. Query a database with one or more client applications? -- Category 2. Query two or more heterogeneous databases simultaneously? -- Category 3. Migrate data from one DBMS to another? If you fall into Category 1, you require our UDA drivers. If you fall into Category 2, you require our Virtuoso suite. For category 3, we recommend the Virtuoso suite. Alternatively, if you are using an existing Data Migration tool such as Oracle HS services, UDA is what you require as these drivers work in conjunction with other data migration utilities such as Ms SQLServer's DTS Wizard. Does OpenLink provide Single-Tier or Multi-Tier drivers for the evaluator's DBMS? -- Category 1 - Yes. -- Category 2 - No. Evaluators in Category 1 may use the appropriate UDA driver for your database. If you fall into the second Category, you may use OpenLink's generic ODBC UDA drivers. Both the generic Single-Tier and Multi-Tier ODBC drivers connect to 3rd-party Data Sources, which allow connectivity to your DBMS. Does your evaluator have the database native client? -- Category 1 - Yes. It is installed on the same machine as the client application. -- Category 2 - Yes. It is installed on a different machine on the network. -- Category 3 - No. For evaluators who fall into the Category 1, we recommend Our OpenLink Single-Tier drivers. We recommend OpenLink's Multi-Tier drivers to evaluators in Category 2. Evaluators in Category 3 must install the OpenLink server components on their database server. NOTE:Evaluators in Category 2 may install the OpenLink server components on their database server or any machine, which contains the database native client. In this scenario, the OpenLink database agent can connect to the database through that database client. Please see the technical article on connecting via in a three-tier environment
rdf:type: schema:Answer

Subject Item: n241:this
schema:name: How can I prevent performance problems? -- Answer
schema:category: JDBC UDA ODBC
schema:text: As the OpenLink MT and ST drivers are middleware software, it is important to note that its performance can be influenced by the Client and Server configurations in use. This means, lack of system memory, kernel configurations, disk space, sql queries, coding techniques, un-indexed tables, network can all play a major part in the performance of the driver. Notwithstanding, we have outlined below ways in which you can increase the performance of the drivers. 1. Use OpenLink Single-Tier drivers where possible. 2. It is always recommended that, OpenLink's latest drivers are used where possible as these contain patches that might alleviate any performance bottlenecks you are facing. Only use OpenLink 4.2 drivers where we do not have a driver available. If you request this driver, please contact a Product Support consultant who will liaise with your Account Manager. 3. Establish 3-Tier Multi-Tier connections when Single-Tier connectivity is not possible. 4. Establish shared memory connections to databases that provide sockets and shared memory alternatives. 5. Check your DSN's "Defer fetching of long data" check box, when your result-sets contain binary data. 6. Locate the Row Buffer Size box that appears on your DSN setup dialog. Set this value to 1. Test. Next, set Row Buffer Size to 99. Test. Do you see a difference? If the first test is faster, your performance problems may stem from the makeup of your result-sets. If the second test is faster, your performance problems may stem from network latency. This awareness will help you set your Row Buffer Size in a manner that is beneficial to your situation. 7. Test a variety of client and server cursor modalities. Choose the modality that suits your application needs and provides the best performance. 8. If you are using the Multi-Tier Drivers, you can also increase the Send & Receive sizes. These might have an adverse effect on the network if you increase it sharply. Please consult your Product Support consultant if you want more information on this. If you increase this value, please ensure the Client (Send size) matches the Server (Receive size) and vice versa. Typically, this value is only increase when sending data from the Server to the client 9. If using the Multi-Tier drivers, please ensure your Reuse Rule is set in a manner that is appropriate for your system. If you anticipate long and complex queries, it is recommended that you do not reuse the agent. Alternatively, if you are in an environment that utilizes short, sharp bursts at the system, it might be conducive if you share agents, this means less system processes and resources will be instantiated on your system. 10. In OpenLink 5.x Multi-Tier, we have introduced the Linger Timeout. This creates a Connection Pooling environment on the server when handling connections. This means dormant connections can be reused.
rdf:type: schema:Answer

Subject Item: n245:this
schema:name: How can I prevent stability problems? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Use the following guidelines to prevent stability problems: 1. Patch databases and operating systems regularly. 2. Contact database and o/s vendors to see if patches are associated with problems. 3. Insure Unix kernel tuning parameters match parameters specified by database and o/s documentation. 4. Insure your machine has adequate memory and processor resources. 5. Comparison test Multi-Tier drivers when Single-Tier drivers appear to expose limitations in a database native client. 6. Re-link Multi-Tier database agents against databases, especially patched databases. 7. Insure PortHigh is set in the [Protocol TCP] section of the Multi-Tier Session Rules Book. This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation. Multi-Tier users perform the following test: 1. login to the machine that contains the OpenLink server components. 2. Run oplshut -s on the command-line. 3. Compare the output to the Windows (Task Manager) or Unix (ps -ef.) 4. Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps. Multi-Tier users experiment with database agent reuse. Users should comparison test the following values: -- ifsame process, upto 5 -- ifsame application, upto 5 -- ifsame database, upto 5
rdf:type: schema:Answer

Subject Item: n228:this
schema:name: How can I tell if a license is or is not corrupt? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Use ASNPRINT.exe to diagnose the functionality of 4.x and 5.x licenses. ASNPRINT.exe displays the terms of functional licenses. It cannot read corrupt licenses. ASNPRINT.exe can not read OpenLink's 1.x and 3.x license file format. Transfer these licenses to the relevant platform. Attempt to register the appropriate product with these drivers. Then, take the action that corresponds to that product: 1. Set the system clock ahead to test Single-Tier data sources. 2. Start the Request Broker with oplrqb -dv to verify the proper license terms.
rdf:type: schema:Answer

Subject Item: n232:this
schema:name: How can I tell if OpenLink produces software for a particular operating system or database? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Go to the OpenLink downloads pages to search for the software for your particular OS. If your Operating System or Database is not available in the list of supported platforms, please contact your Product Support consultant or Account Manager as the software might be available internally but not publicly so.
rdf:type: schema:Answer

Subject Item: n225:this
schema:name: How can I tell what version I have? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Users may employ a variety of methods to obtain their product version information. Windows and Mac Single-Tier users should open their ODBC Administrator. The Single-Tier driver version appears on the Drivers tab of this Administrator. Users simple scroll through the Driver list box, locate their driver, and record the version string, which appears to the right of the driver name.
rdf:type: schema:Answer

Subject Item: n219:this
schema:name: How do I configure Multi-Tier drivers, after I have installed them? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Windows and Mac client users do not need to perform additional steps to configure their Multi-Tier clients. Unix client users must insure that their OpenLink environment variables are set. The following instructions will assist these users with this task: 1. Users must login to their Unix clients. 2. Users must cd into the root of their OpenLink installation. 3. Users may run openlink.sh in a Bash or Bourne shell. Alternatively, users may run openlink.csh in a C shell. All users must insure that their server components are properly configured. The following instructions will assist all users with this task: 1. Unix users must login to their Unix servers and cd into the root of their OpenLink installations. These users may run openlink.sh in a Bourne or Bash shell. Alternatively if you are using a C shell, you require openlink.csh. 2. All users must open their Session Rules Books. The Session Rules Book is the oplrqb.ini file, which reside in the /bin sub-directory of the OpenLink installation. Users may open oplrqb.ini with vi, Notepad, or another text editor. Locate the Environment section that corresponds to your OpenLink database agent and set the variables that are appropriate to to your Database setup. Typically, the main information required is the installation directory and location of the database libraries. If you are unsure what these values are, please request them from your Database or System administrator. Typically running the command `env' under the guise of the database owner will provide you with the necessary information 3. Users must start their OpenLink Request Broker services. To do this on Unix, from the shell or terminal prompt run ./oplrqb either from the /bin sub-directory of your OpenLink installation or if openlink.sh/csh has been run, anywhere in the system. Windows users may start oplrqb with their Services Control Panel utility.
rdf:type: schema:Answer

Subject Item: n113:this
schema:name: How do I configure Single-Tier drivers, after I have installed them? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Windows and Mac users do not need to perform additional steps to configure their Single-Tier drivers. Unix users need to insure that their OpenLink and database environment variables are set. The following instructions will assist Unix users with this task: 1. Users must login to their Unix clients. 2. Users must cd into the root of their OpenLink installation. 3. Users may run openlink.sh in a Bash or Bourne shell. Alternatively, users may run openlink.csh in a C shell. 4. Users must cd into the /bin sub-directory of their OpenLink Single-Tier installations. 5. Users must edit openlink.ini or open the file with a text editor such as vi. 6. Users must identify the Environment section that corresponds to their OpenLink Single-Tier driver. 7. Users must ensure that the relevant variables are set within the Environment section.
rdf:type: schema:Answer

Subject Item: n205:this
schema:name: How Do I Assist Users Who Cannot Start The Multi-Tier Request Broker? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Take the following action: 1. Insure that a valid license appears in the /bin sub-directory of the OpenLink server components installation. The broker will not start without a valid license. ; 2. Check directory and file permissions.; 3. Compare the name of the Unix .taz files with the output of uname -a. Determine whether or not the component is compatible with the operating system.; 4. Use a text editor to open the oplrqb.ini file. Locate the [Protocol TCP] Listen parameter, and take note of the port.; 5. Run netstat -a and open /etc/services or C:/WINNT/SYSTEM32/DRIVERS/ETC/services to determine if the Broker's Listen port is in use by another service. This is typical of Windows XP which uses port 5000 by default.; 6. Run netstat -a open /etc/services or C:/WINNT/SYSTEM32/DRIVERS/ETC/services to determine if UDP port #60001 is in use. This will affect 1.x and 3.x installations.; 7. Attempt to start Windows Brokers with the Services utility and the DOS command line.; 8. Determine what service packs, patches, or upgrades have been applied to the operating system. Some upgrades cause the Broker service to fail.;
rdf:type: schema:Answer

Subject Item: n273:this
schema:name: How Do I Assist Users Who Cannot Set Environment Variables? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Instruct users to perform the following action: -- Insure that the openlink.sh and openlink.csh files are executable.; -- Run . ./openlink.sh in a Bourne and/or a Bash shell. ; -- Run source openlink.csh in a C shell, if the problem persists. ; -- Set the variables--contained within the shell scripts--manually, if the problem persists. Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini . However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI . When in doubt, consult the man pages or another Unix reference.
rdf:type: schema:Answer

Subject Item: n279:this
schema:name: How Do I Configure An JDBC-ODBC Bridge Connection? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Create a Single-Tier JDBC connection URL that passes the following values: jdbc:openlink://ODBC/DSN=Valid ODBC Data Source/UID=database username/PWD=database password Here are some examples: jdbc:openlink://ODBC/DSN=Informix Stores7/UID=informix/PWD=informix ; jdbc:openlink://ODBC/DSN=My Oracle DB/UID=scott/PWD=tiger ; jdbc:openlink//ODBC/DSN=SQLServer Northwind Database/UID=sa
rdf:type: schema:Answer

Subject Item: n282:this
schema:name: How Do I Configure An ODBC-JDBC Bridge Connection? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Unix Single-Tier users pass the following values in your ODBC-JDBC Bridge Data Source: -- Name - Any Descriptive Title ; -- Database Name - JDBC Driver Name String: openlink.jdbc3.Driver ; -- Options - Functional JDBC connection URL.: jdbc:openlink://localhost:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger ; -- Username - JDBC Data Source Userid ; -- Existing Environment - Pass the value that corresponds to your JRE version: JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4. Windows Single-Tier users pass the following values in your ODBC-JDBC Bridge Data Source: -- Data Source Name - Any Descriptive Title ; -- JDBC Driver - JDBC Driver Name String: openlink.jdbc3.Driver ; -- URL String - Functional JDBC connection URL.: jdbc:openlink://localhost:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger ; Multi-Tier users pass the following values in your ODBC-JDBC Bridge Data Source Names: -- Name - Any Descriptive Title ; -- Domain (a.k.a 'ServerType') - Pass the value that corresponds to your JRE version: JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4. ; -- Hostname - Hostname or IP of the machine that contains OpenLink's server components ; -- Database - JDBC Driver Name String: openlink.jdbc3.Driver ; -- Options - Functional JDBC connection URL.: jdbc:openlink://localhost:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger ; -- Login ID - Blank
rdf:type: schema:Answer

Subject Item: n289:this
schema:name: How Do I Configure An ODBC-ODBCBridge Connection? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Multi-Tier users pass the following values in your Data Source Names: -- Name - Any Descriptive Title -- Domain (aka 'ServerType') - Odbc -- Hostname - Hostname or IP of machine containing OpenLink server components -- Database - Exact name of 3rd Party Data Source -- Username - Database username, if required -- Server/Options - Blank Single-Tier users pass a descriptive title in the Data-Source Name field of the Data Sources. Then, use the System, User, and File dialogs to choose the 3rd party Data Source to which you want to connect.
rdf:type: schema:Answer

Subject Item: n256:this
schema:name: How Do I Create A Data Source Name? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Users may employ a variety of means to create OpenLink Data Source Names. Consultants should encourage users to use OpenLink's HTTP-Based iODBC Data Sources Administrator or Multi-Tier Administrative Assistant, whenever possible.
rdf:type: schema:Answer

Subject Item: n251:this
schema:name: How Do I Create A Zero Config DSN? -- Answer
schema:category: JDBC UDA ODBC
schema:text: 1. Open your server's Administrative Assistant in a Web Browser. 2. Expand the Server Components Administration menu. 3. Expand the Zero Config Administration menu. 4. Click Zero Config Administration by Wizard or Zero Config Administration by Form. 5. Edit an existing Zero Config template or add a new one. 6. Hard-code the value that your users need to connect to the database. 7. Reinitialize the Request Broker to register your Zero Config DSN. 7. Supply the name of the Zero Config DSN to your end users. You need to provide your end users with the name of your Zero Config DSN. End users take the following action to use the DSN: 1. Create a new DSN using the Windows Data Source Administrator or the Administrative Assistant. 2. Name the new DSN. 3. Expand the server drop down menu that appears on the first screen of the DSN setup dialog. 4. Locate the Zero Config DSN by name. 5. Allow the Zero Config DSN to auto-fill the fields of the new DSN. 6. Save the new DSN. 7. Test.
rdf:type: schema:Answer

Subject Item: n265:this
schema:name: How do I get a commercial license? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Users must contact an OpenLink Account Manager to obtain a commercial license. Consultants cannot generate non-expiring, commercial licenses for users.
rdf:type: schema:Answer

Subject Item: n259:this
schema:name: How Do I Get An Evaluation License File? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink's downloads page emails licenses to the email account that appears in the user's profile. Take the following action, if a user does not receive a license file: -- Encourage the user to repeat the downloads process and stop, just before he or she downloads the software. The OpenLink web page should send a license key to the user's email. -- Verify the user's email address, if the problem persists.
rdf:type: schema:Answer

Subject Item: n307:this
schema:name: How Do I Install Your Products? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink's Data Access products are easy to install. Follow the instructions that correspond to the user's operating system: 1. Linux/Unix - Download the appropriate component archives and install.sh. Place the archives and install.sh into the same directory. Run the following command and follow the instructions: sh install.sh 2. Mac - Download the .dmg file and extract the .mpkg file that is contained inside it. Double-click the .mpkg file. Then, provide information and follow instructions, as prompted by the installation dialog screens. 3. VMS 4. Windows - Download the appropriate .zip installer. WinZip the installer and run setup.exe. (Setup.exe may appear in the root of the extracted files or in a Disk1 subdirectory.) Provide information and follow instructions, as prompted by the installation dialog screens.
rdf:type: schema:Answer

Subject Item: n312:this
schema:name: How Do I Interpret Admin Assistant Logs? -- Answer
schema:category: JDBC UDA ODBC
schema:text: The Admin Assistant writes the following information to a file, when startup is successful: Thu Mar 04 2004 15:07:11 started http://openlinux.openlinksw.com:8051 Here, we see the URL from which the Admin Assistant is accessed in a browser. The first part of the URL designates the machine (openlinux.openlinksw.com) on which it started. The number appended to the end of the machine is the TCP port on which it listens. This port is also the HTTPServer port that appears in the www_sv.ini file. The www_sv.ini file appears in the /bin/w3config sub-directory of OpenLink server components installations. The Admin Assistant will write simple error messages to the log when startup fails. Consultants must search the knowledge-base for the import of these errors. Finally, we have reviewed the default Admin Assistant log entries. However, users can cause the Admin Assistant to run at log level 7. This is achieved by setting the log level in the [www_sv] of the Session Rules Book. For example: [www_sv] Program = w3config/www_sv Directory = w3config CommandLine = +loglevel 6 Log level 7 causes the Admin Assistant to output an HTTP log that display individual scripts and images as it serves them. Be sure to look for errors interspersed between the entries.
rdf:type: schema:Answer

Subject Item: n103:this
schema:name: How Do I Interpret Classpaths? -- Answer
schema:category: JDBC UDA ODBC
schema:text: The CLASSPATH variable passes the full path to an OpenLink opljdbc.jar or megathin.jar file. Consultant's need to consider the following factors when examining CLASSPATH environment variables: 1. Was CLASSPATH set at the time of reported failure? Review the output of set, the Windows autoexec.bat file, or Windows System utility screen-shots for corroboration. 2. Does CLASSPATH point to a valid .jar file? Review the output of ls or dir in the directory structure for the purpose of corroboration. 3. Do file or directory permissions issues restrict access to the .jar file? 4. Does the .jar file JDK version correspond with the client JRE version? 5. Does CLASSPATH need to be set within application code?
rdf:type: schema:Answer

Subject Item: n299:this
schema:name: How Do I Interpret DBMS Versions? -- Answer
schema:category: JDBC UDA ODBC
schema:text: DBMS server versions can provide a host of information: 1. Compare the user's DBMS version with the Multi-Tier database agent version string or Single-Tier driver version. Is the DBMS compatible with the agent or lite driver? 2. Compare the user's DBMS version with the DBMS version against which OpenLink's product was built. Are they the same? Differences in server version or patch level may contribute to a host of problems including outright compatibility or subtle stability issues. 3. Compare the user's DBMS version with the operating system version and patch level. Does the operating system meet the system requirements of the DBMS? 4. Obtain Unix server's kernel tuning parameters. Do the tuning parameters match the requirements specified in the DBMS documentation? Insufficient tuning parameters contribute to stability problems. 5. Is the user's DBMS server version associated with limitations or bugs? Is the DBMS server's patch level current? Recommend re-links to Multi-Tier users, when their DBMS version and their database agent version strings differ. Relinking resolves some compatibility issues.
rdf:type: schema:Answer

Subject Item: n195:this
schema:name: How Do I Interpret Database Agent Version Strings? -- Answer
schema:category: JDBC UDA ODBC
schema:text: 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.
rdf:type: schema:Answer

Subject Item: n329:this
schema:name: How do I interpret Database Native Error Logs? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink Product Support does not have extensive information pertaining to the interpretation of 3rd-party database error logs. Examine these logs for errors. Then, search OPIE and the database vendor knowledge-bases for additional information.
rdf:type: schema:Answer

Subject Item: n321:this
schema:name: How Do I Interpret Database Profiles? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Database .profiles are Unix files that contain variables that databases need to function. They appear in the root directory of most database installations. Furthermore, these environment variables facilitate ODBC, JDBC, and other data access mechanisms. Multi-Tier users need to insure that pertinent database .profile variables appear in the [Environment] section of their Session Rules Books. The Session Rules Book is the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink server components installation.
rdf:type: schema:Answer

Subject Item: n315:this
schema:name: How Do I Interpret Installation Shell Scripts? -- Answer
schema:category: JDBC UDA ODBC
schema:text: 1. Obtain copies of the user's installation shell script and installation files. 2. Obtain the output of uname -a on the problem machine. 3. Transfer the files to an appropriate test box. 4. Run the installation procedure.
rdf:type: schema:Answer

Subject Item: n340:this
schema:name: How Do I Interpret License Files? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Do you have an OpenLink 4.x or newer license? If so, take the following action: 1. Save the license to the directory that contains asnprint.exe. 2. Open a DOS prompt. 3. cd into the directory that contains asnprint.exe. 4. Run asnprint.exe . For example: asnprint.exe oplrqb asnprint.exe reveals the following, useful information: -- SerialNumber - Does the user report Duplicate Serial Number errors? If so, gather all licenses from the user environment and compare serial numbers. The serial numbers must not be identical. Identical serial numbers show that the user is attempting to break the licensing agreement by using one license on multiple machines. Direct such users to Account Management. -- RegisteredTo - This parameter has no support value. -- NumberOfUsers - This value represents the number of client machines that can connect simultaneously. It is useful in resolving "exceeded maximum number of licensed connections errors." If a user experiences this error, compare the NumberOfUsers parameter to the number of client machines that connect at one time. Traces,log files, or database monitoring tools may also be needed to ascertain the true number of clients that are connected at one time. -- NumberOfConnections - This value represents the number of database sessions that may be opened simultaneously. It is useful in resolving "exceeded maximum number of licensed connections errors." If a user experiences this error, compare the NumberOfConnections parameter to the number of open database sessions. Traces,log files, oplshut -s output, or database monitoring tools may also be needed to ascertain the true number of sessions that are open at one time. -- NumberOfCPUs - This value must match the number of CPUs installed in the user's machine. -- Clients - An ODBC designation will prevent users from using the JDBC Data Access Mechanism. An JDBC designation will prevent users from using the ODBC Data Access Mechanism. -- ExpireDate - Check this parameter, if the user reports license expiration errors. Compare with the current date. -- Platform - Check this parameter, if the user experiences errors that suggest the license is invalid for the operating system. Compare with a uname -a from the actual machine. -- Availability -- Release - Check this parameter, if the user reports invalid license or upgrade license errors. Compare with Multi-Tier Broker and/or agent strings or Single-Tier version information. Consultants may open OpenLink's 1.x and 3.x licenses to obtain the same information. Finally, if licensing problems persist, take the following action: -- Insure that only one license appears on the relevant machine. -- Insure that Multi-Tier Request Brokers are restarted or reinitialized. -- Insure that Single-Tier drivers and Single-Tier licenses share the same product code. As a last resort, reinstall and relicense the product. Wipe references to OpenLink products from Windows registries, where appropriate.
rdf:type: schema:Answer

Subject Item: n345:this
schema:name: How Do I Interpret Name Of Taz Files? -- Answer
schema:category: JDBC UDA ODBC
schema:text: .taz file names are useful for detecting product and operating system incompatibilities. (Failure to install, core dumps, segmentation faults, signals, and blatant incompatibility errors are all possible side effects of product and OS mismatch.) If you suspect an incompatibility, obtain the name of the .taz file and a uname -a from the affected machine. Decode the .taz file name to see if it was intended for the user's operating system.
rdf:type: schema:Answer

Subject Item: n348:this
schema:name: How Do I Interpret Openlink ini Files? -- Answer
schema:category: JDBC UDA ODBC
schema:text: The Single-Tier openlink.ini file associates database specific environment variables and port settings with Single-Tier domain aliases. For example: [Server Types] Oracle 8.1.x = [Environment Oracle 8.1.x] ORACLE_HOME = /dbs5/oracle9i/64bit/v9.2.0.1.0 ORACLE_SID = ora92 ;ORACLE_SERVER = T ;TWO_TASK = P: ;ODBC_CATALOGS = Y ;MULTIPLEX_LDA = 5 ;OPL_USR_TBLS_FIRST = Y SHOW_REMARKS = N CURSOR_SENSITIVITY = LOW ;OCI_PREFETCH_ROWS = 100 ; ;OCI_PREFETCH_MEMORY = 65535 ; ;NLS_LANG = AMERICAN_AMERICA.UTF8 Use the following guidelines to interpret openlink.ini files: 1. Ascertain which server type (a.k.a. "domain alias") is passed in the Single-Tier Data Source. 2. Open the openlink.ini file. 3. Insure that the server type appears in the [Server Type] list. 4. Locate the [Environment] section that is associated with the server type. 5. Insure that the appropriate environment variables are set. 6. Compare the variable settings with the database user .profile to insure accuracy. 7. Use relevant database utilities or configuration files to verify any TCP port settings.
rdf:type: schema:Answer

Subject Item: n354:this
schema:name: How do I interpret Operating System Patch Levels? -- Answer
schema:category: JDBC UDA ODBC
schema:text: Use the following guidelines: 1. Insure that users have applied all, current operating system patches. 2. Determine whether or not the DBMS requires a specific patch level. 3. Ascertain whether patches are associated with issues presented by the user. 4. Compare the user patch level to the OpenLink build server patch level. OpenLink's build servers may require patch updates, if they are behind user patch levels. Users may need patch updates, if they are behind OpenLink's patch level. Otherwise, discrepancies between the machines may contribute to compatibility and stability problems.
rdf:type: schema:Answer

Subject Item: n366:this
schema:name: How Do I Interpret Output Of Java Commands? -- Answer
schema:category: JDBC UDA ODBC
schema:text: 1. Insure that the java command returns driver version information. Failure to return version information may show an incompatibility or environment problem. 2. Insure that successful driver version information matches the expected driver name and version. 3. Check available resources to see if the driver version is associated with limitations, bugs, or other known issues. Bugzilla is the best point of reference for OpenLink JDBC drivers. 4. Compare Multi-Tier JDBC client java output with Request Broker Version and Database Agent Version strings. Differing client and server versions create compatibility and stability problems.
rdf:type: schema:Answer

Subject Item: n87:this
schema:name: How Do I Interpret Output Of Oplshut? -- Answer
schema:category: JDBC UDA ODBC
schema:text: oplshut -s produces the following output: [openlink@openlinux bin]$ ./oplshut -s SVPID SVTYPE MACHINE OPSYS APPLIC DATABASE USERNAME CONNECT -------------------------------------------------------------------------------- 1480 mys3 dyn2.openlinksw msdos cppdmo32 test mysql Mar 30 12:01 Here is a brief overview of the output displayed by oplshut -s: SVPID - Associates a Process Identification Number with a database agent. Users can run oplshut +kill svpid to terminate database agents that will not disconnect. For example: oplshut +kill 1480 oplshut +kill will terminate all connections associated with an agent. This is important since multi-threaded agents may handle multiple connections simultaneously. SVTYPE - Passes a label which identifies the Domain Alias, which was used to establish the connection. The Domain Aliases appear in the Session Rules Book (oplrqb.ini)
rdf:type: schema:Answer

Subject Item: n11:this
schema:name: How Do I Interpret Output Of Set? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink's Unix components require the following ODBC environment variables to be set: -- CLASSPATH A JAVA client variable that passes the full path to an OpenLink JDBC .jar file. This variable should appear on all systems that contain OpenLink JDBC client components. -- LD_LIBRARY_PATH A generic library path variable that appends the full path to OpenLink's lib sub-directory. This variable should be set on any machine that contains Single-Tier or Multi-Tier client or server components. -- LIBPATH An AIX library path variable that appends the full path to OpenLink's lib sub-directory. This variable should be set on any AIX machine that contains Single-Tier or Multi-Tier client or server components. -- ODBCINI Passes the full path to ~/openlink/bin/odbc.ini. This variable should be set on any machine that contains Single-Tier or Multi-Tier client components. -- ODBCINSTINI Passes the full path to ~/openlink/bin/odbcinst.ini. This variable should be set on any machine that contains Single-Tier or Multi-Tier client components. -- OPENLINKINI This Single-Tier variable passes the full path to ~/openlink/bin/openlink.ini. This variable should be set on any machine that contains Single-Tier client components. -- PATH Appends the full path to OpenLink's bin sub-directory. This variable should be set on any machine that contains Single-Tier or Multi-Tier client or server components. -- SHLIB_PATH An HP/UX library path variable that appends the full path to OpenLink's lib sub-directory. This variable should be set on any HP/UX machine that contains Single-Tier or Multi-Tier client or server components. set output should be checked against ls output for the relevant directories structures. This shows: -- Which environment variables are set. -- Which environment variables are missing. -- Whether or not variable paths are correct. -- Whether or not permissions prevent access to files or directories. OpenLink's drivers also require database specific environment variables. set should be run before Single-Tier client installation or Multi-Tier server component installation. Users must insure that the relevant database native environment variables are set. This enables OpenLink's installers to detect the settings and write them into Single-Tier openlink.ini or Multi-Tier oplrqb.ini file.
rdf:type: schema:Answer

Subject Item: n369:this
schema:name: How Do I Interpret Relink Scripts? -- Answer
schema:category: JDBC UDA ODBC
schema:text: OpenLink's re-link scripts are associated with missing library errors and missing symbol errors. Use the following guidelines to troubleshoot these problems: Missing Libraries: 1. Search the machine for the missing library. 2. Insure that no file or directory permissions prohibit access to found libraries. 3. Insure that LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH pass the location of found libraries. 4. Pass the full path to found libraries within the re-link script itself. In most cases, pass the library on the cc -s -o line. However, pass the library on the make -f line in Oracle scripts. Pass the library under $PRO_EXTRA in Progress mkdlc scripts. Missing Symbols 1. Login to the machine. 2. cd into the database's /lib sub-directory. 3. Run the following command: nm -A *.so | grep . For example: nm -A *.so | grep xsendto 4. Record the names of files, which contain the symbols. The filename will be the first name in the nm output. 5. cd to the /lib sub-directory of the OpenLink installation. 6. vi the script that produced the error. 7. Pass the full path to found libraries within the re-link script itself. In most cases, pass the library on the cc -s -o line. However, pass the library on the make -f line in Oracle scripts. Pass the library under $PRO_EXTRA in Progress mkdlc scripts.
rdf:type: schema:Answer

Subject Item: n372:this
schema:name: How Do I Interpret Request Broker Logs? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Use the following guidelines to interpret Request Broker Log files. Tue Oct 15 2002 Make sure the log date corresponds to the occurrence of the problem. 12:25:46 using rule-book /home/openlink/32bit/v42/bin/oplrqb.ini Check the path to oplrqb.ini. Insure that the correct file is referenced. Users can encounter problems, when they have multiple, Multi-Tier installations. Specifically, users will notice that the wrong agents are spawned and the wrong environment variables may be employed. 12:25:46 bound UDP protocol to 0.0.0.0.60001 Check for UDP and "address in use" errors. Use netstat -a & the services file to debug any problems that occur with the UDP port. Likewise, insure that UDP is enabled on the client and server machines that produce UDP broadcast errors. 12:25:46 bound TCP protocol to 0.0.0.0.5000 Check for "address already in use" and other TCP port problems. Use netstat -a & the services file to debug any problems that may occur. In the event of a port conflict, users may change the Broker's Listen port. Users will find the Listen parameter in the [Protocol TCP] section of oplrqb.ini. 12:25:46 using UDP address 192.168.11.116.0 for IPC Check for UDP and "address in use" errors. Use netstat -a & the services file to debug any problems that occur with the UDP port. Likewise, insure that UDP is enabled on the client and server machines that produce UDP broadcast errors. 12:25:46 request broker started by openlink Brokers started by root may cause resource problems or Progress "login by batch" errors. Search for "batch" and resource related problems later in the file. 12:25:46 spawning /home/openlink/32bit/v42/bin/w3config/www_sv www_sv www_sv powers the Admin Assistant. Moreover, it uses the HttpPort passed in the www_sv.ini file. If "address" or other TCP port usage problems occur, run netstat -a and services to debug port conflicts. If necessary, have the user change the HttpPort in ~/openlink/bin/w3config/www_sv.ini file. 12:25:46 started persistent www_sv (pid=12219) 12:25:53 example.com called (*******) 12:25:53 request: domain=Progress 91C database=demo.db serveropts= 12:25:53 connectopts=-S pro91c -N tcp -H **** user= demo_user=unix readonly=0 These parameters are read from the Data Source Name. Check for inappropriate values. Additionally, watch for "Broker cannot resolve your request" errors. "Request" errors occur when the Domain name passed in this parameter list does not appear in the [Domain Aliases] section of oplrqb.ini. Users must create the appropriate in oplrqb.ini or choose an existing alias. 12:25:53 application=odbctest processid=12220 12:25:53 solve mapping: pro91c:demo:blank:other:example.com:odbctest:rw 12:25:53 using mapping: pro91c:*:*:*:*:*:* The Broker takes the abbreviated form of the domain alias and searches for matches in the [Mapping Rules] section of oplrqb.ini. The Broker will use the appropriate rule to prohibit or permit access to the database. Users may encounter "Mapping not found" errors, if their alias does not have an associated rule. Additionally, users may inadvertently create complex rules, which restrict their ability to connect. 12:25:53 using [generic_pro91c] ServerProgram=pro91c_sv Most mapping rules will point the Broker to a [generic] agent configuration section. This section passes the name of the database agent that is written in the database's CLI. It passes the location of database-specific environment variables, and it passes hard-coded connection parameters. Problems will occur on this line, if the agent configuration section does not exist in oplrqb.ini. 12:25:53 connect params: domain=Progress 91C db=demo.db serveropts=-T /tmp -d mdy -TB 31 -TM 31 -q -NL readonly=0 12:25:53 connectopts=-S pro91c -N tcp -H oplushp2 user= demo_user=unix machine=example.com application=odbctest This line shows the final list of parameters that will be used to establish the connection. In essence, the Broker tosses out specific Data Source Name parameters if corresponding parameters are hard-coded in oplrqb.ini. These hard-coded parameters can result in problems, if the user forgets they exist. Typically, users will discover that they are connected to the wrong database, they are authenticated as the wrong user, or they are restricted to read-only access. They may also experience authentication problems, which arise when OPSYSLOGIN is enabled. OPSYSLOGIN uses operating system parameters to authenticate. It does not recognize the typical database username and password. 12:25:53 spawning /home/openlink/32bit/v42/bin/pro91c_sv generic_pro91c This line shows the agent that is spawned for the connection. Problems occur if permissions prohibit spawning. Problems also occur when the agent is not compatible with the operating system or the agent cannot be found. 12:25:53 setting Environment PROGRESS91C 12:25:53 change environment 'CURSOR_SENSITIVITY' -> 'LOW' 12:25:53 change environment 'DLC' -> '/dbs2/progress/v91c' 12:25:53 change environment 'PROCFG' -> '/dbs2/progress/v91c/progress.cfg' The [generic] agent configuration section contains an Environment parameter. This parameter passes the location of an [Environment] section. This [Environment] section passes database-specific environment variables that are needed to establish the connection. Problems arise when the [Environment] section does not exist in oplrqb.ini. 12:25:53 asking agent for server handle "Server handle" errors occur when the preceding environment variables are incorrect. If environment variables are correct, consult the OPIE knowledge-base for additional information. 12:25:53 got it! 12:25:53 asking agent for connection handle "Connection handle" errors occur when connection parameters are incorrect. If the parameters are correct, consult OPIE for additional information. 12:25:53 got it! 12:25:53 accepted blank@example.com.odbctest At this point, your user is connected to the database. However, a wide array of produce and database errors may occur at this point. Consult OPIE for the nature and description of these errors.
rdf:type: schema:Answer

Subject Item: n377:this
schema:name: How Do I Interpret Request Broker Version Strings? -- Answer
schema:category: ODBC UDA JDBC
schema:text: 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.
rdf:type: schema:Answer

Subject Item: n360:this
schema:name: How Do I Interpret Udbc ini Files? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Here are the operative portions of a udbc.ini file: [UDBC] ;DebugFile= /tmp/udbc.out [Communications] ReceiveTimeout = 120 BrokerTimeout = 30; RetryTimeout = 5 SendSize= 4096 ReceiveSize = 16000 ShowErrors= Y DataEncryption = N [dsn_oracle] Description = Sample Oracle DSN Host = 192.62.13.144 ServerType = Oracle 8.1.x FetchBufferSize = 60 Database = ORCL ServerOptions = ConnectOptions = Options = UserName = scott Password = tiger ReadOnly = yes Here is a description of important parameters: DebugFile The DebugFile parameter controls UDBC tracing. Users must remove the semicolon from DebugFile, if they want to instantiate tracing. They must also pass the full path to a file to which DebugFile may write output. Users must place a semicolon in front of DebugFile to stop debug output. Communications The Communications section contains
rdf:type: schema:Answer

Subject Item: n257:this
schema:name: How Do I Test My JDBC Connection URL? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Multi-Tier users may use the Admin Assistant to test their JDBC URLs. The following instructions will assist you with this task: -- Open the Admin Assistant in a Web browser. -- Expand the Sample Applications menu. -- Click JDBC Applet Demos. -- Select your JDK version, as needed. -- Select the appropriate sample application. Single-Tier drivers may use the iODBC Data Sources Administrator on Unix platforms. The following instructions will assist you with this task: -- Open the iODBC Data Sources Administrator in a Web browser. -- Expand the Sample Applications menu. -- Click JDBC Applet Demos. -- Select your JDK version, as needed. -- Select the appropriate sample application. Single-Tier drivers may also use the JDBC sample applications on Windows platforms. The following instructions will assist you with this task: -- Expand your Start menu. -- Expand your Programs menu. -- Locate your OpenLink Single-Tier drivers folder. -- Expand Our OpenLink Single-Tier drivers folder. -- Expand the JDBC Samples sub-folder. -- Expand the JDK sub-folder that corresponds to your JDK version. -- Select the desired application.
rdf:type: schema:Answer

Subject Item: n356:this
schema:name: How Do I Troubleshoot A Failed JDBC-ODBC Bridge Connection? -- Answer
schema:category: ODBC UDA JDBC
schema:text: 1. Insure that the ODBC Data Source Name connects to the target database. 2. Insure that Windows-based ODBC Data Sources are System Data Sources. 3. Insure that OpenLink's Single-Tier driver is installed on the machine that contains the ODBC Data Source Name. 4. Insure that you pass the exact name of the ODBC Data Source in the JDBC connection URL. 5. Insure that your Single-Tier JDBC connection URL uses the following syntax: jdbc:openlink://ODBC[/DSN][/UID][/PWD][/READONLY] For example: jdbc:openlink://ODBC/DSN=Local Oracle ODBC/UID=scott/PWD=tiger
rdf:type: schema:Answer

Subject Item: n351:this
schema:name: How Do I Troubleshoot A Failed ODBC-JDBC Bridge Connection? -- Answer
schema:category: ODBC UDA JDBC
schema:text: 1. Insure that the JDBC connection URL connects to the target database. 2. Insure that OpenLink's Single-Tier client components or Multi-Tier server components are installed on the machine that contains the JDBC connection URL. 3. Multi-Tier users insure that oplrqb and a JDBC Bridge Agent (jdbc13_mv, jdbc14_mv, etc.) appear in the /bin sub-directory of the OpenLink server components installation. 4. Multi-Tier users insure that oplrqb and the JDBC Bridge Agent (jdbc13_mv, jdbc14_mv, etc.) return version and usage information. For example: > jdbc14_mv -? JDBC Database Agent (JDK 1.4)(multi threaded) Version 1.2 as of Thu Sep 04 2003 (Release 5.1 cvsid 00068). Compiled for Linux 2.2.25 (i686-pc-linux-glibc2.1) Copyright (C) OpenLink Software 5. Insure that you pass the exact JDBC driver name string and JDBC connection URL in your OpenLink Data Sources. You can test the driver name string with the java command. It should return version and release information. For example: > java openlink.jdbc3.Driver OpenLink Generic Driver for JDBC(TM) 3.0 Version 04.19 (Release 5.1) 6. Multi-Tier users insure that JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4 appears in the Domain or Server Type field of the Multi-Tier Data Source Name. (Case and spacing matter!) 7. Unix Single-Tier users insure that JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4 appears in the Existing Environment field of the Single-Tier Data Source Name. (Case and spacing matter!) If the problem persists, complete a troubleshooting worksheet. Post the results into an online support case.
rdf:type: schema:Answer

Subject Item: n342:this
schema:name: How do I troubleshoot a failed ODBC-ODBC Bridge connection? -- Answer
schema:category: ODBC UDA JDBC
schema:text: 1. Insure that the non-OpenLink Data Source Name connects to the target database. 2. Insure that OpenLink's Single-Tier client components or Multi-Tier server components are installed on the machine that contains the non-OpenLink Data Source Name. 3. Multi-Tier users insure that oplrqb and odbc_mv appear in the /bin sub-directory of the OpenLink server components installation. 4. Insure that all Windows-based Data Source Names are System Data Source Names. 5. Insure that you pass the exact name of the non-OpenLink Data Source to the OpenLink Data Source. Multi-Tier users pass this name in the Database field of their OpenLink Data Sources. 6. Multi-Tier users insure that "Odbc" appears in the Domain or Server Type field of the Multi-Tier Data Source Name. (Case matters!) If the problem persists, complete a troubleshooting worksheet. Post the results into an online support case.
rdf:type: schema:Answer

Subject Item: n337:this
schema:name: How Do I Uninstall Existing OpenLink Software? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Windows users may use OpenLink's uninstall utility to remove existing software. Windows users may also move the Add or Remove Programs utility, which appears in their Control Panel. OpenLink does not provide an uninstall utility for Unix platforms. Unix users may use rm or rmdir to remove existing builds.
rdf:type: schema:Answer

Subject Item: n318:this
schema:name: How Do Users Configure The Odbc ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Single-Tier users should use their HTTP-Based iODBC Data Sources Administrator to configure the odbc.ini file. Multi-Tier users may use the Admin Assistant to configure the odbc.ini file. All users may configure odbc.ini with vi or a similar text editor, if no graphical assistant exists.
rdf:type: schema:Answer

Subject Item: n324:this
schema:name: How Do Users Configure The Odbcinst ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users should not need to configure the odbcinst.ini file. If configuration is necessary, users may edit it with vi or a similar text editor.
rdf:type: schema:Answer

Subject Item: n326:this
schema:name: How Do Users Configure The Openlink ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users do not want to make manual edits to Unix-based openlink.ini files. Instead, users should perform the following actions, before they install OpenLink drivers: 1. Login to the Unix system. 2. su to the database client user. 3. Execute the database client user's .profile. 4. Run OpenLink's installation procedure. OpenLink's installation procedure should detect the database client user's environment variables and write them into openlink.ini. If this procedure fails, users's should take the following action: 1. vi the database client user's .profile. 2. Record the variables contained in the file. 3. cd into the /bin sub-directory of the OpenLink installation. 4. vi openlink.ini. 5. Locate the [Environment] section that pertains to the OpenLink driver. 6. Set the appropriate environment variables.
rdf:type: schema:Answer

Subject Item: n331:this
schema:name: How Do Users Configure The Oplrqb ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users may use the HTTP-based Administrative Assistant to configure their oplrqb.ini files. There are a wide variety of animated tutorials that explain the Administrative Assistant features. Instruct users to use the Administrative Assistant's refresh feature to initialize changes it makes to the file. Advanced users may edit oplrqb.ini with a text editor. Instruct users to restart the Broker or reinitialize the Broker ( oplshut +reinit ) to initialize changes made to the file.
rdf:type: schema:Answer

Subject Item: n302:this
schema:name: How Do Users Configure The Udbc ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users may install a Multi-Tier Request Broker archive on the machine that contains their Multi-Tier client components. This provides users with the HTTP-based Administrative Assistant. Users may use the Assistant to configure their udbc.ini files. There are animated tutorials, which explain this process. Text-based instructions appear below: 1. Open the client-side Administrative Assistant in a Web browser. 2. Expand the Client Components Administration menu. 3. Expand the Data Source Name Configuration menu. 4. Expand the Edit Data Sources by Wizard menu. 5. Click Edit UDBC Data Sources. 6. Click Add. 7. Answer the questions posed by the Wizard. 8. Save the DSN and test. Advanced users may edit udbc.ini with a text editor.
rdf:type: schema:Answer

Subject Item: n296:this
schema:name: How Do Users Create Data Source Names? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Single-Tier users may create Data Source Names using the following methods: 1. Use the HTTP-Based iODBC Data Sources Administrator. 2. Use the Windows ODBC Data Sources Administrator. 3. Use the Mac OS X OpenLink ODBC Administrator. 4. Use the Mac Classic ODBC Setup PPC. 5. Manually edit Unix-based odbc.ini files. Multi-Tier users may create Data Source Names using the following methods: 1. Use the HTTP-Based Multi-Tier Administrative Assistant. 2. Use the HTTP-Based iODBC Data Sources Administrator. 3. Use the Windows ODBC Data Sources Administrator. 4. Use the Mac OS X OpenLink ODBC Administrator. 5. Use the Mac Classic ODBC Setup PPC. 6. Manually edit Unix-based odbc.ini files.
rdf:type: schema:Answer

Subject Item: n90:this
schema:name: How Do Users Obtain Licenses? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's downloads page forwards temporary licenses to the user's email account. Users must approach an OpenLink Account Manager to obtain a permanent license or purchase using the online ordering system.
rdf:type: schema:Answer

Subject Item: n305:this
schema:name: How Do Users Start The Multi-Tier Request Broker? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Windows users should take the following action: 1. Login to the machine, which contains the OpenLink server components. 2. Open the Services utility. (Control Panel) 3. Locate the OpenLink Request Broker service. 4. Highlight the service. 5. Click the Start icon. Unix users should take the following action: 1. Login to the machine, which contains the OpenLink server components. 2. cd into the root of the OpenLink installation. 3. Execute openlink.sh (Bourne/Bash shell) or openlink.csh (C shell). 4. cd into the /bin sub-directory of the installation. 5. Execute the following command: oplrqb New Unix users may want to start the Request Broker with oplrqb +loglevel 7 +logfile oplrqb.log. This instantiates logging and will elucidate problems that may occur.
rdf:type: schema:Answer

Subject Item: n262:this
schema:name: How Do Users Uninstall OpenLink Software? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Windows and Mac OS X drivers ship with uninstall utilities. OpenLink's Unix and Mac Classic drivers do not ship with uninstall utilities. Users must manually remove Unix and Mac Classic components. Unix users simply rm or rmdir the installation directory. Mac Classic users use their installation reports to identify and locate the components that need to be removed.
rdf:type: schema:Answer

Subject Item: n268:this
schema:name: How Do Your Drivers Work? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Single-Tier drivers are client-side drivers. Users install most Single-Tier drivers on a machine, which contains the database native client. The drivers connect to this native client and send queries-through the client--to the database. In essence, the database native client speaks a proprietary network protocol that bridges the gap between a local driver and a remote database. OpenLink's MS SQLServer, MySQL, PostgreSQL, and Sybase drivers are "wire protocol" drivers. These drivers contain libraries, which allow them to speak their database's native network protocol. Hence, users may install these drivers on any supported operating system. These drivers do not need the database native client to connect. OpenLink's Multi-Tier drivers are client/server drivers. All users install the client on the machine, which contains their client application. Most users install OpenLink's Multi-Tier server components on a machine that contains the database or the database native client. OpenLink's Multi-Tier server components consist of a Broker and a database-specific agent. The Broker responds to client requests and spawns the database agent that is designed to speak to the intended database. This agent is written in the database CLI and may speak directly to the database or proxy queries through the database native client. Moreover, the database agent is responsible for the return of data to the calling application. Finally, persons with MS SQLServer, MySQL, PostgreSQL, and/or Sybase databases may install their Multi-Tier server components on any supported operating system. These agents speak the database native communications protocol. Consequently, they can establish connections to remote databases without the aid of the database native client.
rdf:type: schema:Answer

Subject Item: n248:this
schema:name: How does clustering affect licensing? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Single-Tier users must license each individual Single-Tier installation. Multi-Tier users must obtain a distinct license for each running Request Broker. Hence, all load balancing architectures require two or more Request Broker licenses. Fail-over architectures may share one license, so long as only one Request Broker runs at a time. However, some fail-over architectures may require or benefit from multiple licenses. Note:Please contact your Account Manager for more information on your Clustering License needs
rdf:type: schema:Answer

Subject Item: n253:this
schema:name: How much do licenses cost? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Pricing Information can be obtained from the Sales section (http://www.openlinksw.com/sales ) of the OpenLink Web Site:
rdf:type: schema:Answer

Subject Item: n292:this
schema:name: How To FTP? -- Answer
schema:category: ODBC UDA JDBC
schema:text: FTP all installation shell scripts (install.sh) in ASCII transfer mode. FTP all other files in binary.
rdf:type: schema:Answer

Subject Item: n286:this
schema:name: How To Uncompress Files? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's products ship in a compressed file format: -- .bin Binary Mac Classic -- .dmg Disk Image Mac OS X -- .hqx BinHex Mac Classic -- .tar Compressed Archive Unix Decompress with install.sh -- .taz GZIP Archive Unix Decompress with tar -xvfz or gunzip -- .zip Zip File WinZip Decompress with WinZip
rdf:type: schema:Answer

Subject Item: n276:this
schema:name: I Do Not Know The Correct Values For My Multi-Tier DSN. What Do I Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The following guidelines enable you to establish the values that you need to pass in a client/server Data Source Name. Name Provide any descriptive title for your Data Source Name. Limit the name to 32 characters and start with an alphanumeric character. Description You may provide an optional description for your Data Source Name. Server This field passes the hostname or IP address of the machine that contains your OpenLink server components installation. It also passes the TCP port on which the Request Broker listens. If you do not know the hostname or IP address of the machine, you may run hostname on the console. If you do not have access to the console, contact its System Administrator. The Broker's TCP port is recorded in the Session Rules Book. The Session Rules Book is the oplrqb.ini file that appears in the /bin sub-directory of the OpenLink server components installation. It may be opened with any text editor.
rdf:type: schema:Answer

Subject Item: n2:this
schema:name: I do not know the correct values for my Single-Tier DSN. What do I do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Single-Tier drivers pass a name and a set of database-specific connection parameters. You may name your Data Source Name anything you want, so long as it observes length and special character considerations. However, you should consult your Database Administrator, if you need assistance with the database-specific connection parameters. The database-specific parameters are parameters that the various database native clients use to connect to the database. OpenLink Product Support Staff is familiar with many database native clients. However, these products change frequently. Moreover, your Database Administrator and Database Vendor will have more intimate knowledge of these products as they instantiate in your environment.
rdf:type: schema:Answer

Subject Item: n208:this
schema:name: I Suspect That My User Is Experiencing Port Or Networking Problems. What Do I Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Port and networking problems arise in a variety of contexts. Choose the context that corresponds to your user: 1. Do firewall restrictions prevent a user from download OpenLink software? Test both HTTP and FTP links. Provide a DAV link to the file. Attempt to FTP the file to a user site. Attempt to email components to the user. Provide files to user via CD. (Requires Manager Approval.) 2. Do networking problems prevent transfer of an OpenLink download to the target machine? Urge the user to seek assistance from the on-site network administrator. Tell the user to transfer the file(s) via CD or disk. 3. Do port problems prevent Multi-tier users from starting their Request Brokers? Login to the machine that contains the Multi-tier server components. Use a text editor to open the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink installation. Locate the [Protocol TCP] section. Locate the Listen parameter. (1.x and 3.x users locate PortLow.) Close oplrqb.ini. Run netstat -a. If Listen or PortLow is occupied, assign a new port in oplrqb.ini. If Listen or PortLow is not occupied, this may not be a port problem. 4. Do users not know what ports to pass in OpenLink data source names? Inform users that the only OpenLink-specific ports appear in the [Protocol TCP] section of the server component's ~/openlink/bin/oplrqb.ini file. Any other port would be gleaned from database-related configuration files or utilities. 5. Do firewalls prevent Multi-Tier clients from contacting Multi-Tier Request Brokers? Login to the machine that contains the Multi-Tier server components. Use a text editor to open the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink installation. Locate the [Protocol TCP] section. For example: [Protocol TCP] PingWatchdog = No PingInterval = 600 ;IPAddress = 127.0.0.1 PortLow = 5000 PortHigh = 5020 Make sure PortHigh is uncommented and set. PortHigh should equal PortLow + the number of concurrent connections granted by the license + a few extra ports. Record the PortLow-PortHigh range. Record the Listen port value. (OpenLink 1.x and 3.x do not have Listen.) Close oplrqb.ini. Open the Listen and PortLow-PortHigh TCP ports on the firewall. Open UDP port #60001--in addition to TCP PortLow-PortHigh--to accommodate 1.x and 3.x drivers. 6. Do Multi-Tier port settings restrict the number of concurrent connections? Login to the machine that contains the Multi-Tier server components. Use a text editor to open the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink installation. Locate the [Protocol TCP] section. For example: [Protocol TCP] PingWatchdog = No PingInterval = 600 ;IPAddress = 127.0.0.1 PortLow = 5000 PortHigh = 5020 Make sure PortHigh is uncommented and set. PortHigh should equal PortLow + the number of concurrent connections granted by the license + a few extra ports. Save changes and exit the file. Restart or reinitialize the Request Broker and test.
rdf:type: schema:Answer

Subject Item: n213:this
schema:name: Is OpenLink Support Staff responsible for all user problems? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink Support staff should endeavor to solve most problems. However, some problems are the domain of the user. OpenLink Support staff is not responsible for extensive custom development. Users must code their own applications or seek assistance from OpenLink's Professional Services team. Likewise, OpenLink staff is not responsible for user database and network administration. -- Acceptable: Can you help me write a JDBC connection URL to connect my application to Informix? -- Questionable: Can you help me write a JAVA program? -- Acceptable: Can you help me establish an ODBC connection to Oracle? -- Questionable: Can you help me tune Oracle?
rdf:type: schema:Answer

Subject Item: n216:this
schema:name: My 1x 3x JDBC Type 3 Connections Spawn Multiple Agents That Consume My Licenses. What Do I Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This is expected behavior. OpenLink's 1.x and 3.x Multi-Tier connections spawn a JDBC-specific agent that spawns a database-specific agent. Hence, one JDBC connection results in two concurrent connections. OpenLink's latest drivers do not spawn both a JDBC agent and a database agent. OpenLink's new database agents are equipped to handle JDBC connections in their entirety.
rdf:type: schema:Answer

Subject Item: n222:this
schema:name: What Do I Do If My Applications Fail To Connect After I Upgraded My 1x3x Drivers To 4x5x? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's 1.x and 3.x Multi-Tier drivers use different JDBC connection mechanisms. The older drivers route the request through a JDBC-specific agent that speaks to a database-specific agent. Here is the sequence of events needed to perform this task: 1. User creates a JDBC connection URL. For example: jdbc:openlink://localhost:5000/SVT=Ingres II/DATABASE=iidbdb/UID=ingres/PWD=ingres/JDBCAGENT=jodbc 2. The Broker associates all JDBC connection attempts with one of the JDBC Domains that appear in the [Domain] section of the Session Rules Book (oplrqb.ini). For example: [Domain Aliases] jodbc = jodbc judbc = judbc jdbc = jdbc 3. The Broker uses the Domain Alias to resolve the connection using one of the JDBC Mapping Rules from the [Mapping Rules] section of oplrqb.ini. For example: [Mapping Rules] jodbc:*:*:java:*:*:* = accept jodbc_client judbc:*:*:java:*:*:* = accept judbc_client jdbc:*:*:java:*:*:* = accept jdbc_client *:*:*:java:*:*:* = accept judbc_client 4. The Mapping Rules associate the connection attempt with a JDBC agent configuration section. For example: [jodbc_client] Program = jodbc_sv.exe CommandLine = ;+debug ReUse = never 5. The agent configuration section controls which JDBC agent is spawned to service the connection. In the above instance, jodbc_sv.exe is spawned. The JDBC agent spawns the database agent that corresponds to the SVT parameter of the JDBC connection URL. The following sections of the Rules Book shows how SVT=Ingres II causes the JDBC agent to spawn the oig2_sv database agent: Domain Aliases] Ingres II = oig2 [Mapping Rules] oig2:*:*:*:*:*:* = reject The Ingres II Database Agent is not configured [generic_oig2] Program = oig2_sv.exe Environment = INGRES_II OpsysLogin = Yes ReUse = never OpenLink's newest drivers omit the need for a distinct JDBC agent. JDBC-specific Domains, Mapping Rules, Agent Configuration Sections, and agents are omitted from the connection resolution. Instead, the Broker resolves the JDBC connection URL using only the SVT parameter. The database agent that is spawned is now able to handle both ODBC and JDBC connections Users may prevent most problems by removing JDBCAGENT= from their JDBC connection URLs. If problems persist, advanced users may resolve most problems by editing the Session Rules Book. New users are encouraged to contact OpenLink Product Support. Some 1.x and 3.x users create hybrid connections that pass an ODBC DSN in a Type 3 JDBC URL. For example: jdbc:openlink://localhost:5000/DSN=My Ingres Data Source/UID=ingres/PWD=ingres This connection format is no longer supported.
rdf:type: schema:Answer

Subject Item: n235:this
schema:name: What Do I Do If My Broker Shuts Down Intermittently? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Most intermittent shutdowns share a common origin. Users have copied a single license to one or more machines on a network. Users can not do this. Instead, users must obtain individual licenses for each Multi-Tier server component installation. If the problem persists, apply standard stability troubleshooting guidelines. 1. Patch databases and operating systems, as appropriate. 2. Contact database and o/s vendors to see if patches are associated with problems. 3. Insure Unix kernel tuning parameters match parameters specified by database and o/s documentation. 4. Insure your machine has adequate memory and processor resources. 5. Insure PortHigh is set in the [Protocol TCP] section of the Multi-Tier Session Rules Book. This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation. 6. Multi-Tier users perform the following test: -- login to the machine that contains the OpenLink server components. -- Run oplshut -s on the command-line. -- Compare the output to the Windows Task Manager or Unix ps -ef. -- Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps. 7. Multi-Tier users experiment with database agent reuse. Users should comparison test the following values: -- ifsame process, upto 5 -- ifsame application, upto 5 -- ifsame database, upto 5
rdf:type: schema:Answer

Subject Item: n98:this
schema:name: What Do I Do If My Drivers Occasionally Fail To Disconnect? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Both Multi-Tier and Single-Tier drivers users take the following action. Multi-Tier users see additional comments below. 1. Use your database native transaction monitor to see if OpenLink drivers are locked in pending transactions. OpenLink drivers cannot disconnect from a database while they are still engaged in transactions. 2. Insure that your application does not enforce manual commits. Use of manual commit may encourage the behavior described above. 3. Check the database native error logs for failures that may contribute to this problem. 4. Create a client-side ODBC trace. Examine the trace to insure that the application sends the proper sequence of SQLFree()s and SQLDisconnect()s to the driver. 5. Ensure OpenLink's Progress drivers connect to Progress databases in sockets mode. A Progress shared memory library bug causes failure to disconnect. 6. Contact OpenLink Product Support, if you use Progress 91C or 91D. OpenLink is working to resolve occurrences of lingering agents that are not associated with the shared memory bug. Multi-Tier users perform the following, additional test: 1. Recreate the problem. 2. Run oplshut -s on a command line. 3. Observe the number of OpenLink database agent processes. 4. Compare the output of oplshut -s with a Unix ps -ef or Windows Task Manager. 5. Upgrade if oplshut -s or the Windows Task Manager shows more agent processes.
rdf:type: schema:Answer

Subject Item: n80:this
schema:name: What Do I Do If My Drivers Produce Intermittent Core Dumps? -- Answer
schema:category: ODBC UDA JDBC
schema:text: No product should produce a core dump. Core dumps warrant the creation of a bug report. (Update existing bug reports, as appropriate.) Product Support Staff should attach the core file to the report. Moreover, staff must gather the following information from users: 1. Does the database and operating system contain all current patches? 2. Are the patches associated with stability problems? 3. Do Unix kernel tuning parameters match parameters specified by database and o/s documentation? 4. Does the machine have adequate memory and processor resources? 5. Was the database agent re-linked against the database? 6. Is PortHigh set in the [Protocol TCP] section of the Multi-Tier Session Rules Book? This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation. 7. What happens when users comparison test the following ReUse values: -- ifsame process, upto 5 -- ifsame application, upto 5 -- ifsame database, upto 5 8. Finally, Multi-Tier users should perform the following test: -- login to the machine that contains the OpenLink server components. -- Run oplshut -s on the command-line. -- Compare the output to the Windows Task Manager or Unix ps -ef. -- Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps.
rdf:type: schema:Answer

Subject Item: n156:this
schema:name: What Do I Do If My Drivers Produce Intermittent Protrace Files? -- Answer
schema:category: ODBC UDA JDBC
schema:text: No product should produce a Progress protrace file. Protrace files warrant the creation of a bug report. (Update existing bug reports, as appropriate.) Product Support Staff should attach the protrace file to the report. Moreover, staff must gather the following information from users and post it in the report: 1. Does the database and operating system contain all current patches? 2. Are the patches associated with stability problems? 3. Do Unix kernel tuning parameters match parameters specified by database and o/s documentation? 4. Does the machine have adequate memory and processor resources? 5. Was the database agent re-linked against the database? 6. Is PortHigh set in the [Protocol TCP] section of the Multi-Tier Session Rules Book? This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation. 7. What happens when users comparison test the following ReUse values: -- ifsame process, upto 5 -- ifsame application, upto 5 -- ifsame database, upto 5 8. Finally, Multi-Tier users should perform the following test: -- login to the machine that contains the OpenLink server components. -- Run oplshut -s on the commandline. -- Compare the output to the Windows Task Manager or Unix ps -ef. -- Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps.
rdf:type: schema:Answer

Subject Item: n441:this
schema:name: What Do I Do If My Existing License Key Does Not Work? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Some users cannot use existing licenses to register their software. Take the following action: 1. Ensure that all ftp transfers are conducted in binary transfer mode. OpenLink's licenses are binary executables. 2. Obtain Single-Tier client driver versions or Multi-Tier Broker versions. Use ASNPRINT.exe to ensure that the license and product share the same version. (Consultants must open 1.x and 3.x licenses with Notepad. ASNPRINT cannot read these files.) 3. Remove extraneous, OpenLink licenses from the machine. 4. Insure that the OpenLink's Windows and Unix licenses are passed by the PATH environment variable. Insure that Unix licenses are passed by the Unix OPL_LICENSE_DIR variable. 5. Remove references to old, OpenLink licenses from the registry, if the problem persists. (Search using license product code.) 6. Please reinstall and register the software, if the problem persists. Windows Single-Tier users should remove references to the Single-Tier driver-from their registries-before re-installation. Users may run regedit from a terminal prompt to access their registries.
rdf:type: schema:Answer

Subject Item: n443:this
schema:name: What Do I Do If My Existing License Key Is Expired? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users may obtain additional, temporary license keys from the OpenLink web site. Users proceed through the downloads matrix and stop, when they are presented with the product download links. Licenses are mailed to users, before they click the actual links to obtain the software.
rdf:type: schema:Answer

Subject Item: n445:this
schema:name: What Do I Do If My Multi-Tier DSN Fails To Connect? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Post the problem into an online support case -- http://support.openlinksw.com/support/online-support.vsp
rdf:type: schema:Answer

Subject Item: n447:this
schema:name: What Do I Do If My Multi-Tier DSN Fails To Disconnect? -- Answer
schema:category: ODBC UDA JDBC
schema:text: 1. Use your database native transaction monitor to see if OpenLink drivers are locked in pending transactions. OpenLink drivers cannot disconnect from a database while they are still engaged in transactions. 2. Insure that your application does not enforce manual commits. Use of manual commit may encourage the behavior described above. 3. Check the database native error logs for failures that may contribute to this problem. 4. Create a client-side ODBC trace. Examine the trace to insure that the application sends the proper sequence of SQLFree()s and SQLDisconnect()s to the driver. 5. Perform the following test: -- Recreate the problem; -- Run oplshut -s on a command line. -- Observe the number of OpenLink database agent processes. -- Compare the output of oplshut -s with a Unix ps -ef or Windows Task Manager. -- Upgrade if oplshut -s or the Windows Task Manager shows more agent processes. 6. Connect to Progress databases in sockets mode. A Progress shared memory library bug causes OpenLink's database agents to linger. 7. Contact OpenLink Product Support, if you use Progress 91C or 91D. OpenLink is working to resolve occurrences of lingering agents that are not associated with the shared memory bug.
rdf:type: schema:Answer

Subject Item: n433:this
schema:name: What Do I Do If My ODBC Connectivity Suddenly Stopps Working Altogether? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Sudden loss of functionality is attributed to two factors: 1. License expiration. 2. Installation of database patches, operating system upgrades, or anti-virus software. Consequently, users take the following action: 1. Search their entire machines for expired, temporary licenses. 2. Delete temporary licenses. 3. Send permanent keys to OpenLink Product Support for review. 4. Ascertain whether or not patches, upgrades, or anti-virus software has been applied to the affected machine. OpenLink Product Support may not have immediate answers for problems caused by patches, upgrades, or anti-virus software. Specialized testing may be needed.
rdf:type: schema:Answer

Subject Item: n435:this
schema:name: What Do I Do If My Single-Tier DSN Fails To Connect? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Post the problem into an online support case -- http://support.openlinksw.com/support/online-support.vsp
rdf:type: schema:Answer

Subject Item: n437:this
schema:name: What Do I Do If My Single-Tier DSN Fails To Disconnect? -- Answer
schema:category: ODBC UDA JDBC
schema:text: 1. Use your database native transaction monitor to see if OpenLink drivers are locked in pending transactions. OpenLink drivers cannot disconnect from a database while they are still engaged in transactions. 2. Insure that your application does not enforce manual commits. Use of manual commit may encourage the behavior described above. 3. Check the database native error logs for failures that may contribute to this problem. 4. Create a client-side ODBC trace. Examine the trace to insure that the application sends the proper sequence of SQLFree()s and SQLDisconnect()s to the driver. 5. Ensure OpenLink's Progress Single-Tier drivers establish sockets-based connections to Progress. A Progress shared memory library bug causes failures to disconnect. 6. Contact OpenLink Product Support, if you use Progress 91C or 91D. OpenLink is working to resolve occurrences of lingering agents that are not associated with the shared memory bug.
rdf:type: schema:Answer

Subject Item: n439:this
schema:name: What Is The Compatibility with A Newer DB? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users who possess newer builds of popular databases. For example, OpenLink may provide software for Sybase 11 systems. However, users have Sybase 12. In most instances, consultants should encourage users to download the closest match to their database version. OpenLink's software is upwards compatible and should function with the newer product. Be advised - Progress databases and OpenLink's Progress software are compatible, as long as both products share the same major number. For instance, OpenLink's Progress 8 database agents will connect to most Progress 8 databases. However Progress 7 database agents will not connect to Progress 8 databases.
rdf:type: schema:Answer

Subject Item: n458:this
schema:name: What is the Compatibility With Newer OS? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users who possess newer builds of popular operating systems. For example, OpenLink may provide software for Solaris 2.8 systems. However, users have Solaris 2.9. In this instance, consultants should encourage users to download the closest match to their operating system version. OpenLink's software is upwards compatible and should function on the newer platform.
rdf:type: schema:Answer

Subject Item: n449:this
schema:name: What Licenses are provided? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink provided non-expiring, evaluation licenses with 1.x and 3.x Multi-Tier software. Inform 1.x and 3.x users that OpenLink's latest components use a new licensing model. Then, send these users to Account Management for additional information.
rdf:type: schema:Answer

Subject Item: n27:this
schema:name: What Suitable Software Should Be Used? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Get a uname -a from all machines on which software would be installed. Get the name of the database to which the user wants to connect. See if OpenLink has a matching machine and database installation or database installation media. If OpenLink has the requisite materials, OpenLink can build an agent. If OpenLink does not have the operating system or database, the user may need to consider a custom build. ALERT Users may use OpenLink's Generic ODBC drivers to connect to databases, for which no database agents exist. These users simply need an OpenLink-supported operating system, which contains 3rd-party drivers that connect to the database. Other users may benefit from Single-Tier or application server configuration Multi-Tier connections, when they have a common database on an uncommon operating system. This latter configuration requires the installation of the database native client on an OpenLink-supported O/S.
rdf:type: schema:Answer

Subject Item: n237:this
schema:name: Is there Older DB Compatibility Supported? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Consultants will encounter users who possess older builds of popular databases. For example, OpenLink may provide software for Informix 7.3 systems. However, users have Informix 5. In this instance, consultants should not encourage users to download software. OpenLink's software is not backwards compatible and may not function with the older platform. Be advised - Progress databases and OpenLink's Progress software are compatible, as long as both products share the same major number. For instance, OpenLink's Progress 8 database agents will connect to most Progress 8 databases. However Progress 8 database agents will not connect to Progress 7 databases.
rdf:type: schema:Answer

Subject Item: n450:this
schema:name: Is Older OS Compatibility Supported? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Consultants will encounter users who possess older builds of popular operating systems. For example, OpenLink may provide software for Solaris 2.5 systems. However, users have Solaris 2.4. In this instance, consultants should not encourage users to download software. OpenLink's software is not backwards compatible and may not function on the older platform.
rdf:type: schema:Answer

Subject Item: n451:this
schema:name: OpenLink Data Access Drivers Vs iODBC? -- Answer
schema:category: ODBC UDA JDBC
schema:text: iODBC.org offers free installers and instructions for the open-source iODBC Driver Manager and iODBC SDK. The installers are packaged with source code, header files, make files, and other resources of interest to the development community. These products match OpenLink Software's quality and reliability; however, they, and the iODBC.org web site, cater to highly technical individuals who know how to build the iODBC Driver Manager into their own custom solutions. OpenLink Software provides commercial quality Data Access Drivers, the Virtuoso Universal Server, diagnostic utilities, and related SDKs. In addition, the iODBC Driver Manager is bundled into the OpenLink SDKs and installers for Data Access Drivers and Virtuoso. This software is intended to service businesses and other entities which need a complete, reliable, out-of-the-box solution. OpenLink provides value added components in the OpenLink iODBC variant of the iODBC SDK. This value takes the form of ready-to-run iODBC ports for all supported platforms, and in the case of Mac OS X this currently includes an AQUA and Frameworks based ODBC Administrator.
rdf:type: schema:Answer

Subject Item: n454:this
schema:name: What Do I Do When The Installation Process Hangs Without An Error? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Take the following action, if a hang occurs: 1. Obtain the name of the installation file. Obtain the name and version of the operating system. (Use uname -a on Unix.) Compare the two resources to determine if the software and operating system are compatible. 2. Ask about operating system patches. Patches can interfere with installs on otherwise supported operating systems. 3. Check file and directory permissions. 4. Use the Windows explorer or Unix df -k to check disk space. 5. Insure unnecessary processes are shutdown. 6. Determine how far the installation has progressed. Some Windows installers hang during registry update. However, the actual installation is complete and functional. 7. Attempt to recreate the problem in-house. Consultants should report persistent installation problems to the Tech Support Manager. These problems may indicate critical install bugs.
rdf:type: schema:Answer

Subject Item: n456:this
schema:name: What Do I Do When The Installation Process Produces Errors? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Use the following guidelines to eradicate installation problems: 1. Obtain the name of the installation file. Obtain the name and version of the operating system. (Use uname -a on Unix.) Compare the two resources to determine if the software and operating system are compatible. 2. Ask about operating system patches. Patches can interfere with installs on otherwise supported operating systems. 3. Check file and directory permissions. 4. Use the Windows explorer or Unix df -k to check disk space. 5. Insure unnecessary processes are shutdown. 6. Determine how far the installation has progressed. Some Windows installers hang during registry update. However, the actual installation is complete and functional. 7. Search OPIE for a description of the actual error. 8. Attempt to recreate the problem in-house. Consultants should report persistent installation problems to the Tech Support Manager. These problems may indicate critical install bugs.
rdf:type: schema:Answer

Subject Item: n413:this
schema:name: What Component Naming Conventions is Used? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's client drivers are library files. Consequently, Windows Multi-Tier drivers begin with olod (OpenLink ODBC Driver) and end with a .dll extension. Unix Multi-Tier drivers are named oplodbc (OpenLink ODBC) and end with a .la, .sl, or .so extension. OpenLink's Single-Tier drivers have a variety of names that are too numerous to list. Windows drivers continue to end with .dll, and Unix drivers continue to end with .la, .sl, and .so. However, the similarities end there. The actual Windows Single-Tier driver name begin with `ntl' (WinNT Lite) and end with a series of numbers and letters that denote the driver version and intended database. The actual Unix Single-Tier driver name begins with some combination of letters that represents the intended database, and it ends with _mt_lt (Multi-Threaded Lite) , _mt_lu (Multi-Threaded Lite Unicode), _st_lt (Single-Threaded Lite), _st_lu(Single-Threaded Lite Unicode). OpenLink's Unix-based iODBC Driver Manager is named libiodbc and ends with a .la, .sl, or .so extension. OpenLink's Multi-Tier Request Broker is named oplrqb. OpenLink's Multi-Tier Database Agents begin with a three or four character name that designate the intended database, and they end with a .sv (Single-Threaded version) or .mv (Multi-Threaded version) extension.
rdf:type: schema:Answer

Subject Item: n414:this
schema:name: What to do in case of Installation Failure? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's installers seldom fail. Furthermore, it is easy to troubleshoot installer issues, when they occur. Use the following guidelines to assist your users: 1.Obtain the name of the user's installation files. 2.Obtain the user's operating system and version. UNIX users should provide the output of uname -a. Linux users should provide the output of uname -a and rpm -qa | grep lib. 3.Insure that the installation files are compatible with the user's operating system. Most installers are compatible with the intended o/s and updated versions of the o/s. For instance, Solaris 2.7 software should run on Solaris 2.7 and 2.8. It may not run on 2.5. 4.Tell users to ftp installation shell scripts in ASCII. .taz, .dmg, and .zip files require BINARY transfer. If the problem persists, invite UNIX users to use tar -xvf file name to decompress their .taz files. Use of tar should create a functional installation. However, environment variables may remain to be set in the product configuration files: i.e., openlink.sh, openlink.csh, openlink.ini, oplrqb.ini. Ask Windows users to check their OpenLink installation directories and registry. Occasionally, Windows installers report registry problems. However, these same installers create functional installations with properly configured variables. Consequently, users should attempt to start their brokers and test their DSNs. Finally, some Windows users may need to make substantial edits to their registries after an installer failure. Address this course of action with expert users. Do not encourage novice users to pursue this task.
rdf:type: schema:Answer

Subject Item: n416:this
schema:name: What are the UDA Licensing Model based on? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Both Single-Tier and Multi-Tier license models are based on concurrent "users" and concurrent "connections."
rdf:type: schema:Answer

Subject Item: n400:this
schema:name: What to Do if Can Not Download? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Use the following guidelines to troubleshoot downloads problems: 1. Re-attempt the download. OpenLink's servers occasionally fail due to temporary overload. 2. Right-click product links and use "Save As" to download. 3. Test with an alternative Web browser. 4. Use an FTP client to download the software. 5. Determine if evaluator firewalls prohibit downloads. 6. Login as the user and test the download process in-house. Finally, consultants must report persistent and/or reproducible downloads problems to the Tech Support Manager for immediate attention. Moreover, Consultants should email components to evaluators or provide alternative ftp access to components. Ask your Tech Support Manager for additional information.
rdf:type: schema:Answer

Subject Item: n404:this
schema:name: What Are The Differences Among User System And File DSNs? -- Answer
schema:category: ODBC UDA JDBC
schema:text: User DSN - User DSNs are available for use only to the user who created it. User DSN connection parameters are stored in the HKEY_CURRENT_USER/Software/ODBC/ODBC.INI section of the registry. System DSN - System DSNs are available for use to any user who logs onto the local system. System DSN connection parameters are stored in the HKEY_LOCAL_MACHINE/Software/ODBC/ODBC.INI section of the registry. File DSN - File DSNs comprise a set of DSN connection parameters that are saved to a text file with a .DSN extension. File DSNs typically appear in C:/Program Files/Common Files/ODBC/Data Sources. OpenLink recommends use of System DSNs whenever possible.
rdf:type: schema:Answer

Subject Item: n406:this
schema:name: What Are Your Prerequisites And System Requirements? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users must install OpenLink's Single-Tier drivers on a supported operating system. Users must install DB2, Informix, Ingres, and Progress drivers on a machine, which contains a functional copy of their database native client. Users must install "ODBC Lite" drivers on a system that contains a 3rd party data source, which connects to the user's database. Users must install OpenLink's Multi-Tier client and server components on one or more supported operating systems. DB2, Informix, Ingres, and Progress users must install the server components on a system, which contains the user's database or database native client. Users must install "Generic ODBC" drivers on a system that contains a 3rd party data source, which connects to the user's database. Users must install Virtuoso Universal Server client and server components on one or more supported operating systems. Users must install the iODBC Driver Manager, OpenLink ODBC Bench, and ODBC Scan on a supported client operating system. Some users may require a compiler and library linker, if they intend to develop ODBC compliant applications or re-link OpenLink's agents or Driver Manager.
rdf:type: schema:Answer

Subject Item: n408:this
schema:name: What Can I Do To Assist Users Who Have Lost Their Licenses? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users may repeat the downloads process--up to three times--to obtain new, temporary licenses. However, this option is inconvenient for many persons. Consequently, consultants may generate licenses with the license generators. Alternatively, consultants may ask the Account Manager to generate a temporary key. Users must contact their OpenLink Account Managers to obtain a new, permanent license.
rdf:type: schema:Answer

Subject Item: n411:this
schema:name: What Configuration Files Are Used By Multi-Tier Drivers? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Multi-Tier drivers comprise a client component and a server component. The following files are used by OpenLink's client drivers: openlink.sh and openlink.csh - These files appear in the root of Unix-based, Multi-Tier installations. They contain ODBC-related environment variables. odbc.ini - This file appears in the /bin sub-directory of Unix-based, Multi-Tier installations. It contains Data Source Name connection attributes. Occasionally, it may contain client communication settings and ODBC tracing parameters. odbcinst.ini - This file appears in the /bin sub-directory of Unix-based, Multi-Tier installations. It contains path and setup information for the Single-Tier driver. The following files are used by OpenLink's server components: openlink.sh and openlink.csh - These files appear in the root of Unix-based, Multi-Tier installations. They contain ODBC-related environment variables. oplrqb.ini - This file appears in the /bin sub-directory of all, Multi-Tier server components installations. This file contains database-specific environment variables. It also contains parameters that affect security, port usage, agent behavior, and client/server communications. www_sv.ini - This file appears in the /bin/w3config sub-directory of all Multi-Tier server components installations. This file contains the Web-based Administrative Assistants username, encrypted password, and listening port. Windows drivers do not contain the Multi-Tier client files. Client environment variables appear on the Environment or Advanced tab of the System utility. The odbc.ini and odbcinst.ini files are replaced by the HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI and HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI sections in the registry. Windows server installations retain the oplrqb.ini and www_sv.ini files.
rdf:type: schema:Answer

Subject Item: n426:this
schema:name: What Configuration Files Are Used By Single-Tier Drivers? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Single-Tier drivers rely on the following configuration files: openlink.sh and openlink.csh - These files appear in the root of Unix-based, Single-Tier installations. They contain ODBC-related environment variables. openlink.ini - This file appears in the /bin sub-directory of Unix-based, Single-Tier installations. It contains database-specific environment variables. odbc.ini - This file appears in the /bin sub-directory of Unix-based, Single-Tier installations. It contains Data Source Name connection attributes. Occasionally, it may contain ODBC tracing parameters. odbcinst.ini - This file appears in the /bin sub-directory of Unix-based, Single-Tier installations. It contains path and setup information for the Single-Tier driver. Windows drivers do not contain these files. Environment variables appear on the Environment or Advanced tab of the System utility. The odbc.ini and odbcinst.ini files are replaced by the HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI and HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI sections in the registry.
rdf:type: schema:Answer

Subject Item: n64:this
schema:name: How Do I Assist A User Who Does Not Know What Values To Pass To His Or Her Variables? -- Answer
schema:category: ODBC UDA JDBC
schema:text: All database specific environment variables should appear in the database user's .profile (unix) or other, standard configuration file. Users may open these files to ascertain which values need to appear in their Single-Tier openlink.ini files and their Multi-Tier oplrqb.ini files. In fact, users should execute the database user's .profile before installing Single-Tier drivers or Multi-Tier server components. The installers will detect the variables and write them into the appropriate location. The standardized, ODBC and JDBC variables pass the following values: -- CLASSPATH A JAVA client variable that passes the full path to an OpenLink JDBC .jar file. -- LD_LIBRARY_PATH A generic library path variable that appends the full path to OpenLink's lib sub-directory. -- LIBPATH An AIX library path variable that appends the full path to OpenLink's lib sub-directory. -- ODBCINI Passes the full path to ~/openlink/bin/odbc.ini. -- ODBCINSTINI Passes the full path to ~/openlink/bin/odbcinst.ini. -- OPENLINKINI This Single-Tier variable passes the full path to ~/openlink/bin/openlink.ini. -- PATH Appends the full path to OpenLink's bin sub-directory. -- SHLIB_PATH An HP/UX library path variable that appends the full path to OpenLink's lib sub-directory.
rdf:type: schema:Answer

Subject Item: n429:this
schema:name: Trouble-shooting registering a product with a temporary or commercial license? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Use the following guidelines to troubleshoot licensing problems: 1. Ensure that the Windows Single-Tier license is placed in your Lite32 sub-directories. 2. If on Unix, ensure that the Single-Tier license is placed in the b/in sub-directory of the OpenLink installation. Alternatively, users may pass the full path to licenses to OPL_LICENSE_DIR. This variable may be set using the command line, openlink.sh, openlink.csh, or your .profile. 3. Multi-Tier users ensure the licence is placed in the bin/ sub-directory of the server component installation. 4. Ensure that ftp transfers are conducted in binary. OpenLink's .lic licenses are binary-format files. 5. Windows Single-Tier users should uninstall their software, remove all references to Single-Tier software from the registry, and reinstall, if licensing problems persist. Occasionally, Windows Single-Tier users experience registry corruption, which necessitates the registry wipe and reinstall. OpenLink consultants have other utilities that may help debugging if you suspect a license-file is corrupt. The license version must match the Single-Tier driver version or the Multi-Tier request broker and agent version. Operating System Licenses must be generated for the appropriate operating system. CPU's The number of CPUs cited in the license must match the number of CPUs present in the machine. Access Mechanism Licenses may restrict ODBC or JDBC data access. Other licenses permit both ODBC and JDBC access. Database Licenses must list each of the databases to which the user intends to connect. Applications Certain licenses are limited for use with one application. OpenLink's 1.x and 3.x ship with a license text file. Consultants may open this license with Notepad or a similar text editor. The file should contain the same parameters listed above.
rdf:type: schema:Answer

Subject Item: n431:this
schema:name: What Do I Do If My JDBC Connections Fail? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Post the problem into an online support case -- http://support.openlinksw.com/support/online-support.vsp
rdf:type: schema:Answer

Subject Item: n420:this
schema:name: What Do I Do With The DSNs That I Create? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Data Source Names enable applications to establish ODBC connections to database servers. Once you create your Data Source Name, you must ascertain how your application enables you to display, select, and connect to Data Source Names.
rdf:type: schema:Answer

Subject Item: n422:this
schema:name: What Do I Do With The License File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Windows Single-Tier users must copy the file to their Lite32 directories. Mac and Unix Single-Tier users must copy the files to the /bin sub-directory of their OpenLink installations. No additional action is needed. All Multi-Tier users must copy their licenses to the /bin sub-directory of the OpenLink installation. Then, Multi-Tier users must restart their Request Broker services. ALERT OpenLink's 1.x and 3.x licensing mechanism differs substantially from the current procedure. Single-Tier legacy license holders must transfer their license file to the /bin sub-directory of their OpenLink installation. Then, they must run the register.exe program. Multi-Tier legacy license holders must perform the following actions: Shutdown the OpenLink Request Broker; Transfer the license file to the /bin sub-directory of their server installation; Rename license name.ini to register.ini; Run register.ini; Restart the Request Broker Service.
rdf:type: schema:Answer

Subject Item: n9:this
schema:name: What Do I Need To Establish A Multi-Tier JDBC Connection? -- Answer
schema:category: ODBC UDA JDBC
schema:text: You need to install one of Sun's Java Runtime Environments (JRE) on the machine that contains your client application. You need to install one of OpenLink's .jar files on the machine that contains your JAVA client application. (The JAVA version of the .jar should match the JAVA version of the JRE.) You need to install OpenLink's server components on a machine that contains one of the following entities: The actual database; A database native client that connects to the database.
rdf:type: schema:Answer

Subject Item: n424:this
schema:name: What Do I Need To Establish A Single-Tier JDBC Connection? -- Answer
schema:category: ODBC UDA JDBC
schema:text: You need to install one of Sun's Java Runtime Environments (JRE) on the machine that contains your client application. You need to install one of OpenLink's .jar files on the machine that contains your JAVA client application. (The JAVA version of the .jar should match the JAVA version of the JRE.) You need to insure that a functional database native client is installed on the machine that contains the application and the Single-Tier .jar.
rdf:type: schema:Answer

Subject Item: n383:this
schema:name: What Do I Need To Test The JDBC-ODBC Bridge? -- Answer
schema:category: ODBC UDA JDBC
schema:text: You need a functional ODBC Data Source Name (DSN). This DSN may use OpenLink or non-OpenLink drivers. You need to install Sun's Java Runtime Environment (JRE) on the same machine as the ODBC Data Source. You need to install OpenLink's Single-Tier JDBC driver on the machine that contains the ODBC Data Source and the JRE. You need to run your JAVA application on the machine that contains OpenLink's Single-Tier JDBC driver.
rdf:type: schema:Answer

Subject Item: n385:this
schema:name: What Do I Need To Test The ODBC-JDBC Bridge? -- Answer
schema:category: ODBC UDA JDBC
schema:text: You need JDBC drivers that connect to your target data source. You need to install your Single-Tier client driver or Multi-Tier server components (Request Broker & JDBC Bridge Agent) on the machine, which contains the JDBC connection URL. Your JDBC client application must reside on the machine that contains the Single-Tier client driver or the Multi-Tier client components.
rdf:type: schema:Answer

Subject Item: n189:this
schema:name: What Do I Need To Test The ODBC-ODBC Bridge? -- Answer
schema:category: ODBC UDA JDBC
schema:text: You need 3rd party ODBC drivers that connect to your database; You need to install your Single-Tier driver or Multi-Tier driver server components (Request Broker & Generic ODBC Agent) on the machine, which contains the 3rd party ODBC drivers; Your client application must reside on the same machine as the Single-Tier driver or the Multi-Tier driver client components.
rdf:type: schema:Answer

Subject Item: n389:this
schema:name: What Do I Pass In A Multi-Tier JDBC Connection URL? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Multi-Tier JDBC connection URLs take the following form: jdbc:openlink://<Hostname>:[portnumber] [/UID] [/PWD] [/READONLY] [/SVT] [/APPLICATION] [/FBS|FETCHBUFFERSIZE] [/ENCRYPTED] [/CHARSET] [/UNICODE] [/DLF] [/DATABASE] [/OPTIONS] [/DRIVER] . Here is a description of each of the parameters: Hostname - Network Alias or IP address of machine that runs an OpenLink Request Broker instance; Port Number - TCP port on which the Request Broker listens; /UID - Database username; /PWD - Database password; /READONLY - Read-write or read-only session mode; /SVT - A valid domain alias from the [Domain Aliases] section of the OpenLink server component's oplrqb.ini file. Default domain aliases represent the type of database agent to which the application intends to connect, e.g., DB2, Informix 2000, Oracle 8.1.x. Custom aliases may take any form; /APPLICATION - The Application name. Enables connectivity when restrictive server side rules screen by application name; /FBS - (also FETCHBUFFERSIZE) The Fetch Buffer Size. The Fetch Buffer Size is an integer that represents the number of rows to return during one fetch operation; /ENCRYPTED - Sets the Encrypted flag for outgoing packets. /ENCRYPTED may pass '1', '0', 'Y', 'N', 'y', or 'n.' (This feature is disabled by default.); /CHARSET - Specifies the charset of remote databases. The default value is read from System.getProperty("file.encoding"); /UNICODE - Instantiates unicode. The unicode connection isn't used by default. The value may be '1', '0', 'Y', 'N', 'y', 'n'(This feature is disabled by default.); /DLF - Pushes large, binary objects to the end of the result-set. Smaller data types are retrieved first. This enhances performance. /DLF may be set to '1', '0', 'Y', 'N', 'y', or 'n.' (This feature is disabled by default.); /DATABASE - Actual database name within a particular database environment; /OPTIONS - Optional parameter that passes specialized database native client connection parameters. Used by users who connect to Progress databases in sockets mode. Also used by users who have 3-Tier or application server architectures; /DRIVER - The Driver name contained in curly brackets ({}). Used for DSN-Less connections to remote ODBC Drivers. Here are some sample JDBC connection URLs: jdbc:openlink://localhost:5000/SVT=Ingres II/DATABASE=iidbdb/UID=ingres/PWD=ingres; jdbc:openlink://192.128.13.119:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger; jdbc:openlink://saturn:5000/SVT=Progress 91D/DATABASE=isports/OPTIONS=-S isports -N tcp -H saturn; jdbc:openlink://localhost:5000/SVT=SQLServer 2000/DATABASE=Northwind/UID=sa/OPTIONS= -S SATURN;
rdf:type: schema:Answer

Subject Item: n30:this
schema:name: What Do I Pass In A Single-Tier JDBC Connection URL? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Single-Tier JDBC connection URLs take the following format: jdbc:openlink://ODBC[/DSN][/UID][/PWD][/READONLY] . Here is a description of each of the URL parameters: /DSN - Local ODBC Data Source Name; /UID - Database Username; /PWD - Database Password; /READONLY - Read-write or read-only session mode. Here is a sample Single-Tier JDBC connection URL: jdbc:openlink://ODBC/DSN=Local Oracle ODBC Data Source/UID=scott/PWD=tiger
rdf:type: schema:Answer

Subject Item: n378:this
schema:name: What Do I Tell Users Who Want New Temporary Licenses? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users may repeat the downloads process--up to three times--to obtain new, temporary licenses. However, this option is inconvenient for many persons. Consequently, consultants may generate licenses with the license generators. Alternatively, consultants may ask the Account Manager to generate a temporary key.
rdf:type: schema:Answer

Subject Item: n380:this
schema:name: What Do Users Need To Do To Configure Their Multi-Tier Drivers? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Unix users need to insure that openlink.sh (Bourne/Bash) or openlink.csh (C) is executed in the appropriate shell. These shell scripts set environment variables that pertain to ODBC. They appear in both client and server components installations. Unix users need to run set or env to insure that the environment variables (ODBCINI, ODBCINSTINI, etc.) are actually set. All users need to insure that the appropriate [Environment] section of the ~/openlink/bin/oplrqb.ini file contains the correct environment variables. All users should uncomment and set the PortHigh parameter that appears in the [Protocol TCP] section of the ~/openlink/bin/oplrqb.ini file. PortHigh should equal PortLow + the number of concurrent connections alloted by the license + a few extra ports. All users need to start the Request Broker. The Request Broker is the oplrqb executable that appears in the /bin sub-directory of Multi-Tier server components installation.
rdf:type: schema:Answer

Subject Item: n381:this
schema:name: What Do Users Need To Do To Configure Their Single-Tier Drivers? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Unix users need to insure that openlink.sh (Bourne/Bash) or openlink.csh (C) is executed in the appropriate shell. These shell scripts set environment variables that pertain to ODBC. Unix users need to run set or env to insure that the environment variables (ODBCINI, ODBCINSTINI, etc.) are actually set. Unix users need to insure that the appropriate [Environment] section of the ~/openlink/bin/openlink.ini file contains the correct environment variables. Windows users need to insure that their System and User PATH variables contain the OpenLink driver .dlls and database native client .dlls. (Database native client .dll's are not required for MySQL, PostgreSQL, SQLServer, or Sybase.) Windows users may need to set other System and User PATH variables depending on the database. For example, Progress users need to set PROGRESSINI and PROMSGS.
rdf:type: schema:Answer

Subject Item: n397:this
schema:name: What Do Your Drivers Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Data Access drivers enable users to establish ODBC, ADO.Net, OLEDB and JDBC connections between applications and databases. Applications use these connections to execute SQL queries against the data contained within the databases. Typical SQL queries select, insert, update, or delete data. Other queries add, modify, or delete the structures that contain the data.
rdf:type: schema:Answer

Subject Item: n399:this
schema:name: What Does Count Stored Procedure Parameters In SQL Procedures Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This applies to the Oracle data-source. "Count Stored Procedure Parameters" affects the output from SQLProcedures when "Custom Catalog Views" is enabled. When "Custom Catalog Views" is off, the NUM_INPUT_PARAMETERS, NUM_OUTPUT_PARAMETERS and NUM_RESULT_SETS columns of the SQLProcedures result set all contain -1. When "Custom Catalog Views" in on, "Count Stored Procedure Parameters" is enabled and an internal view, OPENLINK$SQL_PROCEDURES is used; when this is disabled, the internal view, OPENLINK$SQL_PROCS_NOCOUNT is used instead. The result set returned by SQL_PROCEDURES includes the number of input and output parameters for each procedure. The number of result sets is always -1 like the case when "Custom Catalog Views" is off, SQL_PROCS_NOCOUNT returns -1 for the NUM_INPUT_PARAMETERS, NUM_OUTPUT_PARAMETERS and NUM_RESULT_SETS columns.
rdf:type: schema:Answer

Subject Item: n44:this
schema:name: What Does Custom Catalog Views Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: "Custom Catalog Views" controls whether custom OpenLink views are used to return meta-data for some ODBC catalog functions. These custom views provide more meta-data than is normally available. To create and use them, the script odbccat[8|9].sql must be run beforehand. The ODBC catalog functions affected are: SQLForeignKeys, SQLPrimaryKeys, SQLProcedureColumns, SQLProcedures, SQLSpecialColumns
rdf:type: schema:Answer

Subject Item: n97:this
schema:name: What Does Deadlock Timeout Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: If a deadlock occurs within Progress, due to a record been accessed simultaneously by the client, this is the default time in seconds, the database agent will wait for the Progesss server to release its lock before an error will be reported back to the client. The default value is 60 seconds.
rdf:type: schema:Answer

Subject Item: n391:this
schema:name: What Does Default User ID Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option allows a default user to be specified when a connection is attempted to a remote database.
rdf:type: schema:Answer

Subject Item: n357:this
schema:name: What Does Disable Auto Commit Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This data-source option is used to control transactions via the OpenLink driver. This option changes the default commit behavior of the OpenLink Driver. By default, this mode is set to AutoCommit.
rdf:type: schema:Answer

Subject Item: n394:this
schema:name: What Does Disable Interactive Login Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: By enabling this option, the application will not prompt for a username/password when connecting to the database. The assumption here is you do not require a password to connect. This will apply to the following scenarios: The passwords are hard-coded in the server (applies to the Multi-Tier drivers); The database server does not require a password to connect; The application will pass the userid/password using its own method. The only exception where enabling this option will still prompt an interactive login is when creating a new data-source.
rdf:type: schema:Answer

Subject Item: n349:this
schema:name: What Does Disable RowsetSizeLimit Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The OpenLink Scrollable Cursor Library (SCR) by default enforces a maximum cursor row-set size of 100 on any query. This is because the larger the row-set size the more memory the SCR will require to manage this, which could begin to unnecessarily impede performance as the system resources run low. Hence the need for this restriction as general no one should ever have the need to manipulate more data than can be viewed on their screen (ie a row-set). Thus if the an application makes SQLStmtOption(SQL_ROWSET_SIZE, value) where the value is greater than 100 our driver will return SQL_SUCCESS_WITH_INFO at which point a well written application which check SQLError and receive an "Option value changed" message at which point it should call SQLGetStmtOption(SQL_ROWSET_SIZE, &value) to see what it has actually been set to, which would be 100. Some applications, for example Power Builder, ignored the SQL_SUCCESS_WITH_INFO response and assumed the value they requested resulting in errors when they attempted to scroll paste the end of the row-set (100 rows) our driver returned. To enable such applications to work with our driver we thus introduced the Disable Rowset Size Limit option which if set removes our imposed restriction and trusts the application to set the row-set size to a reasonable value.
rdf:type: schema:Answer

Subject Item: n308:this
schema:name: What Does Dynamic Cursor Sensitivity Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set to High, the Cursor Library calculates checksums for each row in the current row-set and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the row-set. When dynamic cursor sensitivity is set to Low, (default) performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. as the application does not need to detect the row status, SQL_ROW_UPDATED.
rdf:type: schema:Answer

Subject Item: n313:this
schema:name: What Does Enable Logging Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option turns on ODBC call tracing and enables OpenLink Driver ODBC logging to a file. If no directory is specified, the logfile will be created in the default OpenLink installation directory.
rdf:type: schema:Answer

Subject Item: n319:this
schema:name: What Does Enable Microsoft Jet Engine Options Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The Jet Engine is synonymous with Microsoft tools such as Access, Excel (http://www.microsoft.com/office) or when developing with DAO (Data Access Objects). If your application falls into any of those categories, it is recommended that +jetfix is selected. This option will map Microsoft Jet data types to compatible SQL Types ready for ODBC and data access. For example, the MSAccess Data Type `Money` will be converted to Float or Decimal. This is because not all databases support this type.
rdf:type: schema:Answer

Subject Item: n24:this
schema:name: What Does Expression Precision Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option is a Progress SQL-89/4GL configuration. It provides an accurate value for Precision and Scale when the result is a Numeric Expression. For instance, select 10 + 12 in Progress will return the result as a numeric expression. In Progress SQL89/4GL, the Precision and Scale are returned as 0 as default. This means Applications, for example MSAccess, might interpret the results as a string and label it a char column. With these variables, the user has complete control over the Precision and Scale used for expressions. By default, the OpenLink drivers will return a default of 15,2 for Precision and scale respectively.
rdf:type: schema:Answer

Subject Item: n287:this
schema:name: What Does Expression Scale Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option is a Progress SQL-89/4GL configuration. It provides an accurate value for Precision and Scale when the result is a Numeric Expression. For instance, select 10 + 12 in Progress will return the result as a numeric expression. In Progress SQL89/4GL, the Precision and Scale are returned as 0 as default. This means Applications, for example MSAccess, might interpret the results as a string and label it a char column. With these variables, the user has complete control over the Precision and Scale used for expressions. By default, the OpenLink drivers will return a default of 15,2 for Precision and scale respectively.
rdf:type: schema:Answer

Subject Item: n293:this
schema:name: What Does Field Size Maximum Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option is similar to the Expression Precision/Scale option. The Progress 4GL database engine allows the storage of character strings which are longer than the declared SQL width. For instance, creating a table with a char column will default to 8 but Progress will allow you to specify more than 8 characters. By specifying a Max value, with this option, the ODBC driver internally will override the value provided by the ODBC call SQLDescribecol and use the value provided.
rdf:type: schema:Answer

Subject Item: n297:this
schema:name: What Does Field Size Minimum Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option is similar to the Expression Precision/Scale option and is related to Field Size Maximum. As the Progress 4GL database engine allows the storage of character strings which are longer than the declared SQL width. For instance, creating a table with a char column will default to 8 but Progress will allow you to specify more than 8 characters. When the values are returned without this option, only the first 8 characters will be returned. By specifying a Min value, the ODBC driver will override the value provided by the ODBC call SQLDescribecol and will use the value provided instead. This is the more important of the two Field Size options and should always be specified first. For example, if your column as defined as char(8) but you have at least 255 characters, please specify a Min Field size of 255.
rdf:type: schema:Answer

Subject Item: n303:this
schema:name: What Does Force Online Database Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This applies to the Informix 7 Database which has support for both Online and Standard Engine. By specifying this value, the Informix type you intend to connect to will be set. (0) SE or (1) ONLINE. If set, the database will always appear as online.
rdf:type: schema:Answer

Subject Item: n352:this
schema:name: What Does Hide Login Dialog Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: By enabling this option, the application will not prompt for a username/password when connecting to the database. The assumption here is you do not require a password to connect. This will apply to the following scenarios: The passwords are hard-coded in the server (applies to the Multi-Tier drivers); The database server does not require a password to connect; The application will pass the userid/password using its own method. The only exception where enabling this option will still prompt an interactive login is when creating a new data-source.
rdf:type: schema:Answer

Subject Item: n358:this
schema:name: What Does Initial SQL Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: On occasions, there is a requirement to execute certain instructions against the database when a connect is done against the database. For example, Transactional statements to set Isolation levels. By specifying this option and providing a SQL script with DB instructions, every database connection run will execute the contents of the sql script against the Database. This option is set by specifying a Path & Filename. The default directory is the OpenLink Installation folder.
rdf:type: schema:Answer

Subject Item: n362:this
schema:name: What Does Log File Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: There are two methods of tracing ODBC calls. Tracing can be set either by the Driver Manager or by the ODBC Driver. By specifying a Path & Filename in the Logfile option, the ODBC trace generated will be done by ODBC driver. This will inform the support team of what information the Driver is sending to the database. Please note you might also be required to provide a Driver Manager trace where applicable.
rdf:type: schema:Answer

Subject Item: n367:this
schema:name: What Does Max Long Data Length Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: "Max Long Data Length" controls the maximum length of SQL_LONGVARCHAR and SQL_LONGVARBINARY data returned when deferred fetching of long data is off. When off, this setting limits the amount of memory which must be allocated for a dataset cell to hold the retrieved value - the value is truncated to this length. The default limit is 60000 bytes. When deferred fetching is enabled, the complete SQL_LONGVARCHAR or SQL_LONGVARBINARY value can be fetched. Note that any value set via SQLSetStmtAttr(SQL_ATTR_MAX_LENGTH) takes precedence over the 'Max Long Data Length' value.
rdf:type: schema:Answer

Subject Item: n330:this
schema:name: What Does Max Rows Override Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: By specifying a value within this option, we specify the maximum number of rows to be returned by any given query as opposed to the actual value of rows contained within the table.
rdf:type: schema:Answer

Subject Item: n335:this
schema:name: What Does Multiplex Sessions Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This determines the connection parallelization mode within the Informix database. Multiplex sessions are now enabled by default.
rdf:type: schema:Answer

Subject Item: n341:this
schema:name: What Does NoQuotedIdentifiers Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The Option is use by the ODBC-JDBC bridge drivers to indicate a give JDBC driver does not support the quoted identifiers, which is required for Jet engine based products like MS Access. From Multi-Tier the environment variable is JET_NOSUPPORTOFQUOTEDIDENTIFIER=[YES|NO]
rdf:type: schema:Answer

Subject Item: n346:this
schema:name: What Does OCIPrefetchMemory Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OCIPrefetchMemory and OCIPrefetchRows control parameters relating to the Oracle OCI's prefetching facility. However, use of this facility has been disabled in the OpenLink agent and Lite driver because of problems experienced with Oracle 8.x and indicator variables. To minimize server round trips and maximize performance, the OCI can prefetch result set rows when executing a query. This prefetching operates independently of OpenLink's prefetching facility. The OCI prefetching can be customized by setting two attributes, OCI_ATTR_PREFETCH_ROWS and OCI_ATTR_PREFETCH_MEMORY. The OCIPrefetchMemory and OCIPrefetchRows settings in the OpenLink setup dialogs map directly to these OCI attributes. OCIPrefetchMemory sets the memory allocated for rows to be prefetched. The application then fetches as many rows as will fit into that much memory. OCIPrefetchRows sets the number of rows to be prefetched. When both of these attributes are set, the OCI prefetches rows up to the OCIPrefetchRows limit, or until the OCIPrefetchMemory limit is reached, if this is lower.
rdf:type: schema:Answer

Subject Item: n220:this
schema:name: What Does OCIPrefetchRows Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OCIPrefetchMemory and OCIPrefetchRows control parameters relating to the Oracle OCI's prefetching facility. However, use of this facility has been disabled in the OpenLink agent and Lite driver because of problems experienced with Oracle 8.x and indicator variables. To minimize server round trips and maximize performance, the OCI can prefetch result set rows when executing a query. This prefetching operates independently of OpenLink's prefetching facility. The OCI prefetching can be customized by setting two attributes, OCI_ATTR_PREFETCH_ROWS and OCI_ATTR_PREFETCH_MEMORY. The OCIPrefetchMemory and OCIPrefetchRows settings in the OpenLink setup dialogs map directly to these OCI attributes. OCIPrefetchMemory sets the memory allocated for rows to be prefetched. The application then fetches as many rows as will fit into that much memory. OCIPrefetchRows sets the number of rows to be prefetched. When both of these attributes are set, the OCI prefetches rows up to the OCIPrefetchRows limit, or until the OCIPrefetchMemory limit is reached, if this is lower.
rdf:type: schema:Answer

Subject Item: n226:this
schema:name: What Does Packet Size Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This is the size of TCP packets sent over the network on every network hop. Increasing this value should increase performance but is risky if a packet becomes lost in the network.
rdf:type: schema:Answer

Subject Item: n79:this
schema:name: What Does Prepare Method Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option is specific to the TDS Driver for MS & Sybase SQLServers, and can take the values None, Partial and Full (connectoptions -O [0, 1, 2] respectively) which are used to determines whether stored procedures are created on the server for calls to SQLPrepare. When set to Full (-O 2), stored procedures are created for every call to SQLPrepare. This setting can result in decreased performance when processing statements that do not contain parameters. When set to Partial (-O 1) (the initial default), the driver creates stored procedures only if the statement contains parameters. Otherwise, the statement is cached and run directly at the time of SQLExecute. When set to None (-O 0), stored procedures are never created. The driver caches the statement, executes it directly at the time of SQLExecute, and reports any syntax or similar errors at the time of SQLExecute.
rdf:type: schema:Answer

Subject Item: n236:this
schema:name: What Does Remote Database Alias Refer To? -- Answer
schema:category: ODBC UDA JDBC
schema:text: An alias identifying the DB2 database to connect to. This alias should be configured using the DB2 Client Configuration Assistant.
rdf:type: schema:Answer

Subject Item: n199:this
schema:name: What Does RowbufferSize Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This attribute specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.
rdf:type: schema:Answer

Subject Item: n203:this
schema:name: What Does SQL_DBMS_NAME Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This option allows overriding of the SQLGetInfo (SQL_DBMS_NAME) response. Ordinarily this is "ORACLE ". This option was introduced to allow our drivers to work with MSProject.
rdf:type: schema:Answer

Subject Item: n209:this
schema:name: What Does Show Remarks Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Show Remarks affects the output from SQLColumns. When enabled, the REMARKS column of a SQLColumns result set includes the comments from the COMMENTS column of the Oracle ALL_COL_COMMENTS data dictionary view. When disabled, the REMARKS column is empty. Disabling Show Remarks improves performance.
rdf:type: schema:Answer

Subject Item: n214:this
schema:name: What Does Space Pad Character Columns Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Space pad character columns controls whether data from Informix CHAR columns are returned "blank padded". When enabled, character values less than the column width are padded to the maximum width with trailing spaces, before being returned. When disabled, any trailing spaces are stripped off.
rdf:type: schema:Answer

Subject Item: n263:this
schema:name: What Does USEANSINulls Padding And Warnings Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This affects the TDS agent & Lite Drivers but only the MS SQLServer database, not Sybase. When enabled, the agent issues the Transact-SQL commands below on connecting: SET ANSI_NULL_DFLT_ON ON . When disabled, the agent issues the commands: SET ANSI_NULLS OFF SET ANSI_PADDING OFF SET ANSI_WARNINGS OFF SET CONCAT_NULL_YIELDS_NULL OFF
rdf:type: schema:Answer

Subject Item: n269:this
schema:name: What Does Use Extended Fetch Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: `Use Extended Fetch'' controls whether Our ODBC Bridge agent/Lite uses the SQLExtendedFetch() function of the underlying ODBC driver, if it's available, when fetching data. Using the bridged driver's SQLExtendedFetch() should improve performance. However it may be necessary to disable this setting- for instance, some drivers do not support extended fetching on a result-set produced by an ODBC catalog call. When extended fetching is disabled, the bridged driver's SQLFetch() function is used instead.
rdf:type: schema:Answer

Subject Item: n274:this
schema:name: What Does Use SPACE For SQL_IDENTIFIER_QUOTE_CHAR Do? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This is a Progress SQL-89 specific option which if set the driver returns " " rather than "" to represent this database does not have a quoted identifier character. The ODBC specification says that " " is what should be returned but some applications (like Crystal Reports) interpret this response as meaning the quoted identifier character is a "space", which obviously does not make sense and fails, as they are expecting "" to be returned hence this need for this option.
rdf:type: schema:Answer

Subject Item: n280:this
schema:name: What Does Users Own Tables First In SQL Tables Mean? -- Answer
schema:category: ODBC UDA JDBC
schema:text: This is an option specific to the UDA Oracle driver enabling the tables owned by the connected to user to be displayed first in the list present by SQLtables rather than purely in alphabetical order.
rdf:type: schema:Answer

Subject Item: n242:this
schema:name: What Environment Variables Need To Be Set On Unix Systems? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Users need to run openlink.sh or openlink.csh in the appropriate shell to set the following variables on all unix systems: CLASSPATH A JAVA client variable that passes the full path to an OpenLink JDBC .jar file. LD_LIBRARY_PATH A generic library path variable that appends the full path to OpenLink's lib sub-directory. LIBPATH An AIX library path variable that appends the full path to OpenLink's lib sub-directory. ODBCINI Passes the full path to ~/openlink/bin/odbc.ini. ODBCINSTINI Passes the full path to ~/openlink/bin/odbcinst.ini. OPENLINKINI This Single-Tier variable passes the full path to ~/openlink/bin/openlink.ini. PATH Appends the full path to OpenLink's bin sub-directory. SHLIB_PATH An HP/UX library path variable that appends the full path to OpenLink's lib sub-directory.
rdf:type: schema:Answer

Subject Item: n246:this
schema:name: What Environment Variables Need To Be Set On Windows Systems? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Most ODBC users do not need to set environment variables on Windows systems. JDBC users must insure that CLASSPATH is set as a System and/or User variable. CLASSPATH passes the full path to OpenLink's JDBC .jar files. This applies to both Multi-Tier and Single-Tier installations. OpenLink's Multi-Tier oplrqb.ini is a server side file that appears in the bin sub-directory of the server components installation. It contains a series of [Environment] sections. These sections pass variables that OpenLink components need to connect to specific databases.
rdf:type: schema:Answer

Subject Item: n160:this
schema:name: What Factors Contribute To Performance Problems? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The following factors contribute to performance problems: Use of OpenLink's older 1.x and 3.x drivers. The RPC communications layer--contained within newer, OpenLink drivers--was redesigned for enhanced performance.; Use of OpenLink's Multi-Tier drivers when use of Single-Tier drivers is possible. Single-Tier drivers boost performance.; Use of sockets connectivity where shared memory connectivity is possible.; Retrieval of large, binary objects.; Non-use or misuse of the Row Buffer Size DSN attribute.; Use of less efficient cursor modalities.; Poor use of indexes and table structuring.
rdf:type: schema:Answer

Subject Item: n170:this
schema:name: What Factors Contribute To Stability Problems? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The following factors contribute to stability problems: Improper use of database agent reuse rules in the Multi-Tier oplrqb.ini file; Inadequate memory; Inadequate processor count; Insufficient allocation of TCP ports in the Multi-Tier oplrqb.ini file; Lack of critical database patches or application of flawed patches; Lack of critical o/s patches or application of flawed patches; Sub-optimal kernel tuning parameters (Unix); Use of deprecated OpenLink components; Use of OpenLink products with an incompatible databases or o/s; Use of Single-Tier drivers on top of unstable database native clients.
rdf:type: schema:Answer

Subject Item: n151:this
schema:name: What Happened To The JdbcJodbc_sv And Judbc_sv Agents? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's 1.x and 3.x Multi-Tier connections spawned a JDBC-specific agent (jodbc_sv, judbc_sv), which spawned a database-specific agent. OpenLink's newer drivers have incorporated the functionality of jodbc_sv and judbc_sv into the database agents. Hence, separate jodbc_sv and judbc_sv agents are no longer needed.
rdf:type: schema:Answer

Subject Item: n155:this
schema:name: What Is A Concurrent Connection? -- Answer
schema:category: ODBC UDA JDBC
schema:text: A concurrent session is an open database session. Users often confuse database connections with perceived application connections. For example, Microsoft Access may appear to open one connection against the target database. However, Access really spawns 2 or more database sessions. This causes an unexpected number of licenses to be consumed. Users must understand that Access and other connections are coded to behave in this manner.
rdf:type: schema:Answer

Subject Item: n159:this
schema:name: What Is A Concurrent User? -- Answer
schema:category: ODBC UDA JDBC
schema:text: A concurrent user is a distinct ip address.
rdf:type: schema:Answer

Subject Item: n127:this
schema:name: What Is ASNPRINT.exe? -- Answer
schema:category: ODBC UDA JDBC
schema:text: ASNPRINT.exe is a diagnostic utility. It reads OpenLink 4.x and 5.x licenses, and displays the terms associated with those licenses. ASNPRINT.exe cannot read corrupt licenses. ASNPRINT.exe cannot read 1.x or 3.x licenses.
rdf:type: schema:Answer

Subject Item: n134:this
schema:name: What is Generic ODBC? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's ODBC Lite and Generic ODBC drivers perform a special function. These drivers enable users to establish ODBC connections to databases, for which OpenLink does not provide an agent. To proceed, users must possess native or 3rd party ODBC drivers that connect to their databases. Then, users must install OpenLink's ODBC Lite drivers on the machine, which contains these drivers. Multi-Tier users must install the Request Broker and Generic ODBC Agent on the machine, which contains these drivers. Multi-Tier users may install the Multi-Tier client on any supported operating system. Finally, OpenLink's ODBC Lite and Generic ODBC drivers proxy SQL requests from the application-through the 3rd party Data Source Name-to the actual database.
rdf:type: schema:Answer

Subject Item: n138:this
schema:name: What Is The JDBC-ODBC Bridge? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The JDBC-ODBC Bridge--or "Type 1" JDBC connection--allows users to establish connections to ODBC Data Source Names using a JDBC connection URL. The JDBC connection URL passes the name of a valid ODBC Data Source as a connection parameter
rdf:type: schema:Answer

Subject Item: n142:this
schema:name: What Is The ODBC-JDBC Bridge? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's ODBC-JDBC Bridge drivers allow ODBC Data Source Names to connect to JDBC connection URLs. This allows ODBC compliant applications to connect to and query JDBC data stores.
rdf:type: schema:Answer

Subject Item: n147:this
schema:name: What Is The ODBC-ODBC Bridge? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink Software builds specific database agents for DB2, Informix, Ingres, MS SQLServer, MySQL, Oracle, PostgreSQL, Progress, and Sybase. However, many users have Access, Paradox, Btrieve, DBase, and other databases for which OpenLink does not build agents. The ODBC-ODBC Bridge enables users to connect OpenLink drivers to these databases. The Bridge proxies OpenLink driver connections through 3rd party drivers that already connect to the database.
rdf:type: schema:Answer

Subject Item: n183:this
schema:name: What is the odbc.ini file? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The odbc.ini file is a standard, ODBC client configuration file. It is not specific to OpenLink drivers. In fact, many systems may have a pre-existing odbc.ini file in /etc or another directory. Nevertheless, OpenLink components ship with their own odbc.ini file. It appears in the /bin sub-directory of Unix installations. odbc.ini contains a list of all the Data Sources that appear within.
rdf:type: schema:Answer

Subject Item: n188:this
schema:name: What Is The odbcinst.ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The odbcinst.ini file is a standard ODBC configuration file. It consists of a list of drivers installed on the operating system and individual configuration sections for each driver. The configuration sections usually contain a Driver parameter, which passes the full path to the driver. These sections also contain a Setup parameter, which passes the location of the setup dialogs that are use to configure data sources that reference the driver. Other parameters appear as needed.
rdf:type: schema:Answer

Subject Item: n192:this
schema:name: What Is The Openlink.ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The openlink.ini file is a Single-Tier configuration file. It appears in the /bin sub-directory of Unix-based, Single-Tier installations. openlink.ini contains database-specific environment variables.
rdf:type: schema:Answer

Subject Item: n25:this
schema:name: What Is The Oplrqb.ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The oplrqb.ini file is the OpenLink Session Rules Book. The OpenLink Session Rules Book contains parameters that the Request Broker uses to resolve Multi-Tier connections. The Session Rules Book also contains: Request Broker configuration parameters; Networking & protocol specific parameters; Expression-based rules that comprise Multi-Tier enhanced security; Some Admin Assistant configuration parameters
rdf:type: schema:Answer

Subject Item: n167:this
schema:name: What Is The Proper Way To Perform An Upgrade? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Single-Tier users should terminate active ODBC connections, which use OpenLink's drivers. All Single-Tier users should back up their licenses, and Unix Single-Tier users should back-up existing odbc.ini and openlink.ini files. Finally, Single-Tier users should proceed with their upgrades. Multi-Tier users should terminate active ODBC connections, which use OpenLink's drivers. Multi-Tier users should also stop their Request Broker services. All Multi-Tier users should back-up their license and oplrqb.ini files, and Unix Multi-Tier users should back-up their odbc.ini files. Finally, Multi-Tier users should proceed with their upgrades. What about upgrading driver name or installing new driver?
rdf:type: schema:Answer

Subject Item: n172:this
schema:name: What Is The Udbc.ini File? -- Answer
schema:category: ODBC UDA JDBC
schema:text: The udbc.ini file contains client configuration parameters and data source connection parameters that facilitate use of OpenLink's UDBC drivers. It is similar in structure to the standard odbc.ini file. Users do not need to configure udbc.ini, unless they choose to use OpenLink's proprietary UDBC data access protocol. Users choose UDBC to bypass dependence on an ODBC driver manager. However, due to prevalence of iODBC and other driver managers on Unix, UDBC is no longer needed. OpenLink has dropped support for UDBC in its 5.0 releases.
rdf:type: schema:Answer

Subject Item: n177:this
schema:name: What Is Zero Config? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's ZeroConfig functionality allows the OpenLink administrator to define sets of database connection parameters using the Administrative Assistant. For instance, the OpenLink Administrator may hard-code the Request Broker host and port, database name, database username, and database password in a ZeroConfig Data Source. Existing ZeroConfig Data Sources are broadcast over the corporate network. End users may create Data Source Names from scratch. Alternatively, users may select a convenient ZeroConfig Data Source Name. Use of ZeroConfig Data Sources allow novice or non-privileged users to connect to the database using an immediate and reliable set of connection parameters.
rdf:type: schema:Answer

Subject Item: n179:this
schema:name: What JDBC Connection Formats Do Multi-Tier Drivers Support? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's Multi-Tier drivers support Type 3 (DSN-Less) JDBC connections. Multi-Tier drivers also support a Type 3 ODBC-JDBC Bridge.
rdf:type: schema:Answer

Subject Item: n52:this
schema:name: What JDBC Connection Formats Do Single-Tier Drivers Support? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Single-Tier drivers support Type 1 (JDBC-ODBC Bridge) JDBC connections. They also provide ODBC-JDBC Bridge connectivity.
rdf:type: schema:Answer

Subject Item: n53:this
schema:name: What Network Protocols Do You Support? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink supports the TCP/IP and IPX/SPX protocols.
rdf:type: schema:Answer

Subject Item: n54:this
schema:name: What Ports Do Users Need To Open On Their Firewalls To Use OpenLink Software? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Single-Tier users should not need to open ports to accommodate the Single-Tier driver. However, ports may need to be opened to facilitate connections between the database native client and the database to which it connects. Multi-Tier users need to take the following action, if a firewall surrounds the machine that contains the Multi-Tier server components
rdf:type: schema:Answer

Subject Item: n55:this
schema:name: What Resources Can I Use To Solve Support Cases? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink consultants have a wide array of resources at their disposal. Resources include: OPIE Knowledge-base & Wiki; OPIE Case Search Page; OpenLink Viewlet Library; UDA Product Documentation; OpenLink Internal Newsgroups; Google Web & Group Search; Database Vendor Sites & User Groups; Support staff should exhaust these resources before approaching senior support or management for assistance.
rdf:type: schema:Answer

Subject Item: n43:this
schema:name: What Services Do Users Start To Use OpenLink Drivers? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink Single-Tier users do not need to start services to use their drivers. Single-Tier users need to start the HTTP-Based iODBC Data Sources Administrator, if they want to use the graphical configuration utility. Use the following command to proceed: iodbc-admin-httpd.sh start OpenLink Multi-Tier users need to start their Request Brokers to use their drivers. Use the following command to start the Broker and the associated Administrative Assistant: oplrqb
rdf:type: schema:Answer

Subject Item: n45:this
schema:name: What Steps Should I Take To Debug My Cases? -- Answer
schema:category: ODBC UDA JDBC
schema:text: No single procedure will enable consultants to resolve all problems. Instead, consultants will need to develop a flexible attitude and a wide-variety of diagnostic skills. In the interim, new consultants may use the following tips to debug their cases
rdf:type: schema:Answer

Subject Item: n48:this
schema:name: What Types Of Problems Do Consultants Debug? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink Support consultants debug a wide array of problems. Problems range from simple downloads, installation, and licensing problems to complex stability, development, and migration problems.
rdf:type: schema:Answer

Subject Item: n50:this
schema:name: What values do I pass for my OpenLink environment variables? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's ODBC drivers recognize the following ODBC-specific environment variables. Users should not set ODBC variables manually. OpenLink's drivers ship with openlink.sh and openlink.csh files. These files appear in the root of the OpenLink installation. openlink.sh should be sourced if using Bourne or Bash shells. openlink.csh should be sourced in C shell.
rdf:type: schema:Answer

Subject Item: n66:this
schema:name: What Values Do Multi-Tier Users Need To Pass In Their Data-Sources? -- Answer
schema:category: ODBC UDA JDBC
schema:text: Multi-Tier users must pass the following values in their Multi-Tier DSNs: Server -- Passes the hostname or IP address of the server on which the Multi-Tier Request Broker listens. Also passes the TCP port on which the Broker listens. The format is host:port. Domain -- This value corresponds to a Domain Alias that appears in the [Domain Aliases] section of the Session Rules Book. Default Domain Aliases are named after the databases to which the database agent connect. Custom Domain Aliases may take any form. Database -- This is the name of the database or Oracle SID. Login ID -- This is a valid database username. Password -- This is a valid database password.
rdf:type: schema:Answer

Subject Item: n62:this
schema:name: What Values Do Single-Tier Users Need To Pass In Their DataSources? -- Answer
schema:category: ODBC UDA JDBC
schema:text: All Single-Tier users must pass a valid Data Source Name.
rdf:type: schema:Answer

Subject Item: n67:this
schema:name: What values must I pass in my Multi-Tier DSN? -- Answer
schema:category: ODBC UDA JDBC
schema:text: You must pass the following values in your Multi-Tier DSN: Name A descriptive name that identifies the Data Source. Server Passes the hostname or IP address of the server on which the Multi-Tier Request Broker listens. Also passes the TCP port on which the Broker listens. The format is host:port. Domain This value corresponds to a Domain Alias that appears in the [Domain Aliases] section of the Session Rules Book. Default Domain Aliases are named after the databases to which the database agent connect. Custom Domain Aliases may take any form. Database This is the name of the database or Oracle SID. Login ID This is a valid database username. Password This is a valid database password. Is your Multi-Tier Request Broker and DBMS installed on separate machines? If so, one of the following values must be added to your DSN: DB2 Server/Adapter Passes a remote DB2 database alias. Informix Server Passes the name of the Informix server. Ingres Net (vnode) Passes vnode::database name. MySQL Connect Options Passes -H host -P port -T. Oracle SQL*Net Alias Passes an Oracle SQL*Net alias. PostgreSQL Connect Options Passes -H host -P port -T. Progress Connect Options Passes Progress -S socket -H host -N tcp parameters. SQLServer Connect Options Passes -S followed by a SQLServer instance name. Sybase Connect Options Passes the Sybase instance name.
rdf:type: schema:Answer

Subject Item: n68:this
schema:name: What Values Must I Pass In My Single-Tier DSN? -- Answer
schema:category: ODBC UDA JDBC
schema:text: UDA Support Primer Data Source Name (DNS) Creation What values must I pass in my Single-Tier DSN All Single-Tier users must pass a valid Data Source Name.
rdf:type: schema:Answer

Subject Item: n57:this
schema:name: Why Do Some Users Require Permanent Licenses Where as Some Users Do Not? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's 1.x and 3.x drivers shipped with built-in, non-expiring, 2 user/10 concurrent connection licenses. This feature mitigated the need for permanent key, so long as usage stayed within these parameters.
rdf:type: schema:Answer

Subject Item: n58:this
schema:name: Why Do Some Users Require Temporary Licenses Where as Some Users Do Not? -- Answer
schema:category: ODBC UDA JDBC
schema:text: OpenLink's 1.x and 3.x drivers shipped with built-in, 2 user/10 concurrent connection licenses. This feature mitigated the need for a temporary license key.
rdf:type: schema:Answer

Subject Item: n61:this
schema:name: Why Should I Upgrade? -- Answer
schema:category: ODBC UDA JDBC
schema:text: End-users are encouraged to upgrade to the latest software version. The latest software contains desirable new features and fixes for bugs. Additionally, support options are limited, when legacy software is involved. Development does not back-patch legacy bugs, and Support staff may have difficulties recreating legacy problems. The following table lists new features for recent software builds: 4.x ODBC 3.5 compliance. Multi-Threaded client & server components. Substantially-revised communications layer. 5.x Unicode support. Zero Config. Best communications layer.
rdf:type: schema:Answer

Subject Item: n65:this
schema:name: Answer to question: What is ODBC?
schema:category: ODBC UDA JDBC
schema:text: ODBC is short for Open Database Connectivity, an Application Programming Interface and Runtime Middleware that loosely-couples Applications and backend Database Management Systems (DBMS). ODBC was originally created by Microsoft as a Windows-specific API and Runtime component. Over the years it has been successfully ported and deployed across macOS, Linux, and a variety of Unix platforms via projects such as iODBC and unixODBC.
rdf:type: schema:Answer

Subject Item: n23:this
schema:name: Answer to question: Why is ODBC important?
schema:category: ODBC UDA JDBC
schema:text: By loosely-coupling how Applications & Services connect to backend Database Management Systems (DBMS), It provides a powerful solution to the data access and integration problems associated with data silos created by database-specific applications and services.
rdf:type: schema:Answer

Subject Item: n26:this
schema:name: Answer to question: What is an ODBC Application or Service?
schema:category: ODBC UDA JDBC
schema:text: An application or service that leverages ODBC for performing data definition and data manipulation operations, using SQL, in a manner that's independent of backend Database Management Systems (DBMS).
rdf:type: schema:Answer

Subject Item: n28:this
schema:name: Answer to question: How Does ODBC Work?
schema:category: ODBC UDA JDBC
schema:text: In similar fashion to a printer selection interaction experience, it enables a compliant application or service to select a target backend Database Management System (DBMS) via a Data Source Name (DSN) associated with a driver -- basically, a Database Management System (DBMS) replaces a printer in this usage scenario.
rdf:type: schema:Answer

Subject Item: n16:this
schema:name: Answer to question: What is JDBC?
schema:category: ODBC UDA JDBC
schema:text: JDBC is short for Java Database Connectivity, an Application Programming Interface and Runtime Middleware that loosely-couples Java Applications and backend Database Management Systems (DBMS).
rdf:type: schema:Answer

Subject Item: n20:this
schema:name: Answer to question: Why is JDBC important?
schema:category: ODBC UDA JDBC
schema:text: By loosely-coupling how Java Applications & Services connect to backend Database Management Systems (DBMS), It provides a powerful solution to the data access and integration problems associated with data silos created by database-specific applications and services.
rdf:type: schema:Answer

Subject Item: n22:this
schema:name: Answer to question: What is a JDBC Application or Service?
schema:category: ODBC UDA JDBC
schema:text: An application or service that leverages JDBC for performing data definition and data manipulation operations, using SQL, in a manner that's independent of backend Database Management Systems (DBMS).
rdf:type: schema:Answer

Subject Item: n37:this
schema:name: Answer to question: How Does JDBC Work?
schema:category: ODBC UDA JDBC
schema:text: In similar fashion to a printer selection interaction experience, it enables a compliant application or service to select a target backend Database Management System (DBMS) via a Data Source Name (DSN) or URL associated with a driver -- basically, a Database Management System (DBMS) replaces a printer in this usage scenario.
rdf:type: schema:Answer

Subject Item: n40:this
schema:name: What to do if ASNPRINT does not read my license file?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n46:this

Subject Item: n42:this
schema:name: Can I Install New Software On Top Of Existing Software?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n49:this

Subject Item: n31:this
schema:name: Can I mix and match client and server components from different OpenLink versions?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n35:this

Subject Item: n32:this
schema:name: Can I run 32 Bit software on a 64 Bit operating system?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n36:this

Subject Item: n33:this
schema:name: Can I run 64Bit software on a 32Bit operating system?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n39:this

Subject Item: n34:this
schema:name: Can I run multiple versions at the same time?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n41:this

Subject Item: n132:this
schema:name: Can OpenLink provide ftp access to the downloads files?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n133:this

Subject Item: n136:this
schema:name: Can OpenLink provide installation files on CD?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n137:this

Subject Item: n125:this
schema:name: Can users install on top of existing OpenLink software installations?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n77:this

Subject Item: n128:this
schema:name: Can users manually extract and install the software?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n129:this

Subject Item: n123:this
schema:name: I cannot download software to the appropriate machine. What do I do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n124:this

Subject Item: n117:this
schema:name: What can I do if I cant solve the problem?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n118:this

Subject Item: n111:this
schema:name: I cant set my OpenLink variables. What do I do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n112:this

Subject Item: n108:this
schema:name: My Request Broker shuts itself down. What do I do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n109:this

Subject Item: n4:this
schema:name: I cant start my Admin Assistant. What do I do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n14:this

Subject Item: n6:this
schema:name: I cant start my Request Broker. What do I do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n15:this

Subject Item: n10:this
schema:name: I cant shutdown my Admin Assistant. What do I do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n19:this

Subject Item: n13:this
schema:name: I cant shutdown my Request Broker. What do I do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n21:this

Subject Item: n95:this
schema:name: Components are missing after installation. What do I do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n96:this

Subject Item: n92:this
schema:name: I think I have OpenLink Software. How can I tell?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n5:this

Subject Item: n101:this
schema:name: Do I need to configure my environment to support my JDBC connections?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n7:this

Subject Item: n99:this
schema:name: Do I need to configure my environment to support ODBC-ODBC Bridge connectivity?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n12:this

Subject Item: n181:this
schema:name: Do I need?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n182:this

Subject Item: n186:this
schema:name: Do users need to employ special configuration to operate in a firewalled environment?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n187:this

Subject Item: n173:this
schema:name: Do you have 16Bit drivers?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n174:this

Subject Item: n178:this
schema:name: Does OpenLink Load Share for Active-Active Clusters?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n144:this

Subject Item: n201:this
schema:name: Does OpenLink produce custom software for evaluators?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n202:this

Subject Item: n197:this
schema:name: Does OpenLink provide data migration facilities?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n198:this

Subject Item: n193:this
schema:name: Does OpenLink function in Fail-over Cluster environments?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n122:this

Subject Item: n190:this
schema:name: Does OpenLink work with Oracle Heterogeneous Services?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n29:this

Subject Item: n140:this
schema:name: Does OpenLink work with SQLServer Linked Servers?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n141:this

Subject Item: n145:this
schema:name: Does OpenLink work with the DTS Wizard?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n146:this

Subject Item: n148:this
schema:name: Can you explain OpenLink installation file naming conventions?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n149:this

Subject Item: n152:this
schema:name: Heavy load causes my ODBC connections to fail. What do I do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n153:this

Subject Item: n162:this
schema:name: How can I bench-test OpenLink drivers?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n163:this

Subject Item: n157:this
schema:name: How can I detect bottlenecks caused by OpenLink drivers?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n158:this

Subject Item: n168:this
schema:name: How can I determine which ports the Multi-Tier Request Broker uses?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n169:this

Subject Item: n164:this
schema:name: How can I assess my data access needs?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n165:this

Subject Item: n240:this
schema:name: How can I prevent performance problems?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n241:this

Subject Item: n51:this
schema:name: How can I prevent stability problems?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n245:this

Subject Item: n227:this
schema:name: How can I tell if a license is or is not corrupt?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n228:this

Subject Item: n231:this
schema:name: How can I tell if OpenLink produces software for a particular operating system or database?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n232:this

Subject Item: n224:this
schema:name: How can I tell what version I have?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n225:this

Subject Item: n218:this
schema:name: How do I configure Multi-Tier drivers, after I have installed them?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n219:this

Subject Item: n210:this
schema:name: How do I configure Single-Tier drivers, after I have installed them?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n113:this

Subject Item: n204:this
schema:name: How Do I Assist Users Who Cannot Start The Multi-Tier Request Broker?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n205:this

Subject Item: n272:this
schema:name: How Do I Assist Users Who Cannot Set Environment Variables?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n273:this

Subject Item: n278:this
schema:name: How Do I Configure An JDBC-ODBC Bridge Connection?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n279:this

Subject Item: n281:this
schema:name: How Do I Configure An ODBC-JDBC Bridge Connection?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n282:this

Subject Item: n288:this
schema:name: How Do I Configure An ODBC-ODBCBridge Connection?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n289:this

Subject Item: n255:this
schema:name: How Do I Create A Data Source Name?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n256:this

Subject Item: n250:this
schema:name: How Do I Create A Zero Config DSN?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n251:this

Subject Item: n264:this
schema:name: How do I get a commercial license?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n265:this

Subject Item: n258:this
schema:name: How Do I Get An Evaluation License File?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n259:this

Subject Item: n73:this
schema:name: How Do I Install Your Products?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n307:this

Subject Item: n311:this
schema:name: How Do I Interpret Admin Assistant Logs?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n312:this

Subject Item: n294:this
schema:name: How Do I Interpret Classpaths?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n103:this

Subject Item: n298:this
schema:name: How Do I Interpret DBMS Versions?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n299:this

Subject Item: n333:this
schema:name: How Do I Interpret Database Agent Version Strings?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n195:this

Subject Item: n328:this
schema:name: How do I interpret Database Native Error Logs?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n329:this

Subject Item: n320:this
schema:name: How Do I Interpret Database Profiles?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n321:this

Subject Item: n314:this
schema:name: How Do I Interpret Installation Shell Scripts?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n315:this

Subject Item: n339:this
schema:name: How Do I Interpret License Files?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n340:this

Subject Item: n344:this
schema:name: How Do I Interpret Name Of Taz Files?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n345:this

Subject Item: n347:this
schema:name: How Do I Interpret Openlink ini Files?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n348:this

Subject Item: n353:this
schema:name: How do I interpret Operating System Patch Levels?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n354:this

Subject Item: n365:this
schema:name: How Do I Interpret Output Of Java Commands?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n366:this

Subject Item: n89:this
schema:name: How Do I Interpret Output Of Oplshut?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n87:this

Subject Item: n373:this
schema:name: How Do I Interpret Output Of Set?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n11:this

Subject Item: n368:this
schema:name: How Do I Interpret Relink Scripts?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n369:this

Subject Item: n371:this
schema:name: How Do I Interpret Request Broker Logs?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n372:this

Subject Item: n376:this
schema:name: How Do I Interpret Request Broker Version Strings?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n377:this

Subject Item: n359:this
schema:name: How Do I Interpret Udbc ini Files?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n360:this

Subject Item: n363:this
schema:name: How Do I Test My JDBC Connection URL?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n257:this

Subject Item: n120:this
schema:name: How Do I Troubleshoot A Failed JDBC-ODBC Bridge Connection?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n356:this

Subject Item: n350:this
schema:name: How Do I Troubleshoot A Failed ODBC-JDBC Bridge Connection?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n351:this

Subject Item: n334:this
schema:name: How do I troubleshoot a failed ODBC-ODBC Bridge connection?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n342:this

Subject Item: n336:this
schema:name: How Do I Uninstall Existing OpenLink Software?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n337:this

Subject Item: n317:this
schema:name: How Do Users Configure The Odbc ini File?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n318:this

Subject Item: n323:this
schema:name: How Do Users Configure The Odbcinst ini File?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n324:this

Subject Item: n325:this
schema:name: How Do Users Configure The Openlink ini File?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n326:this

Subject Item: n105:this
schema:name: How Do Users Configure The Oplrqb ini File?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n331:this

Subject Item: n301:this
schema:name: How Do Users Configure The Udbc ini File?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n302:this

Subject Item: n295:this
schema:name: How Do Users Create Data Source Names?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n296:this

Subject Item: n309:this
schema:name: How Do Users Obtain Licenses?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n90:this

Subject Item: n304:this
schema:name: How Do Users Start The Multi-Tier Request Broker?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n305:this

Subject Item: n261:this
schema:name: How Do Users Uninstall OpenLink Software?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n262:this

Subject Item: n267:this
schema:name: How Do Your Drivers Work?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n268:this

Subject Item: n247:this
schema:name: How does clustering affect licensing?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n248:this

Subject Item: n252:this
schema:name: How much do licenses cost?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n253:this

Subject Item: n291:this
schema:name: How To FTP?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n292:this

Subject Item: n285:this
schema:name: How To Uncompress Files?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n286:this

Subject Item: n275:this
schema:name: I Do Not Know The Correct Values For My Multi-Tier DSN. What Do I Do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n276:this

Subject Item: n270:this
schema:name: I do not know the correct values for my Single-Tier DSN. What do I do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n2:this

Subject Item: n207:this
schema:name: I Suspect That My User Is Experiencing Port Or Networking Problems. What Do I Do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n208:this

Subject Item: n212:this
schema:name: Is OpenLink Support Staff responsible for all user problems?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n213:this

Subject Item: n215:this
schema:name: My 1x 3x JDBC Type 3 Connections Spawn Multiple Agents That Consume My Licenses. What Do I Do?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n216:this

Subject Item: n221:this
schema:name: What Do I Do If My Applications Fail To Connect After I Upgraded My 1x3x Drivers To 4x5x?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n222:this

Subject Item: n234:this
schema:name: What Do I Do If My Broker Shuts Down Intermittently?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n235:this

Subject Item: n230:this
schema:name: What Do I Do If My Drivers Occasionally Fail To Disconnect?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n98:this

Subject Item: n243:this
schema:name: What Do I Do If My Drivers Produce Intermittent Core Dumps?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n80:this

Subject Item: n238:this
schema:name: What Do I Do If My Drivers Produce Intermittent Protrace Files?
schema:category: UDA JDBC ODBC
rdf:type: schema:Question
schema:acceptedAnswer: n156:this

Subject Item: n434:this
schema:name: What Do I Do If My Existing License Key Does Not Work?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n441:this

Subject Item: n436:this
schema:name: What Do I Do If My Existing License Key Is Expired?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n443:this

Subject Item: n438:this
schema:name: What Do I Do If My Multi-Tier DSN Fails To Connect?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n445:this

Subject Item: n440:this
schema:name: What Do I Do If My Multi-Tier DSN Fails To Disconnect?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n447:this

Subject Item: n427:this
schema:name: What Do I Do If My ODBC Connectivity Suddenly Stopps Working Altogether?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n433:this

Subject Item: n428:this
schema:name: What Do I Do If My Single-Tier DSN Fails To Connect?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n435:this

Subject Item: n430:this
schema:name: What Do I Do If My Single-Tier DSN Fails To Disconnect?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n437:this

Subject Item: n432:this
schema:name: What Is The Compatibility with A Newer DB?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n439:this

Subject Item: n283:this
schema:name: What is the Compatibility With Newer OS?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n458:this

Subject Item: n452:this
schema:name: What Licenses are provided?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n449:this

Subject Item: n455:this
schema:name: What Suitable Software Should Be Used?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n27:this

Subject Item: n457:this
schema:name: Is there Older DB Compatibility Supported?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n237:this

Subject Item: n442:this
schema:name: Is Older OS Compatibility Supported?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n450:this

Subject Item: n444:this
schema:name: OpenLink Data Access Drivers Vs iODBC?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n451:this

Subject Item: n446:this
schema:name: What Do I Do When The Installation Process Hangs Without An Error?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n454:this

Subject Item: n448:this
schema:name: What Do I Do When The Installation Process Produces Errors?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n456:this

Subject Item: n405:this
schema:name: What Component Naming Conventions is Used?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n413:this

Subject Item: n407:this
schema:name: What to do in case of Installation Failure?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n414:this

Subject Item: n409:this
schema:name: What are the UDA Licensing Model based on?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n416:this

Subject Item: n412:this
schema:name: What to Do if Can Not Download?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n400:this

Subject Item: n398:this
schema:name: What Are The Differences Among User System And File DSNs?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n404:this

Subject Item: n401:this
schema:name: What Are Your Prerequisites And System Requirements?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n406:this

Subject Item: n402:this
schema:name: What Can I Do To Assist Users Who Have Lost Their Licenses?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n408:this

Subject Item: n403:this
schema:name: What Configuration Files Are Used By Multi-Tier Drivers?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n411:this

Subject Item: n421:this
schema:name: What Configuration Files Are Used By Single-Tier Drivers?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n426:this

Subject Item: n185:this
schema:name: How Do I Assist A User Who Does Not Know What Values To Pass To His Or Her Variables?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n64:this

Subject Item: n423:this
schema:name: Trouble-shooting registering a product with a temporary or commercial license?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n429:this

Subject Item: n425:this
schema:name: What Do I Do If My JDBC Connections Fail?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n431:this

Subject Item: n386:this
schema:name: What Do I Do With The DSNs That I Create?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n420:this

Subject Item: n415:this
schema:name: What Do I Do With The License File?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n422:this

Subject Item: n417:this
schema:name: What Do I Need To Establish A Multi-Tier JDBC Connection?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n9:this

Subject Item: n419:this
schema:name: What Do I Need To Establish A Single-Tier JDBC Connection?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n424:this

Subject Item: n375:this
schema:name: What Do I Need To Test The JDBC-ODBC Bridge?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n383:this

Subject Item: n379:this
schema:name: What Do I Need To Test The ODBC-JDBC Bridge?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n385:this

Subject Item: n70:this
schema:name: What Do I Need To Test The ODBC-ODBC Bridge?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n189:this

Subject Item: n382:this
schema:name: What Do I Pass In A Multi-Tier JDBC Connection URL?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n389:this

Subject Item: n355:this
schema:name: What Do I Pass In A Single-Tier JDBC Connection URL?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n30:this

Subject Item: n361:this
schema:name: What Do I Tell Users Who Want New Temporary Licenses?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n378:this

Subject Item: n364:this
schema:name: What Do Users Need To Do To Configure Their Multi-Tier Drivers?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n380:this

Subject Item: n370:this
schema:name: What Do Users Need To Do To Configure Their Single-Tier Drivers?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n381:this

Subject Item: n392:this
schema:name: What Do Your Drivers Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n397:this

Subject Item: n393:this
schema:name: What Does Count Stored Procedure Parameters In SQL Procedures Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n399:this

Subject Item: n395:this
schema:name: What Does Custom Catalog Views Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n44:this

Subject Item: n396:this
schema:name: What Does Deadlock Timeout Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n97:this

Subject Item: n384:this
schema:name: What Does Default User ID Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n391:this

Subject Item: n387:this
schema:name: What Does Disable Auto Commit Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n357:this

Subject Item: n388:this
schema:name: What Does Disable Interactive Login Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n394:this

Subject Item: n390:this
schema:name: What Does Disable RowsetSizeLimit Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n349:this

Subject Item: n290:this
schema:name: What Does Dynamic Cursor Sensitivity Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n308:this

Subject Item: n38:this
schema:name: What Does Enable Logging Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n313:this

Subject Item: n300:this
schema:name: What Does Enable Microsoft Jet Engine Options Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n319:this

Subject Item: n306:this
schema:name: What Does Expression Precision Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n24:this

Subject Item: n266:this
schema:name: What Does Expression Scale Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n287:this

Subject Item: n271:this
schema:name: What Does Field Size Maximum Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n293:this

Subject Item: n277:this
schema:name: What Does Field Size Minimum Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n297:this

Subject Item: n284:this
schema:name: What Does Force Online Database Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n303:this

Subject Item: n332:this
schema:name: What Does Hide Login Dialog Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n352:this

Subject Item: n338:this
schema:name: What Does Initial SQL Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n358:this

Subject Item: n343:this
schema:name: What Does Log File Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n362:this

Subject Item: n56:this
schema:name: What Does Max Long Data Length Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n367:this

Subject Item: n310:this
schema:name: What Does Max Rows Override Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n330:this

Subject Item: n316:this
schema:name: What Does Multiplex Sessions Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n335:this

Subject Item: n322:this
schema:name: What Does NoQuotedIdentifiers Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n341:this

Subject Item: n327:this
schema:name: What Does OCIPrefetchMemory Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n346:this

Subject Item: n200:this
schema:name: What Does OCIPrefetchRows Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n220:this

Subject Item: n206:this
schema:name: What Does Packet Size Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n226:this

Subject Item: n211:this
schema:name: What Does Prepare Method Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n79:this

Subject Item: n217:this
schema:name: What Does Remote Database Alias Refer To?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n236:this

Subject Item: n184:this
schema:name: What Does RowbufferSize Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n199:this

Subject Item: n191:this
schema:name: What Does SQL_DBMS_NAME Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n203:this

Subject Item: n194:this
schema:name: What Does Show Remarks Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n209:this

Subject Item: n196:this
schema:name: What Does Space Pad Character Columns Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n214:this

Subject Item: n244:this
schema:name: What Does USEANSINulls Padding And Warnings Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n263:this

Subject Item: n249:this
schema:name: What Does Use Extended Fetch Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n269:this

Subject Item: n254:this
schema:name: What Does Use SPACE For SQL_IDENTIFIER_QUOTE_CHAR Do?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n274:this

Subject Item: n260:this
schema:name: What Does Users Own Tables First In SQL Tables Mean?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n280:this

Subject Item: n223:this
schema:name: What Environment Variables Need To Be Set On Unix Systems?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n242:this

Subject Item: n229:this
schema:name: What Environment Variables Need To Be Set On Windows Systems?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n246:this

Subject Item: n233:this
schema:name: What Factors Contribute To Performance Problems?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n160:this

Subject Item: n239:this
schema:name: What Factors Contribute To Stability Problems?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n170:this

Subject Item: n135:this
schema:name: What Happened To The JdbcJodbc_sv And Judbc_sv Agents?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n151:this

Subject Item: n139:this
schema:name: What Is A Concurrent Connection?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n155:this

Subject Item: n143:this
schema:name: What Is A Concurrent User?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n159:this

Subject Item: n150:this
schema:name: What Is ASNPRINT.exe?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n127:this

Subject Item: n121:this
schema:name: What is Generic ODBC?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n134:this

Subject Item: n126:this
schema:name: What Is The JDBC-ODBC Bridge?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n138:this

Subject Item: n130:this
schema:name: What Is The ODBC-JDBC Bridge?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n142:this

Subject Item: n131:this
schema:name: What Is The ODBC-ODBC Bridge?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n147:this

Subject Item: n171:this
schema:name: What is the odbc.ini file?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n183:this

Subject Item: n175:this
schema:name: What Is The odbcinst.ini File?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n188:this

Subject Item: n176:this
schema:name: What Is The Openlink.ini File?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n192:this

Subject Item: n180:this
schema:name: What Is The Oplrqb.ini File?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n25:this

Subject Item: n154:this
schema:name: What Is The Proper Way To Perform An Upgrade?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n167:this

Subject Item: n59:this
schema:name: What Is The Udbc.ini File?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n172:this

Subject Item: n161:this
schema:name: What Is Zero Config?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n177:this

Subject Item: n166:this
schema:name: What JDBC Connection Formats Do Multi-Tier Drivers Support?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n179:this

Subject Item: n88:this
schema:name: What JDBC Connection Formats Do Single-Tier Drivers Support?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n52:this

Subject Item: n91:this
schema:name: What Network Protocols Do You Support?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n53:this

Subject Item: n94:this
schema:name: What Ports Do Users Need To Open On Their Firewalls To Use OpenLink Software?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n54:this

Subject Item: n100:this
schema:name: What Resources Can I Use To Solve Support Cases?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n55:this

Subject Item: n82:this
schema:name: What Services Do Users Start To Use OpenLink Drivers?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n43:this

Subject Item: n83:this
schema:name: What Steps Should I Take To Debug My Cases?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n45:this

Subject Item: n85:this
schema:name: What Types Of Problems Do Consultants Debug?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n48:this

Subject Item: n86:this
schema:name: What values do I pass for my OpenLink environment variables?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n50:this

Subject Item: n107:this
schema:name: What Values Do Multi-Tier Users Need To Pass In Their Data-Sources?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n66:this

Subject Item: n110:this
schema:name: What Values Do Single-Tier Users Need To Pass In Their DataSources?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n62:this

Subject Item: n114:this
schema:name: What values must I pass in my Multi-Tier DSN?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n67:this

Subject Item: n116:this
schema:name: What Values Must I Pass In My Single-Tier DSN?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n68:this

Subject Item: n102:this
schema:name: Why Do Some Users Require Permanent Licenses Where as Some Users Do Not?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n57:this

Subject Item: n104:this
schema:name: Why Do Some Users Require Temporary Licenses Where as Some Users Do Not?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n58:this

Subject Item: n106:this
schema:name: Why Should I Upgrade?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n61:this

Subject Item: n75:this
schema:name: What is a JDBC Application or Service?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n22:this

Subject Item: n76:this
schema:name: How Does ODBC Work?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n28:this

Subject Item: n69:this
schema:name: What is ODBC?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n65:this

Subject Item: n71:this
schema:name: Why is ODBC important?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n23:this

Subject Item: n72:this
schema:name: What is an ODBC Application or Service?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n26:this

Subject Item: n74:this
schema:name: What is JDBC?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n16:this

Subject Item: n78:this
schema:name: Why is JDBC important?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n20:this

Subject Item: n81:this
schema:name: How Does JDBC Work?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n37:this

Subject Item: n491:this
wdrs:describedby: n473:seo
schema:name: How Do I Get Started?
schema:about: n512:this
rdf:type: schema:Question
schema:acceptedAnswer: n468:this

Subject Item: n468:this
wdrs:describedby: n473:seo
schema:name: Getting started is simple. Download and begin a 30-day evaluation license via our on-boarding site
schema:relatedLink: n488:openlinkswcom-pago.openlink-virtuoso-azure-byol-offer-20201017?tab=Overview n506:B08KTPPY8V?ref_=srh_res_product_title n510: n511:openlink n506:B08K97YRGK?ref_=srh_res_product_title n488:openlinkswcom-pago.openlink-virtuoso-azure-pago-offer-20201019?tab=Overview
schema:text: If you are installing on-premise simply download a free evaluation license using our on-boarding service. If you prefer Docker Containers, simply download an appropriate container from our Docker Hub Repository. If you need instant gratification provided by Cloud deployment, you have a choice of Bring-Your-Own-License (BYOL) and Pay-As-You-Go (PAGO) options from the Amazon Web Services (AWS) and Microsoft Azure Clouds.
rdf:type: schema:Answer

Subject Item: n470:this
wdrs:describedby: n473:seo
schema:name: How much does a Virtuoso License cost?
schema:about: n512:this
rdf:type: schema:Question
schema:acceptedAnswer: n492:this

Subject Item: n492:this
wdrs:describedby: n473:seo
schema:name: A selection of offers can be found using our offers page, or by contacting a sales representative.
schema:relatedLink: n508: n514:pricing
schema:text: Entry-Level Pricing can be found on our pricing page. Custom and Enterprise quotes can also be made by contacting a sales representative.
rdf:type: schema:Answer

Subject Item: n493:this
wdrs:describedby: n473:seo
schema:name: What are the Developer, Integrator, Reseller, Distributor, and OEM partnering options?
schema:about: n512:this
rdf:type: schema:Question
schema:acceptedAnswer: n487:this

Subject Item: n487:this
wdrs:describedby: n473:seo
schema:name: Partnering options can be explored through our partners page.
schema:relatedLink: n509:
schema:text: Partnering options can be explored through our partners page.
rdf:type: schema:Answer

Subject Item: n17:afddc5c6ec25e3e1a9ba5473a8032d6e
schema:name: Software License Offer: Virtuoso 8.x Workgroup Development License for any Workstation-class or Server-class Operating System
schema:validFrom: 2020-10-31
schema:price: 999
schema:itemOffered: n17:87c1192e9d5ba99526f89345a340aaa6
schema:priceValidUntil: 2022-06-30
rdf:type: schema:Offer

Subject Item: n17:c09753950666a99dd19a73ceba61421b
schema:description: Concurrency enables flexible exploration and determination of optimal license. Enterprise Edition supports many optional functionality Modules; with the exception of the Elastic Cluster Module, the license in this offer enables all current Modules. Pricing is extremely competitive relative to competing alternatives when performance and capabilities are fully considered.
schema:name: Software License : Virtuoso 8.2 Systems Integration License (expiring, 2 cores, 4 threads)
schema:image: n18:OPL-VIRTOFFER-4CON-2CORE-WIN.png n18:OPL-VIRTOFFER-4CON-2CORE-LIN.png n18:OPL-VIRTOFFER-4CON-2CORE-MAC.png
schema:offers: n17:28a5b5f7923f3d7ce408158a2c8e50b7 n17:e226b0faa57181fab0062ae5f6291c1c n17:8d442715a7e846e34683d45bdd1cb4b8
schema:brand: OpenLink Virtuoso
rdf:type: schema:Product

Subject Item: n17:e226b0faa57181fab0062ae5f6291c1c
schema:name: Software License Offer: Virtuoso 8.2 Application Development License For Linux (Workstation) Operating Systems
schema:validFrom: 2018-11-04
schema:price: 749.99 99.99
schema:itemOffered: n17:9b6dbabc52014cddbe77caa453824fb0 n17:c09753950666a99dd19a73ceba61421b
schema:priceValidUntil: 2019-03-31
rdf:type: schema:Offer

Subject Item: n17:8d442715a7e846e34683d45bdd1cb4b8
schema:name: Software License Offer: Virtuoso 8.2 Application Development License For macOS (Workstation) Operating Systems
schema:validFrom: 2018-11-04
schema:price: 749.99 99.99
schema:itemOffered: n17:c09753950666a99dd19a73ceba61421b n17:9b6dbabc52014cddbe77caa453824fb0
schema:priceValidUntil: 2019-03-31
rdf:type: schema:Offer

Subject Item: n17:28a5b5f7923f3d7ce408158a2c8e50b7
schema:name: Software License Offer: Virtuoso 8.2 Application Development License For WIndows (Workstation) Operating Systems
schema:validFrom: 2018-11-04
schema:price: 749.99 99.99
schema:itemOffered: n17:9b6dbabc52014cddbe77caa453824fb0 n17:c09753950666a99dd19a73ceba61421b
schema:priceValidUntil: 2019-03-31
rdf:type: schema:Offer

Subject Item: n17:9b6dbabc52014cddbe77caa453824fb0
schema:description: Concurrency enables flexible exploration and determination of optimal license. Enterprise Edition supports many optional functionality Modules; with the exception of the Elastic Cluster Module, the license in this offer enables all current Modules. Pricing is extremely competitive relative to competing alternatives when performance and capabilities are fully considered.
schema:name: Software License : Virtuoso 8.2 Systems Integration License (expiring, 4 cores, 5 threads)
schema:image: n18:OPL-VIRTOFFER-5CON-4CORE-WIN.png n18:OPL-VIRTOFFER-5CON-4CORE-LIN.png n18:OPL-VIRTOFFER-5CON-4CORE-MAC.png
schema:offers: n17:28a5b5f7923f3d7ce408158a2c8e50b7 n17:e226b0faa57181fab0062ae5f6291c1c n17:8d442715a7e846e34683d45bdd1cb4b8
schema:brand: OpenLink Virtuoso
rdf:type: schema:Product

Subject Item: n17:94d8a7056f36b75698f30ce2bd1df3aa
schema:description: Workstation-class Virtuoso 8.x Early-Stage-Combo Development License for installation (transferable) on one (1) host running any supported Workstation-class OS. Enables five (5) Client Service Threads, the Column Store, Custom Reasoning & Inference Rules, Advanced Module, and will utilize a maximum of eight (8) processor cores, for one (1) year. Workstation-class Virtuoso 8.x Early-Stage-Combo Development License for installation (transferable) on one (1) host running any supported Workstation-class OS. Enables five (5) Client Service Threads, the Column Store, Custom Reasoning & Inference Rules, Advanced Module, and will utilize a maximum of eight (8) processor cores, for one (1) year.
schema:name: Virtuoso 8.x License: 2020-10-virtuoso-8-early-stage-combo-WKS-ANY 8 cores
schema:image: n18:OPL-VIRTOFFER-5CON-8CORE.png
schema:offers: n17:b6c76969d94702d9fae4b75a8489d9c6
schema:brand: OpenLink Virtuoso
rdf:type: schema:Product

Subject Item: n17:98d2a5f76f4503270f809420f1b54338
schema:description: Workstation-class Virtuoso 8.x Application Development Progject License for installation (transferable) on one (1) host running any supported Workstation-class OS. Enables five (5) Client Service Threads, the Column Store, Linked Data Middleware, Business Analytics, Replication, Custom Reasoning & Inference Rules, Virtual Database, Virutalized Authentication, and Attribute-based Access Controls Modules, and will utilize a maximum of sixteen (16) processor cores, for one (1) year. Workstation-class Virtuoso 8.x Application Development Progject License for installation (transferable) on one (1) host running any supported Workstation-class OS. Enables five (5) Client Service Threads, the Column Store, Linked Data Middleware, Business Analytics, Replication, Custom Reasoning & Inference Rules, Virtual Database, Virutalized Authentication, and Attribute-based Access Controls Modules, and will utilize a maximum of sixteen (16) processor cores, for one (1) year.
schema:name: Virtuoso 8.x License: 2020-10-virtuoso-8-app-developer-project-WKS-ANY 16 cores
schema:image: n18:OPL-VIRTOFFER-5CON-16CORE.png
schema:offers: n17:caa95a6707c76d6a8600d888ef3cb9ce
schema:brand: OpenLink Virtuoso
rdf:type: schema:Product

Subject Item: n17:87c1192e9d5ba99526f89345a340aaa6
schema:description: Server-class Virtuoso 8.x Initial-Deployment License for installation (transferable) on one (1) host running any supported Workstation- or Server-class OS. Enables ten (10) Client Service Threads, the Column Store, Linked Data Middleware, Business Analytics, Replication, Custom Reasoning & Inference Rules, Virtual Database, Virutalized Authentication, and Attribute-based Access Controls Modules, and will utilize a maximum of sixteen (16) processor cores, for one (1) year. Server-class Virtuoso 8.x Initial-Deployment License for installation (transferable) on one (1) host running any supported Workstation- or Server-class OS. Enables ten (10) Client Service Threads, the Column Store, Linked Data Middleware, Business Analytics, Replication, Custom Reasoning & Inference Rules, Virtual Database, Virutalized Authentication, and Attribute-based Access Controls Modules, and will utilize a maximum of sixteen (16) processor cores, for one (1) year.
schema:name: Virtuoso 8.x License: 2020-10-virtuoso-8-initial-deployment-WKSSVR-ANY
schema:image: n489:OPL-VIRTOFFER-10CON-16CORE.png
schema:offers: n17:afddc5c6ec25e3e1a9ba5473a8032d6e n17:3c93e8cc30e750012ec6ca77fb4a3559
schema:brand: OpenLink Virtuoso
rdf:type: schema:Product

Subject Item: n17:3c93e8cc30e750012ec6ca77fb4a3559
schema:name: Software License Offer: Virtuoso 8.x Workgroup Development License for any Workstation-class or Server-class Operating System
schema:validFrom: 2020-10-31
schema:price: 999
schema:itemOffered: n17:87c1192e9d5ba99526f89345a340aaa6
schema:priceValidUntil: 2022-06-30
rdf:type: schema:Offer

Subject Item: n17:b6c76969d94702d9fae4b75a8489d9c6
schema:name: Software License Offer: Virtuoso 8.x Application Development License for any Workstation-class Operating System
schema:validFrom: 2020-10-31
schema:price: 499
schema:itemOffered: n17:94d8a7056f36b75698f30ce2bd1df3aa
schema:priceValidUntil: 2022-06-30
rdf:type: schema:Offer

Subject Item: n17:caa95a6707c76d6a8600d888ef3cb9ce
schema:name: Software License Offer: Virtuoso 8.x Project Development License for any Workstation-class Operating System
schema:validFrom: 2020-10-31
schema:price: 749
schema:itemOffered: n17:98d2a5f76f4503270f809420f1b54338
schema:priceValidUntil: 2022-06-30
rdf:type: schema:Offer

Subject Item: n453:this
schema:name: Answer to question: What is an ODBC Driver (or Connector)?
schema:category: ODBC UDA JDBC
schema:text: A library that ultimately associates an ODBC compliant application with a specific backend Database Management System. This association can occur via a flexible Data Source Name (DSN) or less flexible direct binding.
rdf:type: schema:Answer

Subject Item: n84:this
schema:name: Answer to question: What is a JDBC Driver (or Connector)?
schema:category: ODBC UDA JDBC
schema:text: A Java library that ultimately associates a JDBC compliant application with a specific backend Database Management System. This association can occur via a flexible Data Source Name (DSN), Uniform Resource Locator (URL), or less flexible direct binding.
rdf:type: schema:Answer

Subject Item: n459:this
schema:name: What is a JDBC Driver (or Connector)?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n84:this

Subject Item: n418:this
schema:name: What is an ODBC Driver (or Connector)?
schema:category: ODBC UDA JDBC
rdf:type: schema:Question
schema:acceptedAnswer: n453:this

Subject Item: n481:this
wdrs:describedby: n473:seo
schema:name: What are users/concurrent sessions?
schema:about: oploffer:VirtuosoOffer
rdf:type: schema:Question
schema:acceptedAnswer: n480:this

Subject Item: n480:this
wdrs:describedby: n473:seo
schema:text: Maximum number of concurrent connections available to any number of user and device network address combinations. For instance, a 5 concurrent sessions license sets up a connection pool for 5 shared by any number of user and device combinations.
rdf:type: schema:Answer

Subject Item: n410:this
wdrs:describedby: n473:seo
schema:name: What is CPU Affinity?
schema:about: oploffer:VirtuosoOffer
rdf:type: schema:Question
schema:acceptedAnswer: n479:this

Subject Item: n479:this
wdrs:describedby: n473:seo
schema:text: CPU Affinity is the maximum number of CPU Cores applies to multi-threaded operations. If you had a machine with 32 CPU cores, a 4 CPU license would allocate up to 4 CPUs for multithreaded operations.
rdf:type: schema:Answer

Subject Item: n486:this
wdrs:describedby: n473:seo
schema:name: Do Virtual and Physical Cores count towards CPU Affinity?
schema:about: oploffer:VirtuosoOffer
rdf:type: schema:Question
schema:acceptedAnswer: n485:this

Subject Item: n485:this
wdrs:describedby: n473:seo
schema:text: Yes, virtual and physical cores both contribute to the total CPU Cores count.
rdf:type: schema:Answer

Subject Item: n484:this
wdrs:describedby: n473:seo
schema:name: Are licenses transferable?
schema:about: oploffer:VirtuosoOffer
rdf:type: schema:Question
schema:acceptedAnswer: n482:this

Subject Item: n482:this
wdrs:describedby: n473:seo
schema:text: Yes, but you cannot have duplicates of the same license copied across serveral machines i.e., the License Manager will flag such license terms violations and stop instances from running.
rdf:type: schema:Answer

Subject Item: n374:this
wdrs:describedby: n473:seo
schema:name: Are licenses host operating system-specific?
schema:about: oploffer:VirtuosoOffer
rdf:type: schema:Question
schema:acceptedAnswer: n475:this

Subject Item: n475:this
wdrs:describedby: n473:seo
schema:text: Entry-level licenses are platform indepenedent. Platform-specific options are available for custom and enterprise license requests.
rdf:type: schema:Answer

Subject Item: n474:this
wdrs:describedby: n473:seo
schema:name: What is a License File?
schema:about: oploffer:VirtuosoOffer
rdf:type: schema:Question
schema:acceptedAnswer: n469:this

Subject Item: n469:this
wdrs:describedby: n473:seo
schema:text: A Digitally Signed ASN.1 document that's processed by the License Manager to determine software behavior.
rdf:type: schema:Answer

Subject Item: n477:this
wdrs:describedby: n473:seo
schema:name: What is the License Manager?
schema:about: oploffer:VirtuosoOffer
rdf:type: schema:Question
schema:acceptedAnswer: n476:this

Subject Item: n476:this
wdrs:describedby: n473:seo
schema:text: Software License enforcement technology.
rdf:type: schema:Answer

Subject Item: n8:whatisajdbcdriver
wdrs:describedby: n473:seo
schema:name: What is a JDBC Driver (or Connector)?
skos:related: n495:this
schema:category: JDBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whatisajdbcdriveranswer

Subject Item: n8:whatisajdbcapplicationorservice
wdrs:describedby: n473:seo
schema:name: What is a JDBC Application or Service?
skos:related: n501:this
schema:category: JDBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whatisajdbcapplicationorserviceanswer

Subject Item: n8:wherecaniobtainodbcdrivers
wdrs:describedby: n473:seo
schema:name: Where Can I Obtain ODBC Driver (or Connectors)?
skos:related: n499:this
schema:category: ODBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:wherecaniobtainodbcdriversanswer

Subject Item: n8:howdoesodbcwork
wdrs:describedby: n473:seo
schema:name: How Does ODBC Work?
skos:related: n498:this n499:this n500:this n503:this n504:this n505:this
schema:category: ODBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:howdoesodbcworkanswer

Subject Item: n8:whatisanodbcdriver
wdrs:describedby: n473:seo
schema:name: What is an ODBC Driver (or Connector)?
skos:related: n499:this
schema:category: ODBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whatisanodbcdriveranswer

Subject Item: n8:whatisodbc
wdrs:describedby: n473:seo
schema:name: What is ODBC?
schema:image: n483:udapcategoryodbc.png
skos:related: n502:this
schema:category: ODBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whatisodbcanswer

Subject Item: n8:whatisodbcanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: What is ODBC?
schema:text: ODBC is short for Open Database Connectivity, an Application Programming Interface and Runtime Middleware that loosely-couples Applications and backend Database Management Systems (DBMS). ODBC was originally created by Microsoft as a Windows-specific API and Runtime component. Over the years it has been successfully ported and deployed across macOS, Linux, and a variety of Unix platforms via projects such as iODBC and unixODBC.
rdf:type: schema:Answer

Subject Item: n8:whyisodbcimportant
wdrs:describedby: n473:seo
schema:name: Why is ODBC important?
skos:related: n502:this
schema:category: ODBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whyisodbcimportantanswer

Subject Item: n8:whyisodbcimportantanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: Why is ODBC important?
schema:text: By loosely-coupling how Applications & Services connect to backend Database Management Systems (DBMS), It provides a powerful solution to the data access and integration problems associated with data silos created by database-specific applications and services.
rdf:type: schema:Answer

Subject Item: n8:whatisanodbcapplicationorservice
wdrs:describedby: n473:seo
schema:name: What is an ODBC Application or Service?
skos:related: n502:this
schema:category: ODBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whatisanodbcapplicationorserviceanswer

Subject Item: n8:whatisanodbcapplicationorserviceanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: What is an ODBC Application or Service?
schema:text: An application or service that leverages ODBC for performing data definition and data manipulation operations, using SQL, in a manner that's independent of backend Database Management Systems (DBMS).
rdf:type: schema:Answer

Subject Item: n8:whatisanodbcdriveranswer
wdrs:describedby: n473:seo
schema:name: Answer to question: What is an ODBC Driver (or Connector)?
schema:text: A library that ultimately associates an ODBC compliant application with a specific backend Database Management System. This association can occur via a flexible Data Source Name (DSN) or less flexible direct binding.
rdf:type: schema:Answer

Subject Item: n8:howdoesodbcworkanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: How Does ODBC Work?
schema:text: In similar fashion to a printer selection interaction experience, it enables a compliant application or service to select a target backend Database Management System (DBMS) via a Data Source Name (DSN) associated with a driver -- basically, a Database Management System (DBMS) replaces a printer in this usage scenario.
rdf:type: schema:Answer

Subject Item: n8:wherecaniobtainodbcdriversanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: Where Can I Obtain ODBC Driver (or Connectors)?
schema:text: ODBC Driver (or Connectors) are provided by Driver Vendors who may be the original Database Management System (DBMS) vendors or 3rd party specialists like OpenLink Software.
rdf:type: schema:Answer

Subject Item: n8:whatisjdbc
wdrs:describedby: n473:seo
schema:name: What is JDBC?
schema:image: n507:7511a81c2e4ec244473cc514d997bd0a.jpg
skos:related: n501:this
schema:category: JDBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whatisjdbcanswer

Subject Item: n8:whatisjdbcanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: What is JDBC?
schema:text: JDBC is short for Java Database Connectivity, an Application Programming Interface and Runtime Middleware that loosely-couples Java Applications and backend Database Management Systems (DBMS).
rdf:type: schema:Answer

Subject Item: n8:whyisjdbcimportant
wdrs:describedby: n473:seo
schema:name: Why is JDBC important?
skos:related: n501:this
schema:category: JDBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:whyisjdbcimportantanswer

Subject Item: n8:whyisjdbcimportantanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: Why is JDBC important?
schema:text: By loosely-coupling how Java Applications & Services connect to backend Database Management Systems (DBMS), It provides a powerful solution to the data access and integration problems associated with data silos created by database-specific applications and services.
rdf:type: schema:Answer

Subject Item: n8:whatisajdbcapplicationorserviceanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: What is a JDBC Application or Service?
schema:text: An application or service that leverages JDBC for performing data definition and data manipulation operations, using SQL, in a manner that's independent of backend Database Management Systems (DBMS).
rdf:type: schema:Answer

Subject Item: n8:whatisajdbcdriveranswer
wdrs:describedby: n473:seo
schema:name: Answer to question: What is a JDBC Driver (or Connector)?
schema:text: A Java library that ultimately associates a JDBC compliant application with a specific backend Database Management System. This association can occur via a flexible Data Source Name (DSN), Uniform Resource Locator (URL), or less flexible direct binding.
rdf:type: schema:Answer

Subject Item: n8:howdoesjdbcwork
wdrs:describedby: n473:seo
schema:name: How Does JDBC Work?
skos:related: n495:this n496:this n497:this
schema:category: JDBC
schema:creator: n466:this
schema:dateCreated: 2021-11-24T18:14:00Z
rdf:type: schema:Question
schema:acceptedAnswer: n8:howdoesjdbcworkanswer

Subject Item: n8:howdoesjdbcworkanswer
wdrs:describedby: n473:seo
schema:name: Answer to question: How Does JDBC Work?
schema:text: In similar fashion to a printer selection interaction experience, it enables a compliant application or service to select a target backend Database Management System (DBMS) via a Data Source Name (DSN) or URL associated with a driver -- basically, a Database Management System (DBMS) replaces a printer in this usage scenario.
rdf:type: schema:Answer

Subject Item: n47:VirtVisualizeWithPivotViewerQuestion
wdrs:describedby: n473:seo
schema:name: How do I explore Linked Data using the Microsoft Pivot Viewer?
schema:category: n93:this
schema:relatedLink: n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtVisualizeWithPivotViewerAnswer

Subject Item: n47:VirtVisualizeWithHtmlPivotViewerQuestion
wdrs:describedby: n473:seo
schema:name: How do I explore Linked Data using the HTML5-based Pivot Viewer?
schema:category: n93:this
schema:relatedLink: n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtVisualizeWithHtmlPivotViewerAnswer

Subject Item: n47:VirtRdb2RDFViewsGenerationQuestion
wdrs:describedby: n473:seo
schema:name: How do I use just one click on Virtuoso's HTML-based Wizard to Generate and Deploy RDF-based Linked Data from Relational Databases?
schema:category: n471:this n513:this n502:this n501:this n515:this
schema:relatedLink: n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtRdb2RDFViewsGenerationAnswer

Subject Item: n47:VirtR2RMLQuestion
wdrs:describedby: n473:seo
schema:name: How do I use R2RML to map RDB to RDF with Virtuoso?
schema:category: n471:this n513:this n502:this n501:this n515:this
schema:relatedLink: n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtR2RMLAnswer

Subject Item: n47:VirtLinkRemoteTablesQuestion
wdrs:describedby: n473:seo
schema:name: How do I attach the Virtuoso Virtual Database Engine to ODBC- or JDBC-accessible Data Sources?
schema:category: n471:this n502:this n501:this
schema:relatedLink: n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtLinkRemoteTablesAnswer

Subject Item: n47:VirtDeployingLinkedDataGuideQuestion
wdrs:describedby: n473:seo
schema:name: How do I use Virtuoso to deploy Linked Data to the Web?
schema:category: n93:this
schema:relatedLink: n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtDeployingLinkedDataGuideAnswer

Subject Item: n47:VOSSQL2RDFQuestion
wdrs:describedby: n473:seo
schema:name: How do I create RDF-based Linked Data Views over Relational Data Sources?
schema:category: n471:this n513:this n502:this n501:this n515:this
schema:relatedLink: n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VOSSQL2RDFAnswer

Subject Item: n47:ScaleQuestion
wdrs:describedby: n473:seo
schema:name: What is the Virtuoso strategy to scale? Is it possible to start small and then add servers if needed?
schema:category: n461:this n460:this n463:this n465:this n462:this n467:this
schema:relatedLink: n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:ScaleAnswer

Subject Item: n47:PlansCloudQuestion
wdrs:describedby: n473:seo
schema:name: Are there any Virtuoso plans for Cloud technologies (Openstack, etc.)?
schema:category: n462:this n463:this n464:this n465:this n461:this n478:this
schema:relatedLink: n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:PlansCloudAnswer

Subject Item: n47:ManageClusterQuestion
wdrs:describedby: n473:seo
schema:name: Do I have to stop the cluster to add a node or partition an index?
schema:category: n463:this n465:this n462:this n467:this n460:this n461:this
schema:relatedLink: n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:ManageClusterAnswer

Subject Item: n47:FederationTripleStoreQuestion
wdrs:describedby: n473:seo
schema:name: When will federation of triple stores be available in Virtuosoand how does it compare to clustering?
schema:category: n462:this n463:this n465:this n461:this n460:this n63:this n60:this
schema:relatedLink: n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:FederationTripleStoreAnswer

Subject Item: n47:EvaluatingNoSQLDBQuestion
wdrs:describedby: n473:seo
schema:name: Is Virtuoso currently evaluating NoSQL database for the storage of quads?
schema:category: n516:this n517:this n518:this
schema:relatedLink: n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:EvaluatingNoSQLDBAnswer

Subject Item: n47:ClusterConfigDifQuestion
wdrs:describedby: n473:seo
schema:name: What is the differences in terms of performance/scalability between 2 cluster configurations?
schema:category: n462:this n463:this n460:this n461:this
schema:relatedLink: n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:ClusterConfigDifAnswer

Subject Item: n47:VirtSparqlCxmlQuestion
wdrs:describedby: n473:seo
schema:name: How do I use SPARQL to dynamically generate CXML collections for the Microsoft or HTML5-based PivotViewer?
schema:category: n519:this
schema:relatedLink: n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtSparqlCxmlAnswer

Subject Item: n47:ClusterConfigDifAnswer
wdrs:describedby: n473:seo
schema:text: Configuration A: 4 cluster nodes, 3 instances per cluster node (quorum), 1 instance per host cluster node, 12 host cluster nodes. Configuration B: 4 cluster nodes, 3 instances per cluster node (quorum), 4 instances per host cluster node, 3 host cluster nodes. Performance has more to do with the number of Virtuoso Server processes running on each cluster node. One instance per cluster node will work better than four instances per cluster node. You will have more OS resources available as the Virtuoso instances are reduced. Ideally, you want to spread the instances over distinct machines so that you have resources pooled across those machines.
rdf:type: schema:Answer

Subject Item: n47:EvaluatingNoSQLDBAnswer
wdrs:describedby: n473:seo
schema:text: Virtuoso is a Native Hybrid DBMS it is SQL and NoSQL combined.
rdf:type: schema:Answer

Subject Item: n47:FederationStatusAnswer
wdrs:describedby: n473:seo
schema:text: Virtuoso has supported Federated SPARQL a/k/a SPARQL-FED since the specification was created.
rdf:type: schema:Answer

Subject Item: n47:FederationTripleStoreAnswer
wdrs:describedby: n473:seo
schema:text: Virtuoso has supported Federated SPARQL a/k/a SPARQL-FED since the specification was created. Clustering has more to do with horizontal partitioning of the database across many machines (physical or virtual) to parallelize execution of queries, etc. SPARQL-FED may be used with a Virtuoso Cluster, just as with a Single-Server Instance.
rdf:type: schema:Answer

Subject Item: n47:HighAvailAndRecoverAnswer
wdrs:describedby: n473:seo
schema:text: You can use replication for HA across Elastic Clusters or Single-Server instances. For example, nearly-instantaneous Transactional Replication is used by some of our larger customers (e.g., Globo of Brazil used a Transactional Replication setup for the entire World Cup 2014 without any issues).
rdf:type: schema:Answer

Subject Item: n47:ManageClusterAnswer
wdrs:describedby: n473:seo
schema:text: If the "elastic cluster" option is enabled at DB creation time, adding nodes and repartitioning indexes can be done without stopping the cluster.
rdf:type: schema:Answer

Subject Item: n47:PlansCloudAnswer
wdrs:describedby: n473:seo
schema:text: Virtuoso Open Source Edition (VOS) is part of the LOD2 OpenStack deliverables, but this does not include Enterprise Edition features (i.e., no replication clustering, elastic clustering, fine-grained ABAC security, nor virtual DBMS functionality for making RDF views over external SQL data sources). That said, Virtuoso (both Open Source and Enterprise) may be instatiated on cloud services, including Amazon EC2.
rdf:type: schema:Answer

Subject Item: n47:ScaleAnswer
wdrs:describedby: n473:seo
schema:text: Yes. You start with Single-Server, enable the Elastic Cluster optionand then add nodes as scalability demands increase.
rdf:type: schema:Answer

Subject Item: n47:VOSSQL2RDFAnswer
wdrs:describedby: n473:seo
schema:text: This page discusses the basics of creating RDF-based Linked Data Views over Relational Data Sourcesand links to several other pages with specific guides for various local and remote (ODBC- and JDBC-accessible) data sources.
rdf:type: schema:Answer

Subject Item: n47:VirtDeployingLinkedDataGuideAnswer
wdrs:describedby: n473:seo
schema:text: This page discusses some of the difficulties faced in exposing RDF data and in bridging the "Linked Data Web" and the traditional "Document Web". Two generic approaches to resolving these deployment challenges content negotiation and URL rewriting are described, before looking at OpenLink Virtuoso, from the standpoint of both how it implements these solutions and how Linked Data is deployed.
rdf:type: schema:Answer

Subject Item: n47:VirtFacetBrowserInstallConfigAnswer
wdrs:describedby: n473:seo
schema:text: See required prerequisites, pre-installation steps, VAD package installation, post-installation stepsand example tutorials.
rdf:type: schema:Answer

Subject Item: n47:VirtLinkRemoteTablesAnswer
wdrs:describedby: n473:seo
schema:text: See OpenLink How-To guides to learn how to connect Virtuoso's Virtual Database Engine to local or remote data sources including Firebird, DB2, Informix, Ingres, MySQL, Microsoft SQL Server, Oracle, PostgreSQL, Progress, Sybaseand others accessible by ODBC or JDBC. (Note JDBC requires an ODBC-to-JDBC Bridge, which OpenLink may also supply.)
rdf:type: schema:Answer

Subject Item: n47:VirtR2RMLAnswer
wdrs:describedby: n473:seo
schema:text: R2RML, a W3C Recommendation, is a language for expressing customized mappings from relational databases to RDF data sets. Such mappings provide the ability to view existing relational data in the RDF data model, expressed in a structure and target vocabulary of the mapping author's choice. R2RML mappings are themselves RDF graphs written in Turtle syntax. R2RML is becoming the generic standard adopted by most vendors of tools mapping relational data to RDF, enabling the interoperability of R2RML scripts, whether created with such tools or by hand. This page discusses how to use R2RML specifically with Virtuoso.
rdf:type: schema:Answer

Subject Item: n47:VirtRdb2RDFViewsGenerationAnswer
wdrs:describedby: n473:seo
schema:text: See example of One-Click Linked Data Generation & Deployment of Linked Data Views over Relational Data Sources with Virtuoso.
rdf:type: schema:Answer

Subject Item: n47:VirtSparqlCxmlAnswer
wdrs:describedby: n473:seo
schema:text: See OpenLink How-To guide that demonstrates the generation of CXML-based output from SPARQL queries. This output is then used as input for the Microsoft or HTML5-based PivotViewer.
rdf:type: schema:Answer

Subject Item: n47:VirtVisualizeWithHtmlPivotViewerAnswer
wdrs:describedby: n473:seo
schema:text: See OpenLink How-To guide that showcases how to use a Virtuoso hosted instance of the Microsoft PivotViewer as a Linked Data front-end for follow-your-nose data exploration.
rdf:type: schema:Answer

Subject Item: n47:VirtVisualizeWithPivotViewerAnswer
wdrs:describedby: n473:seo
schema:text: See OpenLink How-To guide that showcases how to use a Virtuoso hosted instance of the Microsoft PivotViewer as a Linked Data front-end for follow-your-nose data exploration.
rdf:type: schema:Answer

Subject Item: n47:FederationStatusQuestion
wdrs:describedby: n473:seo
schema:name: What is the current status of development for Virtuoso federation of triple stores?
schema:category: n60:this n63:this
schema:relatedLink: n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:FederationStatusAnswer

Subject Item: n47:HighAvailAndRecoverQuestion
wdrs:describedby: n473:seo
schema:name: What are the best options to offer High-Avaliability and Disaster Recovery? Is it possible to move data from one datacenter to another and how is data transferred? Are there any numbers about the speed of data replication between two datacenters and consistency of the process?
schema:category: n460:this n461:this n462:this n463:this n464:this n465:this
schema:relatedLink: n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:HighAvailAndRecoverAnswer

Subject Item: n47:VirtFacetBrowserInstallConfigQuestion
wdrs:describedby: n473:seo
schema:name: How do I install and configure the Virtuoso Faceted Browser?
schema:category: n93:this
schema:relatedLink: n47:FederationStatusAnswer n47:FederationTripleStoreAnswer n47:HighAvailAndRecoverAnswer n47:ManageClusterAnswer n47:PlansCloudAnswer n47:ScaleAnswer n47:VOSSQL2RDFAnswer n47:VirtDeployingLinkedDataGuideAnswer n47:VirtFacetBrowserInstallConfigAnswer n47:VirtLinkRemoteTablesAnswer n47:VirtR2RMLAnswer n47:VirtRdb2RDFViewsGenerationAnswer n47:VirtSparqlCxmlAnswer n47:VirtVisualizeWithHtmlPivotViewerAnswer n47:VirtVisualizeWithPivotViewerAnswer n47:ClusterConfigDifAnswer n47:EvaluatingNoSQLDBAnswer
schema:creator: n466:this
schema:dateCreated: 2019-01-30T10:00:00-05:00
schema:dateModified: 2021-12-16T13:38:00-05:00
rdf:type: schema:Question
schema:acceptedAnswer: n47:VirtFacetBrowserInstallConfigAnswer