5. Start SQL *PLUS and login to the database using the username and
password for the database. You may want to use the same username and password you will
use for Turbine, or you will need to create synonyms for the tables and grant the
necessary privilieges (SELECT, UPDATE, INSERT, etc), so Turbine can access the
tables directly without using "user"."table_name".
6. Run the Oracle specific scripts. For the cvs version of Turbine,
these can be found in turbine/src/sql . In SQL*PLUS type :
@path/to/oracle-turbine.sql
7.The oracle-turbine.sql script creates an oracle sequence
for each turbine table. To use these sequences for primary
key generation, the oracle-turbine-security.sql script should
be modified. For example, the following command from the script :
INSERT INTO TURBINE_USER (USER_ID, LOGIN_NAME, PASSWORD_VALUE, FIRST_NAME, LAST_NAME)
VALUES (0, 'turbine', 'turbine', 'turbine', 'turbine');
would be changed to something like :
INSERT INTO TURBINE_USER (USER_ID, LOGIN_NAME, PASSWORD_VALUE, FIRST_NAME, LAST_NAME)
VALUES (TURBINE_USER_SEQ.nextval, 'turbine', 'turbine', 'turbine', 'turbine');
When your changes, if any, are made to the script, run it from SQL*PLUS :
@path/to/oracle-turbine-security.sql
8.If you would rather use Turbine's id-broker to generate
primary keys, run the following scripts to create and populate the
id-broker table :
@path/to/oracle-id-table-schema.sql
@path/to/oracle-turbine-id-table-init.sql