Siebel Installations > Siebel Open UI Installation in Redhat - Step 7 : Create Siebel Database Server extension
We need to run these scripts in database by starting SQLplus or with another Database User Interface
First we create two Tablespaces from SQLplus. Logis as sysdba
SQL> Create tablespace siebelts Datafile 'siebelts01.dbf' Size 2G AUTOEXTEND on NEXT 100M MAXSIZE UNLIMITED; Tablespace created. SQL> Create tablespace siebelindexts Datafile 'siebelindexts01.dbf' Size 2G AUTOEXTEND on NEXT 100M MAXSIZE UNLIMITED; Tablespace created.
After this we need to run grantusr.sql
Grantusr.sql has these commands
rem Create Role sse_role create role sse_role; grant create session to sse_role; rem Create Role tblo_role create role tblo_role; grant ALTER SESSION, CREATE CLUSTER, CREATE DATABASE LINK, CREATE INDEXTYPE, CREATE OPERATOR, CREATE PROCEDURE, CREATE SEQUENCE, CREATE SESSION, CREATE SYNONYM, CREATE TABLE, CREATE TRIGGER, CREATE TYPE, CREATE VIEW, CREATE DIMENSION, CREATE MATERIALIZED VIEW, QUERY REWRITE, ON COMMIT REFRESH to tblo_role;
rem Create SIEBEL user create user SIEBEL identified by SIEBEL; grant tblo_role to SIEBEL; grant sse_role to SIEBEL; alter user SIEBEL quota 0 on SYSTEM quota 0 on SYSAUX; alter user SIEBEL default tablespace &&siebel_tablespace; alter user SIEBEL temporary tablespace &&temp_tablespace; alter user SIEBEL quota unlimited on &&siebel_tablespace; alter user SIEBEL quota unlimited on SIEBELINDEXTS; rem ================================================== rem Create db accounts for Siebel users rem ================================================== create user SADMIN identified by SADMIN; grant sse_role to SADMIN; alter user SADMIN default tablespace &&siebel_tablespace; alter user SADMIN temporary tablespace &&temp_tablespace; alter user SADMIN quota unlimited on &&siebel_tablespace; alter user SADMIN quota unlimited on SIEBELINDEXTS; create user LDAPUSER identified by LDAPUSER; grant sse_role to LDAPUSER; alter user LDAPUSER default tablespace &&siebel_tablespace; alter user LDAPUSER temporary tablespace &&temp_tablespace; create user GUESTERM identified by GUESTERM; grant sse_role to GUESTERM; alter user GUESTERM default tablespace &&siebel_tablespace; alter user GUESTERM temporary tablespace &&temp_tablespace; create user GUESTCST identified by GUESTCST; grant sse_role to GUESTCST; alter user GUESTCST default tablespace &&siebel_tablespace; alter user GUESTCST temporary tablespace &&temp_tablespace;
SQL> @grantusr.sql
After this we need to create db environment
Now open dbenv.sh. This file should be in SIEBSRVR_ROOT/install_script/install directory.
Add the oracle 32 bit client home in dbenv.sh These two lines should be in dbenv.sh
$ORACLE_HOME/lib -- > $LD_LIBRARY_PATH LD_LIBRARY_PATH=${SIEBEL_ROOT}/lib:/u01/siebel/oraclient/db/product/11.2.0/client_1/lib:${SIEBEL_ROOT}/lib/odbc/merant:${MWHOME}/lib:${SQLANY}/lib:/usr/lib:${LD_LIBRARY_PATH}
Now load the dbenv.sh with this command [siebel@siebelserver:/services/siebel/siebsrvr/install]$ . ./dbenv.sh
Start the GUI Installer with this command [siebel@siebelservername config]$ ./config.sh -mode dbsrvr
Enter the two directories and click next. It is standard practive to have both dbsrvr and siebsrvr directories at the same level.
Select Oracle and click next.
We will install a Database. Click next.
Select 'Install Siebel Database' and click next.
Click next.
We have already run grantusr.sql. So click next.
It is always safer to have UNICODE Database. If you have a Customer name that has foreign characters or an address that has a street name in Turkish, you will need UNICODE.
Enter the dsn name, you should get this from the DBA or note down the DSN name during Database installation.
Enter SADMIN and SADMIN password twice.
Now enter SIEBEL as user and SIEBEL's password twice.
Enter the names of the two tablespaces we created before. Click next.
Select 'Do not use Oracle Parallel Indexing option'. Click next.
Always write SSE_ROLE. The DBA is also supposed to use SSE_ROLE.
Write any directory, the directory does not have to exist.
Check the values if there are any errors, save response file and click next.
Click next.
Everything is ok. If there are errors , check the log file.
The DB Server configuration is finished.
|