OnDemand User Group

Support Forums => MP Server => Topic started by: SV on December 06, 2019, 11:00:57 AM

Title: ArcDBP_SegSQL:Unable to exec direct sql db
Post by: SV on December 06, 2019, 11:00:57 AM
AIX CMOD stooped. Not starting. Trace shows these db errors. SQL ERROR code is not showing up in the log


39518276:258 12/06/2019 10:39:25:195243 ERROR arsseg.c(1132)ArcDBP_SegSQL:Unable to exec direct sql db hstmt=65538 db sql str=CREATE TABLE ccsuser.SL1685 ( time_stamp INTEGER NOT NULL, userid VARCHAR(128) NOT NULL, severity CHAR(1) NOT NULL, msg_num SMALLINT NOT NULL, msg_text VARCHAR(2000) NOT NULL, appl_id CHAR(1) NOT NULL, log_id INTEGER NOT NULL, account VARCHAR(60) NOT NULL, doc_name VARCHAR(11) NOT NULL, doc_off INTEGER NOT NULL, doc_len INTEGER NOT NULL, comp_off INTEGER NOT NULL, comp_len INTEGER NOT NULL, annot CHAR(1) FOR BIT DATA NOT NULL, comp_type CHAR(1) FOR BIT DATA NOT NULL, resource INTEGER NOT NULL, pri_nid SMALLINT NOT NULL, sec_nid SMALLINT NOT NULL , time_stamp_dt TIMESTAMP NOT NULL) IN USERSPACE1 sql=CREATE TABLE ccsuser.SL1685 ( time_stamp INTEGER NOT NULL, userid VARCHAR(128) NOT NULL, severity CHAR(1) NOT NULL, msg_num SMALLINT NOT NULL, msg_text VARCHAR(2000) NOT NULL, appl_id CHAR(1) NOT NULL, log_id INTEGER NOT NULL, account VARCHAR(60) NOT NULL, doc_name VARCHAR(11) NOT NULL, doc_off INTEGER NOT NULL, doc_len INTEGER NOT NULL, comp_off INTEGER NOT NULL, comp_len INTEGER NOT NULL, annot CHAR(1) FOR BIT DATA NOT NULL, comp_type CHAR(1) FOR BIT DATA NOT NULL, resource INTEGER NOT NULL, pri_nid SMALLINT NOT NULL, sec_nid SMALLINT NOT NULL , time_stamp_dt TIMESTAMP NOT NULL) IN USERSPACE1 db sql rc=-1,SQL_ERROR


I executed this sql in the above error and got this error
SQL0289N  Unable to allocate new pages in table space "USERSPACE1". 
SQLSTATE=57011
Title: Re: ArcDBP_SegSQL:Unable to exec direct sql db
Post by: jsquizz on December 06, 2019, 01:41:56 PM
Anything in db2diag?
Title: Re: ArcDBP_SegSQL:Unable to exec direct sql db
Post by: Justin Derrick on December 06, 2019, 01:58:06 PM
The database filesystem or tablespace container is full.  Contact the System Admins and/or database admins.

-JD.