Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Apr 11, 2016

Update SQLCMD and SQL JDBC plugin to enhance error handling

By the end of the DB deployment, our process demands a list of all such files that failed during execution. As with the current palettes ? RunSQLCmd and SQL JDBC, it is not possible to get the output of each file on some location, we are trying to pull a list of all failed scripts from the UDeploy logs. But we are facing some challenge ? The output in UDeploy log is such that the name of the failed script is not appearing next to this line: ?Failed to execute?. Instead, the entire script code that got failed gets written next to ?Failed to execute?. In such a case it is challenging for us to pull a list of files that failed.

This can probably be achieved through shell scripting, but we are trying to make use of as many palettes as possible other than shell scripting palette. Can you please suggest on this and check to see if the Udeploy log format for JDBC plugin could be changed so that we can get the failed file name right next to this line- ?Failed to execute?.

[sql] Executing resource: C:\ibm-ucd\XXX\var\work\DDL_DB_Deployment_Testing2\FirstScript.sql
[sql] Executing resource: C:\ibm-ucd\xxxxxxx\var\work\DDL_DB_Deployment_Testing2\SecondScript.sql
[sql] Executing resource: C:\ibm-ucd\xxxxx\var\work\DDL_DB_Deployment_Testing2\ThirdScript.sql
[sql] 1 of 3 SQL statements executed successfully
[sql] Failed to execute: use BondDeploy update bond_deplmj,hjkoy_log set project='Rock' where [db_name] ='DBREF001'
[sql] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ','.
[sql] Failed to execute: use BondDeploy update bond_deploy_log set project='Diamond' where [db_name] ='DBCAM001' dhfhyjuty select * from bond_deploy_log
[sql] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'dhfhyjuty'.

Idea priority Medium
RFE ID 86663
RFE URL
RFE Product UrbanCode Deploy
  • Admin
    Osman Burucu
    Reply
    |
    Jun 22, 2022

    Thank You for entering and providing information to this RFE. Due the age and changes in the products over time additional functionality was introduced which could help to adress this RFE, this RFE will be closed.

    Please provide a new RFE based on the latest versions if needed

  • Guest
    Reply
    |
    Apr 12, 2016

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development. The development team will look to adding highlighting to the output of the plugins.