Siebl 15.6 Patch Installation Steps..

  1. Image Creation



Run the Image Utility for Windows:


Select the option for Image Creation.

Specify The Directory for Image Creation:


Select The Operating System:
Select Product :


Specify the language for Siebel image


  1. Installing the Patch and Upgrading Servers:

                                

2.1  Enterprise Server Patching:


From Siebel Patch location and install Patch for Enterprise Server:

Enter Parameter if it is not taken automatically:

Click on Install:
After This new window will come up just click on  close button.

                                       

2.2  Web Server Patching


From Patch Location->


Select Parameter and Click on Next:

Click on Install button:

After This new window will come up just click on Close button:

3.   Bringing up the Servers:


3.1 Start the Gateway Server


3.2 Start the Siebel Server


4. Verifying the Patch Version:


Goto Tool ->Technical Support

Oracle Database Backup and Restore Using RMAN

                             


BACK UP STEP–
1- We have to check database recovery size.
   C:UsersAdministrator>d:
   D:>cd appAdministratorproduct11.2.0dbhome_1BIN
2-Increase database recovery size using this command.    
   
    First connect to database using sqlplus sys@databasename as sysdba
   
    ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10G SCOPE=BOTH SID=’databasename’;
D:appAdministratorproduct11.2.0dbhome_1BIN>set ORACLE_SID=DBNAME
D:appAdministratorproduct11.2.0dbhome_1BIN>ECHO %ORACLE_SID%
SIEBELDB
D:appAdministratorproduct11.2.0dbhome_1BIN>rman target
                      OR
D:appAdministratorproduct11.2.0dbhome_1BIN>rman target ‘sys@DBNAMEas sysdba’;
Recovery Manager: Release 11.2.0.1.0 – Production on Tue May 12 13:51:05 2015
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
target database Password:
connected to target database: DBNAME(DBID=1837164085)
RMAN> shutdown immediate
using target database control file instead of recovery catalog
database closed
database dismounted
Oracle instance shut down
RMAN> startup mount
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area    3373858816 bytes
Fixed Size                     2180424 bytes
Variable Size               1862273720 bytes
Database Buffers            1493172224 bytes
Redo Buffers                  16232448 bytes
RMAN> backup database;
RMAN>startup

.SPF file in Siebel:

 working on very simple requirement to increase the HTML length of one of the list column, displayed on Opportunity List Applet.

Sounds very simple… right?? So, to increase a Column Length of a List Column, what we need to do is :


1. Query for the specific List Column in Siebel Tools.
2. Increase the “HTML Width” property value to some significant number.
3. Compile the SRF and observe the change on the UI. If it doesn’t look good, then you can play with the “HTML Width” property to increase/decrease the html length of the column.
Thats it ?? The answer is NO.


He (my colleague) followed the exact above mentioned steps and still observed that the HTML length of that particular List Column was as it was earlier. Thought that SRF might not have compiled properly, so compiled the SRF 2-3 times but not able to change the HTML length by a singlecentimeter.

Well, this is something strange that we observerd and after lots of investigation, we came to know about the reason behind this.

The culprit was .SPF file (Siebel Preference file), being created by the system for the user.
This is the file that Siebel creates for every user who logs into the application with the naming convention “‘UserId’&’SiebelApplicationName’.spf” and stored in “//Siebel_server/Web Client/Bin” directory. This file actually stores the lot many information about the UI Changes that user can do on the UI. For Eg :

1. Increased/decreased HTML length of List Columns from the UI, that user might have changed according to his needs.

2. Order of the List Columns on the applet, in case user has changed any.
3. Order of the Screens displayed on the UI. (Application Menu -> Tools -> User Preferences -> Tab Layout)
4. “Recents Records” details being displayed on the “Home” views of various screen like Opportunities Home, Accounts Home etc.
So, the solution was just to delete this .SPF file from Server’s Bin directory and restart the Siebel session.

Note: Deletion of this file will result in lost of all the preferences set the by user. Even I remember, due to this .SPF file only, we came across one another issue related to Views/Responsibilities. User was not able to see a newly added view under the Opportunity Screen, while the newly created responsibility was already been added to the user profile. Later we deleted the .spf file of the user and all worked well.

Migration of Siebel Release To Another Environment:

So prior to deployment you need to: 

a) Perform a full compile to get an SRF file to be deployed. If you dont know how to do this then look it up in the Siebel Bookshelf. 

b) Perform a repository export to get a repository dump file. This can be done using the repimexp tool. Here is an example of how to export the repository using repimexp:

repimexp -a e -c siebsrvr_siebel -u sadmin -p sadmin -d siebel -f c:Siebel_Repository.dat -l c:Siebel_Repository_Export.log

Where: 

-a – this is e for export 
-c – is the odbc source 
-u and -p – these are the credentials for the sadmin user 
-f – this is the siebel repository export file 
-l – this is the log file 

The deployment process is outlined as such: 

1. Stop the Siebel Servers. 

2. In Siebel Tools, rename the current Siebel Repository to another name. In the Object Explorer go to Repository and rename the current Siebel Repository to something like: Siebel Repository Pre v1.1. The current repository needs to be renamed so that you can import the new repository with the name: Siebel Repository. 

3. Import the repository using the repimexp tool. Here is an example of how to import the repository using repimexp: 

repimexp -a i -g ALL -c siebsrvr_siebelsystest -u sadmin -p sadmin -d siebel -r "Siebel Repository" -H 2000 -f c:Siebel_Repository.dat -l c:Siebel_Repository_Import.log



4. Perform a DDLSYNC to apply database level DDL operations to be in sync with the new repository. To do this run the following commands in order: 

ddldict -u sadmin -p sadmin -c siebsrvr_siebelsystest -d siebel -f ../schema.ddl -e y -a y -l ../DDLDICT.log -n "Siebel Repository" -T DCIR



ddlimp -u siebel -p siebel -c siebsrvr_siebelsystest -g SSE_ROLE -f ../schema.ddl -e n -B SIEB_TBLSPC -X SIEB_INDX -R Y -s Y -l ../ddlsync1.log



ddlimp -u siebel -p siebel -c siebsrvr_siebelsystest -g SSE_ROLE -f ../schema.ddl -e y -B SIEB_TBLSPC -X SIEB_INDX -R Y -s Y -l ../ddlsync2.log



5. Deploy files to the Siebel Servers. These files include the SRF, web templates, image files, configuration files, etc. 

6. Generate browser scripts using genbscript. Something like this if you navigate to the bin directory on the siebel servers: 

genbscript ./siebel.cfg ../webmaster



6. Start up the Siebel Servers. 

7. Activate any new or updated workflows in the Administration – Business Process > Workflow Deployment view. 

8. Compile any new or updated PLSQL procedures or packages. 

9. Deploy master data changes. This would include any changes required to LOVS, runtime events, state models, assessment templates, etc. All master data changes. 

10. Restart the Siebel Servers. 

11. (Optionally) Execute any data updates through EIM and/or business service. If these data updates are quite large involving changes to a lot of data then you would most likely want to regenerate the database statistics through consultation with a DBA.