| Summary | Unable to remove an IMR entry for the ORB name |
|---|---|
| Article Number | 18595 |
| Environment | Windows Orbix 6.3.4 |
| Question/Problem Description | Unable to remove an IMR entry for the ORB name ERROR: Unable to remove an IMR entry for the ORB name:IDL:omg.org/CORBA/PERSIST_STORE:1.0: minor = 0 x49540707 (<b>IT_PSS_DB:DB_CALL</b>), completion status = MAYBE |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | This issue is caused by incorrect configuration settings for the Berkeley DB locking subsystem due to the number of concurrent accesses to the IMR being higher than the configured locking resources. |
| Resolution | Ensure you increase the values for the following variables in the locator configuration scope. These variables configure the locking subsystem of the Berkeley DB. plugins:pss_db:envs:it_locator:lk_max_lockers: plugins:pss_db:envs:it_locator:lk_max_locks: plugins:pss_db:envs:it_locator:lk_max_objects: |
| Workaround | |
| Notes | For further information please see the Oracle Berkeley DB documentation, "Getting Started with Transaction Processing for C ", Chapter "Concurrency", section on Locks and Lock Resources. |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 10 September 2011 |
#KnowledgeDocs
#Orbix
