[OPENIDM-7430] IDM 4.5.1 fails to start when Oracle or DB2 is used as repo Created: 16/Jan/17 Updated: 13/Apr/17 Resolved: 13/Apr/17 |
|
Status: | Closed |
Project: | OpenIDM |
Component/s: | Module - Repository JDBC |
Affects Version/s: | OpenIDM 4.5.1 |
Fix Version/s: | OpenIDM 4.5.1 |
Type: | Bug | Priority: | Blocker |
Reporter: | Tinghua Xu | Assignee: | Chris Drake |
Resolution: | Fixed | Votes: | 0 |
Labels: | not-for-release-notes, regression | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
IDM 4.5.1 build runs on a CentOS with Oracle DB and DB2 as repo. |
Attachments: |
![]() ![]() |
Verified Version/s: |
Description |
When used oracle DB as repo, IDM 4.5.1 failed to start, IDM logged the following error(the complete log is attached): Note: Tried to run some queries w/o IDM, the queries were fine, either w/ or w/o results but returned properly. One query select * from internaluser; returned results properly. To reproduce using Pyforge 4.5.0 branch: Put IDM 4.5.1 build under pyforge archives/, make necessary config changes and run the following command: |
Comments |
Comment by Tinghua Xu [ 16/Jan/17 ] |
See the same problem with DB2, attached IDM log file. |
Comment by Tinghua Xu [ 16/Jan/17 ] |
Something related |
Comment by Chris Drake [ 23/Jan/17 ] |
Tinghua Xu Yes, good catch. Backported |
Comment by Laurent Bristiel [X] (Inactive) [ 26/Jan/17 ] |
checked OK in revision 309d917ffef of 4.5.x branch |
Comment by Lana Frost [ 13/Apr/17 ] |
Remove from release notes |