Short data store

Similar Questions

• Load the view definitions in the short data store

  Hi all
  
  If I was able to export the view definitions that there was error on next import
  «"substring on column 5 26 line - ' String index out of range:-161 '"»
  
  I tried the graphic loadviewdefinitions of the QuickStart project and it came with the same error. I also deleted the definition of the base xml view but it error persists.
  
  Thank you

  Please visit the wiki updated post for how to import the display configuration in the format provided by the design of view export configuration template:

  https://wikis.Oracle.com/display/endecainformationdiscovery/import+view+configuration

  -Ryan

• ODI file data store

  Hi all

  I have a confusion about the physical and logical length in the ODI file data store.

  I have a fixed-width file where a c2 col had datatype as string (30).

  I've set this column in the data as string store > physical length 30 > logic length 30

  My interface failed with error as '.

  ORA-12899: value too large for column 'S0_IDM '. «C$ _0S0_EAGLE_DWHCDC_CHRG_MST ".» "" "C2_CHARGE_DESC" (real: 31, maximum: 30).

  When I increased the logical length to 255, the interface worked fine.

  Being always the same 30 physical length.

  How different is it?

  Any help on this will be appreciated.

  Thanks and greetings

  Reshma

  This isn't the official documentation, but here's my point of view, after a few moments of reflection

  Everything you do in the ODI Designer is inspired by the logical architecture. Only when running it manifested in a physical implementation i.e. connection strings are materialized etc. When you perform an integration ODI creates usually a few temporary tables prefixed with C$, I$ etc to be able to perform the necessary data movement and the transformations needed to, for example, to fill a data target (table) store. In your example, your flat file is materialized in such a temporary table before that its content is manipulated (or not) and loaded in the target data store. When ODI generates this code that he uses the logical length emitted in the DDL that generates temporary table column lengths, the physical column is ignored.

  Now in your scenario is not a problem as constraints such as these do not matter to the physical file version knowledge if you were to write to the file, that it would not matter if you wrote return 255 characters or 31. This could be a problem if you were using database tables and varying the logical vs physical lengths but generally you reverse engineer tables from database using ODI rather than manually doing so makes better.

  Anyway, in short, I think that the logical lengths should be taken as representative which will manifest itself in the materialization of the temporary objects used to manged / transform the data from the source models (tables$ CAN) and target (I have tables$) while the physical lengths indicate what the underlying physical representation of these models are in reality.

  EDIT: after reading some logical documentation actually represents the length while physics is related the number of bytes required to store the data. Therefore, you could have a situation with multibyte characters where the physical length could be greater than the logical length but not really the other way around.

• Please help: measure is missing from the data store

  Hello

  I have an a 20 TB drive data store and a magnitude of about 40 TB (local disks, areca raid controller).

  Long story short, I had to delete and re-create the volume 40 to on the RAID controller (without initialization, of course).

  Now all the data is there but eui has changed for the 40 to volume and vmware is unable to mount.

  log/hostd.log:2016-05-10T07:17:16.107Z of information pass [3D380B70] [Originator@6876 sub = Vimsvc.ha - eventmgr] event 118: a connected device eui.001b4d2051676528:1 may be offline. [Backvol1, 55e980d4-386dfa7f-7cb2-0cc47a09ba36] file system now is in a degraded state. While the data store is always available, parts of data residing on the extent which went offline may be inaccessible.

  [root@esxi2:/vmfs/volumes/55e980d4-386dfa7f-7cb2-0cc47a09ba36]

  esxcli instant vmfs storage list

  Volume name:

  VMFS UUID:

  Can mount: false

  UN-mountability reason: a few missing extensions

  Can will: false

  Reason for non-resignaturability: some missing extensions

  County of measure pending: 1

  Can someone help me please?

  Thank you!

  Hello
  You asked for instructions on how to readd a missing measure.
  Basically, it's pretty easy:
  in the VMFS to VMFS-based volume header section, you can assign extends it.
  Lets say that the basic volume is mpx.vmhba1:C0:T3:L0:1
  first of all extend is mpx.vmhba1:C0:T4:L0:1
  second extension is mpx.vmhba1:C0:T5:L0:1
  Then you will see this string in the VMFS header:
  vmhba1:3:0
  and a little later

  MPX.vmhba1:C0:T3:l0:1

  MPX.vmhba1:C0:T4:l0:1

  MPX.vmhba1:C0:T5:l0:1
  Just change the list of stretches.
  But: normally you can't change this section at all, and to add to the confusion, these values are stored in RAM is not trivial to change this value correctly.
  I highly recommend that instead of try it yourself and repeat all the mistakes I made while learning it - call me.
  I rather help you personally to give dangerous advice that will probably make things worse.

