ARS0111E - Revision history

Jderrick: /* Troubleshooting */

2024-03-07T00:19:51Z

Troubleshooting

← Older revision		Revision as of 00:19, 7 March 2024
Line 23:		Line 23:
	== Troubleshooting ==		== Troubleshooting ==
	The troubleshooting is already done. The link needs to be created. You can create a new link using information from the error message, which should allow the file to be retrieved.		The troubleshooting is already done. The link needs to be created. You can create a new link using information from the error message, which should allow the file to be retrieved.

			In terms of error numbers, there are a few common ones, which will give you a better idea of where the problem is:
			; 2
			: No such file or directory - the link points to a file that doesn't exist, or the link to the file doesn't exist.

			; 13
			: Permission denied - check your the permissions on the files/links and their parent directories to ensure you can access the files.

			; 22
			: Invalid Argument - something is broken with the link -- check to ensure that the link doesn't contain special characters or double slashes (//). Consider deleting the link and making a new one.


	In the example above, the link could be re-created with the following command:		In the example above, the link could be re-created with the following command:
Line 45:		Line 56:

	;DOC		;DOC
	: This directory name indicates that documents are stored inside. A directory called RES is used to store resources.		: This directory name indicates that documents are stored inside. A directory called RES is also valid, it is used to store resources.

	;123FAAA		;123FAAA

Jderrick: Fixed the link command. Added more detail to describe the file paths.

2024-03-05T19:17:42Z

Fixed the link command. Added more detail to describe the file paths.

← Older revision		Revision as of 19:17, 5 March 2024
Line 25:		Line 25:

	In the example above, the link could be re-created with the following command:		In the example above, the link could be re-created with the following command:
	ln -s /arscache/~~cache1~~/~~retr~~/ABC/DOC/123FAAA /arscache/~~cache2~~/~~12345~~/ABC/DOC/123FAAA		ln -s /arscache/cache2/12345/ABC/DOC/123FAAA /arscache/cache1/retr/ABC/DOC/123FAAA

	~~If the creation of~~ the link ~~is successful, IBM Content Manager OnDemand should be able~~ to ~~retrieve the documents from the CMOD cache~~.		Inside this command, these are the components:
			;ln -s
			: The UNIX / Linux command to create a symbolic ('soft') link from a file to a new location.

			;/arscache/cache2/12345/ABC/DOC/123FAAA
			: The location of the object in the cache filesystem that doesn't have an associated link. (Which we're building.)

			;/arscache/cache2
			: Presumably, the second cache filesystem.

			;12345
			: This is a CMOD internal date (number of days since January 1st, 1970 (also known as the UNIX epoch).
			: Historically, this date was the date that the documents stored in this subdirectory would expire. In modern versions of IBM Content Manager OnDemand, this numbered directory has practically no meaning, as CMOD Document Objects are expired based on their cache retention period, and the capacity of the cache filesystem.

			;ABC
			: This is the 'Application Group ID Name' - a three letter code representing a specific Application Group. You can find this information inside the CMOD database table called arsag.

			;DOC
			: This directory name indicates that documents are stored inside. A directory called RES is used to store resources.

			;123FAAA
			: This is the CMOD Object Name -- at load time, individual documents are de-duplicated, compressed, then grouped into files called CMOD Objects.

			;/arscache/cache1/retr/ABC/DOC/123FAAA
			: This is the path where the link is to be created.
			: Note that links are ALWAYS located in the first CMOD cache filesystem.
			: While you can add and remove cache filesystems from ars.cache, you cannot move the FIRST cache filesystem.
			: The 'retr' subdirectory is used as a 'map', to tell CMOD where it can find location of the the documents that users are requesting, across ALL of the cache filesystems.
			: The structure is similar to the source, except it excludes the numbered 'expiration date' subdirectory.


			If the creation of the link is successful, IBM Content Manager OnDemand should be able to retrieve the documents from the CMOD cache. Instead of trying to find the individual document in CMOD, run the arsmaint command again, and see if the message has disappeared.

	== Articles Related to this message ==		== Articles Related to this message ==
	[http://www.odusergroup.org/forums/index.php?topic=2629.0;topicseen IBM Content Manager OnDemand User Group Forums]		[http://www.odusergroup.org/forums/index.php?topic=2629.0;topicseen IBM Content Manager OnDemand User Group Forums]

Jderrick: /* Related Errors */

2019-01-13T23:54:59Z

Related Errors

← Older revision		Revision as of 23:54, 13 January 2019
Line 13:		Line 13:

	== Related Errors ==		== Related Errors ==
	Windows Client Message: [[~~Server~~ failed ~~on retrieval from storage set~~]].		Windows Client Message: [[The server failed while retrieving a document]].

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

Jderrick: IBM CMOD error ARS0111E - cannot determine link for file

2019-01-13T22:42:18Z

IBM CMOD error ARS0111E - cannot determine link for file

New page

{{TOCright}}
== What was the error? ==
'''Message Number''': 111

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

'''Message Name''': ARS0111E

'''Message Text''': OnDemand is unable to determine the link for the file >/arscache/cache2/12345/ABC/DOC/123FAAA<. The error number is X Srvr->ondemand 10.0.0.1 non-SSL<-

== Example ==
OnDemand is unable to determine the link for the file >/arscache/cache2/12345/ABC/DOC/123FAAA<. The error number is 2 Srvr->ondemand 10.0.0.1 non-SSL<-

== Related Errors ==
Windows Client Message: [[Server failed on retrieval from storage set]].

== What were you doing? ==
Likely running IBM CMOD's arsmaint command with the "-v" option to validate the cache filesystems.

== What happened? ==
IBM Content Manager OnDemand encountered a file for which there is no link. Without a link inside the cache filesystem, the item cannot be retrieved in the cache. In fact, IBM CM OnDemand will try to retrieve the file from secondary storage (CMOD Storage Set or Storage Node) if one exists, as without a valid link, IBM Content Manager OnDemand will not know where the file exists in the cache filesystem(s).

== Troubleshooting ==
The troubleshooting is already done. The link needs to be created. You can create a new link using information from the error message, which should allow the file to be retrieved.

In the example above, the link could be re-created with the following command:
ln -s /arscache/cache1/retr/ABC/DOC/123FAAA /arscache/cache2/12345/ABC/DOC/123FAAA

If the creation of the link is successful, IBM Content Manager OnDemand should be able to retrieve the documents from the CMOD cache.

== Articles Related to this message ==
[http://www.odusergroup.org/forums/index.php?topic=2629.0;topicseen IBM Content Manager OnDemand User Group Forums]