[MCOL-1033] Internal error: CAL0009: (6)Create table failed due to Created: 2017-11-15  Updated: 2021-01-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: hiller1 Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

[root@um1 ~]# mcsmysql test -e "CREATE TABLE t2 (id int(11)) ENGINE=Columnstore; "
ERROR 1815 (HY000) at line 1: Internal error: CAL0009: (6)Create table failed due to WE: Error creating column file for oid 3317; The File does not exist.

[root@um1 ~]# mcsadmin getSystemInfo

WARNING: running on non Parent OAM Module, can't make configuration changes in this session.
Access Console from 'pm1' if you need to make changes.

getsysteminfo Wed Nov 15 15:55:23 2017

System columnstore-1

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System ACTIVE Wed Nov 15 15:42:03 2017

Module um1 ACTIVE Wed Nov 15 15:42:00 2017
Module pm1 ACTIVE Wed Nov 15 15:41:51 2017
Module pm2 ACTIVE Wed Nov 15 15:41:53 2017

Active Parent OAM Performance Module is 'pm1'
Local Query Feature is enabled
MariaDB ColumnStore Replication Feature is enabled

MariaDB ColumnStore Process statuses

Process Module Status Last Status Change Process ID
------------------ ------ --------------- ------------------------ ----------
ProcessMonitor um1 ACTIVE Wed Nov 15 15:41:16 2017 4513
ServerMonitor um1 ACTIVE Wed Nov 15 15:41:36 2017 4852
DBRMWorkerNode um1 ACTIVE Wed Nov 15 15:41:36 2017 4865
ExeMgr um1 ACTIVE Wed Nov 15 15:41:49 2017 6373
DDLProc um1 ACTIVE Wed Nov 15 15:41:57 2017 7146
DMLProc um1 ACTIVE Wed Nov 15 15:42:01 2017 7156
mysqld um1 ACTIVE Wed Nov 15 15:42:14 2017 7507

ProcessMonitor pm1 ACTIVE Wed Nov 15 15:41:08 2017 4142
ProcessManager pm1 ACTIVE Wed Nov 15 15:41:14 2017 4302
DBRMControllerNode pm1 ACTIVE Wed Nov 15 15:41:29 2017 5115
ServerMonitor pm1 ACTIVE Wed Nov 15 15:41:31 2017 5136
DBRMWorkerNode pm1 ACTIVE Wed Nov 15 15:41:31 2017 5176
DecomSvr pm1 ACTIVE Wed Nov 15 15:41:35 2017 5346
PrimProc pm1 ACTIVE Wed Nov 15 15:41:37 2017 5456
ExeMgr pm1 ACTIVE Wed Nov 15 15:41:48 2017 7607
WriteEngineServer pm1 ACTIVE Wed Nov 15 15:41:52 2017 7772
mysqld pm1 ACTIVE Wed Nov 15 15:42:26 2017 9133

ProcessMonitor pm2 ACTIVE Wed Nov 15 15:41:24 2017 4017
ProcessManager pm2 HOT_STANDBY Wed Nov 15 15:41:25 2017 4084
DBRMControllerNode pm2 COLD_STANDBY Wed Nov 15 15:41:37 2017
ServerMonitor pm2 ACTIVE Wed Nov 15 15:41:40 2017 4380
DBRMWorkerNode pm2 ACTIVE Wed Nov 15 15:41:40 2017 4393
DecomSvr pm2 ACTIVE Wed Nov 15 15:41:44 2017 4429
PrimProc pm2 ACTIVE Wed Nov 15 15:41:46 2017 4439
ExeMgr pm2 ACTIVE Wed Nov 15 15:41:50 2017 4573
WriteEngineServer pm2 ACTIVE Wed Nov 15 15:41:54 2017 4614
mysqld pm2 ACTIVE Wed Nov 15 15:42:32 2017 4995

Active Alarm Counts: Critical = 1, Major = 0, Minor = 0, Warning = 0, Info = 0
[root@um1 ~]#



 Comments   
Comment by hiller1 [ 2017-11-15 ]

MariaDB [test]> create table t1(id int)engine=columnstore;
ERROR 1815 (HY000): Internal error: Lost connection to DDLProc

Comment by David Hill (Inactive) [ 2017-11-15 ]

This looks like a symptom where the System Catalog wasnt created by postConfigure install at the end of its run. Could happen if postConfigure failed and then someone did a startsystem.

Try this to get the System Catalog created, run on pm1:
This is assuming a root install:

/usr/local/mariadb/columnstore/bin/dbbuilder 7

Run that, then try the create tables

Comment by David Thompson (Inactive) [ 2017-11-27 ]

hiller1 did that resolve the problem?

Comment by David Thompson (Inactive) [ 2017-12-14 ]

hiller1 can you confirm if this was the issue?

Comment by max chernyshov [ 2020-04-07 ]
  1. # /usr/local/mariadb/columnstore/bin/dbbuilder 7

Build system catalog was not completed. System catalog appears to exist. It will remain intact for reuse. The database is not recreated.

still same error
ERROR 1815 (HY000): Internal error: Lost connection to DDLProc

Comment by max chernyshov [ 2020-04-07 ]

what are the steps to restart every-thing for ColumnStore to ensure it is initialized correctly

Generated at Thu Feb 08 02:25:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.