Impossible to load a table ColumnsStore

gilbert.solet

unread,

Jun 22, 2016, 9:30:20 AM6/22/16

to MariaDB ColumnStore

Hi,

When I tried to load a table ColumnsStore from a table innodb, I got a message :

"Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore".

Before I had :

Internal error: PM1 : expandAbbrevExtent: error expanding extent for OID-3199; DBRoot-1; part-0; seg-0; IDB-2012: Not able to add extent; adding extent would exceed max file system disk usage

What is wrong in my configuration ?

Tx

Gilbert

Dipti Joshi

unread,

Jun 22, 2016, 9:35:51 AM6/22/16

to gilbert.solet, MariaDB ColumnStore

What exact command are you doing ?

Please include your Calpont.xml

Thanks,

Dipti

--
You received this message because you are subscribed to the Google Groups "MariaDB ColumnStore" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mariadb-columns...@googlegroups.com.
To post to this group, send email to mariadb-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mariadb-columnstore/73d3def8-e2b5-4078-8b02-eeb33d6190d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

gilbert.solet

unread,

Jun 22, 2016, 10:02:04 AM6/22/16

to MariaDB ColumnStore, gilber...@sacem.fr

My command is :

insert into shabi_app.ulysst_ligprog_cst select * from shabi_app.ulysst_ligprog;

ulysst_ligprog_cst : Columnstore

ulysst_ligprog : InnoDB : 1089363 rows

On Wednesday, June 22, 2016 at 3:35:51 PM UTC+2, Dipti Joshi wrote:

What exact command are you doing ?

Please include your Calpont.xml

Thanks,

Dipti

On Wed, Jun 22, 2016 at 8:30 AM, gilbert.solet <gilber...@sacem.fr> wrote:

Hi,
When I tried to load a table ColumnsStore from a table innodb, I got a message :
"Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore".

Before I had :
Internal error: PM1 : expandAbbrevExtent: error expanding extent for OID-3199; DBRoot-1; part-0; seg-0; IDB-2012: Not able to add extent; adding extent would exceed max file system disk usage

What is wrong in my configuration ?

Tx

Gilbert

--
You received this message because you are subscribed to the Google Groups "MariaDB ColumnStore" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mariadb-columnstore+unsub...@googlegroups.com.

Calpont.xml

Daniel Lee

unread,

Jun 22, 2016, 10:09:23 AM6/22/16

to MariaDB ColumnStore

Hello, Gilbert;

How much free disk space do you have in your server? Please post the output for the following command:

df -h

Thanks

----

Daniel Lee, QA and Support Engineer

MariaDB Corporation

www.mariadb.com

gilbert.solet

unread,

Jun 22, 2016, 10:31:26 AM6/22/16

to MariaDB ColumnStore

-sh-4.1$ df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/vg_tmprh6164-lv_root

13G 12G 645M 95% /

tmpfs 8.8G 11M 8.8G 1% /dev/shm

/dev/sda1 485M 84M 377M 19% /boot

/dev/mapper/vg_usr2-lv_usr2

51G 21G 28G 43% /usr2

/dev/mapper/vg_usr3-lv_usr3

99G 63G 32G 67% /usr3

Daniel Lee

unread,

Jun 22, 2016, 11:09:27 AM6/22/16

to MariaDB ColumnStore

Hello, Gilbert;

Thank you very much for the information.

The errors you received indicated that the disk volume which Columnstore is installed ran out of free space. By default, Columnstore is installed in the /usr/local/mariadb/columnstore directory. From the information you provided, the installation is most likely in the /dev/mapper/vg_tmprh6164-lv_root volume. Please verify if that is indeed the case and if it has enough free disk space for your insert operation.

Assuming that you are did a single-node installation and you are using only one dbroot, the following steps may help you to continue testing without adding a new hard drive. The idea is to relocate the Columnstore's data directory (referred to as dbroot) to a volume that has more free space.

1) stop Columunstore

a) execute the 'ma' command from the shell, this command starts the admin console

b) execute "shutdownsystem" to shutdown the Columnstore

2) relocate Columnstore directory

a) execute "mv /usr/local/mariadb/columnstore/data1 /yourNewDirPath". /yourNewDirPath should be on a volume that has enough free space.

