ANS0326E This node has exceeded its maximum number of mount points 解決辦法
ANS0326E This node has exceeded its maximum number of mount points
ANS0326E This node has exceeded its maximum number of mount points.
ANS1813E Image Backup processing of '/fscm8dbubos' finished with failures.
需要增加系統的mount點數
update node AU0431DB1 maxnummp=2
update node CMRM maxnummp=2
update node MS0431BK1 maxnummp=2
update node OADBSRV maxnummp=2
update node OASRV maxnummp=2
Problem Desc: "ans0326e node has exceed maximun tape mounts allowed" error occurs when attempting to run a sql backtrack to TSM. . Server OS: OS/390 Client OS: HP/UX 11.0 SQL Backtrack 3.3.3
Solution: CAUSE: The "maxnummp" needs to be increased to match the number of sessions.
SOLUTION: How to change the maxnummp:
To query use the following command: "q node f=d "
To update use the following command: "update node ... maxnummp=nn"
.
NOTE: In the Administrative Guide for MVS, look under the reference called "Understanding the Query node and Update node".
SOLUTION # 116626
=========================================
Problem Desc: DP for Informix backup fails with the following error in the bar_act.log: XBSA Error (BSAEndTxn): An unspecified XBSA error has occurred: 96 And the following in the dsierror.log: ANS4993E TDP Infmx AIX43 64-bit ANS0326 ANS0326E (RC41) Node has exceeded max tape mounts allowed.
Solution: To resolve this error, run Q NODE F=D on the TSM Server for the TDP for Informix node and look for the following parameter:
Maximum Mount Points Allowed: 1
This value defaults to one, so it must be increased if more than one tape drive needs to be used for the Informix backup. To increase it, run UPDATE NODE MAXNUMMP=2 for the TDP for Informix node.
This error can also be resolved by reducing BAR_MAX_BACKUP to 1 in the onconfig file to limit the backup to 1 session in TSM, or by directing the Informix backups to a disk stgpool on the TSM Server. This can be done by changing the copygroup in the default mgmtclass on the TSM Server, or by using an include statement to direct the backups to a different mgmtclass.
[@more@]來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/52450/viewspace-989955/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-00018: maximum number of sessions exceeded錯誤解決Session
- ORA-00020:maximum number of processes (500) exceeded 錯誤解決方法
- ORA-00018: maximum number of sessions exceededSession
- ORA-00018 maximum number of sessions exceededSession
- This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its de 錯誤解決辦法FunctionNoneSQL
- Oracle - ORA-00020: maximum number of processes (500) exceededOracle
- ORA-00059: maximum number of DB_FILES exceeded 處理
- 深度剖析:ORA-00018: maximum number of sessions exceededSession
- ORA-00059:maximum number of DB_FILES exceed 解決
- This function has none of DETEMINISTIC,NO SQL錯誤解決辦法FunctionNoneSQL
- Myeclipse 錯誤An internal error has occurred 解決辦法EclipseError
- ORA-28001: the password has expired解決辦法
- “command-not-found has crashed” 解決辦法 (*unsolved)
- ORA-00059: maximum number of DB_FILES exceeded 情況分析及實驗處理
- PHP Warning: exec() has been disabled for security 問題解決辦法PHP
- Cargo invocation has failed: Error: exit code: 101.解決辦法CargoAIError
- Oracle opatch apply 時提示oci.dll has active的解決辦法OracleAPP
- ORA-01102: cannot mount database in EXCLUSIVE mode 的解決辦法Database
- [LeetCode] Third Maximum NumberLeetCode
- 【Error】AttributeError: module ‘scipy.misc‘ has no attribute ‘logsumexp‘ 的解決辦法Error
- Starting sendmial: make: Warning: File 'virtusertable.db' has ..的解決辦法2
- node-sass 安裝失敗的原因及解決辦法
- ProTable 報錯Uncaught RangeError: Maximum call stack size exceededError
- LeetCode-Create Maximum NumberLeetCode
- Apache無法啟動解決 the requested operation has failedApacheAI
- 安裝node-sass失敗原因及解決辦法彙總
- js中Uncaught RangeError: Maximum call stack size exceeded錯誤JSError
- android.database.sqlite.SQLiteException: table tb_diary2 has no column named recordPath 解決辦法AndroidDatabaseSQLiteException
- github慢解決辦法Github
- Grub Rescue解決辦法
- /dev/null解決辦法devNull
- MSBuild Tools解決辦法UI
- 解決:NPM ERR! @ dev: `node node_modules/cross-env/bin/cross-env.js 的辦法NPMdevROSJS
- TSM備份ANS0326E錯誤及解決
- 檔案無法粉碎解決辦法
- OpenStack 的NAT解決辦法
- android ExceptionInInitializerError解決辦法AndroidExceptionError
- Could not find *.apk!解決辦法APK