DB gets down automatically

S

sureshp

Member
Hi,
when i try to load a bulk amt of data through CIM file, my DB automatically gets down. could anyone explain me the reason?
 
Please find the log file details

(user JSARAVA4 is trying to load the data)
.
.
15:53:47 Usr 5: Login by jsarava4 on /dev/pts/34. (452)
16:02:12 Usr 5: KILL signal received. (298)
16:02:12 Usr 5: Begin transaction backout. (2252)
16:02:12 Usr 5: Transaction backout completed. (2253)
.
.
16:17:23 Usr 6: SYSTEM ERROR: Memory violation. (49)
16:17:23 Usr 6: ** Save file named core for analysis by Progress Software Co
rporation. (439)
16:17:23 Usr 6: Begin transaction backout. (2252)
.
.
19:41:41 Usr 4: SYSTEM ERROR: Memory violation. (49)
19:41:41 Usr 4: ** Save file named core for analysis by Progress Software Co
rporation. (439)
.
.
21:43:22 Usr 2: Logout by csivara1 on /dev/pts/11. (453)
22:06:27 Usr 3: KILL signal received. (298)
22:06:27 Usr 3: Logout by mkiran2 on /dev/pts/30. (453)
22:14:55 BROKER 0: SIGTERM received. (3694)
22:15:03 BROKER 0: Begin normal shutdown (2248)
22:15:46 BROKER 0: Sending signal 14 to 1 connected user(s). (2261)
22:16:33 BROKER 0: Sending signal 2 to 1 connected user(s). (2261)
22:17:08 BROKER 0: Resending shutdown request to 1 user(s). (2263)
22:17:23 Usr 5: KILL signal received. (298)
22:17:25 Usr 5: Logout by sdeenada on /dev/pts/2. (453)
22:17:25 BROKER : Removed shared memory with segment_id: 53674114
22:17:25 BROKER : Removed shared memory with segment_id: 53706884
22:17:25 BROKER : Removed shared memory with segment_id: 53739681
22:17:25 BROKER : Removed shared memory with segment_id: 53772451
22:17:25 BROKER : Removed shared memory with segment_id: 53805228
22:17:25 BROKER : Removed shared memory with segment_id: 53838018
22:17:26 BROKER : Multi-user session end. (334)
 
are you sure that no one is triggering the kill signal. everytime when you initiate a load DB comnes down right. Are you running this load in multiple threads and is there any piece of code which kills any already started process before inititating a new one.
 
You must log in or register to reply here.
Back
Top