b) execute "ln -s /yourNewDirPath/data1 /usr/local/mariadb/columnstore/data1".

3) start Columnstore

a) execute the 'ma' command from the shell

b) execute "startsystem" to start the Columnstore

Try you "insert...select" operation again to see if that helps.

Let me know if you have additional questions.

Thanks

----

Daniel Lee, QA and Support Engineer

MariaDB Corporation

www.mariadb.com

gilbert.solet

unread,

Jun 22, 2016, 11:28:43 AM6/22/16

to MariaDB ColumnStore

At the begining, I created a link like that on /usr2

[root@tobyc mysql]# pwd

/usr/local/mariadb/columnstore/mysql

[root@tobyc mysql]# ls -l

total 100

drwxr-xr-x 2 mysql mysql 4096 Jun 12 22:03 bin

-rw-r--r-- 1 mysql mysql 1215 Jun 9 16:07 calremoveuserpriority.sql

-rw-r--r-- 1 mysql mysql 2563 Jun 9 16:07 calsetuserpriority.sql

-rw-r--r-- 1 mysql mysql 1854 Jun 9 16:07 calshowprocesslist.sql

lrwxrwxrwx 1 mysql mysql 25 Jun 16 13:42 db -> /usr2/mysql/data/COLDT/db

drwxr-xr-x 8 mysql mysql 4096 Jun 16 11:26 db_orig

-rw-r--r-- 1 mysql mysql 841 Jun 9 16:07 dumpcat_mysql.sql

-rwxr-xr-x 1 mysql mysql 2180 Jun 9 16:07 dumpcat.pl

drwxrwxr-x 2 mysql mysql 4096 Jun 12 22:03 init.d

-rwxr-xr-x 1 mysql mysql 5778 Jun 9 16:33 install_calpont_mysql.sh

drwxr-xr-x 3 mysql mysql 4096 Jun 15 16:06 lib

drwxrwxr-x 3 mysql mysql 4096 Jun 16 14:07 lib64

drwxrwxr-x 2 mysql mysql 4096 Jun 12 22:03 logrotate.d

-rw-r--r-- 1 mysql mysql 6049 Jun 16 14:07 my.cnf

drwxrwxr-x 2 mysql mysql 4096 Jun 12 22:03 my.cnf.d

-rw-r--r-- 1 mysql mysql 6049 Jun 15 16:07 my.cnf.orig

-rwxr-xr-x 1 mysql mysql 13501 Jun 9 16:33 mysql-Columnstore

drwxr-xr-x 2 mysql mysql 4096 Jun 12 22:03 sbin

drwxrwxr-x 5 mysql mysql 4096 Jun 12 22:03 share

-rw-r--r-- 1 mysql mysql 1591 Jun 9 16:07 syscatalog_mysql.sql

It is wrong ? What is the difference between data1 et db ?

Daniel Lee

unread,

Jun 22, 2016, 11:38:21 AM6/22/16

to MariaDB ColumnStore

Hello, Gilbert;

When you create a table using the columnstore engine, all data for that table will be stored in /usr/local/mariadb/columnstore/data1 to ./datan, where n is the number of dbroots you configured during installation. All non-columnstore tables are still stored in the /usr/local/mariadb/columnstore/mysql directory. This design provides benefits for High Availability on a more complex, multi-node configuration.

Did the suggestion in my last post help to solve the out-of-space issue?

Thanks

---

Daniel Lee, QA and Support Engineer

MariaDB Corporation

www.mariadb.com

gilbert.solet

unread,

Jun 22, 2016, 11:47:02 AM6/22/16

to MariaDB ColumnStore

Yes, I will do tomorrow.And I will tell you the result.

Thanks

gilbert.solet

unread,

Jun 23, 2016, 5:25:41 AM6/23/16

to MariaDB ColumnStore

I followed the instructions but I have always the problem...

Thanks

gilbert.solet

unread,

Jun 23, 2016, 8:17:02 AM6/23/16

to MariaDB ColumnStore

On the Console, I have this :

[root@tobyc etc]# mcsadmin

MariaDB Columnstore Admin Console

enter 'help' for list of commands

