Troubleshooting

Troubleshooting: my schema import is stuck or failing

This page covers problems while importing a schema. For how imports work, see What schema import does.

I can’t find the import after starting it

Likely cause: Import details live under Organization Settings, which only organization admins can open.

What to do:

  1. If you’re an admin, go to Organization Settings › Schema Imports and open the import.
  2. If you’re not, watch the schema’s tabs: objects appear as each stage finishes. Ask an admin to check any failures.

It’s been “Analyzing file structure…” for a long time

Likely cause: A large or complex script. Splitting takes longer when AI is involved.

What to do:

  1. Wait a few minutes. The page refreshes itself.
  2. If nothing changes after about 10 minutes, click Refresh. The import keeps running on the server even if the page stopped updating.
  3. If it’s still stuck, cancel and import the script in smaller parts.

A table fails

Likely cause: An unrecognized data type, a vendor-specific clause, or a reserved word used as a column name.

What to do:

  1. Click Fix on the item and read What went wrong.
  2. Edit the DDL. For example, swap BIGLONG for BIGINT, remove a partition clause, or quote the reserved word.
  3. Click Retry with Changes.

If that doesn’t work: Leave it failed, finish the rest, and create the table by hand with Create Table › Paste Code using corrected DDL.

A table shows “Skipped”

Likely cause: A table with that name already exists in the schema. Script imports never overwrite existing tables.

What to do: Nothing, if you meant to keep your version. To take the script’s version, delete or rename the existing table and retry the item.

Indexes fail

Likely cause: The index refers to a table or column that didn’t import.

What to do:

  1. Fix the table first.
  2. Click Resume All Failed, or accept Retry All Dependents when the fixed table succeeds.
  3. If the index refers to something that will never exist, edit its DDL to drop the reference.

Relationships fail

Likely cause: The foreign key refers to a table or column that didn’t import, or the column types don’t match.

What to do:

  1. Check both tables exist and the join columns have matching types.
  2. Remove vendor-specific options (such as deferrable constraints) from the DDL.
  3. Retry or resume.

A view, procedure or function fails

Likely cause: SQL that Kenseme can’t parse, often a vendor-specific extension, or a reference to an object that failed.

What to do:

  1. Check whether a dependency failed. Fix is disabled until it’s fixed.
  2. Click Fix, simplify the SQL, and retry.
  3. If it still fails, create the object by hand and paste the SQL on its SQL tab.

Most objects have no description

Likely cause: The script had no description statements (sp_addextendedproperty, COMMENT ON). A script import doesn’t write descriptions of its own.

What to do: Select the objects on their tab and click Generate Descriptions, or use Import Descriptions on the Info tab if you have descriptions in a file.

The import shows “Failed”

Likely cause: The import stopped before finishing. The banner shows why.

What to do:

  1. Click Refresh. It may have completed.
  2. Read the message, fix the cause, and click Resume Import or start a new import.
  3. If the message points to a server problem, contact your administrator with the schema name and the time you started.

“An import is already in progress for this schema”

Likely cause: Another script import is still running against the schema.

What to do: Wait for it to finish, or cancel it from Organization Settings › Schema Imports.

A connection import can’t read the source

Likely cause: The connection’s credentials, network access or permissions.

What to do:

  1. Read the error in the dialog and click Retry.
  2. Ask an admin to test the connection. See Database connections overview.
  3. If the review page shows extraction warnings, some catalog categories couldn’t be read. The change list may be incomplete; check the connection’s permissions.