Downgrade your iphone 4 os to 3.0 on 3g

I had lot of enthu to upgrade iPhone 3 0s to Iphone 4 OS when it came out butI was not happy for long. Just to name few I could not surf net when playing songs. Both ipod and browser used to crash. After skimming through some third party support pages I hoped for re-start to help but no luck. This morning I went to apple support discussion and found almost 86 pages on Iphone 3g discussing on the same. The steps listed out there work out very well for me to re-store back it to 3 Os. Now I feel that my iphone works at blazing speed.
Before you start on the following steps download .net 4 framework and iphone 3 firmware.
Follow the steps below to re-store your iphone at your own risk..

1.Switch off your iphone using sleep button and sliding power off display
2.Hook u your iphone to your computer
3. Hold home and sleep button together at the same time for 10 seconds
4.After 15 seconds just take your hands off the sleep button and keeping the home button still down for another 15 seconds.
5. This would start your iphone in the recovery mode and you would see the prompt on the itunes for the same.
6. If you don't get this try step 3-5 again
7. After you get the recover option with the shift key down click on rest0re button and navigate to the folder where you downloaded iphone 3 firmware. It'd take 15 minutes to restore
8.If iTunes throw an error after re-storing you can exit the restore mode by pressing the home and sleep button for ten seconds.
8.After it's restored you can restore all your contacts from back up (back up you took before you upgraded to iphone 4.

I followed the above steps and it worked for me.

Invoke PL/SQL procedure from IFB

We have a PL.SQL procedure to sync opportunity team with account team. Yes we could have used Assignment manager but because of bug introduced in 8.0 we had to write up the custom pl.sql proc for the team sync.

One thing I had to make sure is that pl.sql scheduled job does not conflict with EIM rcr. To fix this I thought of developing a shell script that would run the pl.sql proc and EIM in sequence.Not a shell script pro so had do some research before I can develop this. When I was discussing on the same with my manager he introuduced me to a cool feature on IFB that would do it.

I tried this out and it works like a charm. So here is how you can do it.

TYPE = IMPORT
BATCH = 0723002010
TABLE = EIM_OPTY
SESSION SQL = "BEGIN INTEGRATION.TEAM_UPDATE; COMMIT; END;"

After this I included the EIM imports and delete process commands. Now I need to schedule just the RCR and not dependent on one more scheduled job.

Workflow Insert/Update/Query Operation

I've always been using Siebel Operation step to query or update the records on primary business component. But there is always a need to instantiate a differenct business object to get dependent records for update or validation. In such case you can always use a sub process step to call update/query based on new Business Object but this would impact workflow performance. There is a better workaround for this.There is OOB business service which would help us to instantiate a new business object by using Business Object and business componetn as input parameter to business service.

Name of the Business service is Inbound E-mail Database Operations and we can use FindRecord or Insert Record methods on this business service similar to Siebel Operations step.Will post the detail on the same in my next blog.Later.

Insert record position on the applet

There is a nice little feature in Siebel that would help us define the position on an applet when creating a new record. Let's say the user is on the view skimming through list of records and when the user is on the last record decides to create a new record. If there is a sort spec defined on the bc or applet then the user might loose focus after the record is created.

So to make sure the record is inserted in the last or first position on the applet there is a property on the applet, Insert Position. Most of us might not have seen this in Siebel 8 tools because its not displayed by default.So select Applets in object explorer and in the applet list right click and select Columns Displayed. In the list of available columns select Insert position.Now this should be one of the applet properties listed.

Now select an applet and change the property insert position for the applet to either FIRST or LAST. Compile the change and that's it.Next time when you create a new record the record will always be inserted in the first or last position. Well that's it for now...

Spool sql in Siebel

I think in the first few days of working in Siebel you would know that to troubleshoot performance or visibilty issue with any data loads the first question any Siebel techie would ask , did you spool the sql?

To resolve any visibility issue yes you just need to add a switch /s and get the spooled sql. But if you are troubleshooting some preformance issue you need to set some session parameters for Siebel client running on Oracle CBO environment.

alter session set optimizer_mode = first_rows_10;
alter session set hash_join_enabled = false;
alter session set "_optimizer_sortmerge_join_enabled" = false;
alter session set "_optimizer_join_sel_sanity_check" = true;

After setting these parameters the execution time on the spooled file should sync with response time on Siebel application. Later..

Disable button on an applet

Disable button on an applet: This was one of the requirements that came with all the clients I have worked before. This is not tricky configuration and should nt take more than 10 minutes to configure this. My reason to bring this up is there is an easy and neat way to do this.

I'm sure you should have seen this on scripting but there is an applet user property to do this. If you want to disable the new button on an applet create an applet user property like this.

CanInvokeMethod: NewRecord
Value: FALSE


Later..

System Diagnosis

In recent days I have been skimming through some technical support documets as well as bookshelf regarding Siebel system monitoring and diagnosis. I realized this is one of the skill that would come in handy for system crash when you really don't have much time to do your research and troubleshoot. There are ofcourse some basic things you always do to start troubleshooting but I think to read the log files and identify the cause of the crash comes with experience.So here are some basic things that you can start with to troubleshoot the component or object manager crash.

change evtloglvl trace=4 for server server_name component SSEObjMgr_enu

change evtloglvl GenericLog=4 for server server_name component SSEObjMgr_enu

change evtloglvl TaskConfig=4 for server server_name component SSEObjMgr_enu

change evtloglvl SQL=4 for server server_name SSEObjMgr_enu

change evtloglvl SQLError=4 for server server_name SSEObjMgr_enu

change evtloglvl SQLParseAndExecute=4 for server server_name component SSEObjMgr_enu


I'm planning to post more basics on Siebel system diagnosis atleast for the next few days. I think this would help me diagnose the crash faster and better.