enter 'exit' to exit the MariaDB Columnstore Command Console

use up/down arrows to recall commands

Active Alarm Counts: Critical = 1, Major = 1, Minor = 0, Warning = 0, Info = 0

Critical Active Alarms:

AlarmID = 4

Brief Description = DISK_USAGE_HIGH

Alarm Severity = CRITICAL

Time Issued = Thu Jun 16 15:44:09 2016

Reporting Module = pm1

Reporting Process = ServerMonitor

Reported Device = /

The reported device is "/", normal ?

Daniel Lee

unread,

Jun 23, 2016, 9:16:36 AM6/23/16

to MariaDB ColumnStore

Hello, Gilbert;

Yes, that is normal.

From the information you previously provided, the / is the mount point where your Columnstore installation is

/dev/mapper/vg_tmprh6164-lv_root

13G 12G 645M 95% /

----

Daniel Lee, QA and Support Engineer

MariaDB Corporation

www.mariadb.com

Frik Lubbe

unread,

Jun 23, 2016, 11:32:28 AM6/23/16

to Daniel Lee, MariaDB ColumnStore

Good day,

you are indeed seeing these errors because the root device '/' is almost full at 95%. Do a df -kh on the linux prompt and note that root is full. As previously mentioned on the group you will need to point the 'data1' and any other dbroots to another location using symbolic links. The details provided previously explains it well.

--

You received this message because you are subscribed to the Google Groups "MariaDB ColumnStore" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mariadb-columns...@googlegroups.com.

To post to this group, send email to mariadb-c...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mariadb-columnstore/27cbc570-b8bd-48d8-82d6-c33c50db6721%40googlegroups.com.

gilbert.solet

unread,

Jun 23, 2016, 11:35:50 AM6/23/16

to MariaDB ColumnStore

Ok! It's working now.

But you have a problem we want to load a table columnStore from a table innodb:

shabi_app.ulysst_ligprog : innoDB

shabi_app.ulysst_ligprog_cst : ColumnStore

MariaDB [shabi_app]> select count(*) from shabi_app.ulysst_ligprog;

+----------+

| count(*) |

+----------+

| 1089363 |

+----------+

1 row in set (7.60 sec)

An Insert / Select on the whole table doesn't work :

MariaDB [shabi_app]> insert into shabi_app.ulysst_ligprog_cst select * from shabi_app.ulysst_ligprog;

ERROR 1030 (HY000): Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore

But an Insert / Select with only 10 rows works. The table has 66 columns.

MariaDB [shabi_app]> insert into shabi_app.ulysst_ligprog_cst select * from shabi_app.ulysst_ligprog limit 10;

Query OK, 10 rows affected, 55 warnings (4.66 sec)

Records: 10 Duplicates: 0 Warnings: 55

Is it a bug ?

Thanks

Gilbert

Dipti Joshi

unread,

Jun 23, 2016, 11:37:36 AM6/23/16

to gilbert.solet, MariaDB ColumnStore

If you notice, even when you do "limit 10" there are 55 warnings.

Can you do SHOW WARNINGS after that insert and provide us the output ?

Thanks,

Dipti

--

You received this message because you are subscribed to the Google Groups "MariaDB ColumnStore" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mariadb-columns...@googlegroups.com.
To post to this group, send email to mariadb-c...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mariadb-columnstore/f7b8f4c9-f0dd-4b8c-b92f-c87e21566d45%40googlegroups.com.

gilbert.solet

unread,

Jun 23, 2016, 11:48:13 AM6/23/16

to MariaDB ColumnStore, gilber...@sacem.fr

The result :

MariaDB [shabi_app]> insert into shabi_app.ulysst_ligprog_cst select * from shabi_app.ulysst_ligprog;

ERROR 1030 (HY000): Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore

MariaDB [shabi_app]> show warnings;

+-------+------+----------------------------------------------------------------------------------------------------------------------+

| Level | Code | Message |

+-------+------+----------------------------------------------------------------------------------------------------------------------+

| Note | 1051 | Unknown table 'infinidb_vtable.$vtable_429' |

| Error | 1030 | Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore |

| Error | 1815 | Internal error: PM1 : Bulkload Read (thread 0) Failed for Table shabi_app.ulysst_ligprog_cst. Terminating this job. |

