Problem(Abstract)
After a database restore of V6 Tivoli Storage Manager Server, the Server may fail to start with the following error during startup: . ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1406) Thread<1>: Missing sqlState=58005, sqlCode=-902 from table. Returning rc = 9994.
Symptom
You may see the following in the db2diag.log:
2012-08-27-18.02.55.525533-240 I2765065E1078 LEVEL: Error PID : 5337 TID : 140025270232864PROC : db2fm INSTANCE: tsminst NODE : 000 FUNCTION: DB2 Common, Fault Monitor Facility, fmGetInstallPath, probe:60 MESSAGE : ECF=0x90000521=-1879046879=ECF_FM_NO_PERMISSION_TO_INSTALL_PATH No proper access permisions to the install path
Cause
The database was restored using an instance that is different than the one used in the backed up database.
For example, the default instance name is tsminst1, but the customer used the instance name “tsminst”. You can see evidence of the change in the db2diag.log. The correct name: “INSTANCE: tsminst1” will be replaced with: “INSTANCE: tsminst ”
Resolving the problem
As the root user, run the following command making sure to use the correct instance name:
“db2iupdt <NewInstName>”
The server should now start.
written by Bosse
Tivoli Storage Productivity Center v5.x (including Select Edition and Advanced)
|
Supported Platforms
|
Supported Products
|
|
Agents, Servers and GUI
|
HBAs
|
Switches & Directors
|
Storage
|
| 5.1.0 |
5.1.0 |
5.1.0 |
5.1.0 |
Tivoli Storage Productivity Center v4.x (Data, Disk, Disk Midrange Edition, Replication, Standard Edition, Basic Edition, Select, Disk Select)
TotalStorage Productivity Center v3.x (Data, Disk, Fabric, Standard Edition, Basic Edition)
TotalStorage Productivity Center for Replication v3.x
| Supported Platforms |
Supported Products |
| 3.4 |
3.4 |
Cross reference information
| Segment |
Product |
Component |
Platform |
Version |
Edition |
| Storage Management |
Tivoli Storage Productivity Center Basic Edition |
|
Windows, Solaris, AIX, HP-UX, Linux |
3.3.2, 4.1, 4.1.1, 4.2, 4.2.1, 4.2.2 |
|
| Storage Management |
Tivoli Storage Productivity Center for Replication |
|
AIX, Linux, Windows, z/OS |
3.1, 3.3, 3.4, 4.1, 4.1.1, 4.2, 4.2.1, 4.2.2 |
|
| Storage Management |
Tivoli Storage Productivity Center |
|
AIX, HP-UX, Linux, Solaris, Windows, z/OS |
5.1 |
|
written by Bosse
Recovery Entry 6.4 deliver a feature-rich storage management software suite that consists of:
- IBM Tivoli Storage Manager Extended Edition V6.3.3
- IBM Tivoli Storage Manager for Databases V6.3.3
- IBM Tivoli Storage Manager for Enterprise Resource Planning V6.4
- IBM Tivoli Storage Manager for Mail V6.4
- IBM Tivoli Storage Manager for Space Management V6.4
- IBM Tivoli Storage Manager for Storage Area Networks V6.4
- IBM Tivoli Storage Manager for Virtual Environments V6.4
- IBM Tivoli Storage Manager FastBack® V6.1
- IBM Tivoli Storage Manager FastBack for Microsoft Exchange V6.1
- IBM Tivoli Storage Manager FastBack for Bare Machine Recovery V6.1
Tivoli Storage Manager Suite for Unified Recovery V6.4 offers simplified pricing and licensing based on a per terabyte charge metric for data stored within Tivoli Storage Manager primary storage pools and Tivoli Storage Manager FastBack repositories.
For information about the products in this suite, refer to information shown above for each individual product. For information about the Tivoli Storage Manager FastBack products in this suite and more detail about Tivoli Storage Manager Suite for Unified Recovery, refer to the announcement letters in the Reference information section
written by Bosse
Problem(Abstract)
A session is rejected by a target Tivoli Storage Manager server when running node replication via SSL,
Cause
Certificate or Cert256.arm was not imported in cert.kdb on both source and target servers
Environment
Tivoli Storage Manager Server V6.3
Diagnosing the problem
The node replication via SSL fails with the following errors logged in the Tivoli Storage Manager server activity log :
ANR8582E An SSL open-socket error occurred on session 0. The GSKit return code is 575051. ANR0454E Session rejected by server Server_target, reason: Communication Failure.
Resolving the problem
Make sure the following steps are completed in order to set up SSL for node replication.
- Add “SSLTCPPort” in both source and target’s server optioons file (dsmserv.opt).
- Update or define both source and target server’s server definition to use SSLTCPport for the LLA parameter. For example: On source server :
Define server server_target HLA=IP_of_target serverpa=Password_of_target LLA=target_SSLTCPPort SSL=yes On target server : Define server server_source HLA=IP_of_source serverpa=Password_of_source LLA=target_SSLTCPPort SSL=yes
- Recycle both source and target Tivoli Storage Manager Server instance
- Copy the cert256.arm file from the source server to the target server and rename it as cert256.source
- Copy the cert256.arm file from the target server to the source server and rename it as cert256.target
- Import certificate in both directions. On source server :
gsk8capicmd_64 –cert –add –db cert.kdb –pw password –format ascii –trust enable –file cert256.target –label "target" On target server : gsk8capicmd_64 –cert –add –db cert.kdb –pw password –format ascii –trust enable –file cert256.source –label "source"
- Run the node replication
written by Bosse