Is the device/lun/volume healthy?
ll /**/*SAP*
/clusters/cluster-1/storage-elements/extents/extent_01_01_02_103_SAP_DB_01:
Name Value
----------------------------- ------------------------------------------------
application-consistent false
block-count 131072000
block-offset 0
block-size 4K
capacity 500G
description -
health-indications []
health-state ok
So that seems fine.
plus checking the relationships between the files via the CLI shows it's all fine:
---------------------------------------------
View Name: Col_Linux-Oracle-vApps
View Status: ok
---------------------------------------------
LUN-43: SAP_DB_01
(VPD83T3:6000144000000010a0245b40d0473e23)
==> SAP_DB_01 (distributed raid-1)
cluster-1:
==> device_SAP_DB_01_12014Jun03_1115252014Jun03_151326 (raid-0)
==> extent_UAT_SAP_DB_01
==> VPD83T3:6006016060d02c001b4a0bf204ebe311
==> EMC~CLARiiON~CKM00112400948 (EMC~CLARiiON)
cluster-2:
==> device_SAP_DB_01_1 (raid-0)
==> extent_SAP_DB_01
==> VPD83T3:600601608e503000a18d671a05ebe311
==> EMC~CLARiiON~CKM00112101396 (EMC~CLARiiON)
---------------------------------------------
sudo /etc/init.d/VPlexManagementConsole stop
cd to /var/log/VPlex/cli/ and locate the file GUI cache file persistentstore.xml and rename it with "mv" command.
sudo /etc/init.d/VPlexManagementConsole start
Then verify that the GUI cache file has been recreated when the service restarted.
We had no loss of service, or alerts when we did this, but the GUI error wasn't resolved either.
Guess what the answer from the vendor is now? Bug fixed in newer release of the code. Ha!
Do you have any experience or understanding of this error?
No comments:
Post a Comment