Re: SQL2062N: Reason code =406
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. Thanks, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jacques Van Den Berg Sent: Monday, July 10, 2006 10:05 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SQL2062N: Reason code =406 Check file permissions for your errorlog file... Jacques van den Berg TSM / SAP Storage Administrator Pick 'n Pay IT Email : [EMAIL PROTECTED] Tel : 021 - 658 1711 Fax : 021 - 658 1699 Mobile : 082 - 653 8164 Dis altyd lente in die hart van die mens wat God en sy medemens liefhet (John Vianney). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of zareyna Sent: Monday, July 10, 2006 11:14 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SQL2062N: Reason code =406 Hi all, Has anyone has ever countered this problem: SQL2062N An error occurred while accessing media /home/db2admin/sqllib/adsm/libtsm.a. Reason code: 406. Below are the steps that I have done: 1. Setup the environment variables as below DSMI_DIR=/usr/tivoli/tsm/client/api/bin64 DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin64/dsm.opt DSMI_LOG=/usr/tivoli/tsm/client/api/bin64 export DSMI_DIR DSMI_CONFIG DSMI_LOG 2. Copy the dsm.opt and dsm.sys in the /usr/tivoli/tsm/client/api/bin64 /usr/tivoli/tsm/client/api/bin64 # ls -l total 12168 -r 1 root system 108626 Jul 05 12:33 db2uext2.c -rwxrwxrwx 1 root system 763 Jul 10 16:27 dsm.opt -rw-r--r-- 1 root system 782 Sep 17 2005 dsm.opt.smp -rw--- 1 root system 1077 Jul 10 14:08 dsm.sys DSM.OPT SErvername TSM_Server1 DSM.SYS SErvername TSM_SERVER1 COMMMethod TCPip tcpport1500 TCPServeraddress 10.211.214.18 tcpclientaddress 10.211.214.11 passwordaccess generate schedmodeprompted NODENAME PRDDBLA1_DB2 3. Set db2 Userexit=YES, LOGRETAIN= YES 4. Backup database : Offline = SUCCESS 5. Backup database : Online= FAILED (receive the above error prompt: SQL2062N) Our database is DB 8.2.4 running on AIX 5.1 Is there any step that I have missed out? Thanks, Regards, Zareyna Salim Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED] Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.10/384 - Release Date: 7/10/2006
Re: 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
SQL2062N: Reason code =406
Hi all, Has anyone has ever countered this problem: SQL2062N An error occurred while accessing media /home/db2admin/sqllib/adsm/libtsm.a. Reason code: 406. Below are the steps that I have done: 1. Setup the environment variables as below DSMI_DIR=/usr/tivoli/tsm/client/api/bin64 DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin64/dsm.opt DSMI_LOG=/usr/tivoli/tsm/client/api/bin64 export DSMI_DIR DSMI_CONFIG DSMI_LOG 2. Copy the dsm.opt and dsm.sys in the /usr/tivoli/tsm/client/api/bin64 /usr/tivoli/tsm/client/api/bin64 # ls -l total 12168 -r 1 root system 108626 Jul 05 12:33 db2uext2.c -rwxrwxrwx 1 root system 763 Jul 10 16:27 dsm.opt -rw-r--r-- 1 root system 782 Sep 17 2005 dsm.opt.smp -rw--- 1 root system 1077 Jul 10 14:08 dsm.sys DSM.OPT SErvername TSM_Server1 DSM.SYS SErvername TSM_SERVER1 COMMMethod TCPip tcpport1500 TCPServeraddress 10.211.214.18 tcpclientaddress 10.211.214.11 passwordaccess generate schedmodeprompted NODENAME PRDDBLA1_DB2 3. Set db2 Userexit=YES, LOGRETAIN= YES 4. Backup database : Offline = SUCCESS 5. Backup database : Online= FAILED (receive the above error prompt: SQL2062N) Our database is DB 8.2.4 running on AIX 5.1 Is there any step that I have missed out? Thanks, Regards, Zareyna Salim
Re: SQL2062N: Reason code =406
You can search www.ibm.com using the message number and reason code, which yields Technote 1083522 regarding common cause. Richard Sims
Re: SQL2062N: Reason code =406
Check file permissions for your errorlog file... Jacques van den Berg TSM / SAP Storage Administrator Pick 'n Pay IT Email : [EMAIL PROTECTED] Tel : 021 - 658 1711 Fax : 021 - 658 1699 Mobile : 082 - 653 8164 Dis altyd lente in die hart van die mens wat God en sy medemens liefhet (John Vianney). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of zareyna Sent: Monday, July 10, 2006 11:14 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SQL2062N: Reason code =406 Hi all, Has anyone has ever countered this problem: SQL2062N An error occurred while accessing media /home/db2admin/sqllib/adsm/libtsm.a. Reason code: 406. Below are the steps that I have done: 1. Setup the environment variables as below DSMI_DIR=/usr/tivoli/tsm/client/api/bin64 DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin64/dsm.opt DSMI_LOG=/usr/tivoli/tsm/client/api/bin64 export DSMI_DIR DSMI_CONFIG DSMI_LOG 2. Copy the dsm.opt and dsm.sys in the /usr/tivoli/tsm/client/api/bin64 /usr/tivoli/tsm/client/api/bin64 # ls -l total 12168 -r 1 root system 108626 Jul 05 12:33 db2uext2.c -rwxrwxrwx 1 root system 763 Jul 10 16:27 dsm.opt -rw-r--r-- 1 root system 782 Sep 17 2005 dsm.opt.smp -rw--- 1 root system 1077 Jul 10 14:08 dsm.sys DSM.OPT SErvername TSM_Server1 DSM.SYS SErvername TSM_SERVER1 COMMMethod TCPip tcpport1500 TCPServeraddress 10.211.214.18 tcpclientaddress 10.211.214.11 passwordaccess generate schedmodeprompted NODENAME PRDDBLA1_DB2 3. Set db2 Userexit=YES, LOGRETAIN= YES 4. Backup database : Offline = SUCCESS 5. Backup database : Online= FAILED (receive the above error prompt: SQL2062N) Our database is DB 8.2.4 running on AIX 5.1 Is there any step that I have missed out? Thanks, Regards, Zareyna Salim Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED] Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED]
SQL2062N Reason code: 406 When backing up DB2
Se are getting the following error when trying to back up our DB2 database: BACKUP DATABASE SWORDDB ONLINE USE TSM OPEN 1 SESSIONS WITH 4 BUFFERS BUFFER 1024 SQL2062N An error occurred while accessing media /home/jail/sqllib/adsm/libtadsm.a. Reason code: 406. Things were working fine just a few days ago. Then DB2 crashed due to a load job filling up the log file system. Once we got the log thing cleaned up our database reported inconsistent state. We got that cleared up, but now we get this error when we try to take a TSM backup. Our test database backups up fine. Our production DB uses the SAME user exit as test, and mirrors the test profiles. Any ideas? This worked fine before we had the DB2 problems. We have restarted DB2 and Tivoli multiple times. Thanks, Jerry Our main DB2/TSM left recently - Do you Yahoo!? Yahoo! Mail is new and improved - Check it out!
Re: SQL2062N Reason code: 406 When backing up DB2
... BACKUP DATABASE SWORDDB ONLINE USE TSM OPEN 1 SESSIONS WITH 4 BUFFERS BUFFER 1024 SQL2062N An error occurred while accessing media /home/jail/sqllib/adsm/libtadsm.a. Reason code: 406. The Reason Code is the TSM API return code, which you can find in the API manual or the TSM Messages manual, indicating that the options file cannot be found, perhaps because of an errant environment variable. You can see more about the error by searching the IBM site for the essential keywords in the problem:+reason +code +406 +SQL2062N Richard Sims
