This appendix contains topics relating to an upgraded Oracle SES instance. This contains the following topics:
See Also:
Oracle Secure Enterprise Search Installation Guide
"Upgrade Issues" in the Oracle Secure Enterprise Search Release Notes on OTN
There is no direct upgrade support to release 10.1.8.2.
To upgrade to Oracle SES release 10.1.8.2, you must first upgrade to release 10.1.8.1 and then install the patch set for release 10.1.8.2.
When upgrading, if you have changed the SGA size manually, then follow these steps to confirm that Oracle SES has enough memory:
Verify that Automatic Shared Memory Management is turned on by confirming that SGA_TARGET is greater than 0. If SGA_TARGET is set to 0, then you must change it to at least 1536M.
To check SGA_TARGET size, run the following:
SELECT name, value/1024/1024 ||' M' FROM V$PARAMETER WHERE name = 'sga_target';
Note:
SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified as a number greater than zero, then several of the memory pools in the SGA are automatically sized. If any of those automatically tuned memory pools are individually set to nonzero values, then those values are used as minimum levels by Automatic Shared Memory Management. Other memory pools are not affected by Automatic Shared Memory Management.Check the static limits set by the user for dynamic SGA components and current dynamic components usage.
For static limits:
SELECT name, value/1024/1024 ||' M'
FROM V$PARAMETER
WHERE name IN ('db_cache_size', 'shared_pool_size', 'large_pool_size', 'streams_pool_size', 'java_pool_size');
For dynamic sizes:
SELECT component, CURRENT_SIZE
FROM V$SGA_DYNAMIC_COMPONENTS
WHERE COMPONENT IN ('shared pool','large pool', 'java pool','streams pool','DEFAULT buffer cache');
Calculate the free memory. Free SGA memory must be greater than 700MB. If it is not, then reduce static limit parameters.
Free memory = SGA_TARGET - (greater(static(db_cache_size), dynamic(db_cache_size)) + greater(static(shared_pool_size), dynamic(shared_pool_size)) + greater(static(large_pool_size), dynamic((large_pool_size)) + greater(static(java_pool_size), dynamic(java_pool_size)) + greater(static(streams_pool_size), dynamic(streams_pool_size)))
If none of the parameters are set, then either set the following values
SGA_TARGET = 1536M
DB_CACHE_SIZE = 48M
SHARED_POOL_SIZE = 0
JAVA_POOL_SIZE = 0
or set values where you have 80% of free SGA memory before the installation.
After upgrading to SES 10.1.8.2, the OracleAS Portal page group shown by Oracle SES will change case.
In previous Oracle SES releases, the page_path attribute (which appears as lower case) was used for infosource browsing. With release 10.1.8.2, the portal_path attribute (which appears as upper case) is used for infosource browsing instead.
If you have any existing inclusion rules for the OracleAS Portal source, remove them before crawling. The root page of the page group is automatically included.
When an Oracle SES instance is upgraded to 10.1.8, documents in upgraded file sources are not shown in the browse hierarchy. (Documents in newly created file sources are shown in the browse hierarchy).
To make an upgraded file source consistent with a newly created file source, re-crawl the upgraded file source with the re-crawl policy set to Process All Documents on the Home - Schedules - Edit Schedule page.
Oracle Calendar sources created in Oracle SES 10.1.6 may not work after upgrade. 10.1.8 and later releases use a newer version of OC4J, and the soap.jar file included in OC4J is in a different location.
10.1.6 soap.jar location: $ORACLE_HOME/oc4j/soap/lib/soap.jar
10.1.8 soap.jar location: $ORACLE_HOME/oc4j/webservices/lib/soap.jar
Create new Oracle Calendar sources in 10.1.8. Otherwise, to use the Oracle Calendar sources created in 10.1.6, create the directory structure identical to the 10.1.6 location (*$ORACLE_HOME/oc4j/soap/lib/ *) and put a copy of soap.jar there.
To set up secure federated search with a 10.1.8 instance as the federation broker and a 10.1.6 instance as the federation endpoint, consider the following:
The federation broker and the federation endpoint must be connected to the same Oracle Internet Directory server.
Federation parameters are not immediately updated. To see changes immediately, bounce the middle tier on the federation broker.
If you are setting SSO mode 2 (private content alone protected by SSO) in the federation endpoint instance and you are not seeing private results returned by the federation broker instance, then you are hitting a 10.1.6 bug.
Workaround: Open the web.xml file in $ORACLE_HOME/oc4j/j2ee/oc4j_applications/applications/search_query/query/WEB-INF/web.xml. Comment out the filter and filter-mapping elements:
<!-- commenting filter and filter-mapping due to bug 5072567
<filter>
<filter-name>RequestFilter</filter-name>
<filter-class>oracle.search.query.RequestFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>RequestFilter</filter-name>
<servlet-name>OracleSearch</servlet-name>
</filter-mapping>
-->
Then restart the middle tier with searchctl restart.
Note:
If you must have a 10.1.6 instance as the federation endpoint behind SSO, then you cannot configure the instance in secure mode 3.When using the endpoint application entity as the federation endpoint for creating the federated source, make sure to add this entity to the trusted application's group under the federation endpoint instance's application entity entry in Oracle Internet Directory. See the following section.Oracle SES 10.1.8 federating to Oracle SES 10.1.6:
If the federation broker is Oracle SES 10.1.8 and the federation endpoint is Oracle SES 10.1.6, then the administrator of the broker instance must perform the following steps:
Get an entity name(DN) and password that is an entity under the trusted application's group of the application entity created for the Oracle SES 10.1.6 instance in Oracle Internet Directory. If there is no entity found in the trusted application's group, then either create a new entity or add the same application entity(DN) to the uniqueMember attribute of the endpoint's application entity. For example, if the application entity for the endpoint instance is:
orclApplicationCommonName=oesEntity_endpoint,cn=OES,cn=Products,cn=OracleContext,dc=us,dc=oracle,dc=com
add:
orclApplicationCommonName=oesEntity_endpoint,cn=OES,cn=Products,cn=OracleContext,dc=us,dc=oracle,dc=com
to the uniqueMember attribute of
orclApplicationCommonName=oesEntity_endpoint,cn=OES,cn=Products,cn=OracleContext,dc=us,dc=oracle,dc=com
If you are using the application entity of the 10.1.6 instance as the trusted entity, then the password for this entity is same as the Oracle SES admin password when Oracle SES was connected to the directory.
Create a federated source, and use the trusted entity created in the previous step for the Remote Entity Name and Remote Entity Password. The Search User Attribute should be the name of the attribute (in the directory to which broker is connected) corresponding to the orclguid attribute (in the Oracle Internet Directory the endpoint instance is connected to). If both broker and endpoint instance are connected to same Oracle Internet Directory, then the name of the attribute is orclguid.
Oracle SES 10.1.6 federating to Oracle SES 10.1.8:
If the federation broker is Oracle SES 10.1.6 and federation endpoint is Oracle SES 10.1.8, then the administrator of the endpoint instance must perform the following steps:
Get an entity name (DN) and password that is the application entity created for the Oracle SES 10.1.6 instance in Oracle Internet Directory. If the application entity is not found in Oracle Internet Directory, then connect the federation broker to the directory. For example, the application entity of the federation broker is:
orclApplicationCommonName=oesEntity_broker,cn=OES,cn=Products,cn=OracleContext,dc=us,dc=oracle,dc=com
The password for this entity is same as the Oracle SES admin password when Oracle SES was connected to the directory.
Create a federation trusted entity on the endpoint instance with the entity name and password obtained from the previous step. The Authentication Attribute should be the name of the attribute (in the directory to which endpoint is connected) corresponding to the orclguid attribute (in the Oracle Internet Directory the broker instance is connected to). If both broker and endpoint instance are connected to same Oracle Internet Directory, then the name of the attribute is orclguid.
Only authentication by password will be used for this entity.