The only solution to this can be ask your Teradata DBA to give read permissions to the User that you are using in Informatica.

So that you are able to read the file.

You might want to read about umask settings. umask defines the default permission that will be setup for a newly created file. For example if you setup umask 002, the default file permission will be 77(7-2) that is 775.

Hi Rahul,

Adding to Sheet Pangasa's reply, the permissions of newly created file by a process depends on the umask value set at the time of Process startup. The usual place to look for information about a process would be /proc. Unfortunately the umask is not (currently) exposed through this interface. To identify the umask of existing running Integration Service Process do the following:

1. Attach the Integration Service Process to gdb debugger for an interactive debugging session as below:

   gdb $INFA_HOME/server/bin/pmserver <pid_of_IS_process>

2. The command prompt should change to (gdb). Now call umask function as below:

    (gdb) call umask()

    Example output: $1=18

This displays the value of umask in decimal (18) equivalent to 022 (octal) i.e., the permissions of file created by Integration Service Process would be 755 (-rwxr-xr-x).

If required to change the umask value, Integration Service should be stopped and started again after modifying the umask value.

Hope this helps.

Thanks and Regards,

Sindhu

Thanks for the additional information Sindu, do you know how to load the symbol file for use with gdb, most of the times i get something like below:

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffde1e8000

Thanks,

Sheet

Hi Sheet Pangasa,

The symbol file for db can be configured using the command symbol-file <filename>. However, it is not recommended to do so without the help of system administrator as it might affect other executables.

For Integration Service executable ($INFA_HOME/server/bin/pmserver) required symbols are read from $INFA_HOME/server/bin/libpm*.

If all symbols from $INFA_HOME/server/bin/libpm*, then the warning mentioned can be ignored.

Hope this helps.

Thanks and Regards,

Sindhu

Dear rahulmurali are you able to capture loader log generated by Teradata TPT loader in a separate file? It would be very helpful if you could share the idea on the same.