We are using CMOD 8.5.0.5 MP. Last week, a file load into the system resulted in a double load id. Please find the arslog file. What could have been the reason for a double loadid generation.
arsload: Processing file >/prod/xyz/process/ST_COLD_stmts_03012013063544/ST_COLD_stmts_030120130634_1.AFP<
arsload: Load Version <8.5.0.6> Operating System <Linux> <#1 SMP Wed Nov 21 11:42:14 EST 2012.2.6.18-308.24.1.el5>
arsload: Server Version <8.5.0.6> Operating System <AIX> <6.1> Database <ORACLE> <>
arsload: 03/06/13 15:29:03 -- Indexing started, 234000845 bytes to process
APK415I cc=yes
APK415I cctype=a
APK415I cpgid=500
APK415I convert=yes
APK415I trc=no
APK415I dcfpagenames=yes
APK415I fileformat=record
APK415I imageout=asis
APK415I indexobj=all
APK415I indexstartby=1
APK415I formdef=F1ONDMD1
APK415I mcf2ref=cf
APK415I restype=all
APK415I inputdd=/prod/xyz/process/ST_COLD_stmts_03012013063544/ST_COLD_stmts_030120130634_1.AFP
APK415I outputdd=/prod/xyz/process/ST_COLD_stmts_03012013063544/ST_COLD_stmts_030120130634_1.AFP.out
APK415I indexdd=/prod/xyz/process/ST_COLD_stmts_03012013063544/ST_COLD_stmts_030120130634_1.AFP.ind
APK415I resobjdd=/prod/xyz/process/ST_COLD_stmts_03012013063544/ST_COLD_stmts_030120130634_1.AFP.res
APK440I ACIF AT IM43P11 HAS COMPLETED NORMALLY WITH RETURN CODE 0.
arsload: 03/06/13 15:29:32 Indexing completed
arsload: 03/06/13 15:29:32 -- Loading started, 260551470 bytes to process
Resource /prod/xyz/process/ST_COLD_stmts_03012013063544/ST_COLD_stmts_030120130634_1.AFP.res matches the reso
OnDemand Load Id = >5166-2-0-125FAA-15738-15765<
OnDemand Load Id = >5166-2-0-125FAA-15737-15765<
33220 rows written to output file
Document compression type used - OD77. Bytes Stored = >14702092< Rows = >33220<
Loaded 33220 rows into the database
arsload: 03/06/13 15:32:46 Loading completed
arsload: Processing successful for file
I have never seen something like this before.
The only difference that I see in the 2 load IDs is the low date.
Did it load 33220+33220 in the database?
On a completely unrelated note, you'll want to upgrade to 8.5.0.6 -- 8.5.0.5 has a memory leak and TSM-related issues.
Thanks Justin for pointing that out.
Do you have any pointer why we got a double loadid. Is this something we should open up a ticket with IBM. Not sure if any one has experienced this before.
I don't think double load ID's are a problem, but I can't remember off the top of my head why you get more than one. I'm sure this has been discussed before here. It's not an error or a bug.
I raised a PMR on this with IBM and they responded saying that its successful scenario. CMOD adjusts the LOADID as it loads the data in the file. The final loadId is the correct one and should be used for unload purposes if need be.