Apply error 'ORA-01403: no data found' occurring on all clusters every 15 minutes
Originally Published: 2012-01-23
Article Number
Applies To
RKM Appliances configured as multiple clusters joined in a group
Issue
The second and third clusters in the group initially show an Apply error "ORA-06575: Package or function HASH_VALIDATION is in an invalid state", and then subsequently only the other error "ORA-01403: no data found" repeats
Oracle Apply errors "ORA-01403: no data found" and "ORA-06575: Package or function HASH_VALIDATION is in an invalid state" started occurring soon after applying RKM Appliance patch 2.7.1.4
Both errors, ORA-01403 and ORA-06575, are seen on the /status/db page
Cause
The error "ORA-01403: no data found" is caused by replication monitoring feature introduced in 2.7.1.4. This error repeats on each cluster every 15 minutes which is due to the replication monitoring cronjob set by default (in 2.7.1.4) to run every 15 minutes.
Resolution
The problem with Apply errors "ORA-01403: no data found" re-occurring on regular basis (KMA-2446) has been fixed in RKM Appliance hotfix 2.7.1.7. The Apply errors can be cleared out using the procedure below.
*** It is highly recommended to contact RSA Customer Support for a review of /status/db reports before following the procedure below to clear out Apply errors, as the procedure will clear ALL Apply errors. ***
Follow the steps below to clear out the Apply errors:
1. Stop crond service on ALL appliances (after login as root):
service crond stop
2. Update permissions in Oracle db, carry out this step on each cluster (only on the primary node of each cluster):
su - oracle
sqlplus / as sysdba
SQL> GRANT EXECUTE ON DBMS_CRYPTO TO LOCAL;
SQL> exit
exit
3. Delete the Apply errors on each cluster (only on the primary node of each cluster) using the script "cs_delete_apply_errors.sh" (a part of /status pages):
cd /opt/rsa/setup/sh
./cs_delete_apply_errors.sh
(Note that this step may take a long time to complete depending on the number of Apply errors. For example, it took this script approximately 1 hour to clear around 30,000 such Apply errors. You can run this script concurrently on all clusters to save some time.)
4. Start crond service:
service crond start
5. Check /status/db report on all clusters to confirm that the Apply errors have been cleared.
6. If the number of Apply errors was very large (e.g., around 30,000 or so), it is recommended to restart Oracle on all clusters (to avoid potential Replication error ORA-23603). To do so, follow these steps:
- Login as root on each cluster
- To stop Oracle, run the command "service oracle stop"
- To start Oracle, run the command "service oracle start"
Workaround
Notes
KMA-2446
Related Articles
How to resolve the issue of logging proxy server IP address for every request 10Number of Views NT: PIN on token has to be reset every ten minutes 25Number of Views Every application restart loses the customerstrings.properties file in versions 7.0.2 and 7.1.0 of RSA Identity Governance… 45Number of Views Customer getting collected on every login to FI website 3Number of Views 'AFX server is not running' message printed in logs every minute for each unused (Disabled, Not running, or deleted) AFX S… 1Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?