Content Management and Capture

Content Management and Capture

Come for answers. Stay for best practices. All we’re missing is you.

 View Only
Back to discussions
Expand all | Collapse all

FNRAC1004E/16E Unable to create Database connection or object store in FileNet Content Manager

  • 1.  FNRAC1004E/16E Unable to create Database connection or object store in FileNet Content Manager

    Posted Mon February 24, 2025 09:45 AM

    Hello IBM community,

    This is my first post here, and I'd like to share an issue I encountered while setting up a Database connection and Object Store in FileNet Content Manager v5.6, which is part of Cloud Pak for Business Automation v24, along with a solution.

    Problem Definition: I encountered the following error when attempting to create a database connection or object store through the FileNet ACCE GUI.
    Additionally, even after following the IBM documentation for adding a new object store (post-deployment), I was unable to see the newly created object store or database connection.

    The operation was unable to read from or write to the database. Property: 

    2025-02-18T11:38:12.698 0018A824 ENG  FNRCE0016E - ERROR MethodName: verifyProperties, PrincipalName: bpm.dev, 
GlobalTxn: false, UserTxn: false, ExceptionMsg: The operation was unable to read from or write to the database. Property: "JNDIDataSource", 
Value: "DB2JNDI"\ncom.filenet.api.exception.EngineRuntimeException: 
FNRCE0016E: E_DATABASE_ERROR: The operation was unable to read from or write to the database. 
Property: "JNDIDataSource", Value: "DB2JNDI" failedBatchItem=0\n       at com.filenet.engine.persist.CmDatabaseConnectionPersister.verifyProperties(CmDatabaseConnectionPersister.java:174)\n


    I explored several potential fixes, which I will link later in this post, but none of them resolved the problem.


    Solution:

    1. Follow the steps in the first three links to add a new object store (post-deployment).
    2. Take a backup of the icp4adeploy-cpe-config ConfigMap.
    3. Delete the icp4adeploy-cpe-config ConfigMap.
    4. Restart both the cp4a-operator and FileNet(cpe-deploy) pods.
    5. Wait approximately 30 minutes for the new ConfigMap to be created.
    6. Access FileNet ACCE, and you should now see the new database connection and object store. If they didn't get created, you can manually create them without encountering the previously mentioned errors.

    References:
    https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.1?topic=manager-optional-adding-additional-object-stores-post-deployment
    https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.1?topic=cfcmdswrps-creating-secrets-protect-sensitive-filenet-content-manager-configuration-data
    https://www.youtube.com/watch?v=PX7siE93HxE
    https://community.ibm.com/community/user/automation/discussion/acce-database-connection-fail
    https://www.ibm.com/support/pages/when-user-create-object-store-filenet-advanced-console-content-engine-he-meet-error-fnrac1004e-how-solve-it



    ------------------------------
    Peter Victor
    ------------------------------


Related Content