• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 95 subscribers
  • Views 4319 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The system (Database (****)) does not have a data store! error in Target System Browser

Tim Staddon
over 7 years ago

Hi,

I am getting this error when resolving two key resolutions by reference (KRBR for short) on a target table which is used for account-in-group mapping:

Property (vrtKRBR_UserStatus@table) could not read the value from system object (id)!
The system (Database (Oracle: database)) does not have a data store!

But the object matching rules test OK, a simulation of the sync works OK, and the object browser correctly displays the result after throwing this error.

So, the userID one is configured like this.

Name: vrtKRBR_USERID_AsString

Display name: USERID_AsString

Description: Get USERID_AsString (conversion from autonumber to string) from USER table

Base property: USERID (pick from list)

Search property: vrtConv_USERID_AsString (picked from list)

The group one is set up the same way but uses group ID from the GROUP table.

On the Identity Manager side the UNSAccountB and UNSGroupB objects have KRBR pointing to their respective ObjectGUIDs, and the mappings for both tables populate the ObjectGUID by converting the autonumber.

In Object Browser, after I dismiss the errors, the two vrtKRBR attributes are shown correctly and a property join has USERID|GROUPID for all rows, exactly as I'd expect.

So what does the error mean?

Thanks in advance

Parents
  • 0 over 7 years ago
    Hi,

    Not to worry - I found a way round it by using object reference instead.

    The customer's application has different key columns (none configured to be unique) on the USER and GROUP tables, but both tables have an autonumber column which is unique. The mapping table for user in group doesn't use these IDs, it uses a shortname column instead.

    I wanted to use the autonumber IDs as the objectGUIDs, to guarantee 1:1 match. This works fine on importing users and groups but throws the error on the user-in-group mapping table.

    The customer has just confirmed that the shortname columns in each table are generated by code, and so each value is always unique. So I don't need the key reference to get the autonumber.
Reply
  • 0 over 7 years ago
    Hi,

    Not to worry - I found a way round it by using object reference instead.

    The customer's application has different key columns (none configured to be unique) on the USER and GROUP tables, but both tables have an autonumber column which is unique. The mapping table for user in group doesn't use these IDs, it uses a shortname column instead.

    I wanted to use the autonumber IDs as the objectGUIDs, to guarantee 1:1 match. This works fine on importing users and groups but throws the error on the user-in-group mapping table.

    The customer has just confirmed that the shortname columns in each table are generated by code, and so each value is always unique. So I don't need the key reference to get the autonumber.
Children
No Data