ISQL "LOAD FROM" command

ISQL "LOAD FROM" command

Post by Joerg Spilk » Sun, 24 Apr 1994 15:59:26



Hi all,

is there any bug known with the above command when loading larger tables? I
just tried to load about 75000 records which i unloaded prevoiusly with the
"UNLOAD TO" command.

ISQL reports a syntax error in the load file after about 55000 records. But
everything seems to be ok and i had no problems to load all records with
dbload.

Environment: Online 5.0, ISQL 4.1 on a Siemens RM400

Greetings, Joerg

 
 
 

ISQL "LOAD FROM" command

Post by Joe Lumbl » Tue, 26 Apr 1994 22:57:30


: Hi all,

: is there any bug known with the above command when loading larger tables? I
: just tried to load about 75000 records which i unloaded prevoiusly with the
: "UNLOAD TO" command.

: ISQL reports a syntax error in the load file after about 55000 records. But
: everything seems to be ok and i had no problems to load all records with
: dbload.

: Environment: Online 5.0, ISQL 4.1 on a Siemens RM400

: Greetings, Joerg

Joerg,

You are either running out of locks or getting into a long transaction.
The "syntax" error says something like "bad row in load file".  Check your
online.log for specifics about just what caused your crash.

Dbload will solve all of your problems with this.

Bye,
Joe

--
===========================================================================

BancTec Service Corportation     214-450-9894
Dallas, Texas
Watch for my _INFORMIX DBA SURVIVAL GUIDE_ in Fall '94 from Prentice Hall!
===========================================================================

 
 
 

ISQL "LOAD FROM" command

Post by dav.. » Wed, 27 Apr 1994 04:28:24


Quote:> is there any bug known with the above command when loading larger tables?
> I just tried to load about 75000 records which i unloaded prevoiusly with
> the"UNLOAD TO" command.
> ISQL reports a syntax error in the load file after about 55000 records.
> But everything seems to be ok and i had no problems to load all records
> with dbload.
> Environment: Online 5.0, ISQL 4.1 on a Siemens RM400

Check the LOCKS parameter in your tbconfig file.  Then do a "tbstat -u" and
see how many locks the tbload process is holding.  You might be running out
of locks.  If that's the case, then increase your locks.  (check the OnLine
message file also for a "lock table overflow" situation). tbload has a
"feature" where it does row-level locking on a table that it's trying to
load.  Also, if you are loading a table which contains BLOBS, tbload locks
BLOBpages as well.  Since OnLine is limited to only 256,000 locks, there is
a limitation on how big a table you can tbload with it.

##############################################################

GE Information Services         UUCP: uunet!ge!davidn
401 North Washington Street     Voice: 1-301-340-5461
Rockville, MD 20850 USA
##############################################################

 
 
 

ISQL "LOAD FROM" command

Post by Mark Lansl » Wed, 27 Apr 1994 21:28:05



> > is there any bug known with the above command when loading larger tables?
> > I just tried to load about 75000 records which i unloaded prevoiusly with
> > the"UNLOAD TO" command.

> > ISQL reports a syntax error in the load file after about 55000 records.
> > But everything seems to be ok and i had no problems to load all records
> > with dbload.

> > Environment: Online 5.0, ISQL 4.1 on a Siemens RM400

> Check the LOCKS parameter in your tbconfig file.  Then do a "tbstat -u" and
> see how many locks the tbload process is holding.  You might be running out
> of locks.  If that's the case, then increase your locks.  (check the OnLine
> message file also for a "lock table overflow" situation). tbload has a
> "feature" where it does row-level locking on a table that it's trying to
> load.  Also, if you are loading a table which contains BLOBS, tbload locks
> BLOBpages as well.  Since OnLine is limited to only 256,000 locks, there is
> a limitation on how big a table you can tbload with it.

> ##############################################################

> GE Information Services         UUCP: uunet!ge!davidn
> 401 North Washington Street     Voice: 1-301-340-5461
> Rockville, MD 20850 USA
> ##############################################################

As people have already said, you are probably exceeding the number of
available locks or running into a long transaction.

If you are exceeding the number of locks, an alternative to Davids
suggestion is to first lock the table and then load the data as follows :

~sql~example~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

begin work;

lock table <table name> in exclusive mode;

load from <file> insert into <table name>;

commit work;

~end~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This will only generate one lock event (the lock on the table).  This is
applicable to isql and 4gl.  This method will also save you from having
to up the number of available locks on your OnLine instance.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

      Druid Systems Ltd, UK        |  on my usual barking frenzy."
 +44 932 571212 (Vce) 571552 (Fax) |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 
 
 

1. groups and "help" command in ISQL

i' ve found a strange behavor of the "help" command
in ISQL.
In my DB i have 3 users , the first is "DBA" that owns all the table
and the others are "user1" and "user2" that are normal user .

if i grant each user  to select on the table
(grant select on table1 to user1 ...)
 , running the help command from ISQL i have the list of all the tables
owned by the user plus the table that the user can use .
If assign "user1" and "user2" at a group, then i specify that the
group is the default group for "user1" and "user2" and issue
the grant not for each user but for the group
(grant select on table1 to group group1 ...) ,
running "help" the users can not see all the table , only
the tables that they own instead that all (but all the user
are able to use also the other table).

I'm wronging or is it normal ????

TIA (-:

(i hope that the explenation is clear ..... )

2. PLEASE HELP ME!

3. max of ("...","...","..")

4. USING VAR ON ORDER BY (SQL SERVER 7) STORE PROCEDURE

5. ISQL says "SQL Server is unavailable"

6. Help - Admins password and 'SYSTEM.MD?'

7. "Isql: error converting exit value."

8. standard buttons

9. ISQL says "SQL Server is unavailable"

10. "insufficient memory" at ISQL Utility

11. Overriding ISQL "checks"

12. OpenServer application: results "disappear" in ISQL

13. isql searches "language handler"