Skip navigation

Okay, here's the cmd window when I ran my final import command:

Yup, it failed and stopped processing within a minute.  I got errors for the user names and the schedules.  The schedules I expected so I'll work on this one first.  Here's what the error file produced:

Unrecognized target_name Every 60 Minutes found in the mapping file
Unrecognized target_name ??? found in the mapping file
Unrecognized target_scheduled_action_type Extract found in the mapping file
Unrecognized target_scheduled_action_type Extract found in the mapping file
Unrecognized target_scheduled_action_type Extract found in the mapping file
Unrecognized target_scheduled_action_type Extract found in the mapping file
Unrecognized target_scheduled_action_type Extract found in the mapping file
Scheduled action types: Refresh Extracts and Extract must be equivalent
Scheduled action types: Refresh Extracts and Extract must be equivalent
Scheduled action types: Refresh Extracts and Extract must be equivalent
Scheduled action types: Refresh Extracts and Extract must be equivalent
Scheduled action types: Refresh Extracts and Extract must be equivalent
Mapping file's target_scheduled_action_type is Extract but the target schedule, Admin test reporting only - 3 AM, has a different scheduled_action_type: Refresh Extracts
Mapping file's target_scheduled_action_type is Extract but the target schedule, Weekdays - 4:30 AM Pacific, has a different scheduled_action_type: Refresh Extracts
Mapping file's target_scheduled_action_type is Extract but the target schedule, Weekdays - 5 AM Pacific, has a different scheduled_action_type: Refresh Extracts


Line 01 error is due to case-sensitivity!  That would've been nice to know.  I replaced "Minutes" to "minutes".

The unrecognized lines 03-07 (and probably 08-12, even 13-15) must be due to a documentation syntax error in the 8.3 manual.  It says the target_scheduled_action_type should be Extract or Subscription but that doesn't seem to work.  It does mention the following:

*In rare cases, there may be question marks (???) in this column. If there are, replace them with either Extract or Subscription, matching the entry you see under source_scheduled_action_type.

So I'm going to change it to Refresh Extracts to match what is in the column of my output.

We know line 02 is an error because of the ??? that I purposefully left.  I replaced the question marks with "Every Sunday 1:00 AM".

 

Okay, file saved and ran again.  Success!  Well, sort of.  The corrections to the schedule mapper were successful but I still have the user name mapping errors

Here's a snippet of the list of errors (same error, just a different source_name) that had 18 names missing:

source_name AMERRIL is missing from the mapping file
source_name AWHITES is missing from the mapping file
source_name achen69 is missing from the mapping file
...


Again, since this is QA I'm not worried about a few people "missing", however, it's complaining about people who exist on the source Server but they don't exist in the target Server.  I don't care!   I don't want to add them and figure out what Group(s) they belong to, besides, if they really need to be added they'll email me.  What I'm going to do now is import the Site since I know everything else is working and I'll do that using the --no-verify option in the tabadmin importsite command:

BTW, there's a syntax error in the documentation; there should be two dashes in the command line, not one as shown in the example:

 

Well shoot!  The import still failed:

 

It looks like I'll need to something about those users.  Well, this will give me something to do for tomorrow

The next step is to create a Site on the destination Server.  I simply went through the Admin panel on my PROD server and created "8.3 QA" with the ID of "tempqa":

             

It's availability is "Suspended" as I don't want anyone to get into it at this time.

 

The import was much quicker.  My command was:

tabadmin importsite tempqa --file D:\temp\qa.zip --tempdir D:\temp\temp_working

 

It finished within 10 minutes:

(Ignore the first attempt, I forgot to add the name of the zip file).

 

Now don't do what I did and EXIT the cmd window!  Luckily I took this screen shot and posted it above otherwise I would've lost the mappings directory -- doh!  Don't worry, even if you do close the cmd window too quickly the place to look is in the "mappings" folder:

 

