cancel
Showing results for 
Search instead for 
Did you mean: 

SM13 Update request

Former Member
0 Kudos
609

Dear all,

320 DATAMIG1 05.09.2010 23:09:07 MM42 @BB\QSynchronous update@ @3U\QRestart not possible@ @07\QEnqueues released@ @96\QCreated by batch input@ Error (no retry)

320 DATAMIG1 05.09.2010 23:09:04 MM42 @BB\QSynchronous update@ @3U\QRestart not possible@ @07\QEnqueues released@ @96\QCreated by batch input@ Error (no retry)

320 DATAMIG1 05.09.2010 23:09:00 MM42 @BB\QSynchronous update@ @3U\QRestart not possible@ @07\QEnqueues released@ @96\QCreated by batch input@ Error (no retry)

320 DATAMIG1 05.09.2010 22:36:38 MM42 @BB\QSynchronous update@ @3U\QRestart not possible@ @07\QEnqueues released@ @96\QCreated by batch input@ Error (no retry)

320 DATAMIG1 05.09.2010 22:36:34 MM42 @BB\QSynchronous update@ @3U\QRestart not possible@ @07\QEnqueues released@ @96\QCreated by batch input@ Error (no retry)

310 DATAMIG2 05.09.2010 20:52:17 ME22N @07\QEnqueues released@ Enqueues deleted

310 DATAMIG2 05.09.2010 20:49:18 ME22N @07\QEnqueues released@ Enqueues deleted

310 DATAMIG2 05.09.2010 20:45:36 ME22N @07\QEnqueues released@ Enqueues deleted

310 DATAMIG1 03.09.2010 23:13:10 MIGO @07\QEnqueues released@ Enqueues deleted

310 DATAMIG1 03.09.2010 22:52:14 VK11 @07\QEnqueues released@ Enqueues deleted

310 DATAMIG1 03.09.2010 22:48:25 VK11 @07\QEnqueues released@ Enqueues deleted

310 DATAMIG1 03.09.2010 22:12:20 WB02 @BB\QSynchronous update@ @3U\QRestart not possible@ @07\QEnqueues released@ Error (no retry)

310 DATAMIG1 03.09.2010 22:00:06 XD03 @07\QEnqueues released@ Enqueues deleted

310 DATAMIG1 03.09.2010 21:54:47 WB02 @BB\QSynchronous update@ @3U\QRestart not possible@ @07\QEnqueues released@ Error (no retry)

310 DATAMIG1 03.09.2010 21:39:41 WPUK @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:13:39 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:13:29 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:13:20 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:13:11 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:13:01 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:12:52 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:12:40 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:12:30 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:12:18 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:12:07 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:11:55 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:11:43 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:11:29 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:11:14 MM42 @07\QEnqueues released@ Enqueues deleted

320 DATAMIG1 03.09.2010 21:10:57 MM42 @07\

I have never face the above error in SM13 Update request. actually i got the errors after Document Split activation before i have never seen any errors in SM13 .

Kindly advise.

Accepted Solutions (0)

Answers (2)

Answers (2)

volker_borowski2
Active Contributor
0 Kudos

Hi,

as for so many errors in a short period from very diffrent transactions,

I'd investigate at least if there is some DB-problem is involved (freespace, extents, ... or likewise),

to prevent new errors.

But to resolve esp. these broken ones, you need additional help from the functional side.

Volker

Former Member
0 Kudos

Dear all .

Kindly provide suggestion ,

Regards

former_member204746
Active Contributor
0 Kudos

this is not your problem. ask your functional to analyze these error and let them investigate.