+-------+------+----------------------------------------------------------------------------------------------------------------------+

3 rows in set (0.00 sec)

MariaDB [shabi_app]> insert into shabi_app.ulysst_ligprog_cst select * from shabi_app.ulysst_ligprog limit 10;

Query OK, 10 rows affected, 55 warnings (3.65 sec)

Records: 10 Duplicates: 0 Warnings: 55

MariaDB [shabi_app]> show warnings;

+---------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| Level | Code | Message |

+---------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| Note | 1051 | Unknown table 'infinidb_vtable.$vtable_429' |

| Warning | 9999 | Values saturated |

| Note | 1592 | Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. |

+---------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

To unsubscribe from this group and stop receiving emails from it, send an email to mariadb-columnstore+unsub...@googlegroups.com.

To post to this group, send email to mariadb-c...@googlegroups.com.

Dipti Joshi

unread,

Jun 23, 2016, 12:06:26 PM6/23/16

to gilbert.solet, MariaDB ColumnStore, Daniel Lee

Gilbert:

Can you see if the cross-engine join are enabled in your Calpont.xml ?

The section for cross engine you Calpont.xml should look something like

<Host>127.0.0.1</Host>
<Port>3306</Port>
<User>root</User>
<Password>pwd</Password>

</CrossEngineSupport>

Where pwd is the password for root database user for your MariaDB ColumnStore system.

Regards,

Dipti

To unsubscribe from this group and stop receiving emails from it, send an email to mariadb-columns...@googlegroups.com.

To post to this group, send email to mariadb-c...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mariadb-columnstore/f7b8f4c9-f0dd-4b8c-b92f-c87e21566d45%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "MariaDB ColumnStore" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mariadb-columns...@googlegroups.com.

To post to this group, send email to mariadb-c...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mariadb-columnstore/d49f7ed1-f527-40a0-accf-9e049dec37b6%40googlegroups.com.

Justin Swanhart

unread,

Jun 24, 2016, 12:22:02 AM6/24/16

to MariaDB ColumnStore, gilber...@sacem.fr

Hi,

You are getting the 'values saturated' message because you are trying to insert data that works in regular MySQL but not in columnstore because columnstore does not support the full range of values for numeric data types.

Please vote for - https://jira.mariadb.org/browse/MCOL-92

Justin Swanhart

unread,

Jun 24, 2016, 1:19:45 AM6/24/16

to MariaDB ColumnStore, gilber...@sacem.fr

Hi,

I also suggest you vote for https://jira.mariadb.org/browse/MCOL-196

Justin Swanhart

unread,

Jun 24, 2016, 1:33:52 AM6/24/16

to MariaDB ColumnStore, gilber...@sacem.fr

Hi,

INSERT .. SELECT is not work for any tables actually. Vote for https://jira.mariadb.org/browse/MCOL-196

On Thursday, June 23, 2016 at 11:48:13 AM UTC-4, gilbert.solet wrote:

Justin Swanhart

unread,

Jun 24, 2016, 1:34:32 AM6/24/16

to MariaDB ColumnStore, gilber...@sacem.fr

Sorry, I meant: https://jira.mariadb.org/browse/MCOL-197

Justin Swanhart

unread,

Jun 24, 2016, 1:41:21 AM6/24/16

to MariaDB ColumnStore

Hi,

You might want to check the Calpont.xml file and try changing <TempDiskPath>/data/mariadb/logs/dbtmp/disktmp</TempDiskPath> to a path on a device with more space.

It will still munge your data for the insert .. select (hence the value saturated messages and MCOL-197) but that might help you avoid filling up /

--Greenlion

philipp...@sacem.fr

unread,

Jun 24, 2016, 3:27:54 AM6/24/16

to MariaDB ColumnStore

Hi I'm Philippe and I'm working with Gilbert.

I have modified the Calpont.xml file and we still have errors when doing INSERT...SELECT * FROM...

MariaDB [shabi_app]> insert into ulysst_ligprog_cst select * from ulysst_ligprog;

ERROR 1030 (HY000): Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore

MariaDB [shabi_app]> show errors;

+-------+------+----------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+----------------------------------------------------------------------------------------------------------------------+

