[EVEREST_TYPE_NOT_SUPPORTED] Unknown Everest type for a null data dictionary column s

Frosty the Coder

Legendary Poster

I'm debugging an appl where a table-io UPDATE is failing.
I can see that the record exists and that the key to the UPDATE is correct.
I can update the record outside of this appl.

When running from the appl, I get this message in the JAS log, immed before the "update failed" message.

[EVEREST_TYPE_NOT_SUPPORTED] Unknown Everest type for a null data dictionary column specification.

I do not know whether this message is meaningful, or if it is related to the update failing,
but I can't think of anything else at this moment.

This message does NOT occur when an update is performed from a UBE.

Here's a snip from the JAS log when processing the update statement

20 Jul 2015 13:06:01,807 [APP ] GPIEKARSKI - [JAS]
JDBCProxy.jdbcProxy(): Operation is executed under an auto commit JDBj logical connection for
Usersession ID: 4649056188138272768 | UserName : GPIEKARSKI, Environment : DV910, User Role : *ALL

20 Jul 2015 13:06:01,807 [SEVERE] GPIEKARSKI - [JAS]
JDBCProxy.jdbcProxy(): JDBj database operation failed | UserName : GPIEKARSKI, Environment : DV910,
User Role : *ALL com.jdedwards.database.base.JDBException:
[EVEREST_TYPE_NOT_SUPPORTED] Unknown Everest type for a null data dictionary column specification.

20 Jul 2015 13:06:01,807 [APP ] GPIEKARSKI - [RUNTIME]
FQ60600.UPDATETABLE | TABLE | false | 1 | null | null
IN: JOBN | BC[JOBN_FQ60600_0] | MATH01 | GC[186] | PID | BC[USER_FQ60600_0] | UPMJ | BC[UPMJ_FQ60600_0] | UPMT | BC[UPMT_FQ60600_0] |
YQ60C1D | GC[21] | YQ60C1E | GC[22] | YQ60C1F | GC[23] | YQ60CA | GC[14] | YQ60CA1N | GC[57] | YQ60CAA | GC[44] | YQ60CAB | GC[45] | YQ60CAC | GC[46] |
YQ60CAD | GC[47] | YQ60CAE | GC[48] | YQ60CAF | GC[49] | YQ60CAG | GC[50] | YQ60CAH | GC[51] | YQ60CAI | GC[52] | YQ60CAJ | GC[53] | YQ60CAK | GC[54] |
YQ60CAL | GC[55] | YQ60CAM | GC[56] | YQ60CAO | GC[58] | YQ60CAP | GC[59] | YQ60CAQ | GC[60] | YQ60CAR | GC[61] | YQ60CAS | GC[62] | YQ60CAT | GC[63] |
YQ60CAU | GC[64] | YQ60CAV | GC[65] | YQ60CAW | GC[66] | YQ60CAX | GC[67] | YQ60CAY | GC[68] | YQ60CAZ | GC[69] | YQ60CB | GC[15] | YQ60CB1 | GC[448] |
YQ60CB1D | GC[73] | YQ60CB2 | GC[449] | YQ60CB3 | GC[450] | YQ60CBA | GC[70] | YQ60CBB | GC[71] | YQ60CBC | GC[72] | YQ60CBE | GC[74] | YQ60CBF | GC[75] |
YQ60CBG | GC[76] | YQ60CBH | GC[77] | YQ60CBI | GC[78] | YQ60CBJ | GC[79] | YQ60CBK | GC[80] | YQ60CBL | GC[81] | YQ60CBM | GC[82] | YQ60CBN | GC[83] |
YQ60CBO | GC[84] | YQ60CBP | GC[85] | YQ60CBQ | GC[86] | YQ60CBR | GC[87] | YQ60CBS | GC[88] | YQ60CBT | GC[89] | YQ60CBU | GC[90] | YQ60CBV | GC[91] |
YQ60CBW | GC[92] | YQ60CBX | GC[93] | YQ60CBY | GC[94] | YQ60CBZ | GC[95] | YQ60CC | GC[16] | YQ60CG | GC[24] | YQ60CH | GC[25] | YQ60CI | GC[26] |
YQ60CJ | GC[27] | YQ60CK | GC[28] | YQ60CL | GC[29] | YQ60CM | GC[30] | YQ60CO | GC[32] | YQ60CP | GC[33] | YQ60CQ | GC[34] | YQ60CR | GC[35] |
YQ60CS | GC[36] | YQ60CT | GC[37] | YQ60CU | GC[38] | YQ60CV | GC[39] | YQ60CW | GC[40] | YQ60CX | GC[41] | YQ60CY | GC[42] | YQ60CZ | GC[43] |
YQ60SPN | FC[96] | YQ60SPNV | FC[98]
FILTER: MATH01 | = | YQ60SPN | = | YQ60SPNV | =
Last edited:
The BSVW that this grid is based on, had three new DD items added to it.
When I try to use any of those three columns, from the BSVW, on the grid, I get the following JAS error.

"JAS_MSG346: JAS Database failure: [SPEC NOT FOUND] Unable to find OneWorld specification for YQ60CB1".

YQ60CB1 just happens to be one of the three new DD items.
I'm guessing that this DD item, and the other two, in some way, shape, or form, are "incomplete".

Now, being a developer who does NOT think I understand CNC, can someone more learned than I am
PLEASE explain what the JAS error means as far as the DD item's spec "not being found".
Try an update package that includes the table with the "missing" DD items. The problem is probably that the new DD items are not in serialized objects. You could also do a web gen on the table pointing to the serialized objects in central objects.

I'm assuming all this is happening on the web server and is fine on the developer workstation?

Last edited:

Your assumption is incorrect, this is happening on the full client that I'm developing from
AS WELL AS on the web servers where I noticed the update wasn't working.

How do I prove/disprove whether the DD item(s) are in serialized objects?
Will CNC understand if I request "a web gen on the table pointing at serialized objects in central objects"?

I did notice that the three DD items had "UDC browse" for their "visual assist" but nothing for "edit rule".
I've removed the visual assist from the DD items.
If it's failing locally, then it probably is something messed up with the DD. How does UTB or Object Browser behave when you try to view the table or view?
Useless Table Browser, Databrowser and Object Browser all show the table fine,
with the exception of the three new columns not being populated.
Using UTB or object browser removes any web specific issues. Hopefully you will find something in the JDE.LOG generated by UTB or Object Browser. What is the data type of these columns? (By that I mean what is the number you see in the Data Type field in the DD app)


The data type, for these three fields, has a value of "2" (string).
Each is 40 characters long.

When I execute a table-IO update, from an APPL, where I don't reference those three fields,
the update works.

When I add them back into the update statement, I get back to the original message of
"[EVEREST_TYPE_NOT_SUPPORTED] Unknown Everest type for a null data dictionary column specification."

Table-IO update from a UBE, works when I have those three fields specified.

I would LOVE to understand why this is failing, and how to correct it,
even though it will be meaningless (in this case), as I've been instructed to code a "workaround".
(Oracle KG suggests serialization and bouncing servers.)

Oh well.
Do a SQL select (i.e using a SQL tool, not E1) on F9200 and F9210 for those 3 dd items and check for weird characters (like tabs or carriage returns) in the displayed data. You may have to delete and recreate these 3 dd items.