Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    SQL update doesn't actually take effect

    • Article Type: General
    • Product: Aleph
    • Product Version: 21

    Problem Symptoms:
    An SQL update or delete is executed (the "nnn rows updated" appears), but, checking in the GUI or Web, the change has not actually taken effect.

    Failure to include "commit" after the SQL update(s). For an SQL "update" or "delete" to take effect, it needs to be followed by a "commit" command, like this:
    SQL> update znn set yyy = zzz where ....;
    SQL> commit;

    Include "commit" as the final command.

    Additional Information

    There may be a series of related updates which should not take effect until all of them are completed.

    Such as:
    SQL> update <aaa ....>
    SQL> update <bbb ....>
    SQL> update <ccc ....>
    SQL> commit;

    The Ex Libris update examples do not always include the "commit"; it is assumed.

    Also, before performing SQL updates (or ALEPH global changes) the affected table(s) should be backed up using p_file_03 ("Export Database Tables") or an Oracle individual table backup.

    Category: System Management (500)

    • Article last edited: 10/8/2013