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

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

Namespace Prefixes

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

Statements

Subject Item
n2:this
wdrs:describedby
n5:uda-faq.ttl n6:uda-faq.ttl
rdf:type
schema:Answer
schema:answerExplanation
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.