[patch] Add db2 known issue for affected catalogs#197
Merged
Conversation
sanjayprab
changed the title
durera
approved these changes
Feb 18, 2026
durera
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We recently discovered an issue with db2u operator we offer in our latest catalog, it turns out its a known issue according to Db2 docs - https://www.ibm.com/docs/en/cloud-paks/cp-data/5.3.x?topic=SSQNUZ_5.3.x/svc-db2/known-issues-dbs.htm#known-issues-dbs__db2-instance-fails-sql0290n__title__1
Issue is after Db2 restore, users might hit the below db2 issue which causes MAS applications to not connect to Db2 after restore.
ERROR: SQL0290N Table space access is not allowed. SQLSTATE=55039Users are noticing this problem intermittently and a workaround is suggested in the above link. So we need to add them to our known issues as well.