siebel

This is a repost from February 2009, seems that upgrading Siebel CRM doesn't go out of fashion anytime soon, especially with Innovation Pack 2013 . It appears that many of those Siebel consultants are busily upgrading and I think that timeframes are challenging as always ;-) The following command line utilities are here to help you during the upgrade and save your precious time (you'll need it for other tasks ;-). Please note that the list below is not complete. 1. Log Parser When Siebel Upgrade Wizard performs the Upgrade Database Schema (upgrep) and Upgrade Physical Schema (upgphys) and any other step against the database, it forwards the command line utilities' log files to a central directory, a subfolder of the Siebel Server's log directory. You can run the logparse executable from the command line and generate a nice and pretty html summary. The logparse utility is also useful to summarize tasks not related to an upgrade such as a repository migration (notorious...

In the second part of our notes on an upgrade from Siebel 8.1.1.x to Innovation Pack 2013 , we are back waiting for the Siebel Upgrade Wizard to finish its arduous task. When suddenly... 8. Backup the Database and execute DB stats At this step, the Upgrade Wizard stops with the above dialog and urges us to take a backup of the database and then execute DB stats. This is obviously a manual step. The Database Upgrade Guide shares with us the necessary lines for executing DB stats as follows (Oracle database example): EXEC DBMS_STATS.gather_schema_stats (ownname => '', cascade =>true,estimate_percent => dbms_stats.auto_sample_size); The above command (with the correct table owner name which usually is SIEBEL) must be run using a SYSDBA account. Alternatively you can run the more sophisticated stats package available from My Oracle Support as Document Id  781927.1 (thanks to Oli for the link). Because I encountered problems with too many open cursors on a previous occasio...

Siebel Innovation Pack 2013 (aka 8.1.1.11 / 8.2.2.4) is available for a while now. During discussions with customers and students, almost every project wants to be on this release sooner or later. The reason for this might well be Open UI . Regarding the version numbers, going from 8.1.1.x to 8.1.1.11 might well be " but a patch ". But alas, this couldn't be further from the truth. In reality, installing IP 2013 "on top of" a previous 8.1.1.x version is more than a full upgrade than a patch. Recently, I had the privilege of going a full round, upgrading an existing 8.1.1.0 (yes .0, but it could have been any version up to 8.1.1.7) installation to 8.1.1.11. In this two-part article, I would like to share my findings with you. So this is what I had in front of me: A Windows machine with a Siebel 8.1.1.0 server, connected to an Oracle 10g database and also a SWSE/web server machine. 1. Download and create installers First, I duly downloaded, extracted and created ...

If you are following the various articles on Siebel Open UI on My Oracle Support (hopefully using the great Open UI I nformation C enter   available  as Document   1511846.2 ), you might have stumbled upon  Oracle Support Document 1535281.1 ( Latest recommended maintenance pack for Siebel Open UI on Siebel Version 8.1.1.x and Version 8.2.2.x ) which holds some interesting information regarding Oracle's strategy for releasing quick fixes, maintenance releases or patches for future Siebel versions. The biggest news is that from Innovation Pack 2013 (i.e. version 8.1.1.11 and 8.2.2.4) onwards, Oracle will provide monthly patchsets which introduce a fifth digit in the version number. Source: My Oracle Support So the January patchset for 8.1.1.11 is 8.1.1.11.3, as you can see in the above screenshot. The patches can be downloaded as usual from My Oracle Support. Bringing the new monthly patchset strategy together with the traditional version paths results in the followi...