DPS 6 bind to backend error?

Question

Getting error for DPS 6. I think I have everything set up correctly. Binds to the DS are ok and anonymous thru DPS are ok. However when I bind thru DPS I get the access error below.
conn=132 op=0 BIND RESPONSE err=1 msg="Unable to retrieve a backend BIND connection" etime=0
Also in the DSCC under routing > data sources for the DPS is states the "operational status" as not available which I cant explain. Any ideas why I am not binding thru to backend DS?

Answer 1

Thanks Ludovic!
Actually I have tried to create another connectionhandler like directory-manager-connection-handler
aci-source : none
allowed-auth-methods : anonymous
allowed-auth-methods : sasl
allowed-auth-methods : simple
allowed-ldap-ports : ldap
allowed-ldap-ports : ldaps
bind-dn-filters : cn=directory manager
data-view-routing-custom-list : myView1
data-view-routing-policy : all-routable
description : for cn=Directory Manager
domain-name-filters : any
enable-data-view-affinity : false
ip-address-filters : any
is-enabled : true
is-ssl-mandatory : false
priority : 2
request-filtering-policy : no-filtering
resource-limits-policy : no-limits
schema-check-enabled : false
user-filter : any
Here is my data view:
alternate-search-base-dn : ""
alternate-search-base-dn : dc=com
attr-name-mappings : none
base-dn : dc=example,dc=com
contains-shared-entries : false
description : -
distribution-algorithm : none
dn-join-rule : none
dn-mapping-attrs : none
dn-mapping-source-base-dn : none
excluded-subtrees : -
filter-join-rule : none
is-enabled : true
is-read-only : false
is-routable : true
ldap-data-source-pool : myPool1
lexicographic-attrs : all
lexicographic-lower-bound : none
lexicographic-upper-bound : none
non-viewable-attr : none
non-writable-attr : none
numeric-attrs : all
numeric-default-data-view : false
numeric-lower-bound : none
numeric-upper-bound : none
pattern-matching-base-object-search-filter : all
pattern-matching-dn-regular-expression : all
pattern-matching-one-level-search-filter : all
pattern-matching-subtree-search-filter : all
process-bind : -
replication-role : master
viewable-attr : all except non-viewable-attr
writable-attr : all except non-writable-attr
However, when I did ldapsearch, I still got same error
ldapsearch -D "cn=Directory Manager" -w mypwd -h myhost -p port# -b "dc=example,dc=com" -s one "objectclass=*"
ldap_simple_bind: Operations error
ldap_simple_bind: additional info: Unable to retrieve a backend BIND connection
The reason I have kept trying using cn=Directory manaer is that I don't want to make change on our application (even it's only property file) after I migrate to the new version.
Thanks!