| Error | 1030 | Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore |

| Error | 1815 | Internal error: PM1 : Bulkload Read (thread 0) Failed for Table shabi_app.ulysst_ligprog_cst. Terminating this job. |
+-------+------+----------------------------------------------------------------------------------------------------------------------+

2 rows in set (0.00 sec)

See create table attach file, InnoDB source table have exactly the same description.

Regards

Philippe

CREATE_TABLE _ulysst_ligprog_cst.txt

Justin Swanhart

unread,

Jun 24, 2016, 10:16:56 AM6/24/16

to philipp...@sacem.fr, MariaDB ColumnStore

It doesn't work for ANY insert ... Select. Even one from a CS table into SAME table!

Vote for my bug that I created.

Sent from my iPhone

--
You received this message because you are subscribed to a topic in the Google Groups "MariaDB ColumnStore" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mariadb-columnstore/vngq4vAjF60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mariadb-columns...@googlegroups.com.

To post to this group, send email to mariadb-c...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mariadb-columnstore/92d86bb5-4a94-4c1a-914c-fe14b07908b5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

<CREATE_TABLE _ulysst_ligprog_cst.txt>

Justin Swanhart

unread,

Jun 24, 2016, 10:17:03 AM6/24/16

to philipp...@sacem.fr, MariaDB ColumnStore

It can't be "cross engine join" because a small number of rows works.

Perhaps there is some debug flag you can turn on to get more detailed info in your logs. Are there any error messages in your mysql logs?

Can you try placing the entire /usr/local/mariadb directory on another device and creating a symlink to it?

Sent from my iPhone

On Jun 24, 2016, at 3:27 AM, philipp...@sacem.fr wrote:

--

You received this message because you are subscribed to a topic in the Google Groups "MariaDB ColumnStore" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mariadb-columnstore/vngq4vAjF60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mariadb-columns...@googlegroups.com.
To post to this group, send email to mariadb-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mariadb-columnstore/92d86bb5-4a94-4c1a-914c-fe14b07908b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

<CREATE_TABLE _ulysst_ligprog_cst.txt>

Daniel Lee

unread,

Jun 24, 2016, 11:35:01 AM6/24/16

to MariaDB ColumnStore

Hello Philippe;

Please do few things for me:

1) If you have not done it yet, please restart columnstore and try the insert statement again.

2) Execute the same insert with the LIMIT of 1000 rows

3) list the following directory and post output

ls -al /usr/local/mariadb/columnstore

4) post the log files for the date the insert error occurred, in the following directory

/var/log/mariadb/columnstore.

5) provide the output for the following command

df -kh

6) provide output of the "show create table tableName" for both innodb and ColumnStore tables.

7) if possible, provide 50 rows of data in the innodb table.

This is an open forum. If you prefer to send your data to me privately, you can send it to danie...@mariadb.com.

Thanks

Daniel Lee, QA Engineer

MariaDB Corporation

www.mariadb.com

philipp...@sacem.fr

unread,

Jun 27, 2016, 10:38:51 AM6/27/16

to MariaDB ColumnStore

Hi Daniel,

All my responses have been sent by mail.

Thanks for your help.

Regards,

Philippe

On Friday, June 24, 2016 at 5:35:01 PM UTC+2, Daniel Lee wrote:

Hello Philippe;

Please do few things for me:

1) If you have not done it yet, please restart columnstore and try the insert statement again.

2) Execute the same insert with the LIMIT of 1000 rows

3) list the following directory and post output
ls -al /usr/local/mariadb/columnstore

4) post the log files for the date the insert error occurred, in the following directory
/var/log/mariadb/columnstore.

5) provide the output for the following command
df -kh

6) provide output of the "show create table tableName" for both innodb and ColumnStore tables.

7) if possible, provide 50 rows of data in the innodb table.

This is an open forum. If you prefer to send your data to me privately, you can send it to .

Daniel Lee

unread,

Jun 27, 2016, 11:05:38 AM6/27/16

to MariaDB ColumnStore

Hello, Philippe;

I found this error in the err.log file:

