Troubleshooting SqlDBM connectivity
Resolve credential, permission, and visibility issues between SqlDBM and Atlan.
The messages below are the ones SqlDBM shows when the cause is on the Atlan side, or when the fix is in Atlan. Messages about mapping types, deleted fields, and skipped values are explained in Data Governance Integrations on SqlDBM's support site.
Credentials rejected
SqlDBM says: The Atlan credentials were rejected.
The client ID or client secret is wrong, or the OAuth client was deleted in Atlan. Delete the OAuth client and create a new one, then re-enter the values in SqlDBM under Manage > Edit connection.
Credentials lack permissions
SqlDBM says: The Atlan credentials lack the permissions this probe needs.
The persona linked to the OAuth client doesn't grant both Assets > Read and Update custom metadata values on the connection. Edit the persona's metadata policy in Atlan. See Create persona.
OAuth client sees no connections
SqlDBM says: The Atlan OAuth client sees no connections, either none exist yet, or no persona granting metadata read and custom-metadata update is linked to the client.
No persona is linked to the OAuth client, or your workspace has no connections yet. Link the persona to the client in Atlan, and confirm the warehouse connection exists and is covered by the persona's metadata policy. Then select Refresh in SqlDBM.
Atlan can't be reached
The workspace URL is wrong, your network blocks SqlDBM's requests, or Atlan is unavailable. Check the URL, then confirm your network policy permits HTTPS traffic from SqlDBM to the workspace.
Connection missing from SqlDBM's connection list
The list shows the connections the OAuth client can see through its persona. Add a metadata policy on the missing connection to the persona, then select Refresh on the mapping's Settings tab.
Property missing from SqlDBM's attribute list
SqlDBM offers the properties Atlan reports as applicable to tables or columns on the selected connection. Check the property's Applicable asset types and Connections in Atlan, then select Refresh in SqlDBM.
Values pushed but not visible on asset pages in Atlan
The value was written, but the property isn't applicable to the asset's connection, so Atlan doesn't display it. On a SqlDBM-owned structure, SqlDBM adds the connection itself on first push and Atlan reflects it within a minute. On any other structure, add the connection under the property's Connections in Atlan.
Run report says value has no matching option in Atlan
SqlDBM says: "Value" in Field has no matching option in Atlan.
A dropdown or multiselect value in SqlDBM has no option on the Atlan property. On a SqlDBM-owned structure, SqlDBM adds the option on push. On any other structure, add the option in Atlan and push again.
Push refused because it holds too many values
SqlDBM says: This mapping holds more values than one push to the external system can carry, so nothing was sent.
The push can't run in one request and background batching isn't available in your environment. Push fewer objects or fields at a time.
Another project is using this database
SqlDBM says: Another project is pushing to the external container 'X' or A preview of the external container 'X' is running.
Another push or pull is using the same Atlan database. Wait for it to finish and try again.
Atlan is busy with another operation on this container
SqlDBM says: Atlan is busy with another operation on this container.
The same situation, reported from the pull side. Try again in a moment.
Mapped objects no longer exist in Atlan
SqlDBM says: Some mapped objects no longer exist in the external system. Re-map them and push again.
The assets were deleted or re-crawled in Atlan, so their identifiers changed. In SqlDBM, refresh the mapping's Objects tab and re-map the affected objects.
See also
- Set up SqlDBM: Prepare Atlan and connect it from the SqlDBM dashboard.
- What does Atlan crawl from SqlDBM?: Asset coverage, field types, and limits.
Need help
If you can't find the answer you're looking for, contact Atlan support by submitting a request.