Oracle® Secure Enterprise Search

Creating MDS Schema using RCU

To create the MDS schema using RCU:

1. Download the following utility (in the zip archive format) from ARU:

   • V18736-01: Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.2.0) for Linux x86.

2. Extract all the files from the above zip archive into a destination folder.

3. Navigate to destination folder/rcuHome/bin.

4. Set the appropriate values for the following environment variables related to the Oracle SES instance:

   HOSTNAME
   DB_PORT
   ORACLE_SID
   

5. Run the following RCU command to create the database schema. Provide the password for the sysdba user and the password for the newly created MDS schema:

   ./rcu -silent -createRepository -connectString $HOSTNAME:$DB_PORT:$ORACLE_SID -dbUser sys -dbRole sysdba -schemaPrefix DEV -component MDS
   

6. If RCU command fails with the error message "Got minus one from a read call", then open the $ORACLE_HOME/network/admin/sqlnet.ora file in a text editor and update the value for the tcp.invited_nodes parameter by assigning it the name of the host computer from where you are running the RCU.

   For example, if you are running the RCU from the host computer host123, then assign the variable value as follows:

      tcp.invited_nodes=(host123.us.xyz.com,127.0.0.1,host789)
   

   After updating the sqlnet.ora file, save it, and restart the database listener.

Setting Up Database Connection Information using WebLogic Server Administration Console

To setup the database connection information using Oracle WebLogic Server Administration Console:

