The .srf file is a compressed binary database. Siebel eBusiness Applications use compression techniques to optimize  the size and performance of the .srf file at compilation time. Each time a repository object gets written or changed, there is a change to internal block allocation, causing the file size to change.

A partial compile will optimize less than a full compile, because the optimization is confined to the objects being written at that time, without looking at their relation to the repository as a whole. Therefore, it is fairly common to see an increase in .srf file size after a partial compile, even if no objects or properties have been added.

A full compile may also result in slightly different file sizes, as with this example of a comparison between a .srf file compiled from identical repositories in development, test and UAT:

• SIEBEL_DEV.SRF  ---- 10,453 KB
• SIEBEL_TEST.SRF ---- 10,496 KB
• SIEBEL_UAT.SRF  ---- 10,489 KB

The difference in size is due entirely to the optimization functionality, and not to the environment or the machine. Successive full compiles on the same machine may also show file size changes.

If there is a significant change in file size, for example, if a 10 MB file becomes 5 MB or 15 MB, investigate the following:

1.Ensure that prior to compiling, the administrator has opened the correct repository file. To verify the repository name in Siebel Tools, choose File > Open Repository. The highlighted value is the repository whose objects are currently being displayed in the Tools application and the one which will be compiled.

2.Ensure that the database sort order is set up to use binary sort order. Databases used to hold a repository must use binary sort order. Please refer to the Siebel Server Installation Guide for the appropriate operating system for further information. In the Creating the Database section for the appropriate RDBMS, refer to the section Creating the Database > Creating and Setting the Language Characteristics of Your Database.