Subject | identifying where an IB script fails |
---|---|
Author | Mark Meyer |
Post date | 2001-10-24T13:59:02Z |
hi everyone..
i am new to interbase and new to this list.
Question:
what is the best way to identify where and why an IB script failed when
running it inside of either ISQL or WISQL.
Background:
i have written a delphi utility that produces a VERY LARGE interbase script
(several thousand lines). the purpose of the script is to perform mass
updates/deletes/inserts to an IB schema based on a daily oracle .dmp file
that we receive from a vendor.
the intent is to produce the script each day and submit it to either ISQL or
WISQL. i also want to bullet-proof this so that operations can perform this
task.
since the script is so large i need a way of identifying the exact point at
which the script fails - if and when it does fail.
thx for any help
mark
CONFIDENTIALITY NOTICE: The information contained in the transmission is
considered by TravelCLICK and the sender to be confidential. This material
is intended only for the use of the recipient(s) named above and may not be
disclosed to others without express written consent of the sender.
[Non-text portions of this message have been removed]
i am new to interbase and new to this list.
Question:
what is the best way to identify where and why an IB script failed when
running it inside of either ISQL or WISQL.
Background:
i have written a delphi utility that produces a VERY LARGE interbase script
(several thousand lines). the purpose of the script is to perform mass
updates/deletes/inserts to an IB schema based on a daily oracle .dmp file
that we receive from a vendor.
the intent is to produce the script each day and submit it to either ISQL or
WISQL. i also want to bullet-proof this so that operations can perform this
task.
since the script is so large i need a way of identifying the exact point at
which the script fails - if and when it does fail.
thx for any help
mark
CONFIDENTIALITY NOTICE: The information contained in the transmission is
considered by TravelCLICK and the sender to be confidential. This material
is intended only for the use of the recipient(s) named above and may not be
disclosed to others without express written consent of the sender.
[Non-text portions of this message have been removed]