Jun 27 16:19:25 tobyc cpimport.bin[9434]: 25.892026 |0|0|0| E 34 CAL0087: BulkLoad Error: Actual error row count(1) exceeds the max error rows(0) allowed for table shabi_app.ulysst_ligprog_cst

Jun 27 16:19:25 tobyc cpimport.bin[9434]: 25.892392 |0|0|0| E 34 CAL0087: BulkLoad Error: Bulkload Read (thread 0) Failed for Table shabi_app.ulysst_ligprog_cst. Terminating this job.

The error msg indicated that one of the rows has an error in it. The import job relating to the failed "insert...select..." statement is 3249. Can you check the /usr/local/mariadb/columnstore/data/bulk/log directory to see if there are log files for this job? There should be a .bad file that contains the bad row that caused the import to abort.

Daniel Lee, QA Engineer

MariaDB Corporation

www.mariadb.com

philipp...@sacem.fr

unread,

Jun 27, 2016, 11:46:22 AM6/27/16

to MariaDB ColumnStore

Hi Daniel

You can find the log file attached. I can't see no more errors.

Regards

Philippe

Job_3249.log

Daniel Lee

unread,

Jun 27, 2016, 11:51:30 AM6/27/16

to MariaDB ColumnStore

Hello, Philippe;

At the end of the Job_3249.log file, you can find the following:

2016-06-27 16:19:25 (9434) INFO : Number of rows with errors = 1.  Exact error rows are listed in file /usr/local/mariadb/columnstore/etc/ulysst_ligprog_cst.tbl.Job_3249_9434.bad
2016-06-27 16:19:25 (9434) ERR  : Actual error row count(1) exceeds the max error rows(0) allowed for table shabi_app.ulysst_ligprog_cst [1451]

Can you check the .bad file for the row that caused the command to abort.

Thanks

Daniel Lee, QA Engineer

MariaDB Corporation

www.mariadb.com

philipp...@sacem.fr

unread,

Jun 28, 2016, 8:46:07 AM6/28/16

to MariaDB ColumnStore

Hi Daniel,

This file /usr/local/mariadb/columnstore/etc/ulysst_ligprog_cst.tbl.Job_3249_9434.bad didn't have been generated. How is it possible ?

-sh-4.1$ ls -ltr /usr/local/mariadb/columnstore/etc/
total 260
-rw-r--r-- 1 root root   635 Jun 9 16:07 snmptrapd.conf.singleserver
-rw-r--r-- 1 root root 3985 Jun 9 16:07 snmpd.conf.singleserver
-rw-r--r-- 1 root root 6894 Jun 9 16:07 ProcessConfig.xml.singleserver
-rw-r--r-- 1 root root 18086 Jun 9 16:07 ConsoleCmds.xml
-rw-r--r-- 1 root root 18287 Jun 9 16:07 Calpont.xml.singleserver
-rw-r--r-- 1 root root 5593 Jun 9 16:07 MessageFile.txt
-rw-r--r-- 1 root root 14542 Jun 9 16:07 ErrorMessage.txt
-rw-r--r-- 1 root root 18417 Jun 16 14:06 Calpont.xml.installSave
-rw-r--r-- 1 root root 6339 Jun 16 14:07 ProcessConfig.xml.calpontSave
-rw-r--r-- 1 root root 6339 Jun 16 14:07 ProcessConfig.xml
-rw-r--r-- 1 root root   635 Jun 16 14:07 snmptrapd.conf
-rw-r--r-- 1 root root 3937 Jun 16 14:07 snmpd.conf
-rw-r--r-- 1 root root   191 Jun 24 15:33 +
-rw-rw-rw- 1 root root 18521 Jun 24 15:34 Calpont.xml.calpontSave
-rw-r--r-- 1 root root 18521 Jun 24 15:34 Calpont.xml
-rw-r--r-- 1 root root 18521 Jun 25 03:18 Calpont.xml-20160625
-rw-r--r-- 1 root root 18521 Jun 26 03:08 Calpont.xml-20160626
-rw-r--r-- 1 root root 18521 Jun 27 03:41 Calpont.xml-20160627
-rw-r--r-- 1 root root 18521 Jun 28 03:10 Calpont.xml-20160628
-rw-rw-rw- 1 root root 11660 Jun 28 14:43 AlarmConfig.xml