Skip to main content

Getting files which are created after a specific time from Unix Directory Using Touch and Find Commands

Generally, we all know that we can create a file using “touch” command in UNIX. If the given file does not exist then “touch” command will create that file, otherwise it will change the modification time of that file.

Syntax:
touch filename

Suppose, in our project, we will get source files with the naming convention “SOURCE_FILE_YYYYMMDD.dat”.  And today we have received SOURCE_FILE_20140117.dat and tomorrow, we will get SOURCE_FILE_20140118.dat etc. Every day we will receive one file.

We may have a requirement that to take all the files which are created after a specific time based on file created time from UNIX directory.

Step 1: create a dummy file with specific time using TOUCH command.

Syntax:
touch -t 'YYYYMMDDHH24MM.SS' dummy.dat
We should pass the date in YYYYMMDDHH24MM.SS format.

Example:
1)      If you give touch -t '201401240134.55' dummy.dat then the dummy file will be created and created time will be Jan 24, 2014.
2)      If you give touch -t '201401070134.55' dummy.dat then the dummy file will be created and created time will be Jan 07, 2014.
We can see the created/modification time using ls –ltr command in UNIX.

If we want to take all the files which are created after Jan 7th, 2014 01:34.55, then we can use
touch -t '201401070134.55' dummy.dat

Step 2: After done with the step 1, now we have to find the files which are created after Jan 7th, 2014 01:34.55. We can find using “find” command in UNIX.

For the above requirement, we can use below command.
If we are in the directory where we have source files then use
 find ./SOURCE_FILE_*.dat  –newer  dummy.dat
If we are not in the directory where we have source files and source files are there in /infa/sourcefiles then use   find  /infa/sourcefiles /SOURCE_FILE_*.dat  –newer  dummy.dat

Comments

Popular posts from this blog

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...

Labelling and creating queries in informatica

Informatica components i.e. mappings,session,workflows,transformation are moved from one environment to another environment say from development to SIT can be done in various ways such as --Export the xml's and again import the xml's in the respective environment --Drag and Drop objects from one repository to another repository For the above process to be done you should have required access across environments. One other way is labelling the components and then creating queries in repository manager. Using these queries components are moved across environment's We need to go to the repository manager and select the version tab and select label Then click new label and give a name say "Wf Migration" and click OK. There we  have permissions tab where we can give access to other users to use the same label. Now we need to select the workflow which needs to be promoted to higher environment.  Right click on workflow and select "view dependencies...

Pre and Post Sql,Session properties at session level

Sometimes we may have a requirement where might need to drop indexes/truncate table and then load the data. So in here what we can we do is we can go for pre sql in session properties and there we can write the required the sql statements such as dropping indexes or truncating table and after the loads i.e. session gets completed we can recreate the indexes in post sql command. In mapping also we can do the same but it is advisable to do at session level. We even have option in session such as Presession, Postsession command and Postsession failure command. In session go to components tab to find out these options. Upon requirement we can use the following command to run unix scripts for specific purpose. We have email option option for on success/failure scenarios too. Hope this article helps you in understanding post/pre session commands