Skip Headers
Oracle® Secure Enterprise Search Administrator's Guide
10g Release 1 (10.1.8.1)

Part Number B32514-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

B Upgrading Oracle Secure Enterprise Search

This appendix contains topics relating to an upgraded Oracle SES instance. This contains the following topics:

See Also:

Upgrading Oracle Secure Enterprise Search to 10.1.8.1

There is no direct upgrade support to release 10.1.8.1.

Checking Memory Requirements

When upgrading to 10.1.8, if you have changed the SGA size manually, then follow these steps to confirm that Oracle SES has enough memory:

  1. 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 non-zero 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.
  2. 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'); 
    
    
  3. 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)))
    
    
  4. 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.

Upgrading File Sources to 10.1.8

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.

Upgrading Oracle Calendar Sources to 10.1.8

Oracle Calendar sources created in Oracle SES 10.1.6 may not work after upgrade. 10.1.8 uses a newer version of OC4J, and the soap.jar file included in OC4J is in a different location.

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.

Using Secure Federated Search Between 10.1.8 and 10.1.6

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: