We have been monitoring our Oracle databases using Monitor, but after the upgrade to 2025.0, we are not getting any metric data. I verified that our DB is above 19.3. Checking the logs and I get the following error for the SQL that gets geodatabase datasets:
NJS-100: national character set id 871 is not supported by node-oracledb in Thin mode
Solved! Go to Solution.
The error you are referencing was submitted as a defect.
However, after further investigation, there is going to be an additional requirement at 2025 to gather metrics for Oracle. This is the requirement to configure extproc on the database.
This is due to the new functionality at 2025 of gathering inventory on datasets inside the geodatabase. Our documentation will be update.
Hi @Justin_Greco ,
Are you seeing the following error in your inventory observer:
WITH UNFILTERED_TABLES AS ( SELECT GI.PHYSICALNAME AS "table_name", CASE WHEN GI.DEFINITION IS NULL THEN 'other' WHEN XMLQUERY('/*/ShapeType' PASSING XMLTYPE(GI.DEFINITION) RETURNING CONTENT) IS NULL THEN NULL WHEN INSTR(LOWER(XMLQUERY('/*/ShapeType/text()' PASSING XMLTYPE(GI.DEFINITION) RETURNING CONTENT)), 'point') > 0 THEN 'point' WHEN INSTR(LOWER(XMLQUERY('/*/ShapeType/text()' PASSING XMLTYPE(GI.DEFINITION) RETURNING CONTENT)), 'line') > 0 THEN 'line' WHEN INSTR(LOWER(XMLQUERY('/*/ShapeType/text()' PASSING XMLTYPE(GI.DEFINITION) RETURNING CONTENT)), 'polygon') > 0 THEN 'polygon' ELSE 'other' END AS "geometry_type", CASE WHEN BITAND(TR.OBJECT_FLAGS, POWER(2, 3)) <> 0 THEN 'traditional' WHEN BITAND(TR.OBJECT_FLAGS, POWER(2, 25)) <> 0 THEN 'branched' ELSE NULL END AS "versioned_type", CASE WHEN BITAND(TR.OBJECT_FLAGS, POWER(2, 3)) = 0 AND BITAND(TR.OBJECT_FLAGS, POWER(2, 18)) <> 0 THEN 1 ELSE 0 END AS "is_archived" FROM TABLE_REGISTRY TR LEFT JOIN GDB_ITEMS_VW GI ON TR.OWNER || '.' || TR.TABLE_NAME = GI.PHYSICALNAME ) SELECT * FROM UNFILTERED_TABLES WHERE "geometry_type" IS NULL OR "geometry_type" <> 'other' ORDER BY "table_name" ASC - ORA-31011: XML parsing failed ORA-19213: error occurred in XML processing at lines 1 LPX-00245: extra data after end of document ORA-06512: at "SYS.XMLTYPE", line 272 ORA-06512: at line 1
The error you are referencing was submitted as a defect.
However, after further investigation, there is going to be an additional requirement at 2025 to gather metrics for Oracle. This is the requirement to configure extproc on the database.
This is due to the new functionality at 2025 of gathering inventory on datasets inside the geodatabase. Our documentation will be update.
Hello
In our customer's environement same SQL ended with ORA-00942 table or view does not exists (not with ORA-31011). Problem in our case was not st_shapelib configuration, but it was that above mentioned SQL references GDB_ITEMS_VW and not SDE.GDB_ITEMS_VW. We created synonym for that view and then it started to work.