• Completed by TimesTen Server data store connection

  Hello

  I have a problem with an application to connect to a database, TimesTen, but the connection is being terminated by the server and I can't work the reason (error seems internal)

  In summary, the application reads the blocks of data of a schema performs a treatment and then writes the output to a separate schema. When the read operation is simple (a table only reading), it runs without error. When the read operation becomes more complex (reading subdashboards using an IN clause, the JDBC connection reported that the connection is broken that the server came out unexpectedly. )

  The tterrors.log file contains the following error information:

  16:40:35.11 Warn: 26246: 11.2.2.4.1.opadev TimesTen Daemon release began.

  16:53:17.79 Err: SRV: 26345: EventID = 5 | Socket recv() failed.  (104) error: Connection reset by peer. File: /ade/vespa_20121029_kaiser-tt_29086/timesten/VisiChannel/oc/src/vostcpip.cpp; Online: 668

  16:53:17.79 Err: SRV: 26331: EventID = 5 | Socket recv() failed.  (104) error: Connection reset by peer. File: /ade/vespa_20121029_kaiser-tt_29086/timesten/VisiChannel/oc/src/vostcpip.cpp; Online: 668

  16:53:17.79 Err: SRV: 26345: EventID = 68 | Unable to read the request from the client. Closing connection without response.

  16:53:17.79 Err: SRV: 26331: EventID = 68 | Unable to read the request from the client. Closing connection without response.

  16:53:20.37 Err: SRV: 26410: EventID = 3 | Send() Socket failed.  (104) error: Connection reset by peer. File: /ade/vespa_20121029_kaiser-tt_29086/timesten/VisiChannel/oc/src/vostcpip.cpp; Online: 762

  16:57:31.39 Err: 26246: 26483/0x82ca90: failed assertion: sbPtIsCharConst (maxExp) [genTree.c:/main/155:genOrderInList (): 4555] PID 26483 (ttcserver) 1 CONN (javaw) 2014-02-05 16:57:31.396

  16:57:31.39 Err: 26246: 26483/0x82ca90: assert SQL = "SELECT HOUSEHOLD_MEMBER_ID, HOUSEHOLD_ID, AGE OF UK_DATA_HOUSEHOLD_MEMBER WHERE HOUSEHOLD_ID IN ('3 ', '2', '10', '1', '7', '6', '5', ' 4', ' 9 ', ' 8') '"

  16:57:31.39 Err: 26246: 26483/0x82ca90: database marked invalid [genTree.c:/main/155:genOrderInList (): 4555] PID 26483 (ttcserver) 1 CONN (javaw) context 0x82ca90

  16:57:31.71 Err: 26246: 26250/0x7fe3b00009e0: IndexGC could not start a transaction

  16:57:31.71 Warn: 26246: 26250/0xec53a0: / var/TimesTen/opadev/opadev_db forced disconnect

  16:57:31.71 Warn: 26246: 26250/0x7fe3b00009e0: / var/TimesTen/opadev/opadev_db forced disconnect

  16:57:31.71 Warn: 26246: 26250 -: an old instance is disconnected

  16:57:31.71 Err: 26250: subd: IndexGC thread is stopped with error

  Warn 16:57:31.71: 26246:26483 you leave all connected to the data store ' / var/TimesTen/opadev/opadev_db "shm 1509982213 count = 1

  16:57:33.58 Err: 26246: TT14000: TimesTen daemon internal error: could not connect to port subdaemon 9327 [stopManaging - err 799 (error Protocol trying to talk to the demon to port 9327)]

  16:57:33.58 Err: 26246: TT14012: demon subdaemon TimesTen failed: error 791 unmanaging, disabling

  16:57:33.58 Warn: 26246: 26250 -: process of subdaemon is released

  Warn 16:57:33.58: 26246:26250 you leave all connected to the data store ' / var/TimesTen/opadev/opadev_db "shm 1509982213 count = 9

  16:57:33.58 Warn: 26246: daRecovery: subdaemon 26250, management of data store, failed: invalid (failcode = 202)

  To me, this looks like an internal error in TimesTen.

  Any ideas what's going on (short-term memory maybe)?

  How this increase as a SR or searching through the existing SR and TimesTen bug reports?

  Thank you

  Ben

  Hi Ben,

  Yes, the TimesTen server is blocked because of an internal assertion failure. My suggestion would be to first try upgrading to the latest version of 11.2.2.6.x because it has many corrections of bugs compared to 11.2.2.4.1 which is pretty old now. If this does not resolve the problem, then you need to open an SR via My Oracle Support. You will need your CSI to do so and it should cover TiemsTen (i.e. you must have TimesTen covered as part of your Oracle support contract).

  Chris

