If you call your script like this :

Code:

./movedate.sh /usr/sap/${ORACLE_SID}/ifr/otherdirectory/file1 /usr/sap/${ORACLE_SID}/ifr/some_other_directory/

Then your

Code:

path1=$DEFAULT_PATH/$1

will contains :

Code:

/usr/sap/${ORACLE_SID}/ifr/usr/sap/${ORACLE_SID}/ifr/otherdirectory/file1

So you should not call your script that way , but you rather should call it using only the filename and directory name without specifying the path, since you set it up later on with the DEFAULT_PATH.

---------- Post updated at 03:25 PM ---------- Previous update was at 02:19 PM ----------

[[ -f "$DEFAULT_PATH/$1" ]] && [[ -d "$DEFAULT_PATH/$2" ]] && mv $DEFAULT_PATH/$1 $DEFAULT_PATH/$2/$1.$(date +%Y%m%d)

a) Where do you want this *.date file be generated ? in $DEFAULT_PATH or in DEFAULT_PATH/$2 ???

b) The file won't exists since it has been moved ... why don't you just copy it instead or moving it ... so you would let an original copy and avoid this additional step.

c) In the archive destination ? so you want it to be moved to $DEFAULT_PATH ? or $DEFAULT_PATH/$2 ????

d) Try to create which file and where ?

e) Are you trying to make a script that can be launched several time in parallele (concurrent run) ?

f) let's forget the touch part , i first need to understand what is the expected behaviour (please focus on describing the needs, not what you have done, but what is intended)


I think that instead of explaining what you did or how what you did works,
I just need to know : what are the needs (pseudo-code) ?

a). rename $1 with $1.date (all within the same $DEFAULT_PATH directory)
b). archive (move) the $1.date file into the $DEFAULT_PATH/$2 directory ?
c). other ???

Thx

---------- Post updated at 03:29 PM ---------- Previous update was at 03:25 PM ----------

by the way, as far as i understand, your
path_1 will always have the same value as $DEFAULT_PATH so $path_1 is useless : use $DEFAULT_PATH instead.