|
I successfully installed Teamwork 4.6 build 18003 (used Advanced install - pick your database selected Teamwork 4 Standalone with Tomcat select Oracle 10+ as database specify schema name as TEAMWORK specify the correct jdbc url leave the user as SYSTEM and provide it's password test the connection: success) Then I pointed my browser to http://myhost.mydomain:8080/applications/teamwork/security/login.jsp I enter 'administrator' as user name, leave the password field empty and click on [proceed] button I get redirected to the generic error page: http://bugsvoice.com/applications/bugsVoice/site/bv.jsp The same happens on Linux (Oracle Enterprise Linux 5U5) and WindowsXP 32 bit SP3 as well When I install using Test db(HSQL) it works like charm. Can someone tell me how to get it work with a remote or local Oracle database or how to debug what is going on? Further I've tested other possible scenarios: Oracle XE (express edition 10g) locally installed, Oracle XE 11.2 locally installed: same effect, install runs fine, first connection crashes. Further I've tested with MySQL database, that works just fine too. I suspect this is a bug. |
The question has been closed for the following reason "The question is answered, right answer was accepted" by Pietro Polsinelli Jun 13 '11 at 04:49
|
In case anyone using Oracle database and Teamwork 4.6 is interested, here is the Details of the solutions On the installation dialogue box when you select Oracle10+ as a database type and the form asks for schema, username and password, you need to specify the username the same as the schema. If you leave the username the default value 'SYSTEM' and give system pwd, then a portion of the repository tables and one sequence will be created under SYSTEM schema, while other objects will be created under the schema you specified. To do this you have to get that schema/user created in advance and grant create table, create synonym, create view, create sequence and a few other create privileges. I haven't tested exactly which specific object creation privileges are absolutely necessary but after giving those that make sense for a normal schema to do its jobs, it worked. The schema/user does not need to be DBA. P.s.: This small issue might be originated from the fact that Oracle handles the User and Schema concept more or less as synonym (mainly from some historic reason). While other SQL databases clearly separate these concepts. Not clear what is the exact structure of Teamwork repository, it might be that it was intentionally designed to store some objects under 'user' and others under 'schema', but for me it seems unlikely. I suspect the install script just does not specify the schema in some object creation statements, but this is just a guess ;-) Anyway the workaround to make 'schema' and 'user' the same at the install solved my problem and I enjoy Teamwork4 now. |
|
We have several installations and customers running with Oracle. My guess is that there is a problem with the schema name, anyway we are writing you an e-mail with detailed feedback. (Will post here again once we found the problem together.) I've sent detailed investigation results via email. I don't think that it is the schema issue. First of all I had to create the schema manually, I've granted all possible privileges to the schema. I've tried with 10g and 11g databases, however after checking some logs, it seems that some objects are just not created via the installation of the schema structure that the first time login would require. I am using the latest version: 4.6 (build 18003). Is there any customer using this build with Oracle database successfully? If they use other versions/builds, would it be possible to get that version until this bug is fixed? Waiting for your response.
(Jun 06 '11 at 16:00)
Laszlo Gal
|
|
The problem has been solved in direct contact with the customer, and with no modifications to Teamwork 4.6. |
