Error Code details
V-107-58644-943
Severity: n/a 
Component: Replicator 
Message:
RESOURCEGROUP-RVGPrimary:online:vxprint failed with error code 256 and message Error V-107-58644-943: Could not find the object '-lV'.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2009-11-10 02:57:40 PDT
Platform: Generic
Release: Generic
Content:

Description

This error appears if a VvrRvg resource does not exist, or is not online before bringing the RVGPrimary resource online.


Solution

1. From the Replication Group, create a VvrRvg resource.

2. Configure the attributes for the new VvrRvg resource to match the RVG name, the IP resource and the VMDg resource.

3. Set the VvrRvg as the parent resource to the IP and VMDg resources.

4. Modify the existing RVGPrimary resource so that it points to the VvrRvg resource.

5. Online the VvrRvg resource

6. Online the RVGPrimary resource (or the application group where the RVGPrimary resource resides).
 


 

Reference: http://entsupport.symantec.com/docs/286640
http://entsupport.symantec.com/docs/302949
Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2009-11-11 03:23:14 PDT
Platform: Generic
Release: Generic
Content:

Description

This message may appear after running the vxprint command.

Possible causes

- When running the vxprint command, an object was specified as a parameter, but the object does not exist in the configuration.
- At the time that the vxprint command was run, one of the existing objects was being changed and added back to the Veritas Enterprise Administrator (VEA) database from where the vxprint output was supposed to fetch the object properties.  If the vxprint command is run during this time,  the error may appear.

Solution

1. Verify that the disk group name and the object names that were specified as parameters for the vxprint command actually exist
2. Wait for a short duration and try running the command again

If the problem persists, restart the Veritas Storage Agent service (vxvm), then try to run the command again.

Warning: Restarting the Veritas Storage Agent service in a clustered environment may cause Volume Manager Disk Group (VMDG) resources to fault.  

- If Veritas Clustering (VCS) is present, freeze any cluster service groups that contain VMDG resources before restarting the Veritas Enterprise Administrator service  

- If Microsoft Clustering (MSCS) is present, move any cluster resource groups that contain VMDG resources to another node before restarting the Veritas Storage Agent service

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service