oracle开发应用中报以ora类型的9个错误汇总（Oracle development applications reported 9 errors aggregated in ora type）.doc

oracle开发应用中报以ora类型的9个错误汇总（Oracle development applications reported 9 errors aggregated in ora type） Oracle development applications reported 9 errors aggregated in ORA type This article summarizes some common errors in Oracle database operations and their solutions for your reference. Including ORA-01650, ORA-01652, ORA-01578, ORA-01628, ORA-00600, ORA-03113, ORA-00942, ORA-1636, ORA-01688 The reasons for these ora errors will be listed in detail as well as the countermeasures: The first: ORA-01650:unable, to, extend, rollback, segment, NAME, by,, NUM, intablespace, NAME Causes: the above ORACLE error is caused by insufficient rollback table space, and this is also the most common ORACLE error message for ORACLE data administrators. These errors occur when a user makes a very large data operation that results in a shortage of existing rollback segments and enables the allocated rollback segment table space to be full and cannot be allocated again. Solution: use the ALTER TABLESPACE tablespace_name DATAFILE filename SIZE size_of_file command to add tablespace to the specified data. You can add one or more table spaces depending on the specific circumstances of the ADD. Of course, this is also related to your host on the disc device, if you host the bare disk device has no extra space, it is recommended that you do not lightly increase the rollback segment size, you can use the following statements to check the remaining tablespace how much space: Select user_name, sql_text from V$open_cursor where user_name=user_name; if extra space is more, it can be appropriate to append to a large rollback segment for the table space, so as to avoid the mistakes. You can also use the following statement to test the competitive status of rollback segment: Select, class, count, from, V$waitstat, where, calss, in (system, undo, Header, system, undo, block,undo, Header,undo, block); and Select, sum (value), from, V$sysstat, where, name, in (db_block_gets,consistents, gets); if any cla