Error Initialize Environment Failed With Tsm Return Code 106
Contents |
restore or log archive operation via TSM in a multi-partitioned database environment An error occurred while accessing
Error Initialize Environment Failed With Tsm Return Code 106 Db2
media; SQL2062N Technote (troubleshooting) Problem(Abstract) This document provides troubleshooting information for error initialize environment failed with tsm return code 406 the situation where your BACKUP DATABASE or RESTORE DATABASE commands or an attempt to perform a log error initialize session failed with tsm return code 137 archive fail with an SQL2062N error. In particular, this information pertains to when you are using Tivoli Storage Manager (TSM) in a DB2 instance with multiple database partitions.
Initialize Session Failed With Tsm Return Code 168
Symptom An example of the error is as follows: SQL2062N An error occurred while accessing media "/home/db2inst1/sqllib/adsm/libtsm.a". Reason code: "106". Cause In order to work properly with the TSM server, the environment variables used by the TSM client API (for example, DSMI_CONFIG, DSMI_DIR and DSMI_LOG) have to be set up correctly. In an instance with a single
Sql2033n Tsm Reason Code: "106"
database partition, this can be done by simply setting these variables in the .profile file for the instance owner. That method will not work for a multi-partition environment, however. In a multi-partitioned database environment, all of the environment variables used by the TSM client API have to be set in the
full db DBNAME) failed with the following tsm reason codes error: Error: Initialize environment failed with TSM return code 106
Tsm Reason Code 50
As per dsmrc.h return code 106 indicates a permission problem: #define DSM_RC_ACCESS_DENIED 106 /* sql2033n reason code 11 denied due to improper permission */ which was weird, since the user in question is a member of the DB2ADMNS group that is supposed http://www-01.ibm.com/support/docview.wss?uid=swg21251983 to have all required permissions. Further investigation revealed, however, that the issue was indeed caused by missing permissions, namely missing write access to the TSM log directory (%DSMI_LOG%). Access had been removed, because the inheritance settings of a group policy for setting permissions on a parent folder had been http://www.planetcobalt.net/sdb/db2_backup_query_error.shtml (mis-)configured to replace permissions on subfolders instead of just propagating the added permissions. Changing the inheritance setting in the group policy and granting the DB2ADMNS group Modify permissions on the log directory again resolved the issue. Posted 23:40 [permalink] Archives 2016September (1)May (1)April (1)February (1)January (1)2015December (2)September (1)June (2)March (4)February (1)January (5)2014July (2)June (2)March (3)February (3)2013December (2)October (2)August (1)June (1)April (1)March (2)February (1)January (1)2012November (2)October (1)August (1)2011March (1)February (1)January (2)2010June (1)May (1)2009April (1)January (1)2008December (2)October (1)2005February (1)2004December (1)2003December (1) ACL Active Directory Agent Array Backscatter Backup Client cluster Database DataTable DB2 domain dual-boot dynamic Execution Policy Extension file server Filemon filter Group group policy Hyper-V Internet Explorer Linux log Logger Logon Lync macro mail migration Perl permissions plugin policy PowerShell Regmon replication group Repository Restore Scope SCVMM SeaMonkey Server 2012 Share SMTP smtpprox SQL Server Suspect TSM VBA VBScript VBSdoc VSS Writers Windows
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time https://www.experts-exchange.com/questions/28225158/Error-Initialize-environment-failed-with-TSM-return-code-610-TSM-Client-6-2-5.html Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error: Initialize environment failed with TSM return code 610 TSM Client 6.2.5 Want to Advertise Here? Solved Error: Initialize environment failed with TSM return code 610 TSM Client 6.2.5 Posted on 2013-08-28 Unix OS 1 Verified Solution failed with 2 Comments 2,246 Views Last Modified: 2013-08-28 OK, after the installation of TSM CLient 6.2.5 db2 backup is not working.. see ():[db2d] /db2/db2d/tsm -> db2adutl query full Error: Initialize environment failed with TSM return code 610 Believe me, I've been more than hour and half searching but no success... maybe you have an idea about this... I seems to be a variable environment issue 0 Question by:sminfo Facebook failed with tsm Twitter LinkedIn Google LVL 68 Active 1 day ago Best Solution bywoolmilkporc Did you install the 64 bit client? If so, are you aware that the client as well as the api are now in "bin64" subdirectories? The DSMI_DIR and DSMI_CONFIG environment variables set in sqllib/userprofile Go to Solution 2 Comments LVL 68 Overall: Level 68 Unix OS 53 Message Active 1 day ago Accepted Solution by:woolmilkporc2013-08-28 Did you install the 64 bit client? If so, are you aware that the client as well as the api are now in "bin64" subdirectories? The DSMI_DIR and DSMI_CONFIG environment variables set in sqllib/userprofile might be of interest here! 0 Message Author Closing Comment by:sminfo2013-08-28 Yes... and also we had to restart db2 and it's already working.. Thanks.. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Featured Post Free Trending Threat Insights Every Day Promoted by Recorded Future Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses deliv