SpagoBI.log
[SPAGOBI-632] PostgreSQL DB Creation script Created: 07/Jul/11 Updated: 12/Jul/11 Resolved: 12/Jul/11 |
|
| Status: | Closed |
| Project: | SpagoBI |
| Component/s: | SERVER/Database |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Nanni Fabrice | Assignee: | Monica Franceschini |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | Windows 7 64 bit, JDK1.6.0_03-b05, PostgreSQL 8.4 | ||
| Attachments: |
SpagoBI.log
|
| Description |
|
1) The table SBO_EXT_ROLES has an wrong field name: SAVE_INTEGERO_FOLDER instead of SAVE_INTO_FOLDER Extract of the script: SAVE_INTEGERO_FOLDER BOOLEAN DEFAULT TRUE, 2) The table SBI_USER has 3 incompatibles "NOT NULL" constraints on the fields DT_PWD_BEGIN, DT_PWD_END and DT_LAST_ACCESS DATE. These 3 fields do not accept NULL value, and an error is raised when launching tomcat I see it as a DB Script BUG, but maybe this values should really never be NULL and therfore it's an application BUG The error is the following: ERREUR: une valeur NULL viole la contrainte NOT NULL de la colonne « dt_pwd_begin » [main] 07 juil. 2011 15:58:30,419 ERROR it.eng.spagobi.profiling.dao.SbiUserDAOHibImpl.saveSbiUser:168 - Could not execute JDBC batch update See attached file for complete SpagoBI.log Extract of the script: DT_PWD_BEGIN DATE NOT NULL DEFAULT CURRENT_TIMESTAMP, DT_PWD_END DATE NOT NULL DEFAULT CURRENT_TIMESTAMP, DT_LAST_ACCESS DATE NOT NULL DEFAULT CURRENT_TIMESTAMP, |
| Comments |
| Comment by Monica Franceschini [ 12/Jul/11 ] |
| Table SBI_EXT_ROLES problem is solved, just try ipdate your db scripts for postgres in date 12/07/2011 from OW2 project's site. On the contrary problems on table SBI_USER timestamp columns cannot be reproduced. |