Issue with UCX Assessment Installation via Automation Script - Schema Not Found Error

Sudheer2
New Contributor III

‎05-22-2025 09:54 AM

 

Hello,

I'm encountering an issue while installing UCX Assessment via an automation script in Databricks. When running the script, I get the following error:

13:38:06 WARNING [databricks.labs.ucx.hive_metastore.tables] {listing_tables_0} failed-table-crawl: listing tables from database -> ALL : [SCHEMA_NOT_FOUND] The schema `ALL` cannot be found. Verify the spelling and correctness of the schema and catalog.

 

 

However, when I run the same installation manually with the command:

 

 
databricks labs install ucx@v0.57.0

 

 

I’m prompted to specify the following parameters:

  • Comma-separated list of workspace group names to migrate (default: <ALL>)

  • Comma-separated list of databases to migrate (default: <ALL>)

    When I use the default <ALL> values during the manual installation, the process works without any errors, and the UCX dashboard populates correctly.

    In my automation script, I am explicitly setting the following configuration:

     

     
    WORKSPACE_GROUPS="<ALL>" DATABASES="<ALL>"
     

    Despite this, I still get the error: [SCHEMA_NOT_FOUND] The schema 'ALL' cannot be found.

    Could anyone provide insight into why this is happening or how I can resolve this issue in the automation script? Is there any other parameter I need to adjust to make sure the installation runs correctly in the script?

    Thanks in advance!

    #UCX #Assessment #databricks

0 Kudos

mark_ott
Databricks Employee
Databricks Employee

‎11-10-2025 05:29 PM

The error occurs because the automation script explicitly sets WORKSPACE_GROUPS="<ALL>" and DATABASES="<ALL>", which the UCX installer interprets literally as a schema called "ALL"—instead of using the special meaning that the manual prompt does when you just press Enter or accept the default. When you install manually and accept the default <ALL>, the CLI substitutes this internally to mean "all schemas" and "all workspace groups," but the script input is treated as a specific schema name, which does not exist—hence the "SCHEMA_NOT_FOUND" error.​

Correct Way to Use <ALL> in Automation

  • Do not set DATABASES="<ALL>" directly in your automation script.

  • Leave the environment variable unset, or omit the parameter entirely in your automation, so that the CLI falls back to its default behavior and interprets <ALL> correctly.

  • If your script must provide a value, try passing an empty string ("") or not setting the DATABASES and WORKSPACE_GROUPS environment variables at all.

Recommended Fix

  • Remove WORKSPACE_GROUPS and DATABASES variable assignments from your script when you want all databases/groups to be processed.

  • Alternatively, update your script to match exactly how the manual process works—let the installer prompt for these fields, or investigate if simply supplying an empty value ("") works.

Additional Notes

  • This behavior is a known issue in Databricks Labs UCX installations and is noted in troubleshooting forums.

  • Always test automation scripts with parameter variations to determine whether a default prompt or empty string substitutes for <ALL> correctly.​

If you continue to encounter issues, consult the UCX troubleshooting guide or Databricks community discussions for more advanced script configuration examples

0 Kudos