On Jul 11, 2006, at 3:09 AM, zareyna wrote:

I have changed the permission for the errorlog. Still I still have the
error.

On another database server , when I execute dsmapipw in
/usr/opt/db2_08_01/adsm64/dsmapipw, I received " Segmentation Fault
(coredump) and my offline fullbackup failed with error : SQL2079N
Return
code 30.

Did I execute the correct dsmapipw? There 2 folders, adsm and
adsm64 and I
execute the dsmapipw in adsm64.

Appreciate if anyone could give me any suggestions to troubleshoot
this 2
errors.

Some considerations...

IBM Technote 1212707 talks about the error condition.  Don't be shy
about searching the IBM site for helpful info.  ADSM-L can provide
some informal assistance, but the definitive info is on the IBM site.

You haven't revealed what bitmode is in play.  As IBM advises: "The
TSM API bit level needs to match the DB2 bit level; the bit level of
the OS does not affect this. For example, if a 32bit DB2 instance is
installed on a 64bit AIX OS, then the 32bit TSM API should be
installed to match the bit level of the DB2 instance."

Make sure that "the errorlog" is the dsmierror.log, and that DSMI_LOG
allows its use in a directory which is writable.  You can use the AIX
'touch' command like 'touch $DSMI_LOG/whatever' to verify writability
in the directory.  If your executions have created that error log,
then by all means inspect it for supplementary info on the problem.

The environment variables should be in effect within the process
running the DB2 instance, not the process running the 'db2 backup'
command.

Be sure to follow the instructions in redbook "Backing Up DB2 Using
IBM Tivoli Storage Manager".

You haven't told us what level of the TSM API you are using.
Segfaults may occur because of the use of incorrect values; but they
are software defects, and applying the latest maintenance level may
correct them.  If not, TSM Support should be contacted.

  Richard Sims