CPDB Errors (ID 2001 through 2043)
2002 Not enough resource-name resources available to complete allocation. |
The farm requires resources that are currently unavailable.
Solution:Place more devices into the resource pool or wait for more resources to become available.
2005 object-name value is not in correct state for this operation. |
The farm is currently not in the correct state for executing the specified operation.
Solution:Ensure that the farm is allowed to make the transition intended (refer to Chapter 7, Troubleshooting).
2008 Request request-ID could not be materialized from the database. |
This could be caused by incompatible objects on the client and server side.
Solution:Ensure that the packages are up to date. Delete the request and restart the Segment Manager (refer to Chapter 7, Troubleshooting). Retry the operation or reissue the command that previously failed.
2009 Invalid database connection parameters. Check the tspr.properties file. |
The /etc/opt/ terraspring/ tspr.properties file has an invalid entry.
Solution:In the tspr.properties file, check the lines that begin with com.terraspring.db. CpdbConnection and enter the correct connection parameter.
2010 More than one Segment Manager is running on the host. |
You may only have one segment manager running.
Solution:Stop all the segment managers by issuing /opt/terraspring/sbin/sm -stop. Restart the segment manager using /opt/terraspring/sbin/sm -start.
2011 Invalid application state for this operation. |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
2016 Image size is greater than the requested disk size. |
Internal error.
Solution:Ensure that the specified image is of a smaller or equal size than the specified disk. Choose a smaller image or increase the disk size.
2017 Invalid special device type: type |
The type must be BACKHAUL.
Solution:This message is associated with the farm's Farm Markup Language (FML) and Wiring Markup Language (WML). Contact http://sun.com/service/contacting/index.html for assistance.
2031 IP does not belong to subnet |
The specified IP address does not belong to the specified subnet.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
2033 Invalid deQueue request status: request-ID |
The queue is in QUEUED, QUEUED_BLOCKED, or INPROGRESS state.
Solution:Refer to Chapter 7, Troubleshooting for details on dealing with requests.
2035 Duplicate MAC address mac-address cannot be added |
The media access control (MAC) address is already in use.
Solution:Assign a MAC address that is not yet in use.
2036 Subnet cannot be added because it overlaps with an existing one |
This subnet is already defined.
Solution:Assign a subnet that is not yet defined.
2037 CPDB server is probably dead or not allowing connections |
The CPDB connection is failing.
Solution:Check whether the server is running. If not, start it.
Check the listener for the network connection. If the connection has failed, reestablish the network connection.
2038 Farm name: farm-name does not follow the DNS domain label format |
An invalid DNS name has been specified.
Solution:DNS names accept only alphanumeric characters and the minus (-) sign. Specify a proper DNS name.
2039 Customer name: customer-name does not follow the DNS domain label format |
An invalid DNS name has been specified.
Solution:DNS names accept only alphanumeric characters and the minus (-) sign. Specify a proper DNS name.
2040 CP name cannot be null |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
2041 Monitor Node with monitoring_node not found |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
2042 IP Address IP_address is not a valid IP |
An invalid IP address has been assigned.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
- © 2010, Oracle Corporation and/or its affiliates