Beehive Post Upgrade Step, Building a New Search Index of Existing Artifacts, Is Hanging (Doc ID 1257094.1)

Last updated on OCTOBER 21, 2015

Applies to:

Beehive - Version 2.0.1.1.0 and later
Information in this document applies to any platform.
*** Checked for relevance on 30-Sep-2013 ***


Symptoms

When following the post upgrade step Building a New Search Index of Existing Artifacts to run recovery for search index it is observed that the monitoring results are not advancing.

This is seen in the results of the following command run to monitor the recovery process is not showing any changes in progress.
beectl list_operation_statuses --operation_status <replace by Search recovery for scope ID>

In the above the <Search recovery for scope ID> is provided as the result for the "beectl add_search_recovery_scope" command launched during the post upgrade step of Building a New Search Index of Existing Artifacts for Beehive patchsets 2.0.1.2.1, 2.0.1.3 or 2.0.1.2.4.

For example (the numbers in bold face stay the same):
beectl list_operation_statuses --operation_status 1D76:1278:opst:8616E1287104BC78E040A8C020A830BC00000094E675
--------------------------------------------------------------------------------
Name
+---------------------------------------------------------------------------
| Operation
+---+-----------------------------------------------------------------------
| Current Status
+---+-------------------+---------------------------------------------------
| Completion Percentage | Status Code
+-----------------------+---------------------------------------------------

--------------------------------------------------------------------------------
Search recovery for scope 1D76:1278:enpr:8616E1287104BC78E040A8C020A830BC0000000
00AF1
+---------------------------------------------------------------------------
| SEARCH_RECOVERY
+---+-----------------------------------------------------------------------
| 9600 out of 35666 emails processed for workspace 1D76:1278:wspr:32AD1A
| 968A3C456DBB6B25BACBD7EBA0000000000217; 613022 out of 1222592 emails/i
| nvitations processed for the specified scope
+---+-------------------+---------------------------------------------------
| 51 | Executing
+-----------------------+---------------------------------------------------

1 Record(s) displayed.


You could also notice a CPU spike as result of the crawler and indexing not progressing.

The following errors might be seen in the alert log:

Mon Oct 04 14:43:44 2010
Errors in file /u01/app/oracle/diag/rdbms/beedb/beedb/trace/beedb_j007_27106.trc:
ORA-12012: error on auto execute of job 184238
ORA-06532: Subscript outside of limit
ORA-06512: at "BEE_CODE.SS_INDEX_JOB_PKG", line 225

Changes

Beehive patchset 2.0.1.2.1, 2.0.1.3 or 2.0.1.4 was applied in the environment and the command "beectl add_search_recovery_scope" was executed to index old data.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms