Several options:
1) Increase the number of locks to > 1,000,000
2) Lock the table in exclusive mode
3) Turn off logging
4) As stated, break up transaction into smaller chunks
-d
At 07:05 PM 9/11/97 +0000, Yogesh Patel wrote:
}David,
}
}So, for the online 5.0 users, what is the alternative?
}
}I have million rows to delete.
}
}Besides, everytime I try to delete somewhat large amount of rows,
}I get following error message.
}
}-458 Long transaction aborted.
}
}I checked that only 5-6 logs out of 16 logs are filled at the time
}this message pops up.
}
}-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.
}
}
}
}