Handling damaged files - Revision history

Arvind: /* Fixing damaged files that have no process for recreating them */

2018-03-15T13:56:03Z

Fixing damaged files that have no process for recreating them

← Older revision		Revision as of 13:56, 15 March 2018
Line 263:		Line 263:
	Before you proceed with fixing the file, first check for damaged files in the database by running CHK.FILES in maintenance mode as shown in [[Troubleshooting_NEOSYS_Generally#Checking_for_corrupt_database_files\|Checking for corrupt database files]]. Because there may be a scenario of a temporary damaged file which already has got fixed or there are other damaged files in the system.		Before you proceed with fixing the file, first check for damaged files in the database by running CHK.FILES in maintenance mode as shown in [[Troubleshooting_NEOSYS_Generally#Checking_for_corrupt_database_files\|Checking for corrupt database files]]. Because there may be a scenario of a temporary damaged file which already has got fixed or there are other damaged files in the system.

	If FIXFILE takes too long and leads to B703 error, and is not really necessary (e.g. REQUESTLOG), then use CLEARFILE instead.		If FIXFILE takes too long and leads to B703 error, and if the damaged file is not really necessary (e.g. REQUESTLOG), then use CLEARFILE instead.

	''SHADOW'' is a type of log file that can lose some records without serious impact and can therefore also be fixed with FIXFILE.		''SHADOW'' is a type of log file that can lose some records without serious impact and can therefore also be fixed with FIXFILE.

Gregory: /* Fixing damaged file that have a process to recreate them */

2018-03-15T12:57:31Z

Fixing damaged file that have a process to recreate them

← Older revision		Revision as of 12:57, 15 March 2018
Line 149:		Line 149:

	If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.		If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.

	~~For damaged files that don't have a process to recreate them, use CLEARFILE in cases where file is not required e.g. "REQUESTLOG".~~

	The following is an example of the error in the ADS File at the time of backup.		The following is an example of the error in the ADS File at the time of backup.

Gregory: /* Fixing damaged files that have no process for recreating them */

2018-03-15T12:55:55Z

Fixing damaged files that have no process for recreating them

← Older revision		Revision as of 12:55, 15 March 2018
Line 264:		Line 264:

	Before you proceed with fixing the file, first check for damaged files in the database by running CHK.FILES in maintenance mode as shown in [[Troubleshooting_NEOSYS_Generally#Checking_for_corrupt_database_files\|Checking for corrupt database files]]. Because there may be a scenario of a temporary damaged file which already has got fixed or there are other damaged files in the system.		Before you proceed with fixing the file, first check for damaged files in the database by running CHK.FILES in maintenance mode as shown in [[Troubleshooting_NEOSYS_Generally#Checking_for_corrupt_database_files\|Checking for corrupt database files]]. Because there may be a scenario of a temporary damaged file which already has got fixed or there are other damaged files in the system.

			If FIXFILE takes too long and leads to B703 error, and is not really necessary (e.g. REQUESTLOG), then use CLEARFILE instead.

	''SHADOW'' is a type of log file that can lose some records without serious impact and can therefore also be fixed with FIXFILE.		''SHADOW'' is a type of log file that can lose some records without serious impact and can therefore also be fixed with FIXFILE.

Gregory: /* Fixing damaged file that have a process to recreate them */

2018-03-15T12:54:35Z

Fixing damaged file that have a process to recreate them

← Older revision		Revision as of 12:54, 15 March 2018
Line 151:		Line 151:

	For damaged files that don't have a process to recreate them, use CLEARFILE in cases where file is not required e.g. "REQUESTLOG".		For damaged files that don't have a process to recreate them, use CLEARFILE in cases where file is not required e.g. "REQUESTLOG".

	~~If FIXFILE takes too long and leads to B703 error, and is not really necessary (e.g. REQUESTLOG), then use CLEARFILE instead.~~

	The following is an example of the error in the ADS File at the time of backup.		The following is an example of the error in the ADS File at the time of backup.

Gregory: /* Fixing damaged file that have a process to recreate them */

2018-03-15T12:36:35Z

Fixing damaged file that have a process to recreate them

← Older revision		Revision as of 12:36, 15 March 2018
Line 149:		Line 149:

	If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.		If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.

			For damaged files that don't have a process to recreate them, use CLEARFILE in cases where file is not required e.g. "REQUESTLOG".

			If FIXFILE takes too long and leads to B703 error, and is not really necessary (e.g. REQUESTLOG), then use CLEARFILE instead.

	The following is an example of the error in the ADS File at the time of backup.		The following is an example of the error in the ADS File at the time of backup.

Gregory: Undo revision 3171 by Gregory (talk)

2018-03-15T12:26:38Z

Undo revision 3171 by Gregory (talk)

← Older revision		Revision as of 12:26, 15 March 2018
Line 148:		Line 148:
	BRANDS files can be recreated with F5 CREATEBRANDS		BRANDS files can be recreated with F5 CREATEBRANDS

	If the file is actually damaged it might be necessary to initialise it first ~~ARVIND: UNDER WHAT CIRCUMSTANCES?? ~~ using CLEARFILE filename.		If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.

	~~If file is not important (check with superior) use CLEARFILE to delete it~~.

	The following is an example of the error in the ADS File at the time of backup.		The following is an example of the error in the ADS File at the time of backup.

Gregory: Undo revision 3172 by Gregory (talk)

2018-03-15T12:26:18Z

Undo revision 3172 by Gregory (talk)

← Older revision		Revision as of 12:26, 15 March 2018
Line 137:		Line 137:

	Identify the cause of the damaged file and create a report.		Identify the cause of the damaged file and create a report.

	~~If the file is actually damaged it might be necessary to initialise it first ARVIND: UNDER WHAT CIRCUMSTANCES?? using CLEARFILE filename.~~

	~~If file is not important (check with superior) use CLEARFILE to delete it.~~

	Below files can be recreated from the maintenance mode.		Below files can be recreated from the maintenance mode.
Line 152:		Line 148:
	BRANDS files can be recreated with F5 CREATEBRANDS		BRANDS files can be recreated with F5 CREATEBRANDS

			If the file is actually damaged it might be necessary to initialise it first ARVIND: UNDER WHAT CIRCUMSTANCES?? using CLEARFILE filename.

			If file is not important (check with superior) use CLEARFILE to delete it.

	The following is an example of the error in the ADS File at the time of backup.		The following is an example of the error in the ADS File at the time of backup.

Gregory: /* Fixing damaged file that have a process to recreate them */

2018-03-15T12:20:15Z

Fixing damaged file that have a process to recreate them

← Older revision		Revision as of 12:20, 15 March 2018
Line 137:		Line 137:

	Identify the cause of the damaged file and create a report.		Identify the cause of the damaged file and create a report.

			If the file is actually damaged it might be necessary to initialise it first ARVIND: UNDER WHAT CIRCUMSTANCES?? using CLEARFILE filename.

			If file is not important (check with superior) use CLEARFILE to delete it.

	Below files can be recreated from the maintenance mode.		Below files can be recreated from the maintenance mode.
Line 148:		Line 152:
	BRANDS files can be recreated with F5 CREATEBRANDS		BRANDS files can be recreated with F5 CREATEBRANDS

	~~If the file is actually damaged it might be necessary to initialise it first ARVIND: UNDER WHAT CIRCUMSTANCES?? using CLEARFILE filename.~~

	~~If file is not important (check with superior) use CLEARFILE to delete it.~~

	The following is an example of the error in the ADS File at the time of backup.		The following is an example of the error in the ADS File at the time of backup.

Gregory: /* Fixing damaged file that have a process to recreate them */

2018-03-15T12:17:56Z

Fixing damaged file that have a process to recreate them

← Older revision		Revision as of 12:17, 15 March 2018
Line 148:		Line 148:
	BRANDS files can be recreated with F5 CREATEBRANDS		BRANDS files can be recreated with F5 CREATEBRANDS

	If the file is actually damaged it might be necessary to initialise it first using CLEARFILE filename.		If the file is actually damaged it might be necessary to initialise it first ARVIND: UNDER WHAT CIRCUMSTANCES?? using CLEARFILE filename.

			If file is not important (check with superior) use CLEARFILE to delete it.

	The following is an example of the error in the ADS File at the time of backup.		The following is an example of the error in the ADS File at the time of backup.

Arvind: /* Cause */

2018-01-11T11:47:19Z

Cause

← Older revision		Revision as of 11:47, 11 January 2018
Line 8:		Line 8:

	== Cause ==		== Cause ==
	Rare but nasty problem on server 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.		Rare but nasty problem on server, 99% caused by power failure, killing NEOSYS or server hardware or operating system failure.

	*Did somebody kill NEOSYS processes to reboot the server or any other reason?		*Did somebody kill NEOSYS processes to reboot the server or any other reason?