• Lost access to local data store

  Hi people:

  I have ESXi 6.0 running on an Intel S2600CWTS motherboard using the LSI SAS controller onboard and six readers Samsung 850 Pro SSD in a RAID 5 configuration.  This server is about a month and a half, and it worked fine for the first month, but in the last few weeks I started to do in the case where journal messages saying that ESXi has lost access to the data store, then, most of the time, about 15 seconds later access is restored.   Several times it took more time, which one crashed the server.  On these long, the motherboard Intel event log showed that a player had failed and began a regeneration and once the motherboard has shown that two different drives had failed, and it took both offline originally ESXi crashing.  On it that I was able to bring the two records back online via the RAID bios and everything worked fine again.  I suspect that I have hard disk problems because these discs are new and because different readers have been reported as failed, and also because no data has been lost even if 2 drives went offline at the same time.   I guess I could have a bad controller LSI, or a cable has come loose somewhere, but I expect to happen if it is really the case of data loss.

  I also noticed that lost access messages tend to appear in the log at the moment I start a virtual machine.  At first I thought that it would be one thing to flow, thinking a VM departure did a lot of IO, but this happens immediately, before even the bios of the virtual screen machine disappears, so I don't think that the virtual machine is actually reading the disc again.  In addition, as a precaution, I started the migration of some virtual machines on the server to the old server I still had available, and there is no lost access messages in the event log while that was happening, while about 50 megabytes per second of i/o has reached the disk during transfers.  I put the last patch on ESXi in mid-May, about two weeks before this started, and I begin to suspect that the patch may have something to do with it, because it seems to me that if something is happening between ESXi and the disk controller making hang up or lose interruptions during a short period of time , and I wonder if it goes pretty long if material in the motherboard sensors interpret this as some sort of hardware and simply brand failure according to readers I / O was hooked as bad then.

  Unfortunately I'm out of town now so I wanted more I had to the remote server, lest I do not not get back to the top.  I moved a couple of the most critical virtual machines from the old server which I was remotely start and transfer to virtual machines.  I also noticed that this issue tended to occur more frequently when I got to the top of the VCenter Server apparatus that any other (sometimes to others, but has happened every time I tried to start the device VCenter).  So who was the first that I moved to the old server, but strangely enough there is no error logged when I transferred the files, so the issue is not that ESXi had trouble reading the VMs vmdk file when I started it.

  I also wanted to ask you if there are any vibs for the LSI Megaraid controller on motherboard S2600CWTS I could install that would allow me to access the RAID controller without having to pick up the server and do it from the BIOS configuration screens, similar to how you can access the controller RAID from Dell while ESXi is running via a vib add-on.  So far I have not found one.

  My intention when I go to the server is to run an integrity check against the RAID 5 array via the controller and then use the AIMÉ ESXi utility on the data store to see if something is wrong here.  If not, then I guess I'll rewritten can patch.

  Ideas or suggestions welcome.

  Success!  I finally understood what the problem was corrected.  The problem is the fact that although the last vib driver LSI has been installed, for some reason any it would not automatically replace the default ESXi pilot lsi_mr3.  I did not notice that even though the latest driver package vib properly installed LSI controller was still using the original driver.  This could be considered by a 'esxcfg-scsidev - a' command showed that even "vmhba1 lsi_mr3 link-n/a sas.5001e67ca647e000 (0000:0: 00.0) controller LSI MegaRAID SAS Fury."  The second field after the controller (vmhba1) is the current manager used.  The pilot, which was to be used was: "vmhba1 megaraid_sas link-n/a unknown.vmhba (0000:03:00.0) Avago (LSI / Symbios Logic) Invader MegaRAID SAS controller.

  To fix this I had to disable the lsi_mr3 driver so that ESXi is forced to use it.  The procedure to do is the following:

  (1) make sure you have the new EXSi driver you want to use already installed.  I assume that bad things would happen if you have disabled the only driver who could run your disk controller.  Use this command to view the drivers installed: "esxcli software vib list" and you should get something similar to the following:

  [root@intelserver:~] esxcli list of software of vib

  Name Version Date seller installation acceptance level

  -----------------------------  ------------------------------------  ------  ----------------  ------------

  MegaRAID SCSI-sas 6.608.11.00 - 1OEM.600.0.0.2494585 Avago VMwareCertified 2015-07-19

  LSI - mr3 6.606.10.00 - 1OEM.550.0.0.1391871 LSI VMwareCertified 2015-06-19

  mtip32xx-native 3.8.5 - 1vmw.600.0.0.2494585 VMWARE VMwareCertified 2015-04-28

  ATA-pata-amd 0.3.10 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-atiixp 0.4.6 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-cmd64x 0.2.5 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-hpt3x2n 0.3.4 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-pdc2027x 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-serverworks 0.4.3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-sil680 0.4.8 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-via 0.3.3 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  block-cciss 3.6.14 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  CPU-microcode 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  EHCI-ehci-hcd 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  elxnet 10.2.309.6v - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Emulex-10.2.309.6v - 0.0.2494585 VMwareCertified-2015-04-28 VMware esx-elxnetcli

  ESX-based 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  ESX-dvfilter-credits-fastpath 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  ESX-tboot 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  6.0.0 - 0.0.2494585 of xserver-ESX VMware VMwareCertified 2015 - 04 - 28

  IMA-qla4xxx 2.02.18 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-devintf 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-paremeter 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-TR-drv 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LPFC 10.2.309.8 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSI-msgpt3 06.255.12.00 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-hp-hpsa-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-lsi-mr3-plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-lsi-msgpt3-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU lsi megaraid sas plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-mpt2sas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-mptsas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Misc-cnic-register 1.78.75.v60.7 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Misc-pilots 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  NET-bnx2 2.2.4f.v60.10 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-bnx2x 1.78.80.v60.12 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-cnic 1.78.76.v60.13 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000 8.0.3.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000e 2.5.4 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-enic 2.1.2.38 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-forcedeth 0, 61 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-igb 5.0.5.1.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NET-IGB 3.7.13.7.14iov - 20vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-core 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-en 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-nx-nic 5.0.621 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-tg3 3.131d.v60.4 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-vmxnet3 1.1.3.0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  nmlx4-core 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-en 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-rdma 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nVMe 1.0e.0.35 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  OHCI-usb-ohci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  qlnativefc 2.0.12.0 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  REST 2.0.2.0088 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Ahci SATA 3, 0 - 21vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  ATA-SATA-piix 2: 12 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NV-sata-SATA 3, 5 - 4vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  SATA-sata-promise 2: 12 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil24 1, 1 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil 2, 3 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-svw 2, 3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-aacraid 1.1.5.1 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-adp94xx 1.0.8.12 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-3, 1 - aic79xx 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2fc 1.78.78.v60.8 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2i 2.78.76.v60.8 - 1vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  SCSI-DNI 1.5.0.45 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-hpsa 6.0.0.44 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-ips 7.12.05 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid-mbox 2.20.5.1 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid2 2.00.4 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mpt2sas 19.00.00.00 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptsas 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptspi 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-qla4xxx 5.01.03.2 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  UHCI-usb-uhci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  VMware-esx-dvfilter-maclearn-1, 00 1.00 VMware VMwareCertified 2015-05-12

  xHCI-xhci 1, 0 - 2vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Tools-light 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  [root@intelserver:~

  Verify that the scsi-megaraid-sas driver is installed before proceeding.

  (2) to disable the lsi_mr3 driver do the following: "esxcli set of module system - enabled = false - module = lsi_mr3 '

  (3) reboot

  After restarting, do: "esxcfg-scsidev - a" to check megaraid_sas driver is assigned to your disk controller.

  I don't know how ESXi decided to prioritize if two or more drivers are applicable to a single hardware device, or if the installation of the new driver LSI process is supposed to disable or remove default lsi_mr3 driver and simply failed to do so.  Also, I don't know what's going to happen when I put on the next patch of ESXi, specially if the lsi_mr3 driver will be once more the priority.  If anyone knows how the driver installation process is supposed to work in this situation, please let me know.  I am so happy that I finally got this problem because the server has been seriously covered with the data store become unaccessable for 5 to 10 seconds every time a VM started or stopped, and the former driver at least once done something bad enough to deceive the controller into thinking that one of the disks has went wrong and began a RAID Resync.

• DTS moves to the same data store

  Greetings,

  We are short v5.5u1 esxi and vcenter device with DTS clusters installation using thresholds to space only at this time. We do not limit our VM to place records on the same data and store, and in view of the virtual machine can have his records scattered across data warehouses in a cluster of the DS.

  We have many events that seem to do nothing is represented below.  Everyone agrees that something actually happens or vcenter turns his wheels?

  

  Thank you

  Ron

  Just answered my own question... it has to do with my scattered placement of vmdk. Since the vmx file lives on a given data store, the event shows that the activity... However if you check the DTS tab for the cluster data store you will find the disks associated with the virtual machine on other data warehouses were actually moved.

  

• How can I get an alarm for VM in bad condition when you run lack of space on the data store

  Hello

  After ignoring the alarm messages on disk space used almost, a VM doesn't work with this error message:

  "Message from VMHost1.test.net: there is no more space for virtual disk.

  vmfs/volumes/4fb7ee7c-9c2aceee-a0df-00215acb6f4a/VMHost1/VMHost1_1_1.VMDK. You may be able to

  continue this session by freeing up disk space on the relevant volume, and then click Retry. Click Cancel to end this

  session. "

  At this point, I would like to have another alarm to ignore ;-)

  I'm trying to find a VMware alarm that can warn me in this case. (As the alarm 'use of data to drive store"set up to warn me when 90% is used)

  Basically, when the data store is full, and a virtual machine on it ask the e/s, due to the fact that it is thin provisioned, it is currently interrupted by ESXi. All virtual machines that do not require what I/O may still work. When this happens, you get an error like this:

  

  What the virtual machine that will come to you, is basically a VM Message. Using vCenter, you can create an alarm that goes off when the virtual machine (an individual) information message. The message that I used was something like this:

  

  When I then make a virtual machine on a data store set up thin, my alarm clock personalized using thin disks implemented short of space, was triggered.

  

  NB. I saw icon of the virtual machine in a State of alarm after that I clicked retry on the popup. If you don't do this, the virtual machine icon will be the State in question, but will always be triggered the custom alarm.

  Hope this helps,

  Tom

