Description of problem: When activating a role, it returns error 16 and it
doesn't print if role is active or not.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.6.1-16

How reproducible: Consistently

Steps to Reproduce:
1. Install 389-ds-base-1.3.6.1-16
2. Create instance and add few user entries.
3. Add a role.
[root@cloud-qe-06 389ds-replica]# ldapmodify -ax -p 13905 -h localhost -D
"cn=Directory Manager" -w Secret123 << EOF
dn: cn=nrole1,dc=example,dc=com
objectclass: LDAPsubentry
objectclass: nsRoleDefinition
objectclass: nsComplexRoleDefinition
objectclass: nsNestedRoleDefinition
nsRoleDN: uid=usr4role9,dc=example,dc=com
> EOF
adding new entry "cn=nrole1,dc=example,dc=com"
4. Try ns-inactivate.pl and ns-inactivate.pl scripts in sequence.

[root@cloud-qe-06 389ds-replica]# ns-accountstatus.pl -Z slapd-deftestinst -p
13905 -h localhost -D "cn=Directory Manager" -w Secret123 -I
cn=nrole1,dc=example,dc=com
cn=nrole1,dc=example,dc=com - inactivated (directly locked).

[root@cloud-qe-06 389ds-replica]# ns-activate.pl -Z slapd-deftestinst -p 13905
-h localhost -D "cn=Directory Manager" -w Secret123 -I
cn=nrole1,dc=example,dc=com
cn=nrole1,dc=example,dc=com activated.

[root@cloud-qe-06 389ds-replica]# ns-activate.pl -Z slapd-deftestinst -p 13905
-h localhost -D "cn=Directory Manager" -w Secret123 -I
cn=nrole1,dc=example,dc=com
ldap_modify: No such attribute (16)

ns-activate.pl script returns error 16 for roles which are active.

Actual results: It returns error 16.

Expected results:  Its expected to return error 100, if its already active or
activated.