Work Order in Model Management Tool with a Large Number of Maps Causes SQL Error In Weblogic Log

(Doc ID 2322276.1)

Last updated on OCTOBER 27, 2017

Applies to:

Oracle Utilities Network Management System - Version 1.12.0.3 to 2.3.0.0.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 to 2.3.0.0.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.

Symptoms

Model Management tool sql error being reported in weblogic log

A work order was created with 200 maps. Subsequent to this, weblogic log file reports sql error: ERROR: ORA-01489: result of string concatenation is too long. This is generated from population/refresh of the bottom panel in Model Management tool. When this mega work order with about 200 map caused the bottom panel to go blank – you just had to move the “From” date on that bottom panel to be after that patch and it started working again.The query in question appears to be embedded in the Java code and the issue is the concatenation done with the use of SYS_CONNECT_BY_PATH...as 200 maps in the workorder will obviously lead to a filename size greater than the permitted VARCHAR2(4000).

Additionally, when a patch is rebuilt from the lower panel that has a directory, the directory remains after the build completes.

ERROR

2017-10-10 10:11:58,916 WARN session.Session:309 - nms-security or SQL problem: user:nms1 sql: SELECT patch, description, creation, deletion, verified, applied, committed, active, local_edit, commit_start, notified, build_type, error_state, undo_patch, work_order, workorder_status, edit_user, SUBSTR(MAX(REPLACE(SYS_CONNECT_BY_PATH(filename, '|') , '|',', ')),2) IMPORT_FILES FROM ( SELECT p.*, pi.filename, row_number() OVER (PARTITION BY pi.patch ORDER BY pi.patch) ROW# FROM patch_imports pi, patches p WHERE pi.patch = p.patch AND CREATION >= to_date('2017-10-09 10:11:58','YYYY-MM-DD HH24:MI:SS') AND CREATION <= to_date('2017-10-11 10:11:58','YYYY-MM-DD HH24:MI:SS') ) START WITH ROW#=1 CONNECT BY PRIOR patch=patch AND PRIOR row# = row# -1 GROUP BY patch, description, creation, deletion, verified, applied, committed, active, local_edit, commit_start, notified, build_type, error_state, undo_patch, work_order, workorder_status, edit_user

java.sql.SQLException: ORA-01489: result of string concatenation is too long

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms