Empty file script_out*.log after CU7 Manager patch installation

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

After installation of CU7 patch on Domain Manager (or Enterprise Manager), a log file like this is generated : script_out_<date>_<time>.log

This file is empty. Is it normal ?

 

Environment

Client Automation 14.5 CU7

Resolution

During CU7 installation the script runSQLscript.bat is executed.

This script executes a sqlcmd command to execute SQL Script Patch_sqlscripts.sql

 

In log ExecSQLScript.log we should see lines like :

 

command to run: sqlcmd -b -S <sqlserver> -U ca_itrm -P <ca_itrm_password> -d mdb -i Patch_sqlscripts.sql -o C:\TEMP\CU7\script_out_20240731_115840.log

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ITCM MDB updated successfully. Check C:\TEMP\CU7\script_out_20240731_115840.log for more details

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Patch_sqlscripts.sql applied successfully

 

Standard output of script_out_<date>_<time>.log contains these 5 lines :

Changed database context to 'mdb'.
Changed database context to 'mdb'.
Changed database context to 'mdb'.
Changed database context to 'mdb'.
Changed database context to 'mdb'.

 

But in some SQL Server configuration, "changed database context to" are not displayed. So it could be normal that file script_out_<date>_<time>.log is empty

 

To check if SQL Script Patch_sqlscripts.sql has been executed successfully, execute following SQL Query :

 

select * from statjobm

 

and check if column auto_rep_version is present

 

 

If it is present then it means that script Patch_sqlscripts.sql has been executed