ARS1400E - Revision history

Jderrick: /* Crashed load */

2025-01-15T17:07:50Z

Crashed load

← Older revision		Revision as of 17:07, 15 January 2025
Line 49:		Line 49:

	=== Crashed load ===		=== Crashed load ===
	If a load was running, and the arsload processes crashed, you will need to unload the failed file. (Normally, this ~~would be done~~ by adding the -f option to arsload to 'force unload of failed loads'.		If a load was running, and the arsload processes crashed, you will need to unload the failed file. Normally, the [arsload] utility would perform this clean-up work automatically (by adding the -f option to arsload to 'force unload of failed loads'), but can itself fail if the load process was killed or otherwise terminated abnormally, like a network connection being unexpectedly cut, a server reboot, or CMOD or DB2 going offline unexpectedly.

	arsadmin unload -I ARCHIVE -u ADMIN -p PASSWORD -g APPGROUP -Q -L LOADID		arsadmin unload -I ARCHIVE -u ADMIN -p PASSWORD -g APPGROUP -Q -L LOADID

Jderrick: /* Articles Related to this message */

2021-09-28T14:16:04Z

Articles Related to this message

← Older revision		Revision as of 14:16, 28 September 2021
Line 62:		Line 62:
	== Articles Related to this message ==		== Articles Related to this message ==

	~~None available~~.		[https://www.ibm.com/docs/en/cmofm/10.5.0?topic=messages-ars1400e CMOD Messages and Codes: ARS1400E]

Jderrick: /* Troubleshooting */

2021-09-28T14:13:32Z

Troubleshooting

← Older revision		Revision as of 14:13, 28 September 2021
Line 27:		Line 27:

	== Troubleshooting ==		== Troubleshooting ==
			There are two main causes for ARS1400E - either you are running multiple arsload processes that are interfering with each other, or arsload experienced an unrecoverable error and exited without cleaning up after itself, or 'crashed'.

			It's also possible that you tried to load a file with arsload, but didn't use the <code> -f </code> option, which 'forces unload' in the case of a failure during the load.

			=== Find multiple arsload processes ===
			It may be possible that you're running more than one arsload daemon at a time:

	Find the Process ID numbers for the arsload processes with:		Find the Process ID numbers for the arsload processes with:

			On AIX:
	ps -ef \|grep arsload		ps -ef \|grep arsload

			On Linux:
			ps auxw \|grep arsload

	Then issue a kill command for both of the processes:		Then issue a kill command for both of the processes:
Line 37:		Line 47:

	And restart only one instance of the IBM CMOD arsload command.		And restart only one instance of the IBM CMOD arsload command.

			=== Crashed load ===
			If a load was running, and the arsload processes crashed, you will need to unload the failed file. (Normally, this would be done by adding the -f option to arsload to 'force unload of failed loads'.

			arsadmin unload -I ARCHIVE -u ADMIN -p PASSWORD -g APPGROUP -Q -L LOADID

			;Where...
			: ARCHIVE is the name of the CMOD instance that the file was being loaded into
			: ADMIN is a User ID with the the Delete privilege for the App Group
			: PASSWORD is the account password or name of the stash file containing the password for the account
			: APPGROUP is the name of the Application Group that the data was being loaded into
			: LOADID is the Load ID reported by arsload.

	== Articles Related to this message ==		== Articles Related to this message ==

	None available.		None available.

Jderrick: /* Troubleshooting */

2018-03-25T10:09:45Z

Troubleshooting

← Older revision		Revision as of 10:09, 25 March 2018
Line 35:		Line 35:

	kill <process-id-number> <process-id-number>		kill <process-id-number> <process-id-number>

			And restart only one instance of the IBM CMOD arsload command.

	== Articles Related to this message ==		== Articles Related to this message ==

	None available.		None available.

Jderrick: Initial edit - addition of ARS1400E message from CMOD.

2016-10-13T21:08:22Z

Initial edit - addition of ARS1400E message from CMOD.

New page

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

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

'''Message Name''': ARS1400E

'''Message Text''': Loading was unable to continue due to encountering a previously failed load of the same name that has yet to be unloaded. Failed LoadId >5301-18-0-100FAA-20160112000000-20160112000000-5306< was attempted to be loaded at approximately 2016-01-13 15:13:56

== Related Errors ==

None.

== What were you doing? ==

Probably loading files into Content Manager OnDemand with the arsload command, running as a daemon.

== What happened? ==

More than one arsload daemon was launched for the same directory & Application Group -- now the two processes are 'fighting' over files.

== Example ==

ARS1400E Loading was unable to continue due to encountering a previously failed load of the same name that has yet to be unloaded.
Failed LoadId >5316-29-0-100454FAA-20161012000000-20161012000000-5318< was attempted to be loaded at approximately 2016-10-13 15:13:56

== Troubleshooting ==

Find the Process ID numbers for the arsload processes with:

ps -ef |grep arsload

Then issue a kill command for both of the processes:

kill <process-id-number> <process-id-number>

== Articles Related to this message ==

None available.