Hi guys,

I have defined cronjob in my SLES10 server which runs RMAN for archival of archive logs. The crontab looks like this:

00,20,40 * * * * /u02/backup/rman/rman_archive_del.sh>>/u02/backup/rman/rman_archive_del1.log

When I run the script manually, the script will invoke RMAN and do the job well but when I leave it for crontab to run it, it is not invoking RMAN itself.

The same script is working fine in another linux server.

Thanks&Regards,
Natraj

I think this is the usual crontab issue:
1. use full path in your script to invoke rman (and others)
2. save stderr somewhere to see what's happened, otherwise we can only guess.

Hi,

Thanks for the reply.
I added the path of rman. Still the issue remains.

Regards,
Natraj

Attached Files

	script.txt (496 Bytes, 44 views)
	rman log.txt (938 Bytes, 32 views)

you can insert set -xv at the beginning of the script to see what's happening.
And also use bash to start your script:

Thanks for the reply.
The same script is running well on another server but it is not running on this machine. Please help.

Hi,

After making the changes as suggested by you previously, the cronjob is invoking RMAN. But it is throwing error when it runs automatically.

***********Archive file deletion started at Fri Dec 1 14:50:00 IST 2017***********


Recovery Manager: Release 10.1.0.4.2 - Production

Copyright (c) 1995, 2004, Oracle. All rights reserved.

RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12162: TNS:net service name is incorrectly specified

RMAN>
connected to recovery catalog database

RMAN> RMAN> RMAN> RMAN> RMAN> The archival process ended at Fri Dec 1 14:50:00 IST 2017

Where as when I run thye same script manually, it works fine.

***********Archive file deletion started at Fri Dec 1 14:51:02 IST 2017***********


Recovery Manager: Release 10.1.0.4.2 - Production

Copyright (c) 1995, 2004, Oracle. All rights reserved.

RMAN>
connected to target database: CONPRDDB (DBID=2379791943)

RMAN>
connected to recovery catalog database

RMAN> RMAN> RMAN> RMAN> RMAN> The archival process ended at Fri Dec 1 14:51:10 IST 2017

Regards,
Natraj

Cron run its jobs in so called "sanitized" environment. You can read about this in it's manual.
You should source your .bashrc (or .profile or what suits) at beginning of script.

1 members found this post helpful.

I would insert debug statements at the beginning of the script:

date >> /path-to-log
set >> /path-to-log

And then compare environment variables when run manually and via cron.

The script finds all of the binaries. Look closely at the error message in the log you posted -

ORA-12162: TNS:net service name is incorrectly specified

That means your tnsnames.ora file is missing, does not contain the SID connection string, is in the wrong directory, is not readable by the user running the crontab.

Hi guys,

Thanks for the replies. I was out of town for some days.
When I run the script, it finishes normal but when I let the crontab run the script it goes error.

RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12162: TNS:net service name is incorrectly specified

Please suggest.

Thanks&regards,
Natraj

see post #9, there are a lot of tips. Did you check all of them? Please post the result.

Checking that you are aware there are environment differences between an interactive command and a command run by crontab. Not all of the setup in .bash_profile gets run. Plus anything you typo interactively, like setting your oracle environment, don't happen. Find those differences and add them to your script.

Error messages matter. Error messages have meaning. Read them carefully. This says your Oracle environment variables aren't set. Which is expected for a crontab run.

Let's see the lines of your script that set ORACLE_SID, ORACLE_BASE, ORACLE_HOME. Because those variables do need to be set in your script as it's not being run interactively.

This sounds *VERY* familiar:
https://www.linuxquestions.org/quest...ab-4175603618/

You've been working with Oracle for some time now...have you contacted them for assistance with your scripts??? Have you looked at any of the MANY examples you can find by putting "how to run an rman script through cron on linux" into Google?? Things such as:
https://oracle-base.com/articles/mis...hell-scripting

As you were told before, you need to specify these variables in your script. Are you???

1 members found this post helpful.

The following is the script I wrote:

#!/bin/bash

echo "***********Archive file deletion started at `date`***********"
echo " "
export ORACLE_HOME=/u01/oracle_home/contentdb
#cd $ORACLE_HOME
/u01/oracle_home/contentdb/bin/rman <<EOF
connect target /;
connect CATALOG cat/catalog@conprddb;
spool msglog to '/u02/backup/log/rman_archive_del_new.log'
change archivelog all crosscheck;
delete noprompt expired archivelog all;

exit;
EOF
echo "The archival process ended at `date`">>/u02/backup/rman/rman_archive_del1.log

this was the first hit using duckduckgo: http://www.dba-oracle.com/t_ora_1216...rvice_name.htm

Posting a script is useless. You need to explain if you have tried it, what's happened, what was expected ... The script itself is not enough to go further.