Now I check the .csv files for three question marks (???).  My Servers don't have Microsoft products on them so I can't use Excel.  I could open the file from my laptop if I wanted.  I already have Notepad++ installed on the Servers so I'll just use that since the file sizes are small.

 

My "mappingScheduleMapper.csv" has some question marks:

source_name,source_scheduled_action_type,target_name,target_scheduled_action_type

Hourly Schedule,Refresh Extracts,???,???
Saturday night 11PM,Refresh Extracts,???,???
Admin reporting only - 3AM,Refresh Extracts,???,???
Weekdays 4AM,Refresh Extracts,???,???
WeekDays - 5 AM Pacific,Refresh Extracts,???,???


 

Fixing it is pretty easy.  First, these are all extracts so I fix that part:

source_name,source_scheduled_action_type,target_name,target_scheduled_action_type
Hourly Schedule,Refresh Extracts,???,Extract
Saturday night 11PM,Refresh Extracts,???,Extract
Admin reporting only - 3AM,Refresh Extracts,???,Extract
Weekdays 4AM,Refresh Extracts,???,Extract
WeekDays - 5 AM Pacific,Refresh Extracts,???,Extract


 

The next part I have to do is match the source_name of the import Site to one of the source_names on the target Site:

source_name,source_scheduled_action_type,target_name,target_scheduled_action_type
Hourly Schedule,Refresh Extracts,Every 60 Minutes,Extract
Saturday night 11PM,Refresh Extracts,???,Extract
Admin reporting only - 3AM,Refresh Extracts,Admin test reporting only - 3 AM,Extract
Weekdays 4AM,Refresh Extracts,Weekdays - 4:30 AM Pacific,Extract
WeekDays - 5 AM Pacific,Refresh Extracts,Weekdays - 5 AM Pacific,Extract


I don't have a "Saturday night 11PM" schedule so I'm going to leave that as-is and see what happens.

 

My "mappingsSystemUserNameMapper.csv" had 18 out of 2128 Users that had question marks so I simply deleted them.  They weren't licensed Desktop users so I wasn't concerned.

 

Okay, now I'm ready to perform the actual/final import!

We only have one non-production Server, QA.  It's been fine when doing updates since we've only been using version 8.  Now that version 9 is out, it is enough different that a TEST Server would be nice to have.  In the mean time, while waiting for this to happen, here's what I've decided to do...

 

I'm going to have a temporary Site on our PROD Server.  For all intents and purposes this acts like a separate server, it just happens to reside on the same box.  This allows me to keep that QA familiarity for my end users while I blow away the QA 8.3 version and upgrade to 9.0 for them to test upon.

 

The QA Server isn't very big in my opinion, which is good.  QA shouldn't be.  The first step is to export the specific Site using the tabadmin exportsite command.  However, the process took about 50 minutes for the .zip file to be created in the first step!  I'm using the 8.3 Import or Export a Site from the admin manual to help me through the process, along with the actual tabadmin command reference.

 

I opened a cmd window and executed the first command of this process:

tabadmin exportsite "" --file D:\Application\Tableau\backups\qa --tempdir D:\temp

So this means I'm exporting the default Site to the file named "qa" to the D:\Application\Tableau\backups folder.  The process will automatically add the ".zip" file extension.  All of the working files will be placed into the alternate location I chose, which is D:\temp.  This allows me to watch the progress.

 

When the tabadmin command runs the Site will automatically become locked.  Here's what my end users saw when this happened:

                

So if you do this make sure you send out an email when you're done to let them know it's back up

 

I kept my eye on the Windows Task Manager as well as the File Manager to monitor progress.  In the beginning there isn't much and for about 10-15 minutes I thought something failed because I saw no activity after the initial "export__..." folder and a few files were created:

              

                        (I added this example image the next day as I had to re-run the export, this is why the filename and date don't match this blog entry date).

 

After about 15-20 minutes things picked-up and I saw the eventual zip file grow.  When it was done the cmd window looked like this:

                  

 

My temp directory had some left-over files in it:

                 

 

The resultant zip file was 6.03GB in size.  Next step:  Import a Site.