AnsweredAssumed Answered

Selecting distinct roles

Question asked by Neha Singh on Jun 22, 2020
Latest reply on Jul 22, 2020 by Neha Singh

Like • Show 0 Likes0
Comment • 9

I have configured a cache DB based application in IGL through custom connection. I have deployed the driver and did connection, which worked. Although, when I am collecting entitlements in EDC, I am getting error when using distinct keyword in query. The entitlements look complex as you see in below screenshot which I am guessing is the reason. The exception in query test page is below. Please let me know how can i fix this error.

FYI: It works fine without distinct keyword but that will reject if two or more users have access to same entitlements.

No one else has this question

Outcomes

9 Replies

Neha Singh Jun 22, 2020 5:20 AM

Also, I saved query anyway with distinct keyword and tested the collector which was successful but run is failing with below error:

Actions

Ian Staines Jun 22, 2020 11:50 AM
Mark Correct
Correct Answer
I assume this is a database collector right? What is the database and the database driver you are using.

Also what version and patch of RSA Identity Governance & Lifecycle are you on?
Like • Show 0 Likes0
Actions
- Neha Singh @ Ian Staines on Jun 23, 2020 8:17 AM
  Mark Correct
  Correct Answer
  Yes Ian,it is data collector. It is cache database connection which I did after deploying specific driver. Driver class 'com.intersys.jdbc.CacheDriver'
  
  RSA IGL Version: 7.1 patch 02
  Like • Show 0 Likes0
  Actions
  - Ian Staines @ Neha Singh on Jun 23, 2020 12:37 PM
    Mark Correct
    Correct Answer
    I have never heard of that database before and we do not have a published datasheet or any guidance specific to this type of database collector.
    
    The error text "Could not get entitlement bags" usually occurs in context of other errors. Perhaps you could post the full log message(s).
    Like • Show 0 Likes0
    Actions
    - Neha Singh @ Ian Staines on Jun 24, 2020 5:55 AM
      Mark Correct
      Correct Answer
      EC[31002] Context[Collector Name=Centricity Cache EDC, Agent Name=AveksaAgent, Data Run ID=4749Reason=com.aveksa.sdk.collector.CollectionException: com.aveksa.common.DataReadException: ERROR: Could not get entitlement bags: . Caused by com.aveksa.common.DataReadException: ERROR: Could not get entitlement bags: . Caused by java.sql.SQLException: [SQLCODE: <-400>:] [Cache Error: <%0AmBk1+6^%sqlcq.pSYS.cls36.1 ^||%t(1," %ALL %DB_%DEFAULT %DB_CACHEAUDIT %DB_CACHELIB %DB_CACHES>] [Location: ] [%msg: %0AmBk1+6^%sqlcq.pSYS.cls36.1 ^||%t(1," %ALL %DB_%DEFAULT %DB_CACHEAUDIT %DB_CACHELIB %DB_CACHES>]] Message[Data collection failed on the agent]
      --- This is the complete admin error. Could you be please specific if there is any other log you wanted?
      
      FYI: Everything with this application is completed except that I can't use distinct keyword in EDC.
      Like • Show 0 Likes0
      Actions
      - Ian Staines @ Neha Singh on Jun 24, 2020 11:08 AM
        Mark Correct
        Correct Answer
        I think this may be too complicated to resolve in a community discussion. I recommend you open a Support Case so that we can gather full logs for analysis.
        
        Note that this SQL driver has never been tested or qualified so there is no implicit expectation of interoperability.
        
        You might also consider testing the driver and your SQL statement outside of our product using a third party tool (such as Squirrel SQL) to confirm this is not an issue with the driver itself.
        
        I see Intersystems has an integration document for Squirrel SQL
        
        Connecting to Caché with SQuirreL SQL, an external SQL client |
        Like • Show 0 Likes0
        Actions
        Neha Singh @ Ian Staines on Jun 24, 2020 11:39 AM
        Mark Correct
        Correct Answer
        Yes, it might be complex but in this DB connection, I am able to query against other schemas and tablespaces in this DB and get the result set using distinct keyword but only one specific schema which is required gives me this error.
        So, I think driver issues should not be there whereas considering the complexity of the role names as below, IGL might not be able to trace the whole ents and find the distinct values as they long names with special chars . And that is the reason I had brought this topic in discussions over here.
        Like • Show 0 Likes0
        Actions
        Ian Staines @ Neha Singh on Jul 7, 2020 3:25 PM
        Mark Correct
        Correct Answer
        I am sorry no one was able to assist you. Were you able to resolve this isuse?
        Like • Show 0 Likes0
        Actions
        Neha Singh @ Ian Staines on Jul 22, 2020 8:10 AM
        Mark Correct
        Correct Answer
        yeah, came out to be a table column issue which RSA creates dynamically in data collection process and is limited to 256 char limit. As you see here, these cache roles are complex, logical and quite lengthy, hence the reason they are not being read in collection.
        
        Raised another question here - varchar limit for Entitlements in data-collection but there is nothing we can do for this application apart from asking app team to suggest some alternative column representing roles, if they can or else I dont see automation option for it.
        Like • Show 0 Likes0
        Actions

Selecting distinct roles

Outcomes

Related Content

Recommended Content