9 Oracle Ultra Search

This chapter describes issues associated with Oracle Ultra Search. It includes the following topics:

• Section 9.1, "Upgrade Issues and Workarounds"

• Section 9.2, "General Issues and Workarounds"

• Section 9.3, "Documentation Errata"

9.1 Upgrade Issues and Workarounds

This section describes upgrade issues and their workarounds for Oracle Ultra Search. It includes the following topics:

• Section 9.1.1, "SSO Users Cannot Log on to Oracle Ultra Search when Upgrading to 10.1.1"

• Section 9.1.2, "Upgrade Fails When Upgrading to 10.1.2"

9.1.1 SSO Users Cannot Log on to Oracle Ultra Search when Upgrading to 10.1.1

SSO users cannot log on to Oracle Ultra Search to manage Oracle Ultra Search when upgrading from the Oracle9i Application Server 9.0.2 release to the Oracle Application Server 10g 10.1.2 release. This occurs during the upgrade period, after the Identity Management upgrade completes.

The workaround is to log on as the database user to manage Oracle Ultra Search during the upgrade.

9.1.2 Upgrade Fails When Upgrading to 10.1.2

When upgrading Oracle Ultra Search to Oracle Application Server 10g 10.1.2, the upgrade status for Oracle Ultra Search may show "Failed." This is because the validation package (wkvalid.sql) is not installed in the Oracle Application Server 10g 10.1.2 seed database. This will be fixed for 10.1.0.4 database.

The workaround is to first check whether the Oracle Ultra Search status is indeed invalid.

Login as SYS (for example, sqlplus "sys/<SYS PASSWORD> as sysdba")

SQL> SELECT comp_id, status FROM sys.dba_registry WHERE comp_id = 'WK'
/

You should see something like the following:

COMP_ID                       STATUS
------------------------    -----------
WK                            INVALID

If the Oracle Ultra Search status is invalid, then do the following to verify if the upgrade was indeed successful.Download wkvalid.sql from the following site:

http://www.oracle.com/technology//products/ultrasearch/index.html

Connect to database as SYS and install wkvalid.sql.

> sqlplus "sys/<SYS PASSWORD> as sysdba"
@wkvalid.sql

Connect to the database as SYS, and run the Oracle Ultra Search validation package. This package checks the Oracle Ultra Search status and updates it accordingly.

> sqlplus "sys/<SYS PASSWORD> as sysdba"
SQL> exec sys.validate_wk

PL/SQL procedure successfully completed.Check the Oracle Ultra Search status.

> sqlplus "sys/<SYS PASSWORD> as sysdba"
SQL> SELECT comp_id, status FROM sys.dba_registry WHERE comp_id = 'WK'
2  /

You should see the status as VALID, if the upgrade was successful.

COMP_ID                        STATUS
------------------------------ -----------
WK                             VALID

9.2 General Issues and Workarounds

This section describes general issues and their workarounds for Oracle Ultra Search. It includes the following topics:

• Section 9.2.1, "Creating or Editing Oracle Ultra Search ACLs Fails in Non-OracleAS Single Sign-On Mode"

• Section 9.2.2, "OracleAS Portal Users Cannot Log on to Oracle Ultra Search"

• Section 9.2.3, "Users Cannot Access usearch.jsp or search.jsp"

9.2.1 Creating or Editing Oracle Ultra Search ACLs Fails in Non-OracleAS Single Sign-On Mode

An Oracle Ultra Search Administrator can log in as a database administrator or an OracleAS Single Sign-On user who has been granted administrative privileges. In this release, when logging in as a database administrator, under certain circumstances, the administrator will not be able to create or edit administrator-specified ACLs for a data source. An "Access Denied" error is encountered when attempting to create or modify ACLs.

The workaround is to always log in as an OracleAS Single Sign-On user in order to create/modify ACLs for a data source.

9.2.2 OracleAS Portal Users Cannot Log on to Oracle Ultra Search

OracleAS Portal users cannot log on to manage Oracle Ultra Search if the OracleAS Metadata Repository is prepared by a 9.2.0.x database with OracleAS RepCA installed.

The workaround is to log on as a database user to manage Oracle Ultra Search, or invoke the following PL/SQL API to grant orcladmin super-user privileges.

Log on as WKSYS.

BEGIN
  WK_ADM.GRANT_SYSADMIN(
  <orcladmin dn>,
  1,
  null,
  <subscriber dn>
  )
EXCEPTION WHEN OTHERS THEN WK_ERR.RAISE;
END;

Here is an example.

BEGIN
  WK_ADM.SYSADMIN(
  'cn=orcladmin,cn=users, dc=us,dc=oracle,dc=com',
  1,
  null,
  'dc=us,dc=oracle,dc=com'
  );
EXCEPTION WHEN OTHERS THEN WK_ERR.RAISE;
END;

9.2.3 Users Cannot Access usearch.jsp or search.jsp

If a user, who has logged on to the Oracle Single Sign-On server using a browser, tries to access the URL for loading usearch.jsp or search.jsp without logging out of the Oracle Single Sign-On server, then the Web page returns an internal server error.

The workaround is to log out of the Oracle Single Sign-On server and then access usearch.jsp or search.jsp. You can also use a new browser window to access the search queries.

9.3 Documentation Errata

This section describes documentation errata for the Oracle Ultra Search User's Guide. It includes the following topic:

• Section 9.3.1, "Adding and Deleting Subscribers"

9.3.1 Adding and Deleting Subscribers

The "Configuring Oracle Ultra Search in a Hosted Environment" section says to use the usca.sh and usca.bat scripts to add and delete subscribers.

Instead, use the following command to add subscribers:

java -jar ORACLE_HOME/ultrasearch/lib/usca.jar action=add_subscriber 
  oh=ORACLE_HOME oid_user_dn="cn=orcladmin" oid_passwd=<oid_user_dn's password> 
  oid_subscriber_dn=<subscriber's DN> (e.g., "dc=uk,dc=oracle,dc=com")> 
  logfile=<log file path> db_sn=<database service name

Use the following command to delete subscribers:

java -jar $ORACLE_HOME/ultrasearch/lib/usca.jar action=delete_subscriber 
  oh=ORACLE_HOME oid_user_dn="cn=orcladmin" oid_passwd=<oid_user_dn's password>   
  oid_subscriber_dn=<subscriber's DN (e.g., "dc=uk,dc=oracle,dc=com")> 
  logfile=<log file path> db_sn=<database service name