dbschema -d noaa -t ds_fqu
A user running 'dbschema -d noaa -t ds_fqu' on IDS 9.40.UC1 got error -208 (memory allocation failed during query processing), even though normal dbaccess queries worked and the machine wasn't short of memory. Art Kagel suggested the cause was DBSPACETEMP listing only temp dbspaces: dbschema uses logged temp tables, which can't live in temp dbspaces and instead fall back to rootdbs, so he advised adding a normal dbspace to DBSPACETEMP and checking/unsetting PSORT_DBTEMP and PSORT_NPROCS. The user reported the command worked after bouncing the engine, without identifying why, so the root cause was never confirmed.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
When I run ,
dbschema -d noaa -t ds_fqu,
It returned,
BSCHEMA Schema Utility INFORMIX-SQL Version 9.40.UC1
Copyright (C) Informix Software, Inc., 1984-1997
Software Serial Number AAA#B000000
-208 - Memory allocation failed during query processing.
But I can do query in dbaccess with no problem.
I do not have memmory problem and I was the only user using the db.
Thanks,
Frank
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696
Do you have DBSPACETEMP set in this environment? Does it include both temp
dbspaces and normal dbspaces? If it's not set or contains only temp dbspaces
that may be the problem, especially if your ROOTDB dbspace is rather small or
has little free space. Try adding another normal dbspace with lots of free
space to the DBSPACETEMP and see what happens.
Art S. Kagel
----- Original Message -----
From: Yunyao (Fra.... <ids@iiug.org>
At: 5/30 14:50:53
When I run ,
dbschema -d noaa -t ds_fqu,
It returned,
BSCHEMA Schema Utility INFORMIX-SQL Version 9.40.UC1
Copyright (C) Informix Software, Inc., 1984-1997
Software Serial Number AAA#B000000
-208 - Memory allocation failed during query processing.
But I can do query in dbaccess with no problem.
I do not have memmory problem and I was the only user using the db.
Thanks,
Frank
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
My DBSPACETEMP:
DBSPACETEMP dbtemp03:dbtemp01:dbtemp02 # Default temp dbspaces
looks I have lot free space, see below,
Thanks,
Informix Dynamic Server Version 9.40.UC1 -- On-Line -- Up 4 days
03:47:41 -- 463536 Kbytes
Dbspaces
address number flags fchunk nchunks flags owner name
6010d7d8 1 0x1 1 1 N informix dbroot
608f2198 2 0x1 2 1 N informix dbphylog
608f22e8 3 0x1 3 3 N informix dblog
608f2438 4 0x1 4 2 N informix dbdata00
608f2588 5 0x2001 5 1 N T informix dbtemp01
608f26d8 6 0x2001 6 1 N T informix dbtemp02
608f2828 7 0x2001 7 1 N T informix dbtemp03
608f2978 8 0x8001 8 1 N S informix
er_sbdbspace
608f2ac8 9 0x1 9 1 N informix
er_txdbspace
608f2c18 10 0x1 10 1 N informix testdbs
608f2d68 11 0x1 11 1 N informix dbdata01
608f2eb8 12 0x1 12 2 N informix dbdata02
608f4018 13 0x1 13 1 N informix dbdata03
608f4168 14 0x1 14 1 N informix dbdata04
608f42b8 15 0x1 19 1 N informix dbdata05
15 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages flags
pathname
6010d928 1 1 0 50000 48444 PO--
/usr/informix/dev-links/DBROOT_REP1
6010dc68 2 2 1 32000 11947 PO--
/usr/informix/dev-links/DBPHYLOG_REP1
6010dde8 3 3 1 50000 2447 PO--
/usr/informix/dev-links/DBLOG_REP1
60237830 4 4 1 200000 5 PO--
/usr/informix/dev-links/DBDATA_DB_REP1
602379b0 5 5 1 40000 39947 PO--
/usr/informix/dev-links/DBTEMP1_REP1
60237b30 6 6 1 40000 39947 PO--
/usr/informix/dev-links/DBTEMP2_REP1
60237cb0 7 7 1 40000 39947 PO--
/usr/informix/dev-links/DBTEMP3_REP1
60237e30 8 8 1 40000 37284 37284 POS-
/usr/informix/dev-links/DBDATA_ERSB_REP1
Metadata 2663 1716 2663
608f1018 9 9 1 40000 32243 PO--
/usr/informix/dev-links/DBDATA_ERTX_REP1
608f1198 10 10 1 256 203 PO--
/dbbackup/dblinks-temp/testlk
608f1318 11 11 1 50000 7055 PO--
/dbbackup/dblinks-temp/dbdata01_rep1
608f1498 12 12 1 50000 0 PO--
/dbbackup/dblinks-temp/dbdata02_rep1
608f1618 13 13 1 75000 70955 PO--
/dbbackup/dblinks-temp/dbdata03_rep1
608f1798 14 14 1 75000 7731 PO--
/dbbackup/dblinks-temp/dbdata04_rep1
608f1918 15 3 1 50000 1247 PO--
/dbbackup/dblinks-temp/dblog_rep1
608f1a98 16 3 1 25000 3747 PO--
/dbbackup/dblinks-temp/dblog_rep2
608f1c18 17 4 1 100000 14749 PO--
/dbbackup/dblinks-temp/dbdata1_rep1
608f1d98 18 12 1 50000 33869 PO--
/dbbackup/dblinks-temp/dbdata022_rep1
608f2018 19 15 1 50000 26267 PO--
/dbbackup/dblinks-temp/dbdata05_rep1
19 active, 2047 maximum
ART KAGEL, .... wrote:
>Do you have DBSPACETEMP set in this environment? Does it include both temp
>dbspaces and normal dbspaces? If it's not set or contains only temp dbspaces
>that may be the problem, especially if your ROOTDB dbspace is rather small or
>has little free space. Try adding another normal dbspace with lots of free
>space to the DBSPACETEMP and see what happens.
>
>Art S. Kagel
>----- Original Message -----
>From: Yunyao (Fra.... <ids@iiug.org>
>At: 5/30 14:50:53
>
>When I run ,
>
>dbschema -d noaa -t ds_fqu,>
>It returned,
>
>BSCHEMA Schema Utility INFORMIX-SQL Version 9.40.UC1
>Copyright (C) Informix Software, Inc., 1984-1997
>Software Serial Number AAA#B000000
>-208 - Memory allocation failed during query processing.
>
>But I can do query in dbaccess with no problem.
>
>I do not have memmory problem and I was the only user using the db.
>
>Thanks,
>Frank
>
>
>
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696
Yes, but they are ALL temp dbspaces. IDS cannot use temp dbspaces for logged
temp tables. Logged temp tables, which dbschema uses to gsther object
information, must be placed into 'normal' dbspaces. If no normal dbspaces are
listed in DBSPACETEMP then rootdbs is used. Try adding one of the other
dbspaces, like dbdata00 and see what happens. Also, I forgot, look to see if
the PSORT_ parameters are set in the environment (PSORT_DBTEMP and
PSORT_NPROCS)
if so make sure that the filesystems listed in PSORT_DBTEMP have enough free
space for a full copy of any sort data dbschema may be trying to create. If
you're not certain then unset these and see what happens then.
Art S. Kagel
----- Original Message -----
From: Yunyao (Fra.... <ids@iiug.org>
At: 5/30 15:06:23
My DBSPACETEMP:
DBSPACETEMP dbtemp03:dbtemp01:dbtemp02 # Default temp dbspaces
looks I have lot free space, see below,
Thanks,
Informix Dynamic Server Version 9.40.UC1 -- On-Line -- Up 4 days
03:47:41 -- 463536 Kbytes
Dbspaces
address number flags fchunk nchunks flags owner name
6010d7d8 1 0x1 1 1 N informix dbroot
608f2198 2 0x1 2 1 N informix dbphylog
608f22e8 3 0x1 3 3 N informix dblog
608f2438 4 0x1 4 2 N informix dbdata00
608f2588 5 0x2001 5 1 N T informix dbtemp01
608f26d8 6 0x2001 6 1 N T informix dbtemp02
608f2828 7 0x2001 7 1 N T informix dbtemp03
608f2978 8 0x8001 8 1 N S informix
er_sbdbspace
608f2ac8 9 0x1 9 1 N informix
er_txdbspace
608f2c18 10 0x1 10 1 N informix testdbs
608f2d68 11 0x1 11 1 N informix dbdata01
608f2eb8 12 0x1 12 2 N informix dbdata02
608f4018 13 0x1 13 1 N informix dbdata03
608f4168 14 0x1 14 1 N informix dbdata04
608f42b8 15 0x1 19 1 N informix dbdata05
15 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages flags
pathname
6010d928 1 1 0 50000 48444 PO--
/usr/informix/dev-links/DBROOT_REP1
6010dc68 2 2 1 32000 11947 PO--
/usr/informix/dev-links/DBPHYLOG_REP1
6010dde8 3 3 1 50000 2447 PO--
/usr/informix/dev-links/DBLOG_REP1
60237830 4 4 1 200000 5 PO--
/usr/informix/dev-links/DBDATA_DB_REP1
602379b0 5 5 1 40000 39947 PO--
/usr/informix/dev-links/DBTEMP1_REP1
60237b30 6 6 1 40000 39947 PO--
/usr/informix/dev-links/DBTEMP2_REP1
60237cb0 7 7 1 40000 39947 PO--
/usr/informix/dev-links/DBTEMP3_REP1
60237e30 8 8 1 40000 37284 37284 POS-
/usr/informix/dev-links/DBDATA_ERSB_REP1
Metadata 2663 1716 2663
608f1018 9 9 1 40000 32243 PO--
/usr/informix/dev-links/DBDATA_ERTX_REP1
608f1198 10 10 1 256 203 PO--
/dbbackup/dblinks-temp/testlk
608f1318 11 11 1 50000 7055 PO--
/dbbackup/dblinks-temp/dbdata01_rep1
608f1498 12 12 1 50000 0 PO--
/dbbackup/dblinks-temp/dbdata02_rep1
608f1618 13 13 1 75000 70955 PO--
/dbbackup/dblinks-temp/dbdata03_rep1
608f1798 14 14 1 75000 7731 PO--
/dbbackup/dblinks-temp/dbdata04_rep1
608f1918 15 3 1 50000 1247 PO--
/dbbackup/dblinks-temp/dblog_rep1
608f1a98 16 3 1 25000 3747 PO--
/dbbackup/dblinks-temp/dblog_rep2
608f1c18 17 4 1 100000 14749 PO--
/dbbackup/dblinks-temp/dbdata1_rep1
608f1d98 18 12 1 50000 33869 PO--
/dbbackup/dblinks-temp/dbdata022_rep1
608f2018 19 15 1 50000 26267 PO--
/dbbackup/dblinks-temp/dbdata05_rep1
19 active, 2047 maximum
ART KAGEL, .... wrote:
>Do you have DBSPACETEMP set in this environment? Does it include both temp
>dbspaces and normal dbspaces? If it's not set or contains only temp dbspaces
>that may be the problem, especially if your ROOTDB dbspace is rather small or
>has little free space. Try adding another normal dbspace with lots of free
>space to the DBSPACETEMP and see what happens.
>
>Art S. Kagel
>----- Original Message -----
>From: Yunyao (Fra.... <ids@iiug.org>
>At: 5/30 14:50:53
>
>When I run ,
>
>dbschema -d noaa -t ds_fqu,>
>It returned,
>
>BSCHEMA Schema Utility INFORMIX-SQL Version 9.40.UC1
>Copyright (C) Informix Software, Inc., 1984-1997
>Software Serial Number AAA#B000000
>-208 - Memory allocation failed during query processing.
>
>But I can do query in dbaccess with no problem.
>
>I do not have memmory problem and I was the only user using the db.
>
>Thanks,
>Frank
>
>
>
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I can do , dbschema -d noaa -t ds_fqu
after I bounced the engine.
DO not know why.
Thanks,
Frank
Yunyao (Fra.... wrote:
>My DBSPACETEMP:
>
>DBSPACETEMP dbtemp03:dbtemp01:dbtemp02 # Default temp dbspaces
>
>looks I have lot free space, see below,
>Thanks,
>
>Informix Dynamic Server Version 9.40.UC1 -- On-Line -- Up 4 days
>03:47:41 -- 463536 Kbytes
>
>Dbspaces
>address number flags fchunk nchunks flags owner name
>6010d7d8 1 0x1 1 1 N informix dbroot
>608f2198 2 0x1 2 1 N informix dbphylog
>608f22e8 3 0x1 3 3 N informix dblog
>608f2438 4 0x1 4 2 N informix dbdata00
>608f2588 5 0x2001 5 1 N T informix dbtemp01
>608f26d8 6 0x2001 6 1 N T informix dbtemp02
>608f2828 7 0x2001 7 1 N T informix dbtemp03
>608f2978 8 0x8001 8 1 N S informix
>er_sbdbspace
>608f2ac8 9 0x1 9 1 N informix
>er_txdbspace
>608f2c18 10 0x1 10 1 N informix testdbs
>608f2d68 11 0x1 11 1 N informix dbdata01
>608f2eb8 12 0x1 12 2 N informix dbdata02
>608f4018 13 0x1 13 1 N informix dbdata03
>608f4168 14 0x1 14 1 N informix dbdata04
>608f42b8 15 0x1 19 1 N informix dbdata05
>15 active, 2047 maximum
>
>Chunks
>address chunk/dbs offset size free bpages flags
>pathname
>6010d928 1 1 0 50000 48444 PO--
>/usr/informix/dev-links/DBROOT_REP1
>6010dc68 2 2 1 32000 11947 PO--
>/usr/informix/dev-links/DBPHYLOG_REP1
>6010dde8 3 3 1 50000 2447 PO--
>/usr/informix/dev-links/DBLOG_REP1
>60237830 4 4 1 200000 5 PO--
>/usr/informix/dev-links/DBDATA_DB_REP1
>602379b0 5 5 1 40000 39947 PO--
>/usr/informix/dev-links/DBTEMP1_REP1
>60237b30 6 6 1 40000 39947 PO--
>/usr/informix/dev-links/DBTEMP2_REP1
>60237cb0 7 7 1 40000 39947 PO--
>/usr/informix/dev-links/DBTEMP3_REP1
>60237e30 8 8 1 40000 37284 37284 POS-
>/usr/informix/dev-links/DBDATA_ERSB_REP1
>
>Metadata 2663 1716 2663
>608f1018 9 9 1 40000 32243 PO--
>/usr/informix/dev-links/DBDATA_ERTX_REP1
>608f1198 10 10 1 256 203 PO--
>/dbbackup/dblinks-temp/testlk
>608f1318 11 11 1 50000 7055 PO--
>/dbbackup/dblinks-temp/dbdata01_rep1
>608f1498 12 12 1 50000 0 PO--
>/dbbackup/dblinks-temp/dbdata02_rep1
>608f1618 13 13 1 75000 70955 PO--
>/dbbackup/dblinks-temp/dbdata03_rep1
>608f1798 14 14 1 75000 7731 PO--
>/dbbackup/dblinks-temp/dbdata04_rep1
>608f1918 15 3 1 50000 1247 PO--
>/dbbackup/dblinks-temp/dblog_rep1
>608f1a98 16 3 1 25000 3747 PO--
>/dbbackup/dblinks-temp/dblog_rep2
>608f1c18 17 4 1 100000 14749 PO--
>/dbbackup/dblinks-temp/dbdata1_rep1
>608f1d98 18 12 1 50000 33869 PO--
>/dbbackup/dblinks-temp/dbdata022_rep1
>608f2018 19 15 1 50000 26267 PO--
>/dbbackup/dblinks-temp/dbdata05_rep1
>19 active, 2047 maximum
>
>ART KAGEL, .... wrote:
>
>
>
>>Do you have DBSPACETEMP set in this environment? Does it include both temp
>>dbspaces and normal dbspaces? If it's not set or contains only temp dbspaces
>>that may be the problem, especially if your ROOTDB dbspace is rather small or
>>has little free space. Try adding another normal dbspace with lots of free
>>space to the DBSPACETEMP and see what happens.
>>
>>Art S. Kagel
>>----- Original Message -----
>>From: Yunyao (Fra.... <ids@iiug.org>
>>At: 5/30 14:50:53
>>
>>When I run ,
>>
>>dbschema -d noaa -t ds_fqu,>>
>>It returned,
>>
>>BSCHEMA Schema Utility INFORMIX-SQL Version 9.40.UC1
>>Copyright (C) Informix Software, Inc., 1984-1997
>>Software Serial Number AAA#B000000
>>-208 - Memory allocation failed during query processing.
>>
>>But I can do query in dbaccess with no problem.
>>
>>I do not have memmory problem and I was the only user using the db.
>>
>>Thanks,
>>Frank
>>
>>
>>
>>
>>
>
>
>
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696
Thank you, Art! Frank
ART KAGEL, .... wrote:
>Yes, but they are ALL temp dbspaces. IDS cannot use temp dbspaces for logged
>temp tables. Logged temp tables, which dbschema uses to gsther object
>information, must be placed into 'normal' dbspaces. If no normal dbspaces are
>listed in DBSPACETEMP then rootdbs is used. Try adding one of the other
>dbspaces, like dbdata00 and see what happens. Also, I forgot, look to see if
>the PSORT_ parameters are set in the environment (PSORT_DBTEMP and
>PSORT_NPROCS)
>if so make sure that the filesystems listed in PSORT_DBTEMP have enough free
>space for a full copy of any sort data dbschema may be trying to create. If
>you're not certain then unset these and see what happens then.
>
>Art S. Kagel
>
>----- Original Message -----
>From: Yunyao (Fra.... <ids@iiug.org>
>At: 5/30 15:06:23
>
>My DBSPACETEMP:
>
>DBSPACETEMP dbtemp03:dbtemp01:dbtemp02 # Default temp dbspaces
>
>looks I have lot free space, see below,
>Thanks,
>
>Informix Dynamic Server Version 9.40.UC1 -- On-Line -- Up 4 days
>03:47:41 -- 463536 Kbytes
>
>Dbspaces
>address number flags fchunk nchunks flags owner name
>6010d7d8 1 0x1 1 1 N informix dbroot
>608f2198 2 0x1 2 1 N informix dbphylog
>608f22e8 3 0x1 3 3 N informix dblog
>608f2438 4 0x1 4 2 N informix dbdata00
>608f2588 5 0x2001 5 1 N T informix dbtemp01
>608f26d8 6 0x2001 6 1 N T informix dbtemp02
>608f2828 7 0x2001 7 1 N T informix dbtemp03
>608f2978 8 0x8001 8 1 N S informix
>er_sbdbspace
>608f2ac8 9 0x1 9 1 N informix
>er_txdbspace
>608f2c18 10 0x1 10 1 N informix testdbs
>608f2d68 11 0x1 11 1 N informix dbdata01
>608f2eb8 12 0x1 12 2 N informix dbdata02
>608f4018 13 0x1 13 1 N informix dbdata03
>608f4168 14 0x1 14 1 N informix dbdata04
>608f42b8 15 0x1 19 1 N informix dbdata05
>15 active, 2047 maximum
>
>Chunks
>address chunk/dbs offset size free bpages flags
>pathname
>6010d928 1 1 0 50000 48444 PO--
>/usr/informix/dev-links/DBROOT_REP1
>6010dc68 2 2 1 32000 11947 PO--
>/usr/informix/dev-links/DBPHYLOG_REP1
>6010dde8 3 3 1 50000 2447 PO--
>/usr/informix/dev-links/DBLOG_REP1
>60237830 4 4 1 200000 5 PO--
>/usr/informix/dev-links/DBDATA_DB_REP1
>602379b0 5 5 1 40000 39947 PO--
>/usr/informix/dev-links/DBTEMP1_REP1
>60237b30 6 6 1 40000 39947 PO--
>/usr/informix/dev-links/DBTEMP2_REP1
>60237cb0 7 7 1 40000 39947 PO--
>/usr/informix/dev-links/DBTEMP3_REP1
>60237e30 8 8 1 40000 37284 37284 POS-
>/usr/informix/dev-links/DBDATA_ERSB_REP1
>
>Metadata 2663 1716 2663
>608f1018 9 9 1 40000 32243 PO--
>/usr/informix/dev-links/DBDATA_ERTX_REP1
>608f1198 10 10 1 256 203 PO--
>/dbbackup/dblinks-temp/testlk
>608f1318 11 11 1 50000 7055 PO--
>/dbbackup/dblinks-temp/dbdata01_rep1
>608f1498 12 12 1 50000 0 PO--
>/dbbackup/dblinks-temp/dbdata02_rep1
>608f1618 13 13 1 75000 70955 PO--
>/dbbackup/dblinks-temp/dbdata03_rep1
>608f1798 14 14 1 75000 7731 PO--
>/dbbackup/dblinks-temp/dbdata04_rep1
>608f1918 15 3 1 50000 1247 PO--
>/dbbackup/dblinks-temp/dblog_rep1
>608f1a98 16 3 1 25000 3747 PO--
>/dbbackup/dblinks-temp/dblog_rep2
>608f1c18 17 4 1 100000 14749 PO--
>/dbbackup/dblinks-temp/dbdata1_rep1
>608f1d98 18 12 1 50000 33869 PO--
>/dbbackup/dblinks-temp/dbdata022_rep1
>608f2018 19 15 1 50000 26267 PO--
>/dbbackup/dblinks-temp/dbdata05_rep1
>19 active, 2047 maximum
>
>ART KAGEL, .... wrote:
>
>
>
>>Do you have DBSPACETEMP set in this environment? Does it include both temp
>>dbspaces and normal dbspaces? If it's not set or contains only temp dbspaces
>>that may be the problem, especially if your ROOTDB dbspace is rather small or
>>has little free space. Try adding another normal dbspace with lots of free
>>space to the DBSPACETEMP and see what happens.
>>
>>Art S. Kagel
>>----- Original Message -----
>>From: Yunyao (Fra.... <ids@iiug.org>
>>At: 5/30 14:50:53
>>
>>When I run ,
>>
>>dbschema -d noaa -t ds_fqu,>>
>>It returned,
>>
>>BSCHEMA Schema Utility INFORMIX-SQL Version 9.40.UC1
>>Copyright (C) Informix Software, Inc., 1984-1997
>>Software Serial Number AAA#B000000
>>-208 - Memory allocation failed during query processing.
>>
>>But I can do query in dbaccess with no problem.
>>
>>I do not have memmory problem and I was the only user using the db.
>>
>>Thanks,
>>Frank
>>
>>
>>
>>
>>
>
>
>
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696