Troubleshooting Borrower Import

When you run Borrower Import, it creates two files. Each file is denoted by an extension containing a letter followed by a 2-digit number. (For example, E25 and R25.)

These files contain information about how Horizon received the borrower records:

TheError file (E). Shows the borrower records that are not imported. Errors may occur because a record you are adding already exists, a record you are deleting has blocks attached to it, and so forth.
TheRetry file (R). Shows the borrower records that are not imported. You can edit these files and try to import them again.

Both of these files include a number that indicates the run. The run is a sequential number of times you run Borrower Import where one of these messages appears. Open any of these files to view information or edit data from that run.

To retry a run, resolve the reason why the record was not imported. (For example, if you could not delete a borrower because of a block, resolve the block. If you did not supply adequate information, enter the needed fields, and so on.) You can delete the E and R files when you no longer need them.

Many Borrower Import users rename Bimport.exe so they can delete Borrower Import without deleting the executable file. Bimport2A.exe is a common name to use. Leave the .exe extension in place.

Here is an example of a Borrower Import run using S32.

Four borrower records are created to be imported using S32 format.

C> type data.s32
second_id, action_code, name, btype
555-11-5555, A, Beauchamp, Thom M., st.
555-22-5555, A, Hunter, Bonnie, patron
555-33-5555, A, Price, Carrie K., st.
555-44-5555, A, Simmons Danny E., patron

At the command line, Borrower Import starts the import process.

C>bimport /idata.s32 /fs32 /ksecond_id
record line action key(s)
------ ------ ------ ----------------------
1 2 insert 555-11-5555 <ok>
2 3 insert 555-22-5555
failed: DbxInsertRow failed: Database Error|Integrity trigger failed: bad btype in borrower
--Database Error|Integrity trigger failed: bad btype in borrower
3 4 insert 555-33-5555 <ok>
3 5 insert 555-44-5555
failed: DbxInsertRow failed: Database Error|Integrity trigger failed: bad btype in borrower
--Database Error|Integrity trigger failed: bad btype in borrower

Statistics show that out of the four records, two were imported.

statistics:
record 4
insert 4
error 2
C>dir
The volume label in drive C is MSDOS5P0.
The Volume Serial Number is 2F5C:16E1
Directory of C:\mq41

Borrower Import creates an Error file (E) and a Retry file (R) for each run.

Bimport E01 372 6-08-96 11:00p
Bimport R01 127 6-08-96 11:00p
Bimport E02 372 6-08-96 11:00p
Bimport R02 127 6-08-96 11:00p

4 file(s) 456 bytes used 6246400 bytes free

C>type bimport.e02

The Error File explains why the records were not imported (For example, the borrower had a bad btype).

line:3 (2) 555-22-5555
DbxInsertTow failed: database Error|Integrity trigger failed: bad btype in borrower
-- Database Error|Integrity trigger failed: bad btype in borrower
line: 5 (3) 555-44-5555
DbxInsertRow failed: database Error|Integrity trigger failed: bad btype in borrower
-- Database Error|Integrity trigger failed: bad btype in borrower

The Retry File lets you correct the problem, then retry the run. (For example, patron was switched to ptrn.)

C>type bimport.r02
second_id, action_code, name, btype
555-22-5555, A, Hunter, Bonnie, ptrn
555-44-5555, A, Simmons, Danny E., ptrn

At the command line, Borrower Import starts the import process.

C>bimport /idata.r02 /fs32 /ksecond_id
1 2 insert 555-22-5555 <ok>
3 3 insert 555-44-5555 <ok>

Borrower Import imports the remaining files.

statistics:
record 2
insert 2

 

 


© 1998-2017 Sirsi Corporation