Back to bug 1038482
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Takayuki Konishi | 2013-12-05 07:55:06 UTC | Comment 0 is private | 1 | 0 |
| Peter Palaga | 2013-12-10 10:32:44 UTC | CC | cnakamura | |
| CC | mposolda | |||
| Link ID | JBoss Issue Tracker GTNPORTAL-3341 | |||
| Doc Text | Cause: When you configure JPP with Oracle DB (reproduced on Oracle 11gR2) and then you login as root, create user in JPP UI and then try to delete this user in UI | |||
| Doc Text | , you will see error "ORA-02292: integrity constraint (XXXXX) violated" in server.log and user won't be deleted. Consequence: The root cause is the fact that Oracle doesn't know empty strings and it treats them as null. Fix: The fix will always use | |||
| Doc Text | value null for value of UserProfile attribute if it's empty string. The empty string is used in JPP just for attribute "user.language" of UserProfile as this attribute is in UI represented by comboBox. Other UserProfile attributes represented by | |||
| Doc Text | text-fields are already send to UserProfileHandler with value null if they are empty. So actually just attribute "user.language" is usually causing this whole issue. Result: After applying of the fix | |||
| Doc Text | , it would be possible to delete newly created user without problem. BUT for JPP customers, who already have pre-filled DB, the issue may still exists and it may not be possible to delete some users | |||
| Doc Text | , because there may be still some attributes in table JBID_IO_ATTR_TEXT_VALUES, which have value null. To fix the issue in existing environment | |||
| Doc Text | , customer will need to manually clean null attributes by executing this SQL query against his Oracle database: delete from JBID_IO_ATTR_TEXT_VALUES where ATTR_VALUE is null; | |||
| Blocks | 1039924 | |||
| Peter Palaga | 2013-12-10 10:37:30 UTC | CC | ppalaga | |
| Dominik Pospisil | 2014-06-19 13:29:13 UTC | QA Contact | dpospisi | tkyjovsk |
| Jeff Fearn 🐞 | 2020-04-27 01:33:36 UTC | Assignee | jbpapp-maint | nobody |
Back to bug 1038482