Vision Support - Revision history

Anw: Added "Disk Full" support guidelines.

2020-01-17T12:39:06Z

Added "Disk Full" support guidelines.

← Older revision		Revision as of 14:39, 17 January 2020
Line 119:		Line 119:

	Inform the client that the Minimum and Target levels for these Extended Extract Types can now be entered through the system.		Inform the client that the Minimum and Target levels for these Extended Extract Types can now be entered through the system.


			== Disk Full ==
			Typically issues on the machine have caused a crash of the Vision datamine processes.

			These are now cyclically logging errors to the ERROR_LOG table in the MySQL database, which will be taking up the disk space.


			'''Checks:'''
			* Check the error log datafile (error_log.ldb) in the MySQL database area, typically C:\ or E:\, Program Data\MySQL\Database\Productivity1\
			* If this is large, then it should be truncated.


			'''Solution:'''
			* Start MySQL Administrator.
			* Click the box for the database
			* Log on to the database (enter password)
			* Start a new query:
			** TRUNCATE Productivity1.ERROR_LOG;
			* Check that the table's datafile is now small.

			Given that the disk is full, you may not be able to access the database to take this action.

			So several or all of the following steps may be required, and are typically recommended:
			* Stop and disable vision scheduler items.
			* Kill wscript processes using task manager.
			* Stop MySQL service (may take a while).
			* You may need to kill the MySQL service (with Task Manager)
			* Clear as much space as you can.
			* Start MySQL service (may take a while).
			* Truncate the error log as described above.

			The disk space is cleared, so any other processes on the machine can now be started.

			It is recommended that Vision datamining and cleardown remain disabled for a time, as the MySQL service will be busy catching up.

			* Monitor the MySQL process - wait until this is no longer taking up masses of CPU time.
			* At this point, stop and start the MySQL service again, to recover system memory and clear MySQL-specific logs.
			* Re-enable the Vision scheduled processes.
			* Start the Vision Datamine (NOT THE CLEARDOWN)
			* Monitor this until finished - typically this will take a while.


	[[Category:Vision Overview]]		[[Category:Vision Overview]]

Anw: Added section on updating Extended Extract Parameters

2012-11-16T10:42:59Z

Added section on updating Extended Extract Parameters

@@ Line 72: / Line 72: @@
 ** Extract = "Exceptions", Field "ID"
 * Apply all changes.
 [[Category:Vision Overview]]

Anw: Added section on moving WCS machine

2012-10-15T15:39:49Z

Added section on moving WCS machine

← Older revision		Revision as of 17:39, 15 October 2012
Line 54:		Line 54:
	With either resolution, the next time Vision datamining runs, it will update correctly.		With either resolution, the next time Vision datamining runs, it will update correctly.

			==Vision is not updating WCS data (WCS has been moved) ==
			'''Problem'''

			The cause of Vision not updating is is that WCS Logging database doesn't exist where it did before (i.e. the old machine).

			'''Root Cause Resolution'''
			* Enquire on table System_Extracts, to find the WCS Data Mine that is affected. This will be records with:
			** Enabled = "Y"
			** Type = "WCS"
			** DB1_Folder, DB2_Folder and ArchiveDB_Folder will be the machine name or IP address, which needs to be changed to the new address.

			When moved, the Log database may have been recreated as well (check with the WCS team to confirm). To correct:
			* Edit all records on table System_Extract_Points. Blank (i.e. not Null, Change to value Space, then Delete) the Value field on the records with the following values:
			** Extract = "ra_wcs_new", Field "ID"
			** Extract = "RDT Activity", Field "End"
			** Extract = "RDT Activity", Field "Start"
			** Extract = "Exceptions", Field "ID"
			* Apply all changes.

	[[Category:Vision Overview]]		[[Category:Vision Overview]]

Anw: Added Log Database Renamed support resolution entry

2012-06-25T11:39:08Z

Added Log Database Renamed support resolution entry

@@ Line 2: / Line 2: @@
 __FORCETOC__
 ==Vision is not updating==
 The likely issue is that the Vision Data Mining process has stopped for some reason.
 * Log on to the machine and check that the Vision Data Mining processes are still scheduled, using the Windows Scheduler. If not, add or re-start them.
 * If they are running, check the logs, found in {Vision}\Scripts\DataMining_*.log or through the Event Log Vision screen. This may point to errors or suggestions that the processes are scheduled by failing when run.
 * If the processes are failing, pause all the scheduled jobs and kill any processes on the machine called Wscript.exe using the Windows Task Manager. When complete, start the Data Mining tasks again and force run them.
 [[Category:Vision Overview]]

Anw: Added TOC

2011-03-22T08:56:02Z

Added TOC

← Older revision		Revision as of 10:56, 22 March 2011
Line 1:		Line 1:
	This section contains details of any common support issues and how they would be checked and resolved. This section will be added to over time.		This section contains details of any common support issues and how they would be checked and resolved. This section will be added to over time.
			__FORCETOC__
	==Vision is not updating==		==Vision is not updating==
	The likely issue is that the Vision Data Mining process has stopped for some reason.		The likely issue is that the Vision Data Mining process has stopped for some reason.

Anw: Added Vision Support section

2011-03-22T08:52:07Z

Added Vision Support section

New page

This section contains details of any common support issues and how they would be checked and resolved. This section will be added to over time.

==Vision is not updating==
The likely issue is that the Vision Data Mining process has stopped for some reason.
* Log on to the machine and check that the Vision Data Mining processes are still scheduled, using the Windows Scheduler. If not, add or re-start them.
* If they are running, check the logs, found in {Vision}\Scripts\DataMining_*.log or through the Event Log Vision screen. This may point to errors or suggestions that the processes are scheduled by failing when run.
* If the processes are failing, pause all the scheduled jobs and kill any processes on the machine called Wscript.exe using the Windows Task Manager. When complete, start the Data Mining tasks again and force run them.

[[Category:Vision Overview]]