• Local data store has disappeared from the data store window (necessary emergency aid)

  Dear team,

  I m facing a very strange problem, all of a sudden one of the local ESX datastore disappeared thereafter are full details we have encountered/noticed.

  A local data store disappeared from the data store window.able to see this data store to add storage Wizard, which allows us to format the same.

  * If we take a session putty from here we can see and browse this store of data without problem.

  * Virtual computers that are running on this data store work as well (all files are accessible / VM is accessible on the network)

  * Unable to take backup image do error "the object has already been deleted or was not completely created.

  * Not able to take a «cannot complete the copy file... network» clone »

  Getting from newspapers in vmkernel:

  (14 dec 17:11:39 localhost vmkernel: 0:01:55:28.677 cpu1:4097) ScsiDeviceIO: 747: command 0 x 28-the device 'mpx.vmhba1:C0:T1:L0' failed, the data of sense H:0 x D:0 x 2 P:0 x 0 0 valid: 0 x 4 0 44 x 0 x 0.

  (14 dec 17:11:39 localhost vmkernel: 0:01:55:28.677 cpu1:4097) ScsiDeviceToken: 293: Sync IO 0 x 28-the device 'mpx.vmhba1:C0:T1:L0' failed: error/o H:0 x D:0 x P:0 x 0 2 0 valid sense data: 0x4 0 44 x 0 x 0.

  (14 dec 17:11:39 localhost vmkernel: 0:01:55:28.677 cpu6:4110) capability3: 5354: Sync READ error ('. fbb.sf') (ioFlags: 8): i/o error

  Need your help urgently to solve the same.

  concerning

  Mr. VMware

  

  Dear all,

  We have enclosed a case at VMware, please find their findings on the same.

  ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  After the webex session, we just had, I discovered the root cause of the problem reported to an underlying problem on the block device (the logical drive, or a problem on the Board) presented to accommodate the data in question store successfully.

  In short, whenever we try to do raw reading from the disk (from sector 0), the same always fail when we reach the 30932992 bytes (31 MB) brand with an IO error (which is consistent, he is always on this region of the disc that read operations fail, no more, no less). This result can be seen, even if no partition is in the disk (using if = / dev/sdb instead of/dev/sdb1 with dd) and even after zeroing on all sectors (if dd \u003d/dev/zero of = / dev/sdb). Strangely, read operations work fine (as he writes zeros of random data) throughout the entire disk. Keep in mind that the tests I did with no VMware tools (I used almost only dd for these operations), which prohibits certainly a VMware problem (in fact, if you were to try to start the server with a Linux live CD and run the same tests that I did, you would see the same behavior).

  I know that there is no report of material of any bad behavior on the table, but data collected with our tests today completely invalid who. The next step is for you to take this to the server provider to check for problems on the table or discs, because they are there and they are the reason for the problem you reported initially.

  Please let me know if you have other questions about it.

  Thank you

  -

  David Meireles

  Technical Support Engineer

  ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Now we have blocked a case from the hardware vendor, to see what the next move will be.

  concerning

  Mr. VMware

