You need to check what your LTXHWM and LTXEHWM onconfig
parameters are set to. These parameters control the conditions where
the database will intervene when it encounters a long transaction.
I suspect they may be set < 50 percent (they are set as a
percentage of your total logical log space).
-Bill
}
} Hi Folks,
}
} We really need a help here from you, experienced DBAs.
}
} We have ODS 5.0.2 server and we are receiving error# 458 on somewhat
} long transaction. During such transcations, I have been monitoring the
} log files and only 6-8 out of 16 are filled up and we are getting this
} nasty message. I also monitored the available lock but it is also not touching
} limit too.
}
} Is something I am missing??
}
} Any help greatly appreciated.
}
} Thanks/Yogesh
}
} Error:
}
} -458 Long transaction aborted.
}
} The database server (probably OnLine or INFORMIX-OnLine for
} NetWare) ran out of log space in which to record this transaction. A
} transaction that is not fully recorded cannot be rolled back, so to
} preserve database integrity, the operating system ended the
} transaction and rolled it back automatically. All changes made since
} the start of the transaction have been removed. Terminate the
} application and replan it so that it modifies fewer rows per
} transaction. Alternatively, contact the OnLine administrator to
} discuss having the number or the size of the logical logs increased.
} Be prepared to talk about the number of rows being updated or
} inserted and the size of each row.
}
}
}
--
Bill Ennis Voice: 312-474-7516
SSA Fax: 312-474-7460
500 W. Madison email: ennis@ssax.com ennis@accesschicago.net