Hello,
we are using the VDS with two data sources, both are databases with the scope to a single table.
One table contains company addresses while the other one contains data of persons.
If we use one virtual tree and only one node for e.g. the company data source we receive the attribute schema of this table by viewing it with external LDAP browsers like LDAP Admin. So this works for both data sources used in single mode (single data source and single virtual tree).
When we configure another virtual tree for the other data source (persons) as well as another user (only one user per tree) to connect to each tree by different username and password, we only receive the schema of the data source which is selected in the first tree.
Here are a few information about what's happening when we using LDAP Browser LDP.EXE to get the schema.
We used LDP.EXE because it is showing the schema naming context right after binding.
Connecting to LDAP Browser with the corresponding user of tree1 (tree1,o=db,*):
Schema naming context schows up: cn=schema,o=db
Accessing the schema works fine and we receive all attributes.
There is all ok.
Connectiong to LDAP Browser with the corresponding user of tree2 (tree2,o=db2,*):
Schema naming context: cn=schema,o=db
Accessing this schema returns: Server error: Couldn't perform DN to Data source mapping
Shouldn't be the schema of this binding cn=schema,o=db2?
This is even the correct path in the tree2.
Yes, the schemas of both tables are different, but we need to access them.
Is there any possibility or do we have any logical issue here?
Do you have any idea how this could work?
Maybe there is an even better solution where we only need one tree and one single user - that would be even more perfect 
Thank you in advance.
Kind regards,
Bastian