I recently installed Netwrix Access Analyzer 12.0. The install went very smooth. When I started the first scan, I got an error message stating I needed to run the “Create Schema” job first. After running the job, it is now on Task 18. Data Migration and is on SQL Script 1 of 3. It has now been running for almost 48 hours. Is it normal to run that long? Is it possible to run the Create Schema on individual jobs rather than all of them at once? Just wanted to check here first before opening a ticket.
Hi Steven,
First, let me welcome you to the Netwrix Community!
The Create Schema job is responsible for updating and creating tables, functions, and views in your T1 database. In this version, we have introduced a couple of steps that now allow us to support Azure data and migrate data to allow our coordination service to support collections. The time it takes for this job to run is proportional to the size of your environment. This process runs a few queries that incur a one-time cost during the host upgrade and trustee mapping to T1.
Without specifics about your environment of the available resources on your NAA server, it’s difficult to say whether the run time is expected or a sign of a larger problem. If you see this job running and not making progress, we would be happy to work with you on opening up a support case on your behalf and working through collecting the necessary artifacts for development to further triage.
Thanks!
2 Likes
Thanks for the explanation. When working with techs in the past, they’ve had to run this job for different reasons, and it only ran for about 7 seconds. So far, it’s at 78 hours and still on task 18. Data Migration SQL Script 1 of 3. Looking at the job now, not sure if I should have selected individual hosts rather than leaving the Use Default Setting checked. Technically, this job doesn’t inherit any hosts. Could that be why it’s running forever?
After looking at the past results of the Create Schema, the 17. Create Azure Tables and 18. Data Migration are new. I’ll open a ticket to have a tech look into it.
Hi, Steven -
Thanks for keeping us updated. Based on the fact that this is a new behavior, it does sound like a ticket is the path forward. Support should be able to do a deeper dive on what was different during this most recent run.
Best,
-Ben.
1 Like
Thanks for the reply. Ticket has been opened.
1 Like
Hi Steven,
Was Support able to help you resolve your problem?
Yes they were. Apparently, the fix was to remove the primary key restraint on a couple of tables in the database. Once we did that, the job finished without issue.
After reading the analysis of the job, it was migrating columns from one table into a new table, then dropping the columns. Instead of one table with about 20 columns, now there are 2 tables with 10 columns each. We have over 329 million rows and might have been too much for the job to process.
1 Like