When running Full_Extract_Siebel_DW or Refresh_Extract_Siebel_DW, Informatica returns errors similar to: Double-click the workflow to view the log file details. However, the workflow is running, but the server just needs time to complete fetching the sessions into memory. If this takes longer than the server time-out property, the server returns a message that the workflow was unable to run. When you try to run a large workflow, every session in that workflow is fetched into the server's memory. This can happen due to a server time-out property that is usually set to 20 or 40 seconds. 'Request to start workflow (workflow name) on server (server name) not successful.' When you execute a workflow on the Informatica Workflow Manager, Informatica returns the following error message: The risk of increasing the LMSharedMemory too much is that it may start to have a serious effect on overall performance of the machine that the Informatica server is running on. The only workaround is to increase the values of the LMSharedMemory and MaxSessions variables in Informatica.

When running some Informatica mappings for loading the Siebel Data Warehouse, turning on the Performance Statistics can cause the mapping to hang. Using Oracle, some mappings hang while running when performance statistics are switched on. You also may need to change the text editor. The session log files are not set up properly. Double-clicking the workflow yields a Workflow Manager error message: 'The system cannot find the file specified.'

Ibm notes failed to start successfully