Are you using any specific session property ,I mean to say some pre post sql or command? If that is incorrect ,then there are chances of this error.
Please provide detail of your mapping and session.
I would suggest, if you could check the paramter Filename (at the session (and/or) workflow level)
I have generally faced the "unable to fetch session log" error when there is any problem with the parameter file.
Hope that helps
Thank you Divya for quick response ....
Thank you prachi sharma for quick response ....
Hi Prachi Sharma,
Even I am facing the same issue. My mapping is very simple,
I am doing it in my local system Win7 informatica 8.6.1
please help me to resolve...
Please check, if either of the below might be specified incorrectly
- Session Log File directory
- Session Log File Name
- Parameter Filename (at the session (and/or) workflow level)
Also validate your workflow once before restarting it.
Keep us posted for further issues.
- Session Log File directory
If it got resolved, can you please share the root cause and the solution.
If you are changing any relational connections then this may cause of your problem that is
We need to change relational connections of sessions in session level as well as workflow level
Please let me know if this is not working
Perviously i got the same error that time i will check with session in connection level there i missed lookup connection.
Please check with session in connection level and check with parameter file name also.
i think it's usefull.
Plese let me know.
Thanks & Regards
If you have used lookup transformation, set the proper connection for session in workflow manager
Save and execute.
To solve this issue try one of the following:
- If the log file is on another machine, transfer it to the client machine using FTP in binary mode.
- Open the PowerCenter Workflow Monitor.
- In the Workflow Monitor, click Tools > Import Log.
- Navigate to the session or workflow log file directory.
- Select the binary log file you want to view.
- Click Open.
Bharath B S
Please try below below solution
The mapping used for the particular session task has been updated in designer.
In workflow manager, right click on the task/Session, select Refresh Mappings, then validate the session and save the whole workflow. Check out and Check-in as needed.
This should help you rerun your your session and also will be able to see the log.
this will issue will come because of when the Session Log Directory option has not been set in the
Session Properties so do the following:
Edit the session
In the Edit task window, go to the Properties tab
Under the General Options, against the Session Log File Directory attribute, enter $PMSessionLogDir\
I just face the same ERROR, It is because, I have done some chages in the mapping and i forgot to save the mapping and done session work and ran workflow.. So got the error.
Then i just went back to mapping and i saved it and validated and refreshed the mapping and i ran the worklfow. it got succeeded.