• Deletion of snapshots to recover from data store space

  ESXi 4.1

  I have an ESXi host Miss space on one of its data warehouses. No 911 short, but short enough so that something needs to be done in a few weeks. On this data store, we created snapshots of some servers Exchange 2010 hosted before installing a custom Microsoft patch. So we have a server HUB, CASES and MB each with a single shot of several months that we will never have to come back. In this navigation data store, some of these 00001.vmdk files are huge, almost up to the size of the player it is a snapshot of. I believe it happened when we had backup problems and drive full of balls of trans.

  In any case, I want to remove these snapshots in snapshot Manager on each of those virtual machines by selecting the snapshot and hit delete. The problem is I've read different information about what will happen. Some of the information I've read says even this will take even MORE space. I don't know how that's possible, but I wanted to get in the forums before doing anything.

  Delete the snapshots will delete all files in capture instant hard, recovering a ton of space on the data store?

  TIA!

  The OMI 30 GB should be enough. When you delete the snapshot with the virtual machine, a snapshot of assistance is created, which will consume disk space necessary for any change, even if the current snapshot is being deleted more ~ 4GB for the snapshot file (.vmsn).

  With the virtual machine off, you will not need any addiitonal disk sapce. However, you won't be able to turn on the virtual machine again, until it's finished!

  André

