Documentum Connector for User fails RRS feed

  • Question

  • Hi,

    The documentum connector fails to get report from Documentum.

    11:37:23,207 DEBUG [TicketWatchdog$ExpirationScanner] Scanned 0 ticket custodians, 0 tickets were refreshed
    11:39:23,217 DEBUG [TicketWatchdog$ExpirationScanner] Scanning ticket custodians for expired tickets
    11:39:23,217 DEBUG [TicketWatchdog$ExpirationScanner] Scanned 0 ticket custodians, 0 tickets were refreshed
    11:40:08,160 DEBUG [ObjectProtocolV1] deserializeType: 2
    TYPE ERROR_TYPE 0000000000000000 0 0 0
     NULL F
    C  COUNT  INT S 0 0
    D  CODE  INT S 0 0
    E  STAMP  STRING S 0 0
    F  SEVERITY  INT S 0 0
    H  NAME  STRING S 0 0

    11:40:08,162 ERROR [DFCUsersDB] Failed to run query: SELECT a.user_name,a.user_os_name,a.user_login_name,a.user_privileges FROM dm_user a WHERE a.r_is_group='0' AND a.user_state='0' AND NOT EXISTS (SELECT * FROM dm_group b where b.i_all_users_names = a.user_name) ENABLE(ROW_BASED) -  msg - [DM_QUERY_E_CURSOR_ERROR]error:  "A database error has occurred during the creation of a cursor ('ORA-01555: snapshot too old: rollback segment number 51 with name "_SYSSMU51$" too small')."
    11:40:08,162 INFO  [DFCUsersDB] User directory loaded
    11:40:08,575 ERROR [DFCUsers] Error running the user directory connector - null
    11:40:08,575 ERROR [DFCUsers] Error when crawling the source system: java.lang.NullPointerException
    11:40:08,576 ERROR [DFCUsers] java.lang.NullPointerException
            at java.util.AbstractSet.removeAll(
            at com.fastsearch.esp.cctk.usermonitor.UserDirectoryDispatcher.processUserDirectoryFile(
            at com.fastsearch.esp.cctk.usermonitor.UserDirectoryDispatcher.processUserDirectory(
            at com.fastsearch.esp.cctk.usermonitor.UserDirectoryConnector.submit(
            at com.fastsearch.esp.cctk.usermonitor.UserDirectoryConnector.execute(

    This doesnt even allows the values retreived for the users as part of groups to be synced into SAM .

    Thursday, November 15, 2012 6:02 PM

All replies

  • Hi,

    I believe that this is something that is occurring within the Oracle environment, and not in Fast or the Documentum connector.  There is an Oracle article on the ORA-01555 error below:

    There are two fundamental causes of the error ORA-01555 that are a result of Oracle

    trying to attain a 'read consistent' image. These are :

      o The rollback information itself is overwritten so that Oracle is unable to rollback

    the (committed) transaction entries to attain a sufficiently old enough version of the


      o The transaction slot in the rollback segment's transaction table (stored in the

    rollback segment's header) is overwritten, and Oracle cannot rollback the transaction

    header sufficiently to derive the original rollback segment transaction slot.

    This article also contains a solutions section as well that could be helpful with solving this problem.  Let us know your results.


    Rob Vazzana | Sr Support Escalation Engineer | US Customer Service & Support

    Customer Service   & Support                            Microsoft| Services

    Thursday, November 15, 2012 8:00 PM