Backup via Cron

[Toralf Kirsten]

Hi,
we are using DB2 on Fedora

We try to backup the datbases automatically every day (night). For this
purpose, I wrote two scripts, a shell (bash) and a sql script.
The shell script set the profile and call the sql script.

******* short form
/home/db2iusr/sqllib/db2profile
/opt/IBM/db2/V8.1/bin/db2 -tvf /db2/backup/db2-backup.sql
*******

The sql script performs the backup like this:
*******
force application all;
backup database <db> user <user> using <pw> to <dir> without prompting;
quit;
*******

Problem:
--------
When we call the shell script manually using the bash, there is no
problem. But, if we use the unix cron to backup the databases daily and
automatically we receive every time the following error

SQL10007N Message "-1390" could not be retrieved. Reason code: "1".

If we paste all rows from the db2profile to shell script we receive the
same error message with reason code 2.

Any suggestions would be helpful.
Toralf

[Joachim Mueller]

Toralf,

on AIX I have to put the whole PATH in the .ksh-Script

PATH=...
export PATH

But, also you can use the DB2 Scheduler with CC, it works very well.

regards,
Joachim Müller

"Toralf Kirsten" <tk******@izbi.uni-leipzig.de> schrieb im Newsbeitrag
news:ca**********@news.uni-leipzig.de...

Hi,
we are using DB2 on Fedora

We try to backup the datbases automatically every day (night). For this
purpose, I wrote two scripts, a shell (bash) and a sql script.
The shell script set the profile and call the sql script.

******* short form
/home/db2iusr/sqllib/db2profile
/opt/IBM/db2/V8.1/bin/db2 -tvf /db2/backup/db2-backup.sql
*******

The sql script performs the backup like this:
*******
force application all;
backup database <db> user <user> using <pw> to <dir> without prompting;
quit;
*******

Problem:
--------
When we call the shell script manually using the bash, there is no
problem. But, if we use the unix cron to backup the databases daily and
automatically we receive every time the following error

SQL10007N Message "-1390" could not be retrieved. Reason code: "1".

If we paste all rows from the db2profile to shell script we receive the
same error message with reason code 2.

Any suggestions would be helpful.
Toralf

[Ian]

Toralf Kirsten wrote:

Hi,
we are using DB2 on Fedora

We try to backup the datbases automatically every day (night). For this
purpose, I wrote two scripts, a shell (bash) and a sql script.
The shell script set the profile and call the sql script.

******* short form
/home/db2iusr/sqllib/db2profile

This should read:

. /home/db2iusr/sqllib/db2profile

The '.' executes the db2profile in the current shell (i.e. all environment
variables are exported in the _current_ shell).

As you've written it, you are executing the db2profile in a sub shell.
The variables get set in the sub-shell, and then the sub-shell exits.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

[Buck Nuggets]

Toralf Kirsten <tk******@izbi.uni-leipzig.de> wrote in message news:<ca**********@news.uni-leipzig.de>...

Are you really reading the db2profile? On aix you would need to 'dot'
it rather than run it - since it doesn't have a #! at the top.

So, instead of this:

******* short form
/home/db2iusr/sqllib/db2profile
/opt/IBM/db2/V8.1/bin/db2 -tvf /db2/backup/db2-backup.sql
*******
I'd have this:
******* short form
. /home/db2iusr/sqllib/db2profile
db2 -tvf /db2/backup/db2-backup.sql
*******

The fact that you could run it manually could easily be masked by your
own user profile, unless you explicitely isabled it.

buck

[Toralf Kirsten]

Ian,
many thanks for your reply.
You are right. It's a mistake and I corrected the script.
The shell script is now like this:
*******
.. /home/db2iusr/sqllib/db2profile
/opt/IBM/db2/V8.1/bin/db2 -tvf /db2/backup/db2-backup.sql
*******

The sql script is like this:
*******
force application all;
backup database <db> user <user> using <pw> to <dir> without prompting;
quit;
*******

Now I get the same error with reason code 2.
SQL10007N Message "-1390" could not be retrieved. Reason code: "2".
I think it is a simple error, but I don't know what's wrong.

Thanks, Toralf
Ian wrote:

Toralf Kirsten wrote:

Hi,
we are using DB2 on Fedora

We try to backup the datbases automatically every day (night). For
this purpose, I wrote two scripts, a shell (bash) and a sql script.
The shell script set the profile and call the sql script.

******* short form
/home/db2iusr/sqllib/db2profile

This should read:

. /home/db2iusr/sqllib/db2profile

The '.' executes the db2profile in the current shell (i.e. all environment
variables are exported in the _current_ shell).

As you've written it, you are executing the db2profile in a sub shell.
The variables get set in the sub-shell, and then the sub-shell exits.

[David Mooney]

> When we call the shell script manually using the bash, there is no

problem. But, if we use the unix cron to backup the databases daily and
automatically we receive every time the following error

SQL10007N Message "-1390" could not be retrieved. Reason code: "1".

This often means that DB2INSTANCE is not set.

dave

[Toralf Kirsten]

Joachim,
thanks for your reply.
After modifying the script by using the dot in front of calling the
db2profile script, I print out two variables within my script which are
set in db2profile script.

The result is:
backup uses the DB2INSTANCE: db2iusr
use the paths:
/sbin:/bin:/usr/sbin:/usr/bin:/home/db2iusr/sqllib/bin:/home/db2iu
sr/sqllib/adm:/home/db2iusr/sqllib/misc

The db2 instance is set correctly. But, I'm not really sure which
additional path I have to set.

Now, I get the error
SQL10007N Message "-1390" could not be retrieved. Reason code: "2".

Toralf

Joachim Mueller wrote:

Toralf,

on AIX I have to put the whole PATH in the .ksh-Script

PATH=...
export PATH

But, also you can use the DB2 Scheduler with CC, it works very well.

regards,
Joachim Müller

[Toralf Kirsten]

Hi,
just to give the solution of the problem.
There were two errors.

First, as proposed by other guys, the dot in front of the command
loading the db2 environment was missed. The right string is as follows
.. /home/db2iusr/sqllib/db2profile or alternatively
source /home/db2iusr/sqllib/db2profile

Second, we set the lang variables $LANG to en_US.UTF-8 which was set in
the normal user environment but not in the CRON environment.

Hope it helps you in similar cases.
Cheers, Toralf
Toralf Kirsten wrote:

Hi,
we are using DB2 on Fedora

We try to backup the datbases automatically every day (night). For this
purpose, I wrote two scripts, a shell (bash) and a sql script.
The shell script set the profile and call the sql script.

******* short form
/home/db2iusr/sqllib/db2profile
/opt/IBM/db2/V8.1/bin/db2 -tvf /db2/backup/db2-backup.sql
*******

The sql script performs the backup like this:
*******
force application all;
backup database <db> user <user> using <pw> to <dir> without prompting;
quit;
*******

Problem:
--------
When we call the shell script manually using the bash, there is no
problem. But, if we use the unix cron to backup the databases daily and
automatically we receive every time the following error

SQL10007N Message "-1390" could not be retrieved. Reason code: "1".

If we paste all rows from the db2profile to shell script we receive the
same error message with reason code 2.

Any suggestions would be helpful.
Toralf