000034989 - RSA Adaptive Authentication (On-Premise) customer seeing "inserted partition key does not map to any partition" error

Document created by RSA Customer Support Employee on Apr 4, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000034989
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Product/Service Type: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.3
IssueCustomer was finishing up an upgrade of Adaptive Authentication (On-Premise) V6 SP3 P4 to V7.3.
They were attempting an Analyze Soap call, and were getting an error:
java.sql.BatchUpdateException: ORA-14400: inserted partition key does not map to any partition 
Tasks- Database partitioning (USING_DATABASE_PARTITIONS) was enabled in the AAOP database
- A run of the CHECK_PARTITIONING.SQL script was run, and everything looked in order.
-  Confirmed all of the steps were completed as shown in the Install Guide for partitioning
ResolutionHowever, when we ran a query against the ALL_TAB_PARTITIONS:
select PARTITION_NAME,HIGH_VALUE,NUM_ROWS from all_tab_partitions where table_name='EVENT_LOG'; 
It was noticed that only two partitions existed for a two-node Oracle RAC cluster.  There should be three - I0 (eye-zero) plus one for each RAC node.
It was later learned that the customer had run the upgrade with only one node in their cluster, and then added the second node post-installation, but
had not run the ADD_NODE procedure as documented in the Install Guide.
The customer ended up re-running the upgrade with both nodes in the cluster, and the partitioning was created normally & successfully.