The problem is with the windows non-unicode applications configuration. DB2 9.5 supports the english (united states) and spanish (españa) for non-unicode applications. In latinamerica generaly the deployment enginieers have in their the Virtual Machines or Windows servers the configuration different to english (united states) or spanish (españa) in the non-unicode applications. This is the problem, DB2 cannot create the TSM database and show the following error:
lunedì 23 dicembre 2013
ANR0367W The server failed to format... database already exists.
Technote (troubleshooting)
Problem(Abstract)
After a failed initialisation of the Tivoli Storage Manager Server, the second attempt may fail with ANR0367W The server failed to format the database TSMDB1. This database name already exists.
Symptom
After a failed initialisation of a new Tivoli Storage Manager Server, the second attempt may fail with the following:
Tivoli Storage Manager for AIX
Version 6, Release 1, Level 2.0
Licensed Materials - Property of IBM
giovedì 12 dicembre 2013
ANS1512E - ANS1228E - ANS1063E
Tipologia dell'errore:
12/11/2013 17:43:23 ANS1512E Scheduled event 'SETT_VIZIONCORE' failed. Return code = 12.
12/11/2013 18:14:54 ANS1228E Sending of object '\\192.168.35.241\vizioncore\*' failed
12/11/2013 18:14:54 ANS1063E The specified path is not a valid file system or logical volume name.
in dsm.opt add ---- >
12/11/2013 17:43:23 ANS1512E Scheduled event 'SETT_VIZIONCORE' failed. Return code = 12.
12/11/2013 18:14:54 ANS1228E Sending of object '\\192.168.35.241\vizioncore\*' failed
12/11/2013 18:14:54 ANS1063E The specified path is not a valid file system or logical volume name.
in dsm.opt add ---- >
mercoledì 11 dicembre 2013
ANS4974E
Il caso:
Ho una NetApp NAS e un server nodo proxy che sto usando per il backup NAS. Le mie DBA vogliono essere in grado di eseguire il backup della domanda tramite la riga di comando.
Quando eseguire il comando backup: dsmc incr \ \ MYNASNAME \ DBBACKUPS \ prod \-subdir = yes-optfile = nas_dsm.opt L'l'errore ANS4947E.
Ora l'account connesso ha il pieno controllo del capitale e dei dati sotto la quota. Possono accedere, modificare e cancellare i dati che stanno tentando di backup senza problema.
Ho una NetApp NAS e un server nodo proxy che sto usando per il backup NAS. Le mie DBA vogliono essere in grado di eseguire il backup della domanda tramite la riga di comando.
Quando eseguire il comando backup: dsmc incr \ \ MYNASNAME \ DBBACKUPS \ prod \-subdir = yes-optfile = nas_dsm.opt L'l'errore ANS4947E.
Ora l'account connesso ha il pieno controllo del capitale e dei dati sotto la quota. Possono accedere, modificare e cancellare i dati che stanno tentando di backup senza problema.
martedì 10 dicembre 2013
ANS1228E / ANS1611E errors during client schedule backup
Problem(Abstract)
A Tivoli Storage Manager Backup-Archive client and HSM client are installed on the same Windows machine. The schedule backup of file managed by HSM fails with ANS1228E and ANS1611E errors.
Diagnosing the problem
An example of errors logged in the client error log (default=dsmerror.log) follows.
ANR2579E - Schedule schedule name in domain domain name for node node name failed (return code 12).
Resolving the problem
Check the cluster resources to make sure that only one scheduler service is active at any given time. Once the active node fails over the scheduler service should automatically be stopped on the active node and started on the failover node.
To troubleshoot, move all the active node cluster resources over to the failover node. Make sure there is only one Tivoli Storage Manager scheduler service running and that the service has successfully stopped on the inactive node. If the service is still running on the inactive node, the Tivoli Storage Manager scheduler service will have to be removed on both cluster nodes using:
Check the cluster resources to make sure that only one scheduler service is active at any given time. Once the active node fails over the scheduler service should automatically be stopped on the active node and started on the failover node.
To troubleshoot, move all the active node cluster resources over to the failover node. Make sure there is only one Tivoli Storage Manager scheduler service running and that the service has successfully stopped on the inactive node. If the service is still running on the inactive node, the Tivoli Storage Manager scheduler service will have to be removed on both cluster nodes using:
Iscriviti a:
Post (Atom)