ARS0106E - Revision history

Jderrick: Fixed broken link to Content Manager OnDemand Cache Filesystems

2020-09-25T15:20:14Z

Fixed broken link to Content Manager OnDemand Cache Filesystems

← Older revision		Revision as of 15:20, 25 September 2020
Line 27:		Line 27:
	* While running [[arsload]] - the file already exists in the cache, and IBM CMOD couldn't delete it before overwriting it.		* While running [[arsload]] - the file already exists in the cache, and IBM CMOD couldn't delete it before overwriting it.

	The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache ~~Filesystem~~]].		The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[IBM CMOD Cache Filesystems]].

	The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.		The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.

Jderrick: Tweaked the content Manager OnDemand troubleshooting section for ARS0106E.

2017-02-13T13:24:16Z

Tweaked the content Manager OnDemand troubleshooting section for ARS0106E.

← Older revision		Revision as of 13:24, 13 February 2017
Line 22:		Line 22:
	There are four scenarios when this error can occur:		There are four scenarios when this error can occur:

	* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload.		* While running [[arsadmin]] unload - IBM CMOD was unable to delete a file during the unload.
	* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache.		* While running [[arsload]] - during a failed load, IBM CMOD was unable to delete the objects it inserted into the cache.
	* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration.		* While running [[arsmaint]] - during regular expiration processing, IBM CMOD couldn't delete an object eligible for expiration.
	* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it.		* While running [[arsload]] - the file already exists in the cache, and IBM CMOD couldn't delete it before overwriting it.

	The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]].		The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]].

	The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.		The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.

Jderrick: /* What was the error? */

2015-05-10T01:55:49Z

What was the error?

← Older revision		Revision as of 01:55, 10 May 2015
Line 7:		Line 7:
	Message Name: ARS0106E		Message Name: ARS0106E

	Message Text: Unlink failed for file >filename< errno=<ErrorNumber> Srvr->ServerName<-		Message Text:
			Unlink failed for file >filename< errno=<ErrorNumber> Srvr->ServerName<-

	== What were you doing? ==		== What were you doing? ==

Jderrick: Updated error severity text

2015-05-10T01:55:27Z

Updated error severity text

← Older revision		Revision as of 01:55, 10 May 2015
Line 3:		Line 3:
	Message Number: 106		Message Number: 106

	Message Severity: Error		Message Severity: Error (Corrective action is required to continue)

	Message Name: ARS0106E		Message Name: ARS0106E

Jderrick: Standardized the layout.

2015-04-29T00:25:25Z

Standardized the layout.

← Older revision		Revision as of 00:25, 29 April 2015
Line 1:		Line 1:
			{{TOCright}}
			== What was the error? ==
			Message Number: 106

	Message ~~Text~~: ~~'''Unlink failed for file >filename< errno=<ErrorNumber> Srvr->ServerName<-'''~~		Message Severity: Error

	~~The server couldn~~'t ~~delete a~~ file in the ~~cache filesystem~~.		Message Name: ARS0106E

			Message Text: Unlink failed for file >filename< errno=<ErrorNumber> Srvr->ServerName<-

			== What were you doing? ==

			Probably loading data, or performing an unload of report data that may or may not have completed successfully.

			== What happened? ==

			When CMOD tried to delete a file, the operating system returned an error. Either the user who ran the command didn't have permission, or the file was missing. If the file was missing, this is more of a warning, and less of an error requiring corrective action.

			== Troubleshooting ==

	There are four scenarios when this error can occur:		There are four scenarios when this error can occur:

Jderrick: Doh.

2015-03-24T10:50:45Z

Doh.

← Older revision		Revision as of 10:50, 24 March 2015
Line 6:		Line 6:
	There are four scenarios when this error can occur:		There are four scenarios when this error can occur:

	* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload.		* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload.
	* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache.		* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache.
	* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration.		* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration.
	* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it.		* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it.

	The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]].		The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]].

	The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.		The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.

Jderrick: Formatting

2015-03-24T10:49:37Z

Formatting

← Older revision		Revision as of 10:49, 24 March 2015
Line 6:		Line 6:
	There are four scenarios when this error can occur:		There are four scenarios when this error can occur:

	* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload.		* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload.
	* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache.		* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache.
	* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration.		* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration.
	* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it.		* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it.

	The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]].		The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]].

	The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.		The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time prior to when the cache filesystem was backed up.

Jderrick: Initial edit.

2015-03-24T10:48:35Z

Initial edit.

New page

Message Text: '''Unlink failed for file >filename< errno=<ErrorNumber> Srvr->ServerName<-'''

The server couldn't delete a file in the cache filesystem.

There are four scenarios when this error can occur:

* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload.
* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache.
* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration.
* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it.

The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]].

The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time *prior* to when the cache filesystem was backed up.