This content is now out of date.

Visit Our Community

Secondary DS is not getting deleted

Hi Team,

We are using currently YF build 20140827.

What we have observed that if the datasource (DS) connection has secondary pool enabled and in future if we want to drop/delete the DS connection the DS still doesn't get deleted completely from back end.

In the Meta data when we checked we got to know there are primary and secondary pool connection for same data source. When a user deletes DS connection from UI only the primary data source connection gets deleted .Due to this when a user tries to create a free hand SQL report the older DS still shows up. This is because secondary pool connection is not got deleted.

This could be a serious issue because every DS is bound to a client�s data. If a user has accidentally imported wrong DS and deletes from UI , they might not know that it�s not been deleted completely. For the end user who creates free hand SQL reports this DS connection will still appear.

We observed that if in DS connection secondary pool is disabled and then deleted, this issue would not appear. However this shouldn't work this way. If DS connection is deleted why still secondary DS should exists?

Please look into this issue on high importance as we had faced lot of trouble due to this

Hello Mala,

Thanks for your post. Indeed the issue you've described is problematic, to say the least. I have replicated your issue in YF 7.1 build 20140827, have lodged a Product Defect # 174695, and will bring the issue to the attention of the Development team.

Apologies for any inconvenience this issue has caused, please let me know if you need further information or assistance.

Kind Regards,

Hi Team,

Could you please provide ETA for the Above Task ID.


Thank you for your inquiry.

Unfortunately it doesn't appear that this task
has been addressed by our Dev team yet.

I have gone ahead and updated the task to
HIGH priority and also will send a note to our
Senior Support staff to see if they can provide
you with a better idea of when this task will
be fixed.

Thank you for your patience.


Hi Mala,

Thanks for your patience on this issue.
The task is allocated with the development team, though doesn't look like it can make it into the January release.
We're aiming for Feb.

In the meantime, you will need to remove the secondary data source from the database manually.
Just email with reference to this post and we can provide more information on how this can be done.

Apologies again for the inconvenience this has caused.