Introduction. Application Versions. Assumptions. Delete $$ExportTempFolders. Tech Note 930 Wonderware System Platform Clean-up Guide



Similar documents
Tech Note 743 Configuring Reporting Services 2008 Configuration for a New Host Name in Windows 2008 R2

Tech Note 847 Installing Wonderware Information Server (WIS) on the Windows Server Window 7 64 and 32-bit Operating System

Tech Note 868 Troubleshooting Wonderware Software Resource Issues with Performance Monitor

Introduction. Application Versions. Installing Virtual SMTP Server. Tech Note 692 Using Virtual SMTP Server for SCADAlarm Notifications

Introduction. Notes. Important Considerations. Application Versions. Assumptions. 8/22/13 Setting Up Historian Servers for Tier-2 Summary Replication

Tech Note 782 Installing Remote Desktop Services on Windows 2008 Server R2 for Wonderware Products

Tech Note 920 Resolving Disabled ActiveFactory Reporting Website for Wonderware System Platform R2

Migrating QI 8.0 Admin and Process Databases from Microsoft Access to Microsoft SQL Server

Introduction. Symbol Script Timeout Setting. Sample MES Custom Code in Symbol Script. Application Versions. Sample Code

Tech Note 782 Installing Remote Desktop Services on Windows 2008 Server R2 for Wonderware Products

