Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for Microsoft Windows B15501-23 |
|
![]() Previous |
![]() Next |
This chapter describes issues associated with Oracle Ultra Search. It includes the following topics:
This section describes upgrade issues and their workarounds for Oracle Ultra Search. It includes the following topics:
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
This section describes general issues and their workarounds for Oracle Ultra Search. It includes the following topics:
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.
This section describes documentation errata for the Oracle Ultra Search Administrator's Guide. It includes the following topic:
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