• vSphere - external USB drive to the data store local copy

  Hello world

  Yesterday, I created this post: http://communities.VMware.com/message/2135813
  With your help, we managed to find the only way to install ESXi to ISO image to USB external hard drive is to be attached to the machine near her and run the Setup from there, cannot be done directly.

  Today, we need your help in the next step, as it seems.

  We have a Dell r.620 physical machine with VMware ESXi 5.0 installed U1. We have an external hard drive with the operating system installation ISO images, software backup and a little more.

  The question is - how to copy the data from the external USB connected directly to the ESXi host to the data store local disk on the host.

  Yes, we know that we can do in the way that connect us to the machine on the same location and copy it into the data from there store. But we would do it directly. And we don't very well see by ourselves or using Google Uncle again.

  Poor ability to research, or is not possible?

  Thank you very much for your help!

  The court to do is to use the Datastorebrowser or WinSCP

  ESXi itself can only read the Fat16 drives - so what looks like the short path is the long way ;-)

• Configuration of San - data store have more than 1 LUN

  Hello

  We look at our San configuration for improvements. Our San has about 10 TB total.

  We currently have 6 LUN 1.5 TB all which are enclosed in 1 store 10 TB data

  It was suggested that we should NOT combine multiple LUNS in a data store for the reason if 1 LUN goes wrong then the entire data store is non-refundable.

  Although our SAN LUNS are created on top of raid 6 and are therefore a bit 'protected' by councils LUN 1 data store is interesting

  Does anyone have ideas to share?

  Thank you

  Tom D

  I would say that having a single data store, regardless of the underlying storage architecture is probably not a good idea.  Although this configuration is authorized you can paint yourself in a corner fairly quickly.

  1. one wonders about the maximum number of VMDK you should have by the data store.  http://communities.VMware.com/message/944120  Basically the more s VMDK on the SCSI data store more blocking of activity taking place on the disk, causing performance problems.  Each VMware engineer, I've talked about seems to stay around the VMDK 20 a range of data store, but that could change with vSphere.

  2 - How this data store backup and how long does it take?  What happens during a restore scenario?  10 TB is plenty of space and could take some time for the backup.  If you push it on tape and you must always restore the together 10 to it could take weeks or months.  This space by breaking into warehouses of smaller data gives you smaller segments of data that you can restore in case of disaster.

  3 - the number of data warehouses you have is very important if you are always looking to implement the Site Recovery Manager.  SRM relies on your storage device to replicate data between the sites.  There could be serious consequences on the rate of change of the data for a single LUN 10TB.  If you are moving in several data stores that it will make it easier to handle your recovery plan.

  Apart from the considerations above of VMware. I guess 7 performance LUNS in RAID-6 is not so great.  You have a lot of protection, but you pay for it with capacity and performance.  If you went to 10 stores of data and the LUN 10 you can change RAID settings at each data store to optimize performance, protection, and capacity.  For example 4 LUN RAID-10 high performance DB apps and 6 LUNS to RAID-5 for the ability.  With smaller LUN and data warehouses a disk or LUN failure will affect only a smaller set of services rather than your entire data center.

  In short, unless there is a really compelling reason to go with a single store of 10 TB database, I recommend you to change your architecture.