How To Migrate Qi Analyst To A New Database On A Microsoft Access (Windows) From A New Version Of Qi.Io To A Newer Version Of A New Qi 8.0 (Windows 7.3

Tech Note 338 How to Change the ActiveFactory Reporting Website Default Install Location

Introduction. Tech Note 884 Setting Up Historian Servers for Tier-2 Summary Replication

Tech Note 882 Configuring Time Synchronization for Historian Server Using Net Time and Windows Task Scheduler

Tech Note 663 HMI Reports: Creating Alarm Database (WWALMDB) Reports

This tech note will explain how to use the following parameters in Configurator General Parameters.

Introduction. Back Up the Runtime Database. Application Versions

Tech Note 1042 Solving Historian Memory Issue with SQL Server MemToLeave Configuration

Tech Note 1010 SQL Server Authentication and ArchestrA Network Account Restrictions When Installing Wonderware Historian

Instead, use the following steps to update system metadata that is stored in sys.servers and reported by the system function

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

1. Under Application Objects, open the $Tank object and then open the $TankDisplay as shown in Figure 1 (below).

Tech Note 1035 Moving the Historian Runtime Database to Another Machine Using SQL Server 2012

Tech Note 882 Configuring Time Synchronization for Historian Server Using Net Time and Windows Task Scheduler

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

This Tech Note provides detailed guidelines and options for defragmenting and maintaining your production databases.

Note: This Tech Note was formerly titled Installing Microsoft SQL Server 2008 for Wonderware Historian v10.0.

This Tech Note provides step-by-step procedures to install Microsoft SQL Server 2012 on a 32- or 64-bit Operating System.

Tech Note 813 Troubleshooting Wonderware Information Server (WIS) Part Four: Client License Release

8/22/13 Configuring Windows SharePoint Services for PEM v1.0 to Work with SuiteVoyager v2.6

Introduction. Issues. Symptoms. Application Versions. Case 1: Deploy an ArchestrA Object - UDO4DevUsers_001_001 - Has Error Messages

How To Write A Summary On A Historyorian Server

Tech Note 751 Installing InBatch Report Contents for Wonderware Information Server (WIS)

Using Network Application Development (NAD) with InTouch

This Tech Note describes working with Microsoft Reporting Services in order to publish InBatch Reports to Wonderware Information Server.

Tech Note 400 Configuring Remote Connections for Windows 2000/2003/XP

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Enabling Cross-Machine Distributed Transactions (via MSDTC)

Tech Note 551 Configuring SQLMail or Database Mail for the Historian Event

Part I: Setting up Bristol Babcock's OPC Server

Industrial Application Server Redundancy: Troubleshooting Guidelines

Note: Not all messages in the log are indicative of a problem. Contact Technical Support if questions arise.

Introduction. Application Versions. Compatibility and System Requirements. Firewall and DCOM Settings

Tech Note 905 Troubleshooting Wonderware Information Server (WIS) Part Six: ArchestrA Graphics No Live-Data

Communication to End Device Going In and Out of Slow Poll Mode

Tech Note 612 Upgrading DLL Version Mismatches Between CBM Solution and System Platform

Introduction. Configuration: Entity and OCO Modeling. Application Version: OCO General Configuration

Tech Note 652 Changing an ArchestrA Symbol's Custom Property Expression or Reference in Runtime

Tech Note 957 Creating Custom Password Entry on Intermec-Supported Handhelds

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

SWP-0054 Creating a SQL Maintenance Plan. Revision: 1. Effective Date: 4/26/2011

To allow SQL Server Agent to trigger when a report is executed, we need to provide a set of report group types.

Database Maintenance ZENworks Mobile Management 2.7.x August 2013

Using SQL Server 2008 Automated Backup

Moving the Web Security Log Database

4cast Server Specification and Installation

Moving the TRITON Reporting Databases

HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE

Tech Note 912 Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Introduction. There are several bits of information that must be moved:

ArchestrA Log Viewer User s Guide Invensys Systems, Inc.

Lab 05: Deploying Microsoft Office Web Apps Server

Migrating Trend Micro Mobile Security for Enterprise (TMMS) 8.0 to TMMS 9.0

8/22/13 Configuring the SST5136SD PCI Card Using the New SSTDHP IO Server V8.1 or the DASDHPlus Server

8/23/13 Configuring the Wonderware SECS-II/GEM Host Creator (SERIAL-RS232)

Creating IBM Cognos Controller Databases using Microsoft SQL Server

Security Settings for Wonderware Products

InformationNOW SQL 2005 Database Backup and Restoration

Juris Installation / Upgrade Guide

Migrating Mobile Security for Enterprise (TMMS) 8.0 to version 9.0

InformationNOW SQL 2008 Database Backup and Restoration

Configuring a Custom Load Evaluator Use the XenApp1 virtual machine, logged on as the XenApp\administrator user for this task.

STIDistrict SQL 2000 Database Management Plans

How to schedule SQL Maintenance Plan

This Tech Note describes modem connections using DAServers and provides some guidelines on how to make the modem connection work.

SAM Server Utility User s Guide

Tech Note 128 Configuring InBatch For Standalone PCs With SQL Server and IndustrialSQL Server

8/23/13 Configuring SIDirect DAServer to Communicate with S7 PLC Over TCP Connection

Automated backup. of the LumaSoft Gas database

1. Open the License Manager either via the Start Menu or from C:\Keri\DoorsNET directory.

Tech Note 213 Finding Memory Leaks in Windows 95/98/98SE Using System Monitor

Installing LearningBay Enterprise Part 2

SafeGuard Enterprise upgrade guide. Product version: 7

When you publish data to a SharePoint site, you first

Studio 5.0 User s Guide

SafeGuard Enterprise upgrade guide. Product version: 6.1

Backups and Repository Maintenance

Uni Sales Analysis CRM Extension for Sage Accpac ERP 5.5

BizTalk Server Business Activity Monitoring. Microsoft Corporation Published: April Abstract

Restoring Sage Data Sage 200

Tech Note 53 Configuring the Siemens SINEC H1 CP1413 for Windows NT

Install SQL Server 2014 Express Edition

Silect Software s MP Author

Database Operations (Backup/Restore/Move/Manage) Technical Support Engineering Rosslare Security NA For more information please see

Metalogix SharePoint Backup. Advanced Installation Guide. Publication Date: August 24, 2015

DigiVault Online Backup Manager. Microsoft SQL Server Backup/Restore Guide

Step-by-Step Guide for Microsoft Advanced Group Policy Management 4.0

Desktop Deployment Guide ARGUS Enterprise /29/2015 ARGUS Software An Altus Group Company

Transcription:

Tech Note 930 Wonderware System Platform Clean-up Guide All Tech Notes, Tech Alerts and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information. Topic#: 002746 Created: February 2013 Introduction When working with a Galaxy, some of the Galaxy-related files can become quite large, impacting system performance. Investigation and continued testing has confirmed that "cleaning up" certain file sets provides the following benefits: Improves time to open templates and objects. Improves time to check-in objects and templates. Deploying the InTouch app is faster. Restoring a Galaxy is faster. Backup was faster and smaller. You can delete the files listed in the following sections. Doing so can shrink the Galaxy size dramatically. Although some of the directories can safely be deleted even while the Galaxy is deployed, it is strongly recommended that any deletions should be done when all the display nodes of a Galaxy have been un-deployed, (i.e. during an upgrade). When all the display nodes of a Galaxy are undeployed, none of these directories should exist, so they can all be deleted. Important: Always make backups before you delete anything! Application Versions Wonderware Application Server 3.1 and later Assumptions This Tech Note assumes you are familiar with the following: Galaxy operations such as Deploy, Un-deploy, Object Export, Backup/Restore, etc. SQL Server Database management operations. Delete $$ExportTempFolders

The $$$ExportTempFolders are created when you do an Object Export from the Galaxy. These files are normally automatically deleted on completion. If the export fails or something goes wrong during the export, these directories are not deleted and remain there. All the $$ExportTempFolders directories can be deleted. FiGuRe 1: $$$EXPORtTeMPFOLDeRS Delete BAK Directories The BAK directories are created when you make a backup of an InTouch Application when opening the application from within the IDE using WindowMaker. The default directory is in the application directory itself, so it permanently doubles the size of the application. When a backup is required, specify an alternate directory and do not use the default. You can delete all the BAK directories.

FiGuRe 2: BAK DiReCtORY CONteNtS Delete Deployed Directories Important! These files should only be deleted after all the display nodes of the Galaxy are un-deployed. The Deployed directories are sometimes created when you deploys an InTouch application, but are not always deleted again when the application is un-deployed. These files can build up over time. Un-deploy all the display nodes, and then delete all the directories left over. Afterwards deploy all the InTouch Applications again.

FiGuRe 3: DePLOYeD DiReCtORieS Delete InTouch Application Directories Important! These should only be deleted when all the display nodes of the Galaxy have been un-deployed. For each deployed InTouch Application, a copy is created in this directory. Various scenarios can result in these directories building up over time (Backing up and restoring the Galaxy, running Platform remove on a node that hasn't been un-deployed, etc). Un-deploy all the display nodes, and then delete all the directories that are left over. Afterwards deploy all the InTouch Applications again.

FiGuRe 4: INTOuCH APPLiCatiON DiReCtORY COPieS Clear GOBJECT_CHANGE_LOG Table The size of the table in the MSSQL Galaxy Database called dbo.gobject_change_log can become very large over time when there is a large amount of development. This table can be cleaned up by executing the following script on the database: USE {Galaxy_Name eg KH_G} DELETE FROM gobject_change_log WHERE change_date <= DATEADD(dd,-15,GetDate()) This query deletes all the entries in the change log more than 15 days old.

FiGuRe 5: CLeaR the CHaNGe LOG Shrink Transaction Log Files You can shrink the Database Log Files. In SQL Server Management Studio, select the Database which corresponds to the Galaxy Name (e.g. KH_G). 1. Right-click on the Database, then click Tasks. 2. Click Shrink, then Files (Figure 6 below).

FiGuRe 6: SHRiNk DatabaSe LOG FiLeS 3. In the File type dropdown list, select Log, leave all other defaults and click OK:

FiGuRe 7: SHRiNk LOG FiLe TYPe In this example, the original allocated space was 1310.25 MB. After shrinking, it is reduced to 0.49 MB:

FiGuRe 8: SHRiNk FiLe ALLOCateD SPaCe Run Galaxy Database Scrubber on Database The Wonderware Galaxy Database Scrubber utility should only be run on Galaxies that have been completely un-deployed and backed up. This scrubber utility will delete all Unused Packages in the database and clean the Transaction Log files. 1. Double-click GalaxyDatabaseScrubber.exe to start the scrubber. Please take note of the warning pop-up:

FiGuRe 9: GaLaXY SCRubbeR WaRNiNG MeSSaGe at StaRtuP 2. Select the Galaxy that needs to be scrubbed and click Connect. 3. Click the Scrub Database button and wait until it is finished. Wonderware South Africa Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., 26561 Rancho Parkway South, Lake Forest, CA 92630. There is also technical information on our software products at Wonderware Technical Support. For technical support questions, send an e-mail to wwsupport@invensys.com. Back to top 2013 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, broadcasting, or by anyinformation storage and retrieval system, without permission in writing from Invensys Systems, Inc. Terms of Use.