Error Table 'tablename' does not exist when running upd_stat.sql on sql server

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

When running a job to cleanup statistics we receive the following error when running upd_stat.sql on sql server

"Table 'LASLM' does not exist."

This can happen on other tables as well

Environment

Release : 12.3.8

Resolution

The file being called, upd_stat.sql, is running a lot of update statistics statements.  It gets to the following (could be a different table besides LSALM):

update statistics LASLM
GO

and then decides there isn't an LASLM table and that's why it throws the error it does.  There should be an LASLM table in the Automic database.  To troubleshoot this, A DBA should be involved.  My suggestion would be go down these steps:

1. Put in a print statement into the job you sent so that it prints out &uc4_db_server, &uc4_db_db, &uc_db_user, &uc4_install_dir, &uc4_install_dir, &sql_install_dir
2. Run the job and get the values for above (the &uc4_db_pass optionally, but hopefully they have this on hand elsewhere as I know it's tricky to ask someone to plain text print a password)
3. Create a file on the same server called runme.sql or something like that
4. Put these lines into the file:
   
   update statistics AH
   GO
   update statistics LASLM
   GO
   update statistics MELD
   GO
   
   
5. Run the commands from the command line, replacing the &variables with the values from #1 above:
   
   PATH=c:\WINNT\system32;c:\WINNT\system32\dll;c:\WINDOWS\system32;c:\WINDOWS\system32\dll;&UC4_INSTALL_DIR\bin;&SQL_INSTALL_DIR\Client SDK\ODBC\130\Tools\Binn
   sqlcmd -S&UC4_DB_SERVER -d&UC4_DB_DB -U&UC4_DB_USER -P&UC4_DB_PASS -r1 -b -i "[folder where you created runme.txt]\runme.sql"
   
   
6. Check the results - we should still see an error here, but if we don't let me know - that means there's a problem specifically with running it either from upd_stat.sql or from a job
7. Assuming that we do see the error, log into SSMS as the user from the command above
8. Have that user look at the tables for the database in SQL Server.  See if LASLM is there.  
9. Have that user run the following:
   
   update statistics AH
   GO
   update statistics LASLM
   GO
   update statistics MELD
   GO
   
   
10. If it fails, a DBA needs to check from an admin account that the LASLM table does exist (it should) and they'll need to check why the user from above can't access that table or run this update statistics command.
11. If this error is holding up all other tables from having their statistics run, another option is to remove the lines from upd_stat.sql:
    
    update statistics LASLM
    GO

The problem is that the user being used is unable to see or run this update statistics command against the LASLM table and a DBA will be the best to say why that is.