Issues following bulk load

3 posts / 0 new
Last post
StephenHutchings
StephenHutchings's picture
Offline
Last seen: 3 years 10 months ago
Joined: Sep 13 2010
Junior Boarder

Posts: 16

Stephen Hutchings
Issues following bulk load

Hi,

I have 2 problems related to the same issue I've been trying to solve (creating a copy of an existing InfiniDB instance on a second machine). Any advice would be welcome. Thanks again.

(i)

I’ve encountered an error in trying to bulk load from an outfile into which I had I selected the results of a table join.

For some reason the cpimport failed after approx 50 minutes. From the InfiniDB.log output (too big to paste here) it looks as if it’s tried to rollback but failed. The last set of log messages say “DMLProc failed to start. Database is not in working state due to problem with rollback. Please restore your database.”

The cpimport output is:

[spoiler]C:\infinidb\bin>cpimport -j 106

Bulkload root directory : C:/infinidb/bulk
job description file : Job_106.xml
2010-09-27 15:40:15 (2172) INFO : successfully load job file C:/infinidb/bulk/jo
b/Job_106.xml
2010-09-27 15:40:15 (2172) INFO : PreProcessing check starts
2010-09-27 15:40:15 (2172) INFO : PreProcessing check completed
2010-09-27 15:40:15 (2172) INFO : preProcess completed, total run time : 0 seconds
2010-09-27 15:40:15 (2172) INFO : No of Read Threads Spawned = 1
2010-09-27 15:40:15 (2172) INFO : No of Parse Threads Spawned = 3
2010-09-27 16:34:25 (2172) CRIT : extendColumn: error adding extent after column OID-3357; DBRoot-1; part-1; seg-30; newDBRoot-1; newpart-1; newseg-31; IDB-2012: Unknown Error [1039]
2010-09-27 16:34:25 (2172) CRIT : extendColumn: error adding extent after column OID-3360; DBRoot-1; part-1; seg-30; newDBRoot-1; newpart-1; newseg-31; IDB-2012: Unknown Error [1039]
2010-09-27 16:34:25 (2172) CRIT : extendColumn: error adding extent after column OID-3358; DBRoot-1; part-1; seg-30; newDBRoot-1; newpart-1; newseg-31; IDB-2012: Unknown Error [1039]
2010-09-27 16:34:25 (2172) ERR : writeToFileExtentCheck: extend column failed:IDB-2012: Unknown Error [1039]
2010-09-27 16:34:25 (2172) ERR : writeToFileExtentCheck: extend column failed:IDB-2012: Unknown Error [1039]
2010-09-27 16:34:25 (2172) CRIT : Bulkload Parse (thread 1) Failed for Table perf_test.####temp during parsing. Terminating this job. [1039]
2010-09-27 16:34:25 (2172) CRIT : Bulkload Parse (thread 0) Failed for Table perf_test.####temp during parsing. Terminating this job. [1039]
2010-09-27 16:34:25 (2172) ERR : writeToFileExtentCheck: extend column failed:IDB-2012: Unknown Error [1039]
2010-09-27 16:34:25 (2172) CRIT : Bulkload Parse (thread 2)

davidhill
davidhill's picture
Offline
Last seen: 1 month 4 days ago
Joined: Oct 27 2009
Administrator

Posts: 595

david hill
Re:Issues following bulk load

Hey Stephen, based on the error code of #2012 reported in the cpimport logs, cpimport had a problem writing to disk. One of the reasons for this error code is running out of disk space. But that seems strange since you reported you started with ~200gb of free space.

So could you check a couple of things for us:
1. available disk space, if there a chance that it's out of local disk space
2. And you reported you check permissions, can you can successfully right to
the data disk directory, \Calpont\data1 and \Calpont\dbrm?

Also if you could post the last half cpimport log, that might provide some more info:

\Calpont\bulk\log\Job_106.txt

StephenHutchings
StephenHutchings's picture
Offline
Last seen: 3 years 10 months ago
Joined: Sep 13 2010
Junior Boarder

Posts: 16

Stephen Hutchings
Re:Issues following bulk load

Thanks David.

This is a bit of a non-thread now (my fault) for the following reasons:

1. I reported that I started out with 200 GB of available space. Unfortunately I can't find much evidence to back that statement up. Please assume this was my mistake, and that I just didn't have enought space - so apologies for wasting your time on that one.

The \Calpont\bulk\log\Job_106.txt relating to this point was completely empty, by the way.

2. Before I'd received your reply, we performed an uninstall and reinstall of InfiniDB, then recreated the DB from bulk loads (just not the large data I mentioned in (1). So unfortunately I can no longer check that I had writes to the directories you mentioned as that install has been overwritten. If I'm in a postion to perform the copy again though, I'll check this first.