Home > Oracle, Siebel > Installing Siebel 8.2.2 on Linux x86-64 Part-3

Installing Siebel 8.2.2 on Linux x86-64 Part-3

In this part we will Siebel database configuration tool to populate Siebel  database but fire we need to some preparation tasks as explained in following section.

4. Preparing to run the Siebel Database Configuration Tool.
 In This section we will prepare our system for running the Siebel database configuration tool.
Our aim is to prepare our database to be populated with  Siebel data.We will run grantusr.sql in dbsrvr directory.

  • Update grantusr.sql in dbsrvr ,to  add GUESTERM  and GUESTCST
  • It is recomended  take a backup of grantuser.sql
  • Add the following line to grantusr.sql
    Note:- It is very important to keep in mind that  grantuser.sql does not create GUESTERM  and GUESTCST user we need to manually add lines to grantuser.sql  to create these two users. :-)
  • Run the updated grantusr.sql
  • Enter username , password for Siebel Database Object
    {In earlier versions of grantuser.sql Siebel user was by default table owner but in this new version of grantusr.sql we can manually specify Table owner user} .
  • Select Table space created earlier when asked for default table space.
  • Also Enter Passwords for SADMIN and LDAPUSER users {It is highly recommended not to change SADMIN user}.
  • TO test we can connect to database as SADMIN user
    sqlplus SADMIN@OBIDB as sysdba
  • Next step is to Populate the Siebel database but first create environment file from scripts located inside siebsrv directory
    # cd /u01/siebel/8.2.2.0.0/ses/siebsrvr/install_script/install
  • Run CreateDbSrvrEnvScript as
    # ./CreateDbSrvrEnvScript /u01/siebel/8.2.2.0.0/ses ENU Oracle
    Here first argument is SIEBEL Base and  ENU is for language English , Oracle For dbserver database type.
  • It will create
    dbenv.csh and dbenv.sh files under siebsrvr directory.
  • Source the newly created file.
  • Modify LD_LIBRARY_PATH and add 32-bit database client libraries to this path as :-
  • Note:- It is very important to add 32-bit database client libraries.
  • Above step is a very important step because , .odbc.ini file uses SEor825.so file and all of its supported libraries are not present until we add database client libraries to LD_LIBRARY_PATH.{We can also manually edit dbenv.sh file to include database client libraries to LD_LIBRARY_PATH }
  • Now we can test database connection using a tool “ odbcsql “ present in the siebsrvr/bin directory . We can use this tool as :-
    [dbuser@vm50 bin]$ ./odbcsql /source Veebrij_8_DSN /user SADMIN /password SADMINPASSWORD
  • If all went well you should be able to connect successfully.
  • and as we can see we were able to connect successfully.
  • Now we are ready to run Siebel database configuration tool and populate the Siebel database. (Explained in next step)

5 . Running Siebel Database tool to populate the Siebel Database.
In this section we will do the following :-

  1. Run database Configuration tool
  2. Populate and Test Siebel database.

To run database configuration tool:-

  • Navigate to config sub-directory
  • Run the configuration tool in dbsrvr mode as
    # ./config.sh -mode dbsrvr
  • Installer will automatically detect Siebel Server and Gateway name Server directory from the Environment file that we sourced earlier.
  • Select Oracle here :-
  • Select Install Database option.
  • Select Installation operation
  • As we have already run grantusr.sql script earlier , we can click next.
  • Select encoding type :-
  • Enter the ODBC data source that we tested earlier.
  • Enter database username and password created earlier (when we ran grantusr.sql).
  • If there is any error after above step, we need to retest database connectivity and environment variables settings.
  • Enter the table space owner name and password.
  • Now it will ask for Index table space name {Which we have created earlier in Part-1.}
  • Note: – In Siebel 8.2.2.0 grantusr.sql script assumes there is only one table and does not grant permission on Index Table Space.
    So we will manually need to grant permissions as:-
    SQL>alter user SADMIN quota unlimited on SIEBELINDEXTS;
    SQL>alter user SIEBEL quota unlimited on SIEBELINDEXTS;
  • Enter the tablespace name that we created earlier(Part-1).
  • Enter the Product license key. Siebel  License Key can be obtained from
    http://www.oracle.com/us/support/licensecodes/siebel/index.html
  • Follow the GUI for next steps.
  • In linux Configuration tool generates a master_<Process>.ucf file in $SIEBEL_ROOT/siebsrvr/bin directory. We now need to use Siebel Server Upgrade Wizard to run that file.
  •  Click next to execute settings.
  • Click exit after you get a success message.

Our Next step is to run Server upgrade Wizard with the master install file that was created by the configuration tool in siebsrvr/bin directory. For this

  • Navigate to siebsrvr bin directory and call Server Upgrade wizard as
    # ./srvrupgwiz /m master_install.ucf
  • It will take a while to complete the process(around 60 minutes.)
    and screen like following will appear.
  • After completion you should get screen like below :-
  • Note that it took 60 minutes to complete the process.
  • Once the import is complete we can test if the tables are populated or not. As :-
  • Also we can check size of the SIEBELTS Table space which has grown up-to 1 GB
    So we are fairly confident that database has been populated.
Advertisements
  1. February 23, 2014 at 8:43 pm
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: