For my case, it’s as simple as updating the hostname information defined in sqllib/db2nodes.cfg configuration file!
-http://www.walkernews.net/2007/09/07/how-to-fix-db2-sql6048n-error-of-db2start/-
2011年7月20日
2011年7月17日
Problems with restarting the upgrade process after database insertion failure
Symptoms
When you try to restart the process, using either the upgrade wizard (dsmupgdx) or commands, you receive messages that the database already exists, or that directories are not empty.
Causes
The problem occurs because a database instance was already created, despite the failure. Directories that you specified in the wizard or with the DSMSERV LOADFORMAT command might no longer be empty because the failed process started to write information in these directories. To do the formatting operation again, the directories must be empty.
Resolving the problem
Try the following actions to resolve the problem.
Ensure that you are logged in with the same user ID that you were using when the insertion operation failed. This should be the user ID that you created specifically for the server instance that you were upgrading when the failure occurred.
Attention: Ensure that you are using the correct user ID. The database that is owned by the user ID that you log in with now is the database that will be destroyed in the following step. Do not perform the following steps when you are logged in with a user ID that owns a valid, working V6 server instance.
Remove the database instance that was created.
dsmserv removedb TSMDB1
Alternate method: If the DSMSERV REMOVEDB command fails for some reason, use the DB2® command to drop the database. Issue the following commands:
db2start
db2 drop db tsmdb1
To reuse the database and log directories that you specified in the failed attempt to create the server instance, verify that each directory is now empty.
Restart the upgrade wizard for the server instance that you are upgrading.
If you are using commands, restart at the step in which you issue the DSMSERV LOADFORMAT command.
--http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=%2Fcom.ibm.itsm.srv.upgrd.doc%2Fts_srv_upgrd_restartupgrd.html--
When you try to restart the process, using either the upgrade wizard (dsmupgdx) or commands, you receive messages that the database already exists, or that directories are not empty.
Causes
The problem occurs because a database instance was already created, despite the failure. Directories that you specified in the wizard or with the DSMSERV LOADFORMAT command might no longer be empty because the failed process started to write information in these directories. To do the formatting operation again, the directories must be empty.
Resolving the problem
Try the following actions to resolve the problem.
Ensure that you are logged in with the same user ID that you were using when the insertion operation failed. This should be the user ID that you created specifically for the server instance that you were upgrading when the failure occurred.
Attention: Ensure that you are using the correct user ID. The database that is owned by the user ID that you log in with now is the database that will be destroyed in the following step. Do not perform the following steps when you are logged in with a user ID that owns a valid, working V6 server instance.
Remove the database instance that was created.
dsmserv removedb TSMDB1
Alternate method: If the DSMSERV REMOVEDB command fails for some reason, use the DB2® command to drop the database. Issue the following commands:
db2start
db2 drop db tsmdb1
To reuse the database and log directories that you specified in the failed attempt to create the server instance, verify that each directory is now empty.
Restart the upgrade wizard for the server instance that you are upgrading.
If you are using commands, restart at the step in which you issue the DSMSERV LOADFORMAT command.
--http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=%2Fcom.ibm.itsm.srv.upgrd.doc%2Fts_srv_upgrd_restartupgrd.html--
2011年6月30日
TSM v6 select statement example，DB2中有關日期和時間的函數，及應用
APAR status
Closed as documentation error.
Error description
The "Changes to the SELECT command" section in the
Tivoli Storage Manager V6.1 Information Center can be found at
the following web site :
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ib
m.itsm.srv.upgrd.doc/r_srv_upgrd_cmd_select.html
The same section can also be found in the Tivoli Storage Manager
V6.2 Information Center which can be found at the following web
site :
http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.
ibm.itsm.srv.upgrd.doc/r_srv_upgrd_cmd_select.html
This section mentions the following :
The following statement is an example of correct usage:
select * from actlog where second(current_time-date_time) <= 60 The above select statement does not work. When issued on a V6.1 server, it produces the following error : ANR0162W Supplemental database diagnostic information: -1:42819:-402 ([IBM][CLI Driver][DB2/NT64] SQL0402N The data type of an operand of an arithmetic function or operation "-" is not numeric. SQLSTATE=42819). ANR0516E SQL processing for statement select * from actlog where second (current_time-date_time ) <= 60 failed. ANS8001I Return code 3. The example incorrectly lists current_time when it should be current_timestamp. Also, the intent of the above statement is to provide the actlog entries from the last 60 seconds. To achieve this, the DB2 timestamptdiff can be used. To list the actlog entries for the last 60 seconds, use : select * from actlog where TIMESTAMPDIFF(2,CHAR(current_timestamp-date_time)) <= 60 To list the actlog entries for the last 60 minutes, use : select * from actlog where TIMESTAMPDIFF(4,CHAR(current_timestamp-date_time)) <= 60 For more information on the DB2 timestampdiff function, refer to the DB2 information center link below : http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.i bm.db2.luw.sql.ref.doc/doc/r0000861.html TSM Versions Affected: TSM Servers V6.1 on all platforms. DAYNAME 返回一個大小寫混合的字符串，對於參數的日部分，用星期表示這一天的名稱（例如，Friday）。 DAYOFWEEK 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期日。 DAYOFWEEK_ISO 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期一。 DAYOFYEAR 返回參數中一年中的第幾天，用範圍在 1-366 的整數值表示。 DAYS 返回日期的整數表示。 JULIAN_DAY 返回從公元前 4712 年 1 月 1 日（儒略日曆的開始日期）到參數中指定日期值之間的天數，用整數值表示。 MIDNIGHT_SECONDS 返回午夜和參數中指定的時間值之間的秒數，用範圍在 0 到 86400 之間的整數值表示。 MONTHNAME 對於參數的月部分的月份，返回一個大小寫混合的字符串（例如，January）。 TIMESTAMP_ISO 根據日期、時間或時間戳記參數而返回一個時間戳記值。 TIMESTAMP_FORMAT 從已使用字符模板解釋的字符串返回時間戳記。 TIMESTAMPDIFF 根據兩個時間戳記之間的時差，返回由第一個參數定義的類型表示的估計時差。 TO_CHAR 返回已用字符模板進行格式化的時間戳記的字符表示。TO_CHAR 是 VARCHAR_FORMAT 的同義詞。 TO_DATE 從已使用字符模板解釋過的字符串返回時間戳記。TO_DATE 是 TIMESTAMP_FORMAT 的同義詞。 WEEK 返回參數中一年的第幾周，用範圍在 1-54 的整數值表示。以星期日作為一周的開始。 WEEK_ISO 返回參數中一年的第幾周，用範圍在 1-53 的整數值表示。 要使當前時間或當前時間戳記調整到 GMT/CUT，則把當前的時間或時間戳記減去當前時區寄存器： current time - current timezone current timestamp - current timezone 給定了日期、時間或時間戳記，則使用適當的函數可以單獨抽取出（如果適用的話）年、月、日、時、分、秒及微秒各部分： YEAR (current timestamp) MONTH (current timestamp) DAY (current timestamp) HOUR (current timestamp) MINUTE (current timestamp) SECOND (current timestamp) MICROSECOND (current timestamp) 因為沒有更好的術語，所以您還可以使用英語來執行日期和時間計算： current date + 1 YEAR current date + 3 YEARS + 2 MONTHS + 15 DAYS current time + 5 HOURS - 3 MINUTES + 10 SECONDS 從時間戳記單獨抽取出日期和時間也非常簡單： DATE (current timestamp) TIME (current timestamp) 而以下示例描述了如何獲得微秒部分歸零的當前時間戳記： CURRENT TIMESTAMP - MICROSECOND (current timestamp) MICROSECONDS 如果想將日期或時間值與其它文本相銜接，那麼需要先將該值轉換成字符串。為此，只要使用 CHAR() 函數： char(current date) char(current time) char(current date + 12 hours) 要將字符串轉換成日期或時間值，可以使用： TIMESTAMP ('2002-10-20-12.00.00.000000') TIMESTAMP ('2002-10-20 12:00:00') DATE ('2002-10-20') DATE ('10/20/2002') TIME ('12:00:00') TIME ('12.00.00') TIMESTAMP()、DATE() 和 TIME() 函數接受更多種格式。上面幾種格式只是示例，我將把它作為一個練習，讓讀者自己去發現其它格式。 有時，您需要知道兩個時間戳記之間的時差。為此，DB2 提供了一個名為 TIMESTAMPDIFF() 的內置函數。但該函數返回的是近似值，因為它不考慮閏年，而且假設每個月只有 30 天。以下示例描述了如何得到兩個日期的近似時差： timestampdiff (, char(
timestamp('2002-11-30-00.00.00')-
timestamp('2002-11-08-00.00.00')))
對於，可以使用以下各值來替代，以指出結果的時間單位：
1 = 秒的小數部分
2 = 秒
4 = 分
8 = 時
16 = 天
32 = 周
64 = 月
128 = 季度
256 = 年
當日期很接近時使用 timestampdiff() 比日期相差很大時精確。如果需要進行更精確的計算，可以使用以下方法來確定時差（按秒計）：
(DAYS(t1) - DAYS(t2)) * 86400 +
(MIDNIGHT_SECONDS(t1) - MIDNIGHT_SECONDS(t2))
為方便起見，還可以對上面的方法創建 SQL 用戶定義的函數：
CREATE FUNCTION secondsdiff(t1 TIMESTAMP, t2 TIMESTAMP)
RETURNS INT
RETURN (
(DAYS(t1) - DAYS(t2)) * 86400 +
(MIDNIGHT_SECONDS(t1) - MIDNIGHT_SECONDS(t2))
)
@
如果需要確定給定年份是否是閏年，以下是一個很有用的 SQL 函數，您可以創建它來確定給定年份的天數：
CREATE FUNCTION daysinyear(yr INT)
RETURNS INT
RETURN (CASE (mod(yr, 400)) WHEN 0 THEN 366 ELSE
CASE (mod(yr, 4)) WHEN 0 THEN
CASE (mod(yr, 100)) WHEN 0 THEN 365 ELSE 366 END
ELSE 365 END
END)@
最後，以下是一張用於日期操作的內置函數表。它旨在幫助您快速確定可能滿足您要求的函數，但未提供完整的參考。有關這些函數的更多信息，請參考 SQL 參考大全。
SQL 日期和時間函數
DAYNAME 返回一個大小寫混合的字符串，對於參數的日部分，用星期表示這一天的名稱（例如，Friday）。
DAYOFWEEK 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期日。
DAYOFWEEK_ISO 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期一。
DAYOFYEAR 返回參數中一年中的第幾天，用範圍在 1-366 的整數值表示。
DAYS 返回日期的整數表示。
JULIAN_DAY 返回從公元前 4712 年 1 月 1 日（儒略日曆的開始日期）到參數中指定日期值之間的天數，用整數值表示。
MIDNIGHT_SECONDS 返回午夜和參數中指定的時間值之間的秒數，用範圍在 0 到 86400 之間的整數值表示。
MONTHNAME 對於參數的月部分的月份，返回一個大小寫混合的字符串（例如，January）。
TIMESTAMP_ISO 根據日期、時間或時間戳記參數而返回一個時間戳記值。
TIMESTAMP_FORMAT 從已使用字符模板解釋的字符串返回時間戳記。
TIMESTAMPDIFF 根據兩個時間戳記之間的時差，返回由第一個參數定義的類型表示的估計時差。
TO_CHAR 返回已用字符模板進行格式化的時間戳記的字符表示。TO_CHAR 是 VARCHAR_FORMAT 的同義詞。
TO_DATE 從已使用字符模板解釋過的字符串返回時間戳記。TO_DATE 是 TIMESTAMP_FORMAT 的同義詞。
WEEK 返回參數中一年的第幾周，用範圍在 1-54 的整數值表示。以星期日作為一周的開始。
WEEK_ISO 返回參數中一年的第幾周，用範圍在 1-53 的整數值表示。
link from
https://www-304.ibm.com/support/docview.wss?uid=swg1IC67375
http://big5.webasp.net/article/21/20822.htm
Closed as documentation error.
Error description
The "Changes to the SELECT command" section in the
Tivoli Storage Manager V6.1 Information Center can be found at
the following web site :
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ib
m.itsm.srv.upgrd.doc/r_srv_upgrd_cmd_select.html
The same section can also be found in the Tivoli Storage Manager
V6.2 Information Center which can be found at the following web
site :
http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.
ibm.itsm.srv.upgrd.doc/r_srv_upgrd_cmd_select.html
This section mentions the following :
The following statement is an example of correct usage:
select * from actlog where second(current_time-date_time) <= 60 The above select statement does not work. When issued on a V6.1 server, it produces the following error : ANR0162W Supplemental database diagnostic information: -1:42819:-402 ([IBM][CLI Driver][DB2/NT64] SQL0402N The data type of an operand of an arithmetic function or operation "-" is not numeric. SQLSTATE=42819). ANR0516E SQL processing for statement select * from actlog where second (current_time-date_time ) <= 60 failed. ANS8001I Return code 3. The example incorrectly lists current_time when it should be current_timestamp. Also, the intent of the above statement is to provide the actlog entries from the last 60 seconds. To achieve this, the DB2 timestamptdiff can be used. To list the actlog entries for the last 60 seconds, use : select * from actlog where TIMESTAMPDIFF(2,CHAR(current_timestamp-date_time)) <= 60 To list the actlog entries for the last 60 minutes, use : select * from actlog where TIMESTAMPDIFF(4,CHAR(current_timestamp-date_time)) <= 60 For more information on the DB2 timestampdiff function, refer to the DB2 information center link below : http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.i bm.db2.luw.sql.ref.doc/doc/r0000861.html TSM Versions Affected: TSM Servers V6.1 on all platforms. DAYNAME 返回一個大小寫混合的字符串，對於參數的日部分，用星期表示這一天的名稱（例如，Friday）。 DAYOFWEEK 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期日。 DAYOFWEEK_ISO 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期一。 DAYOFYEAR 返回參數中一年中的第幾天，用範圍在 1-366 的整數值表示。 DAYS 返回日期的整數表示。 JULIAN_DAY 返回從公元前 4712 年 1 月 1 日（儒略日曆的開始日期）到參數中指定日期值之間的天數，用整數值表示。 MIDNIGHT_SECONDS 返回午夜和參數中指定的時間值之間的秒數，用範圍在 0 到 86400 之間的整數值表示。 MONTHNAME 對於參數的月部分的月份，返回一個大小寫混合的字符串（例如，January）。 TIMESTAMP_ISO 根據日期、時間或時間戳記參數而返回一個時間戳記值。 TIMESTAMP_FORMAT 從已使用字符模板解釋的字符串返回時間戳記。 TIMESTAMPDIFF 根據兩個時間戳記之間的時差，返回由第一個參數定義的類型表示的估計時差。 TO_CHAR 返回已用字符模板進行格式化的時間戳記的字符表示。TO_CHAR 是 VARCHAR_FORMAT 的同義詞。 TO_DATE 從已使用字符模板解釋過的字符串返回時間戳記。TO_DATE 是 TIMESTAMP_FORMAT 的同義詞。 WEEK 返回參數中一年的第幾周，用範圍在 1-54 的整數值表示。以星期日作為一周的開始。 WEEK_ISO 返回參數中一年的第幾周，用範圍在 1-53 的整數值表示。 要使當前時間或當前時間戳記調整到 GMT/CUT，則把當前的時間或時間戳記減去當前時區寄存器： current time - current timezone current timestamp - current timezone 給定了日期、時間或時間戳記，則使用適當的函數可以單獨抽取出（如果適用的話）年、月、日、時、分、秒及微秒各部分： YEAR (current timestamp) MONTH (current timestamp) DAY (current timestamp) HOUR (current timestamp) MINUTE (current timestamp) SECOND (current timestamp) MICROSECOND (current timestamp) 因為沒有更好的術語，所以您還可以使用英語來執行日期和時間計算： current date + 1 YEAR current date + 3 YEARS + 2 MONTHS + 15 DAYS current time + 5 HOURS - 3 MINUTES + 10 SECONDS 從時間戳記單獨抽取出日期和時間也非常簡單： DATE (current timestamp) TIME (current timestamp) 而以下示例描述了如何獲得微秒部分歸零的當前時間戳記： CURRENT TIMESTAMP - MICROSECOND (current timestamp) MICROSECONDS 如果想將日期或時間值與其它文本相銜接，那麼需要先將該值轉換成字符串。為此，只要使用 CHAR() 函數： char(current date) char(current time) char(current date + 12 hours) 要將字符串轉換成日期或時間值，可以使用： TIMESTAMP ('2002-10-20-12.00.00.000000') TIMESTAMP ('2002-10-20 12:00:00') DATE ('2002-10-20') DATE ('10/20/2002') TIME ('12:00:00') TIME ('12.00.00') TIMESTAMP()、DATE() 和 TIME() 函數接受更多種格式。上面幾種格式只是示例，我將把它作為一個練習，讓讀者自己去發現其它格式。 有時，您需要知道兩個時間戳記之間的時差。為此，DB2 提供了一個名為 TIMESTAMPDIFF() 的內置函數。但該函數返回的是近似值，因為它不考慮閏年，而且假設每個月只有 30 天。以下示例描述了如何得到兩個日期的近似時差： timestampdiff (
timestamp('2002-11-30-00.00.00')-
timestamp('2002-11-08-00.00.00')))
對於
1 = 秒的小數部分
2 = 秒
4 = 分
8 = 時
16 = 天
32 = 周
64 = 月
128 = 季度
256 = 年
當日期很接近時使用 timestampdiff() 比日期相差很大時精確。如果需要進行更精確的計算，可以使用以下方法來確定時差（按秒計）：
(DAYS(t1) - DAYS(t2)) * 86400 +
(MIDNIGHT_SECONDS(t1) - MIDNIGHT_SECONDS(t2))
為方便起見，還可以對上面的方法創建 SQL 用戶定義的函數：
CREATE FUNCTION secondsdiff(t1 TIMESTAMP, t2 TIMESTAMP)
RETURNS INT
RETURN (
(DAYS(t1) - DAYS(t2)) * 86400 +
(MIDNIGHT_SECONDS(t1) - MIDNIGHT_SECONDS(t2))
)
@
如果需要確定給定年份是否是閏年，以下是一個很有用的 SQL 函數，您可以創建它來確定給定年份的天數：
CREATE FUNCTION daysinyear(yr INT)
RETURNS INT
RETURN (CASE (mod(yr, 400)) WHEN 0 THEN 366 ELSE
CASE (mod(yr, 4)) WHEN 0 THEN
CASE (mod(yr, 100)) WHEN 0 THEN 365 ELSE 366 END
ELSE 365 END
END)@
最後，以下是一張用於日期操作的內置函數表。它旨在幫助您快速確定可能滿足您要求的函數，但未提供完整的參考。有關這些函數的更多信息，請參考 SQL 參考大全。
SQL 日期和時間函數
DAYNAME 返回一個大小寫混合的字符串，對於參數的日部分，用星期表示這一天的名稱（例如，Friday）。
DAYOFWEEK 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期日。
DAYOFWEEK_ISO 返回參數中的星期幾，用範圍在 1-7 的整數值表示，其中 1 代表星期一。
DAYOFYEAR 返回參數中一年中的第幾天，用範圍在 1-366 的整數值表示。
DAYS 返回日期的整數表示。
JULIAN_DAY 返回從公元前 4712 年 1 月 1 日（儒略日曆的開始日期）到參數中指定日期值之間的天數，用整數值表示。
MIDNIGHT_SECONDS 返回午夜和參數中指定的時間值之間的秒數，用範圍在 0 到 86400 之間的整數值表示。
MONTHNAME 對於參數的月部分的月份，返回一個大小寫混合的字符串（例如，January）。
TIMESTAMP_ISO 根據日期、時間或時間戳記參數而返回一個時間戳記值。
TIMESTAMP_FORMAT 從已使用字符模板解釋的字符串返回時間戳記。
TIMESTAMPDIFF 根據兩個時間戳記之間的時差，返回由第一個參數定義的類型表示的估計時差。
TO_CHAR 返回已用字符模板進行格式化的時間戳記的字符表示。TO_CHAR 是 VARCHAR_FORMAT 的同義詞。
TO_DATE 從已使用字符模板解釋過的字符串返回時間戳記。TO_DATE 是 TIMESTAMP_FORMAT 的同義詞。
WEEK 返回參數中一年的第幾周，用範圍在 1-54 的整數值表示。以星期日作為一周的開始。
WEEK_ISO 返回參數中一年的第幾周，用範圍在 1-53 的整數值表示。
link from
https://www-304.ibm.com/support/docview.wss?uid=swg1IC67375
http://big5.webasp.net/article/21/20822.htm
2011年6月13日
ANR2968E error with sqlcode -2033 and sqlerrmc 610 during backup db process
Problem(Abstract)
A database backup operation may fail with ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 610.
Symptom
ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 610.
Cause
The proper locale file may not be linked in the correct location if the API or TSM Server was recently upgraded.
Environment
Tivoli Storage Manager 6.1 and 6.2
Diagnosing the problem
Checking the list of files in the 64-bit API directory will reveal that the local directory containing the message codes is missing:
tsm:/opt/tivoli/tsm/client/api/bin64 # ls -ltra
total 5824
-rw-r--r-- 1 root root 0 Dec 3 13:37 dsmerror.log
-rw-rw-r-- 1 root root 486 Jan 27 22:51 dsm.sys
-r-xr-xr-x 1 root bin 3259048 Mar 2 09:58 libApiTSM64.so
-rwsr-xr-x 1 root bin 2670186 Mar 2 09:58 dsmtca
-r--r--r-- 1 root bin 971 Mar 9 03:28 dsm.sys.smp
-r--r--r-- 1 root bin 782 Mar 9 03:28 dsm.opt.smp
drwxr-xr-x 4 root bin 4096 Mar 22 10:50 ..
drwxr-xr-x 2 root bin 4096 Mar 22 10:50 sample
drwxr-xr-x 3 root bin 4096 Mar 24 11:31 .
Resolving the problem
Link the appropriate locale directory to a location inside your /opt/tivoli/tsm/client/api/bin64 location. For example:
tsm:/opt/tivoli/tsm/client/api/bin64 # pwd
/opt/tivoli/tsm/client/api/bin64
tsm:/opt/tivoli/tsm/client/api/bin64 #
ln -s /opt/tivoli/tsm/client/lang/EN_US/ /opt/tivoli/tsm/client/api/bin64
After doing this you can check the link was created properly:
tsm:/opt/tivoli/tsm/client/api/bin64 # ls -ltra
total 5824
-rw-r--r-- 1 root root 0 Dec 3 13:37 dsmerror.log
-rw-rw-r-- 1 root root 486 Jan 27 22:51 dsm.sys
-r-xr-xr-x 1 root bin 3259048 Mar 2 09:58 libApiTSM64.so
-rwsr-xr-x 1 root bin 2670186 Mar 2 09:58 dsmtca
-r--r--r-- 1 root bin 971 Mar 9 03:28 dsm.sys.smp
-r--r--r-- 1 root bin 782 Mar 9 03:28 dsm.opt.smp
drwxr-xr-x 4 root bin 4096 Mar 22 10:50 ..
drwxr-xr-x 2 root bin 4096 Mar 22 10:50 sample
lrwxrwxrwx 1 root root 17 Mar 24 14:46 EN_US -> ../../lang/EN_US/
drwxr-xr-x 3 root bin 4096 Mar 24 14:46 .
After this is done, the database backups should no longer fail with an sqlerrmc of 610. No restart of the Tivoli Storage Manager server is required.
--link from https://www-304.ibm.com/support/docview.wss?uid=swg21425691&wv=1--
A database backup operation may fail with ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 610.
Symptom
ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 610.
Cause
The proper locale file may not be linked in the correct location if the API or TSM Server was recently upgraded.
Environment
Tivoli Storage Manager 6.1 and 6.2
Diagnosing the problem
Checking the list of files in the 64-bit API directory will reveal that the local directory containing the message codes is missing:
tsm:/opt/tivoli/tsm/client/api/bin64 # ls -ltra
total 5824
-rw-r--r-- 1 root root 0 Dec 3 13:37 dsmerror.log
-rw-rw-r-- 1 root root 486 Jan 27 22:51 dsm.sys
-r-xr-xr-x 1 root bin 3259048 Mar 2 09:58 libApiTSM64.so
-rwsr-xr-x 1 root bin 2670186 Mar 2 09:58 dsmtca
-r--r--r-- 1 root bin 971 Mar 9 03:28 dsm.sys.smp
-r--r--r-- 1 root bin 782 Mar 9 03:28 dsm.opt.smp
drwxr-xr-x 4 root bin 4096 Mar 22 10:50 ..
drwxr-xr-x 2 root bin 4096 Mar 22 10:50 sample
drwxr-xr-x 3 root bin 4096 Mar 24 11:31 .
Resolving the problem
Link the appropriate locale directory to a location inside your /opt/tivoli/tsm/client/api/bin64 location. For example:
tsm:/opt/tivoli/tsm/client/api/bin64 # pwd
/opt/tivoli/tsm/client/api/bin64
tsm:/opt/tivoli/tsm/client/api/bin64 #
ln -s /opt/tivoli/tsm/client/lang/EN_US/ /opt/tivoli/tsm/client/api/bin64
After doing this you can check the link was created properly:
tsm:/opt/tivoli/tsm/client/api/bin64 # ls -ltra
total 5824
-rw-r--r-- 1 root root 0 Dec 3 13:37 dsmerror.log
-rw-rw-r-- 1 root root 486 Jan 27 22:51 dsm.sys
-r-xr-xr-x 1 root bin 3259048 Mar 2 09:58 libApiTSM64.so
-rwsr-xr-x 1 root bin 2670186 Mar 2 09:58 dsmtca
-r--r--r-- 1 root bin 971 Mar 9 03:28 dsm.sys.smp
-r--r--r-- 1 root bin 782 Mar 9 03:28 dsm.opt.smp
drwxr-xr-x 4 root bin 4096 Mar 22 10:50 ..
drwxr-xr-x 2 root bin 4096 Mar 22 10:50 sample
lrwxrwxrwx 1 root root 17 Mar 24 14:46 EN_US -> ../../lang/EN_US/
drwxr-xr-x 3 root bin 4096 Mar 24 14:46 .
After this is done, the database backups should no longer fail with an sqlerrmc of 610. No restart of the Tivoli Storage Manager server is required.
--link from https://www-304.ibm.com/support/docview.wss?uid=swg21425691&wv=1--
2011年5月24日
TSM v5 upgrade to v6
1. install new server OS, config iptables
2. make SAN connect to new server, define a LUN to new server (ex. 500G)
3. install new TSM v6, config TSMDB data
4. install TSM upgrade rpm, backup your DB
5. run dsmupgrd preparedb to update DB to new version
6. run dsmupgdx on new server for config all setting
7. run dsmserv insertdb (NEW) dsmupgrd extractdb hladdress=x.x.x.x lladdress=1500
8. wait.... (amount 30 min)
9. 決定性的一刻來臨...
2. make SAN connect to new server, define a LUN to new server (ex. 500G)
3. install new TSM v6, config TSMDB data
4. install TSM upgrade rpm, backup your DB
5. run dsmupgrd preparedb to update DB to new version
6. run dsmupgdx on new server for config all setting
7. run dsmserv insertdb (NEW) dsmupgrd extractdb hladdress=x.x.x.x lladdress=1500
8. wait.... (amount 30 min)
9. 決定性的一刻來臨...
2011年5月23日
PowerPath "unlic" I/O status
PowerPath show “unlic” status
Unlic indicates that unlicensed PowerPath is running for a CLARiiON array (no license key has been installed), Unlicensed defaults to "basic Fail/Over policy, we made change yet.
Workaround
1. powermt check_registration
2. powermt set policy=co dev=all (Set the Policy to co = Clariion Optimization)
3. powermt display dev=all
4. powermt save
--引用自http://sysinfo.bascomp.org/solaris/powerpath-show-unlic-status/--
Unlic indicates that unlicensed PowerPath is running for a CLARiiON array (no license key has been installed), Unlicensed defaults to "basic Fail/Over policy, we made change yet.
Workaround
1. powermt check_registration
2. powermt set policy=co dev=all (Set the Policy to co = Clariion Optimization)
3. powermt display dev=all
4. powermt save
--引用自http://sysinfo.bascomp.org/solaris/powerpath-show-unlic-status/--
2011年5月11日
抽獎用
用【自然人憑證】網路報稅真方便，分享好康訊息可以抽多功能讀卡機、自然人憑證悠遊紀念卡，還有「iPad2平板電腦」可連抽四次！想省時省事賺好康的朋友們，記得快去申辦自然人憑證喔！https://idcard.moica.hinet.net/code/2011/index.html
訂閱：
文章 (Atom)