A DBNAME defined in a CV's RESOURCE TABLE in order to ship the database work to another CV is having no effect - the transaction is running in the local CV.
Release: All supported releases.
The DBNAME was derived as a result of a subschema mapping defined in the original DBNAME.
Only the original DBNAME supplied by the application will be searched for in the RESOURCE TABLE when considering if the database work should be performed in a remote CV.