Troubleshooting OIM - Error - Cause - Solution

Troubleshooting OIM - ORA Error:

1] Catalog search in OIM showing error when user is clicking on Request access
Error:
IAM-7130125 : Search token caused Oracle text DRG issue, DB exception is :ORA-29902: error in executing ODCIIndexStart() routine ORA-20000: Oracle Text error: ORA-30576: ConText Option dictionary loading error ORA-04031: unable to allocate 24368 bytes of shared memory ("shared pool","CAT_TAGS","KGLH0^eaf287a9","drdmlpo:new policy") 29902

Cause:
The error message you provided indicates that there was an issue with Oracle Text and a failure occurred during the execution of the ODCIIndexStart() routine. Additionally, there was a problem with loading the ConText Option dictionary, and the shared pool memory allocation failed.

The ORA-29902 error typically occurs when there is a problem with the Oracle Text index. It could be caused by a variety of factors such as incorrect syntax in the query, missing or invalid index metadata, or insufficient privileges.

The ORA-30576 error suggests that there was an issue with loading the ConText Option dictionary, which is responsible for managing thesaurus and stopword lists. This can occur if the dictionary files are missing or corrupt, or if the dictionary configuration is incorrect.

Finally, the ORA-04031 error indicates that there was a failure in allocating shared memory in the shared pool. This can happen if there is insufficient memory available, or if the shared pool size is too small.

To resolve this issue, you may need to perform the following steps:

  • Verify that the Oracle Text index and the associated metadata are valid and correctly configured.
  • Check that the ConText Option dictionary files are present and correctly configured.
  • Increase the shared pool size to allow for more memory allocation.
  • Consider optimizing the query to reduce memory usage.
  • Check for any other errors in the database log and resolve them accordingly.
If you are unsure how to proceed or require further assistance, it is recommended to consult with a database administrator or Oracle support representative.

Solution: 
To increase the shared pool size in Oracle Database, you can follow these steps:
Connect to your Oracle Database instance using a database administrator account.
Check the current size of the shared pool by running the following SQL command:

SELECT name, bytes/1024/1024 "Size in MB"
FROM v$sgastat
WHERE name LIKE '%shared pool%';

This will display the current size of the shared pool in megabytes.

Determine the new size for the shared pool. This will depend on the memory requirements of your database and the available resources on your server. Oracle recommends that the shared pool size be at least 100 MB for most installations.

Modify the size of the shared pool by running the following SQL command:

ALTER SYSTEM SET shared_pool_size=<new_size> scope=spfile;
Replace <new_size> with the new size for the shared pool in bytes. For example, if you want to increase the shared pool size to 500 MB, you would run:

ALTER SYSTEM SET shared_pool_size=500M scope=spfile;
Note that you need to specify the size in bytes or using a shorthand notation like "M" for megabytes or "G" for gigabytes.

Restart the database for the changes to take effect by running:

SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP;
Alternatively, you can run the following command to apply the changes without restarting the database:

ALTER SYSTEM SET shared_pool_size=<new_size> scope=both;
However, this may cause a performance impact and is not recommended in production environments.

After completing these steps, your Oracle Database instance will have a larger shared pool size, allowing for more memory allocation.



2] Exception during execution of SQL Query using Catalog Tag string search
Errorclause is: CONTAINS(TAGS,'<query> <textquery grammar="CTXCAT">Test*</textquery></query>' )>0

Exception occurred
java.sql.SQLException: ORA-20000: Oracle Text error:
DRG-10599: column is not indexed

        at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:509) ~[ojdbc8.jar:19.3.0.0.0]
        at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:461) ~[ojdbc8.jar:19.3.0.0.

Solution:  Refer below oracle official documentation

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=258386712968283&parent=EXTERNAL_SEARCH&sourceId=TROUBLESHOOTING&id=1612970.1&_afrWindowMode=0&_adf.ctrl-state=11mgryr4k0_53



Comments

Popular posts from this blog

PUTTY - The server's host key is not cached in the registry cache

OIM-12c Installation - FMW - SOA - IDM

SAML & OAuth 2.0