This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Print session info for long transaction in msg log or DUMPDIR
I searched to see if anyone had opened up a RFE for the below and did not find one, if there is one then please disregard.
One of our customers has now hardened down security to such a degree that I can no longer connect to the server in which Informix resides to troubleshoot DBA related problems in an expedient manner . (I am also sure other DBA' s are starting to encounter the same challenges.)
One problem that does crop up (infrequently) is long transaction rollback(s) . During such an event the trx id (onstat -x) is posted to the online msg log and that's all I have to go on since by the time I do manage to get connected the trx has rolled back. It would be very convenient if the session id and output to onstat -g ses/sql would also be output to either the online log or DUMPDIR to assist in determine the offending sql. Also include output to onstat -x since that would reveal the begin log which helps determining if it's really a long trx or simply a trx that remained open too long.
Do not place IBM confidential, company confidential, or personal information into any field.