Does anyone come across a situation that a file was successfully loaded in CMOD, but there was no msg 87 for the file in System Log and there was no record found in System Load either?
Thanks.
Shouldn't happen. Are you on the right machine? If there's no trace of it in the logs, are you sure it loaded? (Compare the DocID in the thick client to the Load ID in the System Log.)
Can you give us some more background on what lead up to this situation?
-JD.
Justin,
A job runs everyday during the week, the problem does not have a pattern, some time the msg 87 was written into System Log and some time it did not.
For example, the arsload log indicated that a file is loaded on Aug 13 with the load-id 6170-60-0-492FAA-16660-16660
arsload: 08/13/15 01:22:41 -- Indexing started, 116061574 bytes to process
OnDemand Load Id = >6170-60-0-492FAA-16660-16660<
Loaded 7607 rows into the database
But when I do a search on the System Log for the last few days with the Message like '%6170-60-0-%' and it came back with the following:
08/14/2015 01:24:02 Application Group Load: Name(xxxx) LoadId(6170-60-0-493FAA-16661-16661) File(xxxx) InputSize(138302820) OutputSize(11437880) Rows(8322) Time(40.7700) Appl(xxxx)
08/12/2015 01:27:58 Application Group Load: Name(xxxx) LoadId(6170-60-0-491FAA-16659-16659) File(xxxx) InputSize(128745633) OutputSize(10189512) Rows(7942) Time(33.1840) Appl(xxxx)
08/11/2015 01:39:34 Application Group Load: Name(xxxx) LoadId(6170-60-0-490FAA-16658-16658) File(xxxx) InputSize(190263880) OutputSize(14236925) Rows(11985) Time(43.9570) Appl(xxxx)
That's all I find in the System Log.
Thanks.
-jw
It is possible, and happens every time you archive something with ODWEK (ODFolder.storeDocument(...) method), then you will see nothing in "System Lo(g|ad)"... unfortunately...
Loading using arsadmin load command also does not put a 87 log message
Thanks Justin, Alessandro and Rick for your info.
-jw