Skip to main content
Skip table of contents

Bug fixes (MongoDB)

1.2.0

Bug number

Resolution

CE-142

Fixed an issue where dSource enable failed with “IllegalObjectAccess” after replication failover.

CE-189

Fixed an issue when a MongoDB instance is terminated with kill that would sometimes fail and leave child processes orphaned.

CE-240

Fixed an issue where sh.addShard() fails if the staging database password contains special characters.

CE-256

sudo rule examples in MongoDB staging and target requirements have been corrected.

CE-79

A description of the expected format for backup files has been added.

CE-186

Fixed an intermittent MongoDB issue where it errors out with “Address already in use” if temporary socket files for available ports exist on the staging environment.

1.1.0

Bug number

Resolution

DXE-986

Removed an additional “Source sharded” prompt if the type of data source (dSource_Type) has already been selected as shardedsource.

DXE-987

Removed the "Convert each shard to replica set" option from the dSource linking process, as it applies only to VDBs.

1.0.2

Bug number

Resolution

DXE-985

Fixed an issue where the incorrect date format in backup metadata files produce a linking error.

DXE-964

Fixed an issue where enabling authentication with User Auth Mode as ldap breaks dSource/VDB creation.

1.0.1

  • Sharded dSource creation workflow has been fixed.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.