Release Notes
11g Release 1 (11.1.2.0.0)
E14877-07
March 2012
This document contains important information for Oracle Secure Enterprise Search 11g Release 1 (11.1.2.0.0) that is not included in the regular documentation.
This document may be updated after it is released. To check for updates to this document and to view other Oracle documentation, refer to the Documentation section on the Oracle Technology Network (OTN) Web site:
http://www.oracle.com/technology/documentation/
This document contains the following topics:
You can download software patches from My Oracle Support at
Install this patch after installing or upgrading to 11.1.2:
9647327: SES 11.1.2 GROUPBY AND SORTBY ERROR MESSAGE "UNABLE TO FETCH ADDITIONAL RESULTS"
Install this patch during an upgrade, as described in "Patch 9740780 Upgrade Instructions":
9740780: UPGRADE TAKES VERY LONG TIME FOR LARGE INDEX
Install this patch after installing or upgrading to 11.1.2:
9625180: EQ_SYS AND EQ_TEST DB PASSWORDS EXPIRE AFTER 180 DAYS, SEARCH THROWS ORA-28001
Patch 9740780 significantly reduces the time needed to upgrade the index. The following steps supplement but do not replace the upgrade procedures in the Oracle Secure Enterprise Search Installation and Upgrade Guide for your Linux or UNIX-based platform.
To install the patch during an interactive upgrade to Oracle SES 11.1.2.0.0:
Complete the preupgrade steps in the Oracle Secure Enterprise Search Installation and Upgrade Guide.
Review "Upgrade Issues" for additional preupgrade steps.
Download patch 9740780 to the installation system from My Oracle Support at
Tip: Do not unzip it yet.
Start Oracle Universal Installer for Oracle SES 11g Release 1 (11.1.2.0.0).
Choose to upgrade the existing installation, and enter the installation paths and administrative password as required.
On the Install page, watch the installation messages closely. Click Stop Installation when "Installation in progress" changes to "Install successful." Do not exit from Oracle Universal Installer. Allow the Exit dialog box to remain open while you complete the next step.
You can stop the installation at any time during the Link or Setup phases, while "Configuration pending" is still displayed.
Unzip the patch into the new 11g ORACLE_HOME in $ORACLE_HOME/search/patch/11.1.2.0.0. For example:
unzip p9740780_111200_Generic.zip -d /oracle/product/11.1.2.0.0/ses/seshome/search/patch/11.1.2.0.0
This directory will already contain other patches, which were copied there by the installer.
In the Exit dialog box, resume the installation by clicking No in response to "Are you sure you want to stop the installation and exit?" Do not exit from the installer.
Complete the upgrade and postupgrade steps in the Oracle Secure Enterprise Search Installation and Upgrade Guide.
Download and install patch 9625180, which is described in "9625180: EQ_SYS AND EQ_TEST DB PASSWORDS EXPIRE AFTER 180 DAYS, SEARCH THROWS ORA-28001".
Review "Upgrade Issues" for additional postupgrade steps.
Release 11.1.2 supports Oracle Access Manager 10.1.4 or later to SSO-protect the Oracle SES default search application running on WebLogic Server. Crawling support for OAM-protected sources is planned for a future release of SES. For configuration instructions, see "Security in Oracle Secure Enterprise Search" in the Oracle SES Administration Guide on Oracle Technology Network. These instructions are not part of the documentation that is included with the product.
Oracle SES uses Oracle Text to convert binary documents to HTML. This section lists the changes to supported document types for this release.
Support is dropped in Oracle SES release 11.1.2 for these document types:
Applix Word
Applix Spreadsheet
IBM DCA-RFT
Folio Flat File
Fujitsu Oasys
Microsoft Visio XML Format
Support is added in Oracle SES release 11.1.2 for these document types:
Microsoft Office 2007
SUN StarOffice
Haansoft Hangul Documents
For a complete list of supported document types, open the Oracle SES Administration tool from within the product. Customize a data source and select the Document Types subtab.
This section contains features and functionality that is desupported for this release.
This section contains these topics:
The V1 Agent, called the Crawler Agent API in Oracle Ultra Search, is desupported in Oracle SES release 11.1.2. (The V1 Agent is the predecessor of the current crawler plug-in API in Oracle SES.)
The Oracle SES 10g Administration API is deprecated in this release (searchadminctl and the associated Web services). The Oracle SES release 11.1.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
This section contains the latest known issues and bugs for this release and contains these topics:
Note:
For updated information on bugs, workarounds, and best practices, visit the Oracle SES Web site at: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 -ignorePrereq -silent -debug -responseFile ~/upgrade.rsp
You only need to 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.
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, 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 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 originally created in Oracle SES 10.1.8.0 will 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 GUI to delete them, or take these steps:
Open SQL*Plus and connect as eqsys.
Run the EQ_ADMIN.USE_INSTANCE procedure:
EXECUTE eq_adm.use_instance(1);
Delete the trusted entities:
DELETE FROM eq$trusted_entity;
Save the changes:
COMMIT;
After the upgrade is complete, re-create the trusted entities.
9326121: POST 10G-11.1.2 UPG ZONE-TO-FIELD CONVERSION VERY SLOW FOR 15M+ ZONE SECTIONS
The postupgrade 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 postupgrade 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, 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 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.
BUG 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".
This section lists general open bugs that affect the Linux platform.
If your Linux operating system supports Internet Protocol version 6 (IPv6), then the search stopall command may not be able to connect to localhost using IPv4.
If your system supports IPv6, then you will see entries like the following example in the /etc/hosts file:
# 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
Workaround: Comment out the IPv6 entries in /etc/hosts. For example:
# 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
This section lists the general known bugs for this release.
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.
7294661: CANNOT DOWNLOAD LHA.JAR
The LHA compression file format is supported in this release. To use this feature, you must manually download and deploy the libraries needed for supporting the file format.
Workaround: Go to the download location at http://pnuts.org/doc/extensions.html.
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 problem is the cause for display 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 the display problem.
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 MIDTIER START/STOP WARNING MESSAGES (SECURITY NOTICE BEA-090898)
Security warnings appear when connecting to the node manager with WebLogic as the midtier. This is because WebLogic does not recognize the CA certificates from the midtier 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, 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 WebLogic midtier, 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.
9130467: PRE-11.1.2 UPGRADE PATCH HISTORY NOT PRESERVED FROM 10G
The opatch lsinventory does 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 x86 for procedures.
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 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 SES query application, even if both the OracleAS Portal instance and the SES instance are pointing to the same identity server (for example, the OID).
Workaround: Configure the OracleAS Portal instance and the SES query application to both utilize Single Sign-on (SSO), and configure the SES query application to require login for all content. Then, when the user is redirected to the display JSP for the search result, they will be logged in through SSO and will therefore authorize their 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: DEFAULT CACHE STORAGE WILL BE OS
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 WLS 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. Oracle Web Services Manager (OWSM) template requires a data source to be defined.
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 avoid this problem, the Oracle SES release 11.1.2 query WS client API should be run in JDK 1.6 or higher. This workaround is not confirmed on all systems.
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.
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 should 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 midtier, the logging Rotation type configuration in the WLS Admin Console still shows as NONE. The logfile rotation setting has not been reenabled.
Workaround: A partial workaround for this problem is as follows.
Go to the WLS Console at http://host:port/console.
Select Servers/AdminServer and click the Logging tab.
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.)
Click Activate Changes.
Restart the Oracle SES midtier.
The configuration changes made in the WLS Console will take effect and will stay in effect even after further Oracle SES midtier restarts.
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 SES Portlet on Portal 10.1.4.2 against an SES 11.1.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.
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:
Open the QueryPlan.xml file in a text editor. The QueryPlan.xml file is located at ORACLE_HOME/search/tools/weblogic/deploy/plans/.
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>
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.
Note:
You can also contact the Oracle support and request for an OPatch to fix this bug.This section contains corrections to the Oracle SES documentation set.
The list of certified browsers is incorrect. The default Search Application and the Administration GUI are certified on the following browsers:
Firefox 3.x
Internet Explorer 7.x, 8.x
Safari 4.x
"Deinstallation Tasks" should include this sentence: Deinstallation does not remove all directories in Oracle base, because they may be shared by other Oracle homes.
Installing ossoiap.jar for Single Sign-on Security
In "Configuring OracleAS and Oracle SES for Single Sign-on Security" in Chapter 11, "Security in Oracle Secure Enterprise Search," the ossoiap.jar referenced in step 1 is available in Oracle HTTP Server 11g only. If you are configuring Oracle Single Sign-On using Oracle HTTP Server 10.1.3, then install Oracle HTTP Server 11g separately to obtain this JAR file.
Importing SSL Certificates into JVM
"Managing the Keystore" in Chapter 11 should include this information: For connectors that interact with external SSL-enabled repositories at crawl time and query time, you must import the SSL certificate into the keystore of the Oracle SES crawler Java Virtual Machine (JVM) and the mid-tier JVM. The keystore in the crawler's JVM is used at crawl time, and the keystore in the mid-tier JVM is used at query time to build the security filter.
Following are the paths to the two JREs into which to import the SSL certificate:
ORACLE_HOME/jdk/jre
ORACLE_BASE/jrockit_160_14_R27.6.5-32/jre
The following step should be added to "Configuring QueryPlan.xml in Oracle SES" in Chapter 11:
For changes made to this file to take effect on Linux, run the deployer.sh file:
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
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.
For example, if you install Oracle SES on the host exampleServer and port 7777, and the Oracle SES administration password is welcome1, then issue the following command:
sh ./deployer.sh -serverURL t3://example:7777/ -user weblogic -password welcome1 -name search_query -plan $ORACLE_HOME/search/tools/weblogic/deploy/plans/QueryPlan.xml -process redeploy
"Using Backup and Recovery" in Chapter 12 should include this information: The searchctl stopall command does not close active background tasks before initiating an immediate shutdown. This may raise internal errors, which you can ignore.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Secure Enterprise Search Release Notes, 11g Release 1 (11.1.2.0.0)
E14877-07
Copyright © 2006, 2012, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.