The migration of my Oracle DB server to another one was successful except one thing, and its important one. It’s the backup running from task scheduler !
Since my backups where script based, in past I did not have problems with it.
After migration, server was up, db was working, clients were happy, the backup script when run manually was successfully creating backups.
I was about to add the .bat script to task scheduler, but that part was struggling me for half a day.
I tried all the suggested methods that included, running script as system, changing location of script, running through powershell, or running script as admin etc…
I always had same behavior, and that is : task was in running state, but script wasn’t started and the backup file was not generated.
Solution for me was that the Program/Script path had to be under quotes marks.
Even though I didn’t have any “spaces” in filenames of path, the script won’t run.
After adding quotes marks to file path, the task scheduler was able to run the script and create backup.
Running scripts that includes network mapped drives will require that task is configured to run only when user is logged on. This is because you cant have mapped drive without user logged on system.