Hi All, I have managed to solve the problems below: It lead me to lot of error code; Starting with Reason Code 137, Segementation Fault, 406, 106 . Below were the steps or solution that I have done. Thanks for all the tips. Now my DB backup run succesfully and now trying to set the DB backup on SAN. Hope I will have a succesful configuration on the SAN.
Reason Code 137: Changed the password of client and server communication (which I key in the same password). DSMAPIPW works. Segmentation Fault: Upgrade the TSM API to the latest from 5.3.2 to 5.3.4. The Servers and BAC are 5.3.2. Dunno whether it would create a prob someday. Reason Code 406 : Dsm.sys and dsm.opt permission to chmod to 777/775 Reason Code 106: 1. try chmod /db2/SID/log_dir/NODE0000/ dir's as 775/777 (even for the user) 2. then cd /home/db2sid/sqllib/adsm (or wherever you put the TSM stuff, and the TSM dir should be 775 at a min), Remove all dsm logs for the db2 instance (*log, A*, U*). Wait a min until logs don't recreate 3. then retry backup 4. new logs should be produced 5. if that fails - check all db2sid files are 755 or 775 check all root/system owned files are 777 accessible Thanks, Regards, Zareyna Salim -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, July 11, 2006 7:54 PM To: [email protected] Subject: Re: [ADSM-L] SQL2062N: Reason code =406 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 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.10/385 - Release Date: 7/11/2006
