ARS1400E
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
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 -f 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:
On AIX:
ps -ef |grep arsload
On Linux:
ps auxw |grep arsload
Then issue a kill command for both of the processes:
kill <process-id-number> <process-id-number>
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, 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
- 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.