• If I put in place an openfiler VM as a data store iSCSI & vmfs on two ESXi hosts, both ESXi hosts can access two data warehouses?

  If I put in place an openfiler VM as a data store iSCSI & vmfs on two ESXi hosts, both ESXi hosts can access two data warehouses?

  The reason why I ask, is that I have two hosts ESXi ESXi 4 running.  I do my backups with ghettoVCB, which I modified to create thin backups on one of the drives the.  I then wput them to the server, which causes them to become thick.  Directly targets the backup in a vmfs iSCSI on the server in the face shop.  It would save a step and the vmdk backup should remain thin.

  Thank you!

  The short answer is Yes. If you allow the ESX servers to see the LUN. This setting is configured to the Openfiler.

• Reconfigured HP Data Replication Group does not present as a group of SRM data store

  Hello

  I configured in two data centers with an EVA4000 on the source site and an EVA4400 on the destination site, countered with Continuous Access EVA of SRM.

  I had replicated two EVA virtual disks (and ESX data warehouses) on the EVA4000 Source called EXCHANGE01 and EXCHANGE02 that have been configured in separate groups, data replication (named EXCHANGE01-GROUP and EXCHANGE02 GROUP) of the HP Command View EVA. These have been picked up properly by SRM as replicated data stores.

  So I decided that it would be preferable to not not two data stores more as a single unit and therefore re-configured continued access by removing the virtual disk EXCHANGE02 of its data replication group and adding as a member of a GROUP named EXCHANGE01. After that, the GROUP named EXCHANGE01 is fail-over for Command View EVA unit and contains EXCHANGE01 to virtual disks and EXCHANGE02. The problem is that when I use the "Rescan replicated storage" option in SRM, you can still see the two Datastores EXCHANGE01 and EXCHANGE02. As it is, I need to create two groups, one by the data store, while in reality a continuous access switch the two as a single unit. The MRS server has been restarted, the berries reread several times, and in fact the EVA4000 has been restarted.

  Two things, I guess. Am I right in thinking that SRM should report to the Group of data replication HP (despite the fact that he refers to it as a\ group data store)? If I am, is there a way I can fix it (preference to short to remove all the replication groups in Command View EVA, a new analysis in the MRS and re - duplicate records?

  I have attached two screenshots - one to SRM showing the list of groups of data store after a new analysis and the other from Command View EVA, showing the Group of data recovery

  AX

  Hi Bob.

  The term SRM data store group is intentionally generic because MRS. support many different providers, and all could use a term "Replication group" as EVA does. If MRS. may correspond to a data store that was created on a LUN that the one being replicated is returned by the adapter, it considers that the store of data as being replicated. It's the storage provider for code adapter for return information LUN appropriate to their table - if you look at the SRM newspapers you will see EVA adapter returns each LUN replicated individually with no information about the relationship of Group of replication at all, so it would be impossible for SRM to have knowledge of this relationship as well.

  Although the LUN in a replication failover as one group power group, they can be taken individually for use during the test of SRM, so maybe it's one of the reasons why HP choice to list each ONE separately.

  In all cases, you have several alternatives: one is to keep your existing environment and configure two groups of protection; on the side of recovery, you can set up a restoration plan unique to switch both of these groups; In addition, you may have configured 2 other recovery plans, one for each protection group, which would be only used for the test, and which would test each LUN and virtual machines on it individually - this could reduce the load on the DR ESX servers during the test rather than to test simultaneously. Of course, you can create a single LUN as well and that of course would make the theoretical discussion - it could be better if your virtual machines must be tested together because the application dependencies.

  You might consider following up with HP if you want more insight as to the relationship of EVA "Replication groups" viz SRM, which is why they chose to not to expose information to the replication group.

• How to advocate for regional change of short date format

  This is something relatively trivial but annoying all the same, but I don't know where to go to advocate for change.

  Have just updated for Sierra and one of the first things I notice is the addition of a point at the end of the month in short date format, i.e. 'September 19, 2016'.

  "In Australia, as in the United Kingdom, the standard must not use this period - it should be just'19 Sep 2016", and in the past, that's how it appeared in OSX for the Australia. Don't know why the change.

  This abbreviation is not replaceable by the user, so where can I go to provide appropriate feedback and I hope to have this problem on the track?

  A solution is to make my default language and region of the United Kingdom, but do not know if there is a price to pay for it.

  You can provide feedback to Apple asking them to change it:

  www.Apple.com/Feedback