1. Log on to the Oracle WebLogic Server Administration Console (http://host:port/console).

2. Set the domain instance to Lock & Edit mode.

3. In the left navigation menu, select Services > JDBC > Data Sources.

4. Replace the value of mds-owsm > Connection Pool with the appropriate values:

   • URL: jdbc:oracle:thin:@$HOSTNAME:$DB_PORT:$ORACLE_SID

   • Driver: oracle.jdbc.OracleDriver

   • Properties:

        user=dev_mds
        oracle.net.CONNECT_TIMEOUT=10000
     

   • Password: The password provided during creating the MDS schema described in step 5 of "Creating MDS Schema using RCU".

5. Click Activate Changes.

6. Restart the Oracle WebLogic Server by running the following command:

   $ORACLE_HOME/bin/searchctl restart admin_passwd="SES Admin password"
   

Verifying OWSM Setup

To verify the OWSM setup:

1. Log on to the Oracle WebLogic Server Administration Console (http://host:port/console).

2. In the left navigation menu, select Deployments > wsm-pm > Testing.

3. Expand the entry /wsm-pm and click the default Test Point link. The Policy Manager Validator page is displayed.

4. On the Policy Manager Validator page, click Validate Policy Manager. The OWSM setup is successful, if the Policy Manager Validator page displays a list of policies.

Desupport of V1 Agent

The V1 Agent, called the Crawler Agent API in Oracle Ultra Search, is desupported in Oracle SES release 11.1.2.2 (The V1 Agent is the predecessor of the current crawler plug-in API in Oracle SES.)

Deprecated Public Web Services

The Oracle SES 10g Administration API is deprecated in this release (searchadminctl and the associated Web services). The Oracle SES release 11.1.2.2 Administration API replaces it. Therefore, the following public Web services are deprecated in this release:

• oracle.search.admin.ws.client.SearchAdminClient

  The operations for this service include:

  • getEstimatedIndexFragmentation

  • getSchedules

  • getScheduleStatus

  • optimizeIndexNow

  • startSchedule

  • stopSchedule

  • login

  • logout

• oracle.search.admin.ws.client.Schedule

• oracle.search.admin.ws.client.ScheduleStatus

Deprecated Connectors

The following connectors are deprecated in this release, so that maintenance will be provided only when issues are raised by existing customers. No active development, testing, or certification will be provided for any of these connectors.

• FileNet Image Server

• FileNet P8 Content Engine

• Open Text LiveLink Enterprise Server

• Hummingbird DM

• IBM DB2 Content Management

Installation Issues

This section contains known issues for this release that affect installation.

8503413: RUNINSTALLER DOES NOT HONOR THE -IGNORESYSPREREQS FLAG

In interactive or silent mode, the -ignoreSysPrereqs flag is ignored and runInstaller performs the checks for system prerequisites.

Workaround: Execute runInstaller as in the following example:

./runInstaller -ignoreSysPrereqs -silent -debug -responseFile ~/upgrade.rsp

You must specify a response file if you use the -responseFile flag. The ignoreSysPrereqs flag skips the very first, initial system prerequisite check, which checks swap, memory, and color depth.

9295102: INSTALLATION FAILS WITH ORA-01031 WHEN PASSWORD IS MULTI-BYTE

The installation fails with an ORA-01031 error when multibyte characters are entered for the administrator password.

Workaround: Enter only ASCII characters for the password.

12719964: INVALID ORACLE SES SOFTWARE INSTALL LOCATION ENTRY RESULTS IN INCORRECT INSTALL SCREEN REDIRECTION ON WINDOWS OPERATING SYSTEMS

When an invalid software install location is provided during the Oracle SES installation process, the installer displays the following error message:

OUI-10150:Error:You must enter a value for Search Admin Password in component
Oracle Secure Enterprise Search 11.1.2.2.0. Installation
can not continue for this component.

If you navigate back using the installation wizard to rectify the software install location, the installation wizard page containing the software install location does not show the administrator password entry.

Workaround: Exit the Oracle SES installer by canceling the installation process. Start the installation process again and provide a valid software install path.

13998112: THE "ROOTPRE.SH" SCRIPT FILE AND "ROOTPRE" DIRECTORY ARE MISSING IN THE SES 11.1.2.2 MEDIA FOR THE IBM AIX PLATFORM

In the SES 11.1.2.2 software for the IBM AIX platform, the "rootpre" files (the "rootpre.sh" script and "rootpre" directory) are missing from the media (the actual DVDs, and the SES software download available on the websites - http://edelivery.oracle.com and http://www.oracle.com/technetwork). The "rootpre" files are required only for the IBM AIX platform, and the script "rootpre.sh" should be run during the first time installation of an Oracle product on an IBM AIX system.

Workaround: Follow the instructions provided at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1454237.1 to obtain the "rootpre" files.

16327495: INSTALLATION FAILS ON SERVER HAVING LARGE NUMBER OF CPUs

On a server with large number of CPUs, such as 32 CPUs, the Oracle SES installation fails during the "Oracle Database Configuration Assistant" wizard page with the following error messages:

ORA-12801: error signaled in parallel query server P050
ORA-00018: maximum number of sessions exceeded
ORA-06512: at "SYS.UTL_RECOMP", line 760
ORA-06512: at "SYS.UTL_RECOMP", line 773
ORA-06512: at line 1

This error occurs because the values provided for the Database configurations - maximum number of Database processes and maximum number of Database sessions - in the Database template file General_Purpose.dbc are very low (such as 150), and these Database configurations must be assigned a mush higher value, such as 1500.

Workaround: The following are the steps to solve this issue:

1. Exit the Oracle SES installation wizard.

2. Go to the root directory (example, installImageDir directory) where you unzipped the Oracle SES installation software zip file after downloading/copying it from the media (DVD or Oracle website).

3. Update the Database configurations file General_Purpose.dbc. Following are the steps to achieve this:

   1. Go to the "DataFiles" directory:

      $ cd stage/Components/oracle.search.seeddb/11.1.2.2.0/1/DataFiles
      

   2. Create a temporary directory "tmp" under the "DataFiles" directory:

      $ mkdir tmp
      

   3. Move the file "filegroup2.jar" to the "tmp" directory:

      $ mv filegroup2.jar tmp
      

   4. Go to the "tmp" directory and unjar the "filegroup2.jar" file:

      $ cd tmp
      $ jar -xvf filegroup2.jar
      

   5. Open the file assistants/dbca/templates/General_Purpose.dbc in a text editor, example:

      $ vi assistants/dbca/templates/General_Purpose.dbc
      

   6. Search for the parameter "processes" and change its value from 150 to 1500:

      <initParam name="processes" value="1500"/>
      

   7. Add a new parameter "sessions" by adding a line next to the "processes" parameter, and set its value to 1500:

      <initParam name="processes" value="1500"/>
      <initParam name="sessions" value="1500"/>
      

   8. Recreate the jar file "filegroup2.jar" from the "tmp" directory:

      $ rm filegroup2.jar
      $ jar -cvf filegroup2.jar *
      

   9. Move the "filegroup2.jar" file to its orignal place, that is, to the "DataFiles" directory, which is the parent directory of the "tmp" directory (where you currently are):

      $ mv filegroup2.jar ..
      

   10. Go to the "DataFiles" directory (parent directory of the "tmp" directory) and remove the "tmp" directory:

       $ cd ..
       $ /bin/rm -rf tmp
       

       Make sure that the "DataFiles" directory now contains the updated "filegroup2.jar" file.

4. Go to the installImageDir directory (mentioned in Step 2) and run the runInstaller command to start the Oracle SES installation process.

Upgrade Issues

This section lists known issues that affect the upgrade process.

8662950: VERSION OF IDENTITY PLUGIN IS 10.1.8.2.0 IN UPGRADE INSTANCE

In Oracle SES 11.1.2.2, when identity plug-in configuration is exported using the Oracle SES Administration API searchadmin, the release number (also referred to as version number) of a few identity plug-ins may be incorrect in the exported XML. Only the release number string of a few identity plug-ins are affected in the exported XML. This does not have any impact on the identity plug-in itself.

Workaround: The release number string will be displayed correctly in the Oracle SES Administration UI on importing the same XML into an Oracle SES 11.1.2.2 instance.

9261343: CDB PERFORMS FORCED CRAWL AFTER UPGRADE EVEN IF MODE IS INCREMENTAL

Content Database Source (CDB) executes a forced crawl even though the mode is set to incremental after the upgrade. This happens only during the first crawl performed immediately after upgrade (CDB indexes all documents even when mode is set as incremental and no changes are made on the repository side).

Workaround: There is no workaround.

9290561: MIGRATE_10184_SECURITY_DATA FAILED

Trusted entities that were created in Oracle SES 10.1.8.0 cause an error during the last stage of the upgrade:

ORA-28817: PL/SQL function returned an error. 
ORA-06512: at "SYS.DBMS_CRYPTO_FFI", line 67 
ORA-06512: at "SYS.DBMS_CRYPTO", line 44 
ORA-06512: at "EQSYS.DEOBFUSCATE", line 10

Workaround: Delete all trusted entities before starting the upgrade. Use the Oracle SES Administration UI to delete them, or take these steps:

1. Open SQL*Plus and connect as eqsys.

2. Run the EQ_ADMIN.USE_INSTANCE procedure:

   EXECUTE eq_adm.use_instance(1);
   

3. Delete the trusted entities:

   DELETE FROM eq$trusted_entity;
   

4. Save the changes:

   COMMIT;
   

5. After the upgrade is complete, re-create the trusted entities.

9326121: POST 10G-11.1.2 UPG ZONE-TO-FIELD CONVERSION CAN TAKE EXTRA TIME WITH A LARGE NUMBER OF DOCUMENT ATTRIBUTES

The post-upgrade script enable_ses1112_improve.sql performs the zone-to-field conversion very slowly.

Workaround: There is no workaround.

9336801: POST-UPGRADE SCRIPT REQUIRES LARGE AMOUNT OF DISK SPACE

Running post-upgrade script enable_ses1112_improve.sql requires a large amount of disk space.

Workaround: Before upgrading Oracle SES from 10.1.8.4.0 to 11.1.2.2, download Oracle SES patch 9403944 to estimate the disk space required to run enable_ses1112_improve.sql.

9374665: ORA- ERRORS IN INSTALL LOG FOR 10.1.8.4 -> 11.1.2.2 UPGRD

Miscellaneous ORA errors appear in the install log after upgrading. These also appear in seshome/cfgtoollogs/searchctl_install.log. For example:

.... creating policy for markup
begin
*
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-10700: preference does not exist: eq_filter
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.CTX_DDL", line 954
ORA-06512: at line 2

Workaround: These errors can be safely ignored.

11818382 : 11.1.2.2_LIN.X64_RC2: ORA-04043 ERROR IN SEARCHCTL_INSTALL LOG FOR UPGRD

ORA-04043 error appears in the install log (seshome/cfgtoollogs/searchctl_install.log) after upgrading.

... drop temporary procs
drop procedure repos_mkdir_p
*
ERROR at line 1:
ORA-04043: object REPOS_MKDIR_P does not exist

Workaround: This error can be safely ignored.

9740780: UPGRADE TAKES VERY LONG TIME FOR LARGE INDEX

An upgrade appears to hang during processing of a very large eq$cache table on Linux and UNIX platforms.

Workaround: Install patch 9740780 during the upgrade, as described in "Patch 9740780 Upgrade Instructions".

11839505: 11122LNXRC2UPG1112: AUDIT_FILE_DEST IN THE UPGRDED SES INSTANCE IS DEPENDENT ON THE OLD SES INSTANCE

After upgrading from Oracle SES 11.1.2 to Oracle SES 11.1.2.2, the fields audit_file_dest and db_recovery_file_dest in the upgraded Oracle SES instance file sesupd1/seshome/dbs/initses1.ora are still dependent on the files in the old Oracle SES instance. The upgraded Oracle SES instance does not work if these dependent files are removed from the old Oracle SES instance.

Workaround: Do not remove the original SEARCH_BASE after running the deinstall_ses script to deinstall the old Oracle SES instance. Specifically, the admin and the flash_recovery_area directories must be retained.

9130467: PRE-11.1.2 UPGRADE PATCH HISTORY NOT PRESERVED FROM 10G

The Opatch lsinventory does not return all patch history carried over from earlier releases.

Workaround: In order to see the history for earlier instances, you must query each Oracle home and print or note the history. Additionally, after you have verified that the upgraded Oracle SES 11g instance is working, you may remove the Oracle SES 10g home. See Oracle Secure Enterprise Search Installation and Upgrade Guide for Linux for procedures.

11798419 and 12629799: DEINSTALL OF OLD SES HOME MAKES THE UPGRADED SES HOME NON-FUNCTIONAL

During upgrade from Oracle SES 10.1.8.4/11.1.2.0 to Oracle SES 11.1.2.2, when the old Oracle SES instance (10.1.8.4/11.1.2.0) is deinstalled, the new upgraded Oracle SES instance (11.1.2.2) becomes non-functional.

This happens because after deinstalling the old Oracle SES instance (10.1.8.4/11.1.2.0), the contents of oradata directory get deleted, making the new upgraded Oracle SES instance (11.1.2.2) non-functional.

Workaround: Download the patch 11798419 from ARU and install it. This patch is available as a zip file having the following details:

• 11798419_10184.zip - Use this patch file when upgrading from Oracle SES 10.1.8.4 instance to Oracle SES 11.1.2.2 instance.

• 11798419_11120.zip - Use this patch file when upgrading from Oracle SES 11.1.2.0 instance to Oracle SES 11.1.2.2 instance.

See Oracle Secure Enterprise Search Installation and Upgrade Guide for Linux for more information on the steps for upgrading from Oracle SES 10.1.8.4/11.1.2.0 to Oracle SES 11.1.2.2.

9298458: ORACLE TEXT ERRORS IN UPGRADE LOG

This Oracle Text error appears twice in the installActions log:

ORA-20000: Oracle Text error: 
DRG-10700: preference does not exist: eq_filter

Workaround: Ignore these errors. They do not affect the upgrade.

11890791: INVALID OBJECT EQ$INDEX_TOKENS AFTER UPGRADING FROM SES 11.1.2.0 TO SES 11.1.2.2

The status of EQ$INDEX_TOEKNS view becomes INVALID after upgrading from Oracle SES 11.1.2.0 to Oracle SES 11.1.2.2.

Workaround: You may ignore this, as there is no functionality impact because of the invalid EQ$INDEX_TOEKNS view.

12679253: ERROR WHEN RUNNING THE POST-UPGRADE SCRIPT WHILE UPGRADING FROM SES 10.1.8.4 TO SES 11.1.2.2

When running the post-upgrade script enable_SES1112_improve.sql while upgrading from Oracle SES 10.1.8.4 to Oracle SES 11.1.2.2, the following error message is displayed on the command line:

ERROR occurs during executing eqpostupg1112.z2f.
ORA-01489: result of string concatenation is too long
declare
*
ERROR at line 1:
ORA-20000: Fatal error in eqpostupg1112.z2f
ORA-06512: at line 19

This error occurs when the Oracle SES 10.1.8.4 instance contains very large string custom attribute values (> 3979 bytes).

Workaround: To solve this issue, restore the Oracle SES 10.1.8.4 instance, install the patch 12679253, and run the post-upgrade script enable_ses1112_improve.sql.

9340427: ERROR WHEN RUNNING THE POST-UPGRADE SCRIPT ENABLE_JAPANESE_BIGRAM.SQL WHILE UPGRADING FROM SES 10.1.8.4 TO SES 11.1.2.2

When running the post-upgrade script enable_Japanese_bigram.sql while upgrading from Oracle SES 10.1.8.4 to Oracle SES 11.1.2.2, the following error message is displayed on the command line:

*** ERROR ***
Unexpected error occurred.
ORA-01422: exact fetch returns more than requested number of rows

This error occurs when the source parameter Preserve Document Cache is configured in the Oracle SES Administration UI. Due to this error, the information about the sources that have Japanese documents is not available for performing the full crawl.

Workaround: After displaying the above mentioned error message, the script also displays a message prompting you to either enter "yes" to proceed executing the remaining part of the script, or enter any other character to exit the script execution. Enter "yes" on the command line. When the script execution is complete, run the following SQL commands in SQL*Plus after connecting as EQSYS user.

select ds_name
from eq$data_source
where ds_id in (
       select distinct ds_id from eq_test.eq$doc
where lang = 'ja');

The output of the above SQL commands shows all the sources that have Japanese documents. Now you can do the full crawl for these sources.

Open Bugs

This section lists the general known bugs for this release.

6934015 and 10013814: IPv6 COMPATIBILITY ISSUE

This issue is applicable for all the operating systems supported by Oracle SES.

If your operating system supports Internet Protocol version 6 (IPv6), then under some circumstances, this may lead to the failure in starting up the Oracle SES middle tier (Oracle WebLogic Server).

Workaround:

If IPv6 is enabled on your operating system, then disable it before installing Oracle SES.

Following are the steps to disable IPv6 on Linux and Windows operating systems. For disabling IPv6 on other operating systems, refer to your operating system specific documentation.

For Linux:

Comment the IPv6 entries in the /etc/hosts file as shown below:

# special IPv6 addresses 
# ::1             localhost ipv6-localhost ipv6-loopback 
 
# fe00::0         ipv6-localnet 
 
# ff00::0         ipv6-mcastprefix 
# ff02::1         ipv6-allnodes 
# ff02::2         ipv6-allrouters 
# ff02::3         ipv6-allhosts 
 

For Windows:

Disable all the IPv6 components, except the IPv6 loopback interface, as explained below:

1. Click Start, enter regedit in the Start Search box, and then click regedit.exe in the Programs list.

2. In the User Account Control dialog box, click Continue.

3. In Registry Editor, locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\.

4. Double-click DisabledComponents to modify the DisabledComponents entry.

   Note:

   If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:

   1. From the Edit menu, select New, then select DWORD (32-bit) Value.

   2. Enter DisabledComponents, and then press ENTER.

   3. Double-click DisabledComponents.

5. Enter 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface.

6. Click OK.

For more information on disabling the IPv6 components on Windows, refer to the Microsoft website: http://support.microsoft.com/kb/929852.

6400299: RICH QUERY UI DOES NOT RENDER CORRECTLY FOR BIDIRECTIONAL LANGUAGES

The new Rich Query UI in this release does not support correct rendering for bidirectional languages (for example, Arabic and Hebrew).

Workaround: There is no workaround.

6860280: ISSUE WITH THE PARAMS OF THE TOPIC CLUSTERING METADATA EXTRACTION

Two query-time clustering parameters under Global Settings/Clustering Configuration do not work. Under Single Word Extraction: Minimum occurrence and Maximum number of words to extract do not work. Under Phrase Extraction: Minimum occurrence and Maximum number of phrases to extract do not work.

Workaround: There is no workaround.

7456946: CHINESE DISPLAYED INCORRECTLY IN SUGGESTED CONTENT

Under certain scenarios, content with Chinese character set does not display correctly. See the bug for scenario and setup.

Workaround: There is no workaround.

7488403: GARBAGE CODE IS DISPLAYED WHEN CRAWL A PDF FILE FROM OTN

Characters in PDF documents with custom-encoded fonts do not index correctly. This is a known limitation in Oracle Text. Oracle Text, and therefore Oracle SES, cannot determine the countless ways that embedded fonts might have been customized. To see if this issue is the cause for displaying garbage in a PDF, in Acrobat Reader click File and Properties, and select the Fonts tab. You can verify that custom-encoded fonts are the cause of this issue.

Workaround: Avoid using custom-encoded fonts when creating PDF documents. There is no workaround for viewing PDF documents that were created using custom-encoded fonts.

8659019: INTERNAL QUERY SYNTAX ERROR OCCURS WHEN SEARCHING FOR ATTRIBUTE TAG

Tag attribute search is not supported in Oracle SES 11.1.2 (in fresh installations and in upgraded installations). For example, TAG:="info" fails and generates an error:

Internal query syntax error

Workaround: Do not search on Tag attribute.

8982493: SES MIDDLE TIER START/STOP WARNING MESSAGES (SECURITY NOTICE BEA-090898)

Security warnings appear when connecting to the node manager with WebLogic as the Oracle SES middle tier. This is because WebLogic does not recognize the CA certificates from the middle tier of the earlier Oracle SES release.

Workaround: Ignore the warning messages in the log. If you are concerned about the log indicating the warnings, remove the offending CA certificates from the truststore (or keystore). By default, Oracle WebLogic Server is configured with DemoTrust.jks and ignores the JDK CA certificate trust stores. Therefore, removing the offending CA certs from the JDK CA certs file should cause the warning to cease.

Alternatively, the following solution may be applied.

Set the Dweblogic.StdoutSeverityLevel system property to limit the number of warnings:

-Dweblogic.StdoutSeverityLevel=16

(Or substitute a lower number depending on how many messages you want to display, such as 8, 4, 2,1.)

9091672: CANNOT OBTAIN XACONNECTION, NO RESOURCES LEFT IN ENTERPRISESEARCHDS

When XA Connection is enabled and seems to not be efficiently utilized by Oracle SES, an exception is thrown while creating a connection for pool EnterpriseSearchDS. The listener refuses the connection with the following error:

ORA-12528, TNS:listener: All appropriate instances are blocking new connections

By default the min and max values of JDBC connection pool capacity are 20/100. In extreme scenarios (>= 1500 concurrent users, >= 2 million docs/50 GB content size), and especially where the hardware specification is less than 4 CPUs and 16 GB RAM, available resources will not be able to handle new connections. In this case, tuning the values to 200/200 can provide a solution.

Workaround: XA Connections will eventually get freed up when traffic subsides. If this is a recurring issue, then consider tuning the Oracle WebLogic Server's JDBC Connection Pool max and min capacity values, for example, to something like 200/200. See Oracle Database Performance Tuning Guide for procedures.

9112217: IMPDP FAILED FOR PARTITIONED TGT, ORA-00059: MAX # OF DB_FILES EXCEEDED

If the deployment has a large number of DBFs under ORADATA that are pushing above the limits of the db_files value, then impdp of multi-source dump into the target Oracle SES instance fails.

Workaround: Update init.ora to increase the value of db_files to something like 10% more than the current DBF count.

9154080: SEARCHCTL RESTART TAKES APPROXIMATELY 2.5 MINUTES

The searchctl restart takes about 2.5 minutes to complete in this release. This is due to integration with Oracle WebLogic Server, which provides substantially more services. (The previous Oracle SES release used OC4J.)

Workaround: There is no workaround.

9192452: PORTLET- REDIRECT PAGE SHOWS UNAVAILABLE CONTENT FOR FILE ETC SOURCE

The query user may not be logged in to the Oracle SES query application, even if both the OracleAS Portal instance and the Oracle SES instance are pointing to the same identity server (for example, the OID).

Workaround: Configure the OracleAS Portal instance and the Oracle SES Query application to use Single Sign-on (SSO), and configure the ORacle SES Query application to require login for all content. Then, when the users are redirected to the display JSP for the search result, they will be logged in through SSO and will therefore have access to the content.

9233383: DB DUMPED CORE AFTER HITTING ORA-600 [KDSGRP1] DURING LIGHT PUBLIC QUERY STRESS

This intermittent failure is observed during deployment, and happens only with the concurrent execution of low level read and write activities during a timeslice.

Workaround: There is no workaround.

9241318: MULTIBYTE NAMES NOT SUPPORTED BY WNA

Multibyte login name is not supported by WNA since the underlying WebLogic implementation for Kerberos authentication does not support such names.

Workaround: There is no workaround.

9246468: THE DEFAULT CACHE IS STORED ON THE OPERATING SYSTEM

The Mailing List data source uses storage on the operating system.

Workaround: All new Mailing List sources must use the same cache location as the default parent Mailing List source.

9268418: THE JDBC HEALTH STATUS IN ADMINSERVER IS ALWAYS CRITICAL

After installing or upgrading to this release, when you log in to the Oracle WebLogic Server Administration Console (http://$HOST_NAME:$WLS_LISTEN_PORT/console) and check the status of AdminServer, the status is shown as Critical instead of OK. Then when you check the detail health information of the server, you can see that the status of JDBC is Critical with reason "Connection Pool Name = null:null:mds-owsm, State = Unhealthy."

Workaround: Define the JDBC data source for the Oracle Web Services Manager (OWSM) as described in the section "Setting Up Database Connection Information using WebLogic Server Administration Console" in this document.

9280235: EXCEPTION BEING PRINTED WITH FULLY QUALIFIED PATH

The old stack used to throw javax.xml.soap.SOAPException. The new stack throws javax.xml.rpc.soap.SOAPFaultException, which is mapped back to SOAPException on the client side. When the exception message is printed, it starts with the fully qualified name of the exception class and not just the name of the exception class. For example, javax.xml.SoapException instead of just SoapException.

Workaround: To solve this issue, the Oracle SES query web service client API must be run in JDK 1.6 or higher. This workaround is not confirmed on all operating systems.

9361080: WEB-SERVICES BASED CONNECTOR PLUG-IN DEVELOPMENT

In order to develop any identity or authorization plug-in that is based on a Web service, the proxy stub classes that the plug-in uses to access the Web service must be added to commons-plugins-stubs.jar.

Workaround: Add the proxy stub classes that your plug-in uses to:

Oracle_Home/search/lib/plugins/commons-plugins-stubs.jar

9359467: WEBLOGIC SERVER - LOG ROTATION FAILS TO WORK AS EXPECTED

After setting rotate_logfile back to true and restarting the Oracle SES middle tier (Oracle WebLogic Server), the logging Rotation type configuration in the Oracle WebLogic Server Administration Console still shows as NONE.

Workaround: A partial workaround for this issue is as follows.

1. Go to the Oracle WebLogic Server Administration Console http://host:port/console.

2. Select Servers/AdminServer and click the Logging tab.

3. On the Logging tab, click Lock & Edit and make the appropriate configuration changes and click Save. (You must save your changes before activating them in the next step.)

4. Click Activate Changes.

5. Restart the Oracle WebLogic Server.

9369154: EXCEPTION WHEN OPEN QUERY PAGE OF SSO INSTANCE

Some of the required SSO parameters are not configured by default in the query plan.

Workaround: When enabling SSO using the query application deployment plan, which is located at $ORACLE_HOME/search/tools/weblogic/deploy/plans/QueryPlan.xml, in addition to the sso_enabled flag, the following parameters must be configured:

    <variable>
      <name>sso_vendor_name</name>
      <value>osso</value>
      <description>The SSO vendor name.</description>
    </variable>

    <variable>
      <name>sso_user_guid_header</name>
      <value>Osso-User-Guid</value>
      <description>The HTTP header name that the SSO server uses to pass the
user GUID to SES. The value in the header should match the value of the users
canonical attribute for the active identity plugin.</description>
    </variable>

    <variable>
      <name>sso_username_header</name>
      <value>REMOTE_USER</value>
      <description>The HTTP header name that the SSO server uses to pass the
search username to SES. The value in the header should match the value of the
users authentication attribute for the active identity plugin. Specify
REMOTE_USER to use getRemoteUser in the HTTP request to retrieve the
username.</description>
    </variable>

9589783: REGISTERING SES PORTLET FAILS ON PORTAL 10.1.4.2.0 + PSE PATCH 7560661

Registering an Oracle SES Portlet on Portal 10.1.4.2 against an Oracle SES 11.1.2.2 end point running on Solaris SPARC (64-Bit) or IBM AIX, results in the following error message:

An error occurred during the call to the WSRP Provider: Java stack trace from root exception:
java.rmi.ServerException: java.lang.RuntimeException: Internal Error

Workaround: There is no workaround.

9625180: EQ_SYS AND EQ_TEST DB PASSWORDS EXPIRE AFTER 180 DAYS, SEARCH THROWS ORA-28001

Search functionality breaks after 180 days of use.

Workaround: Install patch 9625180.

9755414: "ORACLE VSS WRITER" SERVICE DOES NOT START OR STOP USING THE SEARCHCTL COMMAND

The database service Oracle VSS Writer does not start or stop using the Oracle SES command searchctl on Microsoft Windows operating system.

Workaround: Oracle SES is currently not using this service on Microsoft Windows operating system, because it is a separate service on Microsoft Windows for database backup and recovery. You should manually start or stop this service.

8924865: "EQUALS" OPERATOR DOES NOT REMOVE THE DOUBLE QUOTATION MARKS PRESENT IN THE ATTRIBUTE VALUE DURING SEARCH

The search query does not work as expected, when the filter value in the attribute filter is enclosed in double quotes in the query page.

Workaround: There is no workaround.

9914304: SHAREPOINT CONNECTOR DOESN'T HANDLE CAD FILES

Sharepoint connector does not crawl CAD files stored in a Sharepoint server.

Workaround: To crawl CAD files, you should insert the following text in the beginning of the ORACLE_HOME/search/data/config/crawler.dat file: MIMEINCLUDE application/octet-stream.

11867873: CANNOT SEARCH IN THE GROUP CONTAINING PORTAL SOURCE ONLY

When Parallel Query option is enabled with partitioning based on the data source type in Oracle SES, the search operation in the Oracle SES Query application does not return any result for the data source group that contains only the OracleAS Portal type of source.

Workaround: There is no workaround.

11894473: ALTERNATE WORD NOT DISPLAYED WHEN USING PHRASE SEARCH

The alternate word is not displayed when using the phrase search in the Oracle SES Query application.

Workaround: There is no workaround. In the Oracle SES 11.1.2.2 release, the alternate words expansion is turned off for searches that use advanced constructs like thesaurus-based search, proximity search, fuzzy search, phrase search, and compulsory exclusion search.

10647571: INTRODUCE A MODE IN IMAP EMAIL CONNECTOR TO EXCLUDE ATTACHMENTS

In the Oracle SES releases earlier to 11.1.2.2, when attachments are excluded by document type exclusion rules, there is no efficient way to revisit them again in the future, unless doing a force recrawl.

Workaround: In Oracle SES 11.1.2.2, Imap Email connector has been enhanced to track the skipped attachments. A new parameter "Revisit Skipped Attachments" is now added, so that when set to TRUE, the connector revisits the skipped attachments from the earlier crawls based on the current document type inclusion rules. By default, the value of this parameter is set to FALSE, and the skipped attachments from the earlier crawls are not revisited.

12328699: SES 11.1.2.0 NODEMANAGER PROCESS IS STILL ALIVE AFTER UPGRADING TO SES 11.1.2.2

After upgrading from Oracle SES 11.1.2.0 to Oracle SES 11.1.2.2, the NodeManager process for the old SES instance (11.1.2.0) is still running.

Workaround: There is no functional impact. You may kill the process for the old SES instance after the upgrade.

12321729: FEDERATION ENGINE CONFIGURATION MAX/MIN THREADS VALUE IS SET TO 20 INSTEAD OF 100 AFTER UPGRADING FROM SES 10.1.8.2 TO SES 11.1.2.2

After upgrading from Oracle SES 10.1.8.2 to Oracle SES 11.1.2.2, the values for the minimum and the maximum number of threads of Federation Engine Configuration and Security Filter Configuration are set to 20 instead of their earlier value of 100.

Workaround: You should manually set these thread values to 100 in the Oracle SES 11.1.2.2 instance after the upgrade. Following are the steps to achieve this using SES Administration UI:

1. In the Oracle SES Administration UI, navigate to Global Settings > Query Configuration.

2. In the Federation Engine Configuration section, set the values of Minimum Number of Threads and Maximum Number of Threads to 100.

3. In the Security Filter Configuration section, set the values of Minimum Number of Threads and Maximum Number of Threads to 100.

4. Click Apply.

Alternately, you can use SES Administration API to achieve this. Run the following command at the command line:

searchadmin export queryConfig -o qc.xml

Open the qc.xml file in a text editor, and set the values for the minimum and the maximum number of threads of Federation Engine Configuration and Security Filter Configuration to 100. Save these settings using the following command:

searchadmin update queryConfig -i qc.xml -a overwrite

12420134: OTEXT QUERY OPERATOR "DEFINEMERGE" FAILED WITH SES QUERY JAVA API

The following OTEXT query throws oracle.search.query.internal.SearchException:

otext::DEFINEMERGE(((DEFINESCORE((selling within Title),DISCRETE*0.417)), (DEFINESCORE((idea within Title),DISCRETE*0.1234))),OR,ADD)

when used with the following SES query Java API function:

doOracleSimpleSearch(query,
                     startIndex,
                     docsRequested,
                     dupRemoved,
                     dupMarked,
                     returnCount);

Workaround: Attribute names must be enclosed in double quotes when used in an OTEXT query. For example:

otext::DEFINEMERGE(((DEFINESCORE((selling within "Title"),DISCRETE*0.417)), (DEFINESCORE((idea within "Title"),DISCRETE*0.1234))),OR,ADD)

12673184: ERROR 404 DISPLAYED WHEN PERFORMING BI SEARCH

For a BIEE data source, when a URL listed as a part of a search result is clicked, the error message "Error 404 - Not Found" is displayed. This error occurs when the value of the Display URL Prefix parameter for the Authorization Manager Plug-in concatenated with the access URL of a document in the data feed does not form a valid URL.

Workaround: Enter a final slash (/) to the Display URL Prefix parameter value if the access URLs do not begin with a slash, or omit the final slash from its value if the access URLs begin with a slash. Be careful to avoid having either two slashes or none when the values are combined to form a URL.

12630247: ERROR WHILE EXECUTING SEARCHADMIN CREATE SOURCE COMMAND ON IBM AIX

On IBM AIX on POWER Systems (64-Bit) platform, the Oracle SES Administration tool command searchadmin create source throws the following Java exception when "-c" option is not specified while creating a federated source:

java.lang.IllegalStateException: The current state is not START_DOCUMENT.
 at
com.ibm.xml.xlxp.api.stax.msg.StAXMessageProvider.throwIllegalStateException(S
tAXMessageProvider.java:46)
 at
com.ibm.xml.xlxp.api.stax.XMLStreamReaderImpl.getCharacterEncodingScheme(XMLSt
reamReaderImpl.java:1580)
...

On IBM AIX on POWER Systems (64-Bit) platform, the searchadmin command fails to invoke remote SES query web service endpoint to fetch federated attributes during source creation. This happens because, when running the searchadmin command, the platform specific JDK is used to invoke the query web service endpoint, which is not compatible with the JDK version that comes bundled with the Oracle WebLogic Server shipped with Oracle SES.

Workaround: Run the Oracle SES Administration tool command searchadmin create source with "-c" option, that is, specify the web service URL while creating a source.

12699691: CANNOT ACCESS THE ORACLE SES MIDDLE TIER AFTER RESTARING THE WINDOWS 64-BIT COMPUTER

On Windows 64-bit computers, the Oracle SES middle tier (Oracle WebLogic Server) does not start automatically after restarting the computer.

Workaround: Perform the following steps to solve this issue:

1. Open Windows Explorer and navigate to the folder %ORACLE_BASE%\wlserver\common\nodemanager.

2. Open the file nodemanager.properties in a text editor.

3. Set the value for the CrashRecoveryEnabled parameter to true.

   CrashRecoveryEnabled=true
   

4. Save the nodemanager.properties file.

5. Restart the Oracle WebLogic Server.

12970023: THE SEARCH APPLICATION STOPS RENDERING SKINBUNDLE AFTER RESTARTING THE ORACLE SES INSTANCE

The look and feel of the Oracle SES Search Application can be customized using templates that implement SkinBundle. Sometimes, this customized look and feel of the Oracle SES Search Application is lost when the Oracle SES instance is restarted.

Workaround: Set the "template_update_delay" configuration parameter in the "QueryPlan.xml" file to a large value, such as 7200 (that is, 2 hours).

To update the template_update_delay parameter: 

1. Open the QueryPlan.xml file in a text editor. The QueryPlan.xml file is located at ORACLE_HOME/search/tools/weblogic/deploy/plans/.

2. Set the appropriate value for the template_update_delay parameter as shown in the following example:

   <variable>
       <name>template_update_delay</name>
       <value>7200</value>
       <description>Time in seconds since last checking for a newer version of a template before checking again. Default is 3600 seconds.</description>
   </variable>
   

3. Run the deployer.sh file for the changes made to this file to take effect:

   On Linux:

   sh $ORACLE_HOME/search/tools/weblogic/deploy/deployer.sh -serverURL t3://host:port/ -user weblogic -password password -name search_query -plan $ORACLE_HOME/search/tools/weblogic/deploy/plans/QueryPlan.xml -process redeploy
   

   On Windows:

   %ORACLE_HOME%\search\tools\weblogic\deploy\deployer.bat -serverURL t3://host:port/ -user weblogic -password password -name search_query -plan %ORACLE_HOME%\search\tools\weblogic\deploy\plans\QueryPlan.xml -process redeploy
   

   Where:

   host is the host name, and port is the WebLogic service port. This is the same port that you use to open the Administration GUI. password is the password for eqsys.

Oracle Secure Enterprise Search Installation and Upgrade Guide

Apply Mandatory One-Off Patches for Oracle SES 10.1.8.4

The content in the last line in the second bullet point is incorrect. It should read:

"Patch 11798419 is available as a zip file 11798419_10184.zip and is present in the /Patches directory of the Oracle SES 11.1.2.2 software distribution."

Apply Mandatory One-Off Patches for Oracle SES 11.1.2.0

The content in the last line in the first bullet point is incorrect. It should read:

"Patch 11798419 is available as a zip file 11798419_11120.zip and is present in the /Patches directory of the Oracle SES 11.1.2.2 software distribution."

Oracle Secure Enterprise Search Installation Guide for Microsoft Windows (64-Bit)

Deinstallation Tasks

The deinstallation steps are incorrect. They should read:

To deinstall Oracle SES: 

1. Log on as a member of the Administrators group to the system where Oracle SES is installed. Close any other remote sessions owned by this user.

2. Stop Oracle SES from the Windows Start menu by selecting Oracle - search_server_name - Stop SES.

3. Deinstall Oracle SES:

   • From the Windows Start menu, select Oracle - search_server_name - Uninstall SES.

     or

   • Open the Control Panel and select Program and Features. Select Oracle Secure Enterprise Search - <search_server_name> (remove only).

4. Manually remove the shortcuts directory for Oracle Weblogic Server (Oracle WebLogic Current BEA Home) that is present under the directory C:\Documents and Settings\user\Start Menu\Programs.

Oracle Secure Enterprise Search Administration API Guide

Deletion of Storage Area Files

The description for storageArea Administration API object type in Chapter 2 should include this information:

Windows (64-bit) Usage: After executing the delete operation of Administration API for deleting a storage area, you may still need to delete the corresponding physical data file manually. A storage area file cannot be deleted until it is released by all the processes, which may prevent Oracle SES from completing the delete operation.

Oracle Secure Enterprise Search Administrator's Guide

Customizing the Search User Interface

In the Table 10-1 "List of Template Files", the information about configuring the cache page logo is incorrect. The correct way to configure the cache page logo is to set the two parameters - use_cache_page_img and cache_page_img - in the QueryPlan.xml file, which is located at ORACLE_HOME/search/tools/weblogic/deploy/plans/.

• use_cache_page_img: Flag indicating whether to display the image specified in the cache_page_img attribute value as the logo for the cached page. It takes the values true or false. If set to true, then the image specified in the cache_page_img is displayed as the logo for the cached page. If set to false, then the string "ORACLE" is displayed in place of the cache page logo. Default value is false.

• cache_page_img: Absolute URL of the cached page logo image.

To configure the cache page logo: 

1. Open the QueryPlan.xml file in a text editor.

2. Set the appropriate values for the two attributes - use_cache_page_img and cache_page_img - as shown in the following example:

   <variable>
       <name>use_cache_page_img</name>
       <value>true</value>
       <description>Whether to use the image specified in cache_page_img attribute as the logo for the cached page. Default is false.</description>
   </variable>
     
   <variable>
       <name>cache_page_img</name>
       <value>http://www.xyz.com/logo/images/cache_page_logo.gif</value>
       <description>The absolute URL of the cached page logo image.</description>
   </variable>
   

3. Run the deployer.sh file for the changes made to this file to take effect:

   On Linux:

   sh $ORACLE_HOME/search/tools/weblogic/deploy/deployer.sh -serverURL t3://host:port/ -user weblogic -password password -name search_query -plan $ORACLE_HOME/search/tools/weblogic/deploy/plans/QueryPlan.xml -process redeploy
   

   On Windows:

   %ORACLE_HOME%\search\tools\weblogic\deploy\deployer.bat -serverURL t3://host:port/ -user weblogic -password password -name search_query -plan %ORACLE_HOME%\search\tools\weblogic\deploy\plans\QueryPlan.xml -process redeploy
   

   Where:

   host is the host name, and port is the WebLogic service port. This is the same port that you use to open the Administration GUI. password is the password for eqsys.

Creating a Document Service

The last paragraph of the "Document Service API" section contains the line: "After registering a document service plug-in, you can create an instance from it". But, the steps to create an instance of a document service plug-in are not described in the guide.

The following are the steps to create a document service:

1. Create a document service plug-in Java Class:

   You must first create a document service plug-in Java class and store the implemented class in a jar file. Refer to the section "Document Service API" for more information about creating a document service plug-in Java class.

2. Create a document service instance:

   The following are the steps to create an instance for a document service:

   1. In the Administration GUI, click Global Settings - Document Services.

   2. On the Document Service page, click Create button under the Document Services section.

   3. On the Create Document Service page, either select an already defined documentation manager from the Available Managers list or create a new documentation manager by selecting the Create New Manager option.

   4. Click Next.

   5. On the Create Document Service Manager page, enter the document manager class name and its jar file path of the document service plug-in Java class that was created in step 1.

      Note:

      Enter the full name of the document manager class including the package path, example, oracle.search.plugin.doc.extractor.MyDocumentManager. If the document manager jar file is placed in the ses_home/search/lib/plugins/doc directory, then its relative file path can be specified, else its absolute file path must be specified.

   6. Click Next.

   7. On the Create Document Service Instance page, enter the name for the document service instance and enter the appropriate values for its parameters, which control the way data needs to be extracted from text documents and image files.

   8. Click Create.

3. Specify the order for invoking document service instances using a pipeline:

   The following are the steps to specify the order for invoking document service instances using a pipeline:

   1. In the Document Services Pipelines section of the Document Service page, either click the Edit icon to update an existing pipeline or click the Create button to create a new pipeline.

   2. In the Create/Edit Document Service Pipeline page, enter the name and description for the pipeline. In the Document Services section, select the document service instances from the list of already defined instances to build the pipeline. The document service instances will be invoked in the order in which they are listed in the pipeline.

   3. Click Create for creating a new pipeline. Click Apply for updating an existing pipeline.

Oracle Secure Enterprise Search Language Model

Different components of Oracle SES, such as crawler, Query application, Administration GUI, Administration API, Query API, and ODL support different set of languages.

Languages Supported By Crawler

An Oracle SES data source can contain documents in different languages, for example, one document can be in English, while other can be in Japanese. Oracle SES associates a single document with a single language.

A data source can explicitly specify a language for a document. Oracle SES recognizes only the document languages that are specified using the ISO 639-1 standard, but not all of the languages.

The Administration GUI can also be used to set one of the following document languages as a default language for a data source - Arabic, Chinese, Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Slovak, Spanish, Swedish, and Turkish.

If a default language is not set for a data source using Administration GUI, then the crawler can automatically detect a document's language by reading its metadata. The crawler can detect the following document languages automatically - Arabic, Chinese, Danish, Dutch, English, French, German, Greek, Japanese, Korean, Italian, Lao, Portuguese, Spanish, Thai, and Tibetan.

The crawler determines a document's language by performing the following checks in the mentioned order:

• From the HTTP response header Content-Language for a Web data source

• From the HTML Language meta tag, for example, <meta name="Language" content ="en">

• From the HTML content-language meta tag, for example, <meta http-equiv="content-language" content="fr">

• From the LANGUAGE column of a Table data source

• From the language specified for a crawler Plug-in

• Using the automatic language detection feature (if this feature is enabled)

• From the default language specified for a data source

Languages Supported By the Query Application and Query API

The default query application supports the following languages - Arabic, Catalan, Chinese, Czech, Danish, German, Greek, English, Spanish, Finnish, French, Hungarian, Italian, Japanese, Korean, Dutch, Norwegian, Polish, Portuguese, Romanian, Russian, Slovak, Swedish, Thai, and Turkish.

The default query application obtains the client-side language, territory, and character-set information from the Web browser. The language information is then passed as is to the Query API, only if CJK characters (Chinese, Japanese, and Korean) are not present in the query, otherwise, the language is set to the most likely one among the CJK in the Query API.

A query in Oracle SES can be specified using only one language. A document that is not in the same language as specified in the query, is either not searched at all or is assigned lower relevancy score in the query search result depending upon the Oracle SES configuration.

Oracle SES Query API supports different languages for different types of search as described in the following table.

Languages Supported by the Administration GUI and Administration API

The Administration GUI supports the following languages - Chinese, English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish.

You can translate the search attribute names to the following languages using Administration GUI and Administration API - English, Arabic, Brazilian Portuguese, Catalan, Czech, Danish, Dutch, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Simplified Chinese, Slovak, Spanish, Swedish, Thai, Tradition Chinese, and Turkish.

Languages Supported by ODL Logs

Oracle SES uses ODL for logging the warning and error messages into log files. Oracle SES supports the following languages for logging these messages - English, German, Spanish, Franch, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese.

Oracle Secure Enterprise Search Administration GUI Online Help

Configuring Search Operation for Relevancy

The Administration GUI Online Help for the Relevancy page in the Search tab should include this information:

Locate by Search functionality works only with the unsecured sources.

Oracle Secure Enterprise Search Java API Reference

Java API Methods Not Supported

Oracle SES Java API methods OracleSearchService.logUserClick() and OracleSearchService.getUserStats() are not supported in this release.

J2SSH Software

J2SSH is dual licensed; you may distribute it under an Apache style license or the LGPL. You may select whichever license suits your needs.

 /*
 * ============================================================================
 * J2SSH Software License
 * ============================================================================
 *
 *  Copyright (C) 2002-2003 Lee David Painter and Contributors.
 *
 *  Contributions made by:
 *
 *  Brett Smith
 *  Richard Pernavas
 *  Erwin Bolwidt
 *
 * Redistribution and use in source and binary forms, with or without modifica-
 * tion, are permitted provided that the following conditions are met:
 *
 * 1. Redistributions of source code must retain the above copyright notice,
 *    this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright notice,
 *    this list of conditions and the following disclaimer in the documentation
 *    and/or other materials provided with the distribution.
 *
 * 3. The end-user documentation included with the redistribution, if any, must
 *    include  the following  acknowledgment:  "This product includes  software
 *    developed  by   SSHTools  (http://www.sshtools.com/)."
 *    Alternately, this  acknowledgment may  appear in the software itself,  if
 *    and wherever such third-party acknowledgments normally appear.
 *
 * 4. The names "J2SSH", "Lee David Painter" and "SSHTools"  must not be used to
 *    endorse  or promote  products derived  from this  software without  prior
 *    written permission. For written permission, please contact
 *    lee@sshtools.com.
 *
 * 5. Products  derived from this software may not  be called "J2SSH" or
 *    "SSHTools", nor may these names appear in their name,  without prior
 *    written permission  of Lee David Painter.
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
 * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
 * FITNESS  FOR A PARTICULAR  PURPOSE ARE  DISCLAIMED.  IN NO  EVENT SHALL  THE
 * LEE DAVID PAINTER, SSHTOOLS OR ITS CONTRIBUTORS  BE LIABLE FOR  ANY DIRECT,
 * INDIRECT, INCIDENTAL, SPECIAL,  EXEMPLARY, OR CONSEQUENTIAL  DAMAGES (INCLU-
 * DING, BUT NOT LIMITED TO, PROCUREMENT  OF SUBSTITUTE GOODS OR SERVICES; LOSS
 * OF USE, DATA, OR  PROFITS; OR BUSINESS  INTERRUPTION)  HOWEVER CAUSED AND ON
 * ANY  THEORY OF LIABILITY,  WHETHER  IN CONTRACT,  STRICT LIABILITY,  OR TORT
 * (INCLUDING  NEGLIGENCE OR  OTHERWISE) ARISING IN  ANY WAY OUT OF THE  USE OF
 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 */