Vertex

Hi,
We are using SAP 4.6 C currently. We are upgradingto ECC 6.0. Assuming the requirements remain the same what work is required in the new ECC 6.0 system to interface it with vertex? I mean what config. steps would we need to consider and are there any interfaces that need to be re-written in SAP during this upgrade.
Any help willbe apeciated.
Thanks,
ALAM.

hi
only you have to check the conectivity between the interface and SAP.

Similar Messages

  • Is OCZ Vertex Turbo 60GB 2.5" SSD compatible with my Mac Pro, or do I need

    Is OCZ Vertex Turbo 60GB 2.5" SSD compatible with my Mac Pro, or do I need the Vertex Mac Edition?
    I have decided to purchase a SSD to use as a boot drive in the spare optical drive bay.
    There are so many brands available, and Intel X25-M 'G2' seems generally to be the most highly rated overall. However, there is virtually no stock of 80GBs in the UK at present, except at extortionate prices, and I don't need 160GB.
    Kingston SSDs are very reasonably priced, but seem to be a bit of an unknown quantity, although I rate their DDR3 memory very highly.
    I have visited the websites of several manufacturers, and read various online reviews, and the recently introduced OCZ Vertex Turbo has had some good reviews, albeit on PC forums.
    At the moment I can buy the 60GB Turbo for £170.66 inc.VAT from ebuyer.com, whereas their price for the standard Vertex 60GB is £193.99 inc. VAT, which seems very strange!
    When I googled "OCZ Solid State Drives +UK", Amazon UK appeared on the listings, but there was a footnote which said " not suitable for use on Mac".
    OCZ list a Vertex Series Mac Edition on their website, and that is why I am asking this question.
    Unfortunately, there are no UK listings when I google the Mac Edition, and I am hoping that somebody of the ilk of "the hatter" or "samsara" will be able to answer my question.
    If anybody else is using the Vertex Turbo in a Mac, I would be very grateful for your input. Likewise if you have had bad experiences with OCZ SSDs.
    If I wait 3-4 weeks I should be able to buy an Intel X25-M G2 80GB for round about the same price as the Vertex Turbo 60GB, i.e. if prices remain the same as currently being quoted by vendors who are out of stock.
    All input will be very gratefully received. If it is positive, I will go ahead and order a Vertex Turbo from ebuyer, in case they run out of stock (which is 16 at present).
    Many thanks in anticipation, guys!

    Hi Samsara,
    Many thanks for your advices once again.
    60GB will be more than adequate as my boot drive. At the moment I am using a VelociRaptor 300GB, and I have used less than 30GB of space. That is after reinstalling all my applications and software, and includes all my files, folders, and printer drivers etc.
    I have utilised under 50GB of the original 640GB hard drive, but that includes a lot of photo images which I imported into both iPhoto and Aperture.
    When I receive my Agility EX SSD I will clone from the VelociRaptor using Super Duper, and I will then set up a 4 drive RAID 0 using 4 VelociRaptor 300GB disks. That set up should suit my needs for many years to come, even when I eventually upgrade from Photoshop Elements 8 to CS5.
    I will back up the Agility EX to the 640GB hard drive using Super Duper Smart Update, and that will be my spare boot drive.
    The 4 drive RAID 0 will be backed up to the My Book Studio Edition II 2TB, using Time Machine.
    In your experienced opinion, do you think that set up will be satisfactory?
    The Agility EX is actually the latest generation of OCZ SSDs, and it is one of only 2 models in their "Maximum Performance" range, whereas the original Agility was only a "Mainstream" model.
    The key factor is that the Agility EX uses single-level cells (SLC), instead of multi-level cells (MLC). It is second only to the Vertex EX Series in terms of performance per GB in the OCZ range of SATA 2.5" Solid State Drives.
    In very recent reviews it has outperformed both the Vertex Turbo and Vertex 120GB models from the OCZ "Performance" range in most of the test benchmarks.
    http://www.hardwarecanucks.com/forum/hardware-canucks-reviews/24507-ocz-agility- ex-60gb-ssd-review.html
    http://www.phoronix.com/scan.php?page=article&item=oczagilityex&num=1
    http://www.guru3d.com/article/ocz-agility-ex-ssd-60gb-review-test/3
    The above are just a few of the very favourable reviews of the Agility EX SSD.
    I preferred to buy a 60GB SLC, rather than a 120GB MLC, because SLCs reputedly have 10 times more life expectancy, and performance wise per GB there is no comparison.
    Only time will tell if I have made the right decision!

  • OCZ Vertex 2 in Mac Pro 2009

    Although this has already been discussed a few times I'd like to add my experience with the OCZ Vertex SSD over 8 months. Since I got mostly shoulder shrugs everywhere else, I hope a competent tech head will stumble upon this and point me in the right direction.
    The initial install was a doddle and this drive is insanely fast as a main system drive. I heard about the issues with SSDs wearing out over time without TRIM etc but never fully understood it. I'm not a tech head. A couple of days ago my Mac started to behave strangely with complete freezes to the point that I had to do hard reboots (power button). One out of two times OSX would boot back normally but then freeze completely after about 10-15 min. of use. The other times it wouldn't even find the startup drive (blank screen and folder with ?). So logically the SSD must be the culprit. I was lucky to have made a time machine backup and restore OSX to a HD. The backup runs fine, so there is no issue with OSX itself.
    The OCZ is on firmware 1.2. There are other users having the same problem and apparently it has something to do with the fact that OCZ drives don't handle power functions too well on a Mac, like sleep, hibernation etc. For most of those users, a firmware upgrade did not solve the problem. I followed all the other hints, disable sleep, downloaded TRIM for non-Apple SSDs etc but to no avail.
    Before I start the RMA process (which OCZ might refuse?), does it make sense to upgrade the firmware on a device that was running fine for several months? I mean, it can't be the firmware if it was always working before, can it? I actually suspect the SSD to have become bad over time. However I think I'm still far off having had enough read/write cycles to wear out the drive according to the specs floating about.
    I'm inclined to demand a replacement drive, a brand new one, but on the other hand I've lost all confidence in SSDs. Especially as the main system drive. It's very irritating when the whole system freezes in the middle of a project. How long are those drives supposed to last, REALLY honestly?? I simply can't believe the "up to" 20 years myth.
    Cheers for any hint.

    TRIM Enabler support thread:
    http://forums.macrumors.com/showthread.php&t=1125400
    http://www.groths.org/?p=308
    I don't know that model but I would update the firmware.
    I'd also let the SF controller do its think and not use TE unless you feel it is safe and the current version. That may not have always been true. SF Background GC should be enough. And wipe/reinstall if not.
    As for sleep etc, hibernation is a laptop feature. And even PC BIOS have had to be updated (two PCs, Intel and Gigabyte) and until then it was an issue at times.
    OWC uses SF and does not recommend TRIM for OS X.
    So, what I would say is this:
    When your computer has a hard freeze, it needs you to act/react accordingly:
    Safe Boot at minimum to clean up and attempt to repair its directory.
    Not sure why or what but that can happen to anyone almost and may not even be SSD related.
    I'd keep the drive, check back OCZ and firmware, talk to others on the MacRumors and Groths.
    note: I reformat drives regularly, couple times a year, replace system drive also, and it is the amount of writes and I/O your SSD has to handle, not years. Even DVDs don't last two decades.

  • New CRM implemetation with R/3 4.7 as the backend using vertex

    I am trying to figure out how my new CRM system and my existing R/3 system should be configured to user Vertex.  I spoke to Vertex and they indicated only one of these systems should communicate directly with Vertex.  If that is the case, the existing R/3 system should continue to communicate with Vertex.  Then the question becomes how do we configure CRM to communicate with R/3 in order to get taxes from Vertex? 
    Thanks for any assistance

    hi,
    as far i see from the documentation , ECC has to be used as backend.
    But anyway you have to wait for the master guide to come up in the service market place , which will give details of what all combinations is possible.
    can you please check out on service market place wether master guide is released already , as far as i know it is yet to be released.

  • Need to find impact of Vertex O series upgrade on ECC and changes required?

    Hello experts,
    My client is upgrading Vertex series to O from Q.
    As part of Q series, additional fields such street will be used to identify correct tax jurisdiction code in system. 
    Also, zip code used will be 9 digits (zip+4) instead of 5 digits.
    We need to correct existing master data and open transactions in system with new jurisdiction code along with supporting new data in system.
    Below are the questions:
    1. What changes are required in ECC side to support new vertex series in interface etc?
    2. How can we achieve integration of vertex O series with new master and transnational data getting created in system to have right TXJCD value?
    3. What all possible solutions are available to correct master data and transnational data in system with correct TXJCD value?
    Any pointers to experience with Vertex will be rewarded.
    Thank you,
    Gouri. 

    Hi,
    > 1. is there any dependency for the remaining systems in the landscape (SRM 5.0 SPS15, NW 7.0 SPS18, PI 7.1 SPS8, >SOLMAN EHP01 SPS22)?
    As such there is no dependency between component you specified but SAP always says to be on latest patches. As far as solution manager is concerned you should have minimum support pack level Solman 7.0 SP17 but anyway you are more than that.
    > 2. we are using AIX Version 5.3 and "DB2 v9.5.0.2", does it support ECC 6.0 EHP04 or do I need to upgrade?..
    It is fine with your upgrade.
    > 3. Java version for NW 7.0 is as follows:
    > java version "1.4.2"
    > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
    > Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20080122 (SR10) (JIT enabled: jitc))
    > Does it support my requirement or any upgrade is required?
    >
    Java version is also fine.
    Thanks
    Sunny

  • SAP TAX is updated OK, Vertex is missing 2 weeks of tax data from SAP

    Hello FI Gurus,
    We have an issue where Vertex data are not updating for two weeks.  Although when running report "RFYTXDISPLAY" all indicated that documents were updated to external system.  We are mssing 2 weeks of data on the Vertext side.  Does anyone know if there is a way to manually update SAP billing with tax to Vertex so it can be recorded?
    Thanks in advance,
    HarryT

    Would need more detail on whether this is the last two weeks and issue still persists or if it was for only 2 weeks and everything now is fine.
    If the RFYTXDISPLAY/ TRFC Queue is clear(unblocked), make sure that the transactions are listed in the queue by doc #.
    How do you know the items aren't in Vertex?
    You wouldn't be able to duplicate in SAP to write taxes to Vertex.  It would throw off your G/L.
    If you still have issues, I'd call Vertex support 800-281-1900

  • MSI P67A-C43 (B3) & OCZ Vertex 3 VTX3-25SAT3 Issues

    Specifications:
    Quote
    Mobo/Laptop: MSI P67A-C43 (B3)
    BIOS: 1.B (2011-04-14)
    CPU: Intel Core i5-2500K
    RAM: 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 CML8GX3M2A1600C9B
    Vid: ASUS ENGTX560 TI DCII TOP/2DI/1GD5 GeForce GTX 560 Ti
    PSU: HX750 (CMPSU-750HX)
    HDD: OCZ Vertex 3 VTX3-25SAT3-120G v2.11
    Chipset: Intel P67 (B3) RSD v10.6.0.1002
    OS: Windows 7 Ultimate 64 Bit SP1
    Let's start from the beginning: So I built my PC in July and ever since I've been having on and off BSODs with the Vertex 3 drive. Mostly they'll happen once a week. When I first built the machine my drive came with Firmware 2.06. I installed all the drivers from MSI's website as well as the latest Intel Rapid Storage Drivers. Eventually I flashed the SSD to 2.11 when it was released but still had similar issues. Hotplugging was enabled when I installed Windows 7 for the first time AND when I flashed to 2.11 from 2.06. Some members over on the OCZ boards stated this might have been the cause of the BSOD. Basically the PC froze, BSOD'd, restarted, and then the system couldn't detect the drive. I had to power the system down, remove the power cable, wait 10 seconds, re-connect the cable and power on the PC. After I did this Windows booted normally.
    I received some advice on the OCZ forums to reset CMOS and leave hotplugging disabled. Then re-flash the drive to 2.11 with hotplugging disabled. Some members thought this would make the drive act like an internal drive, not an external drive. However, a week after doing this the same BSOD appeared. I've started from scratch last week by secure erasing the drive and re-installing Windows, but same issues. I noticed MSI released a new BIOS for my board in July. I have the one from April currently.
    Is it worth upgrading my BIOS? The listed fixes don't say anything about SSDs.
    I plan on trying this when I get home from work:
    Quote from: Tony;676791
    Going to keep this brief and to the point, this hack will force the 2 primary sata2 or sata3 ports on the motherboards to be designated Internal only...You can do this hack for all Intel chipsets from around ICH8 onwards in win7 and Vista.
    You also need to make sure hotplugging is disabled in uefi/bios if your boards bios has the option(s) do this first before you do any of these regedits etc
    1 Remove all traces of Intel drivers on your system, that means remove the management engine driver, the RST driver and the INF driver, you do this thru the programs and features option in control panel.  I remove them all before I reboot, the system will automagically set you using the MSAHCI driver.
    2 Now reboot, let win7 detect the ssd and reboot again.
    3 now open a elevated command window (CMD with administrator privileges) and copy/paste the following...then hit enter.
    Code: [Select]
    reg.exe add "HKLM\SYSTEM\CurrentControlSet\Services\msahci\Controller0\Channel0" /f /v TreatAsInternalPort /t REG_DWORD /d 0x00000001 
    Once you hit enter you can then add the following again using copy/paste.
    Code: [Select]
    reg.exe add "HKLM\SYSTEM\CurrentControlSet\Services\msahci\Controller0\Channel1" /f /v TreatAsInternalPort /t REG_DWORD /d 0x00000001 
    Hit enter and close CMD.EXE down, reboot
    This will now force the 2 sata 3 ports to Internal only, this means they will apply LPM if you set it and will support Automatic Partial to slumber.
    I now suggest you experiment with power schemes, for some high performance may work better than balanced...try both
    You also need to make sure hotplugging is disabled in uefi do this first before you do any of these regedits etc
    If you want to go a step further than this you can try the following...ONLY do this after you have done the steps above.
    remove the SSD to start
    1 create a temporary win7 install on a hdd, use the msahci driver and once installed do the hack to force the 2 ports to internal only. Have the hdd connected to port 1 on the motherboard.
    2 once the install is ready and you have installed toolbox to it power down and connect the SSD to port 0
    3 now boot to the HDD, use the manual boot menu option to make sure you are booting to the HDD and make sure hotplugging is OFF in UEFI
    4 once in win7, flash the FW to the drive, when its finished flashing, close toolbox, reboot back to the HDD and back into win7...make sure the SSD is detected in my computer.
    5 now power off, remove the HDD...then boot to UEFI and make sure to set the SSD as first boot device
    6 Power up, boot to the SSD
    Stay using the MSAHCI driver for now, do not install any INF, IME or RST drivers.
    Edit 09/09/11
    Had a few end users quoting disabling TRIM solved BSOD for them...now im not saying it will solve BSOD for all but it may be worth trying. Remember the SandForce controller was originally designed without TRIM in mind, it functions just fine without it so you should see no loss of performance. If you want to help the controller stay fast you could always add some extra over provisioning by reducing the volume on the drive and leaving that space unallocated...totally up to you what you do though....
    I like 25% OP on my drives, this means if I have a 120 with 115GB showing in windows I lose 15GB to OP and use 100GB for the volume....
    A forum member wrote a little script to enable /disable trim...he wrote in support for wiper for Indilinx drives also...just ignore that part and use the TRIM function only...
    http://www.ocztechnologyforum.com/forum/showthread.php?63830-A-small-script-to-enable-disable-Trim
    Here is a link to force TRIM also.. http://www.ocztechnologyforum.com/forum/showthread.php?73888-Here-s-a-tool-to-force-TRIM-your-entire-drive&p=523305&viewfull=1#post523305  you could if you wanted use this once a week to force the drive to TRIM all marked deleted blocks if you turn off native TRIM in win7.
    Again....not saying this cures any BSOD but a few end users have said they disabled TRIM and issues went away...anything I have suggested here is totally reversible and will do no harm to your systems.
    If this doesn't work and I get a BSOD after a week I'll disable TRIM and if that doesn't work I have no idea. OCZ said they're working on a new firmware release so who knows. I just hate feeling like I am a beta tester.
    If anyone has any suggestions let me know.

    OK, had some time to go test your suggestions here
    These are the 1.5V Vengeance RAM Modules.  Tried installing 2 of the RAM on slots 2 and 4 on their own.  System Boots Fine.
    Went into the BIOS and changed the voltage applied to the RAM modules from
    AUTO to 1.575V.   On AUTO it says is applying 1.5V to the 2x 4GB modules.
    Installed the full 4x RAM on all slots... and the system just shuts down.  Power cycling again.
    What do you think here?  Bad Motherboard?  Can't think of anything else to try...  totally stumped! 
    Thanks!

  • Mac Mini (Late 2014) not recognizing SSD OCZ Vertex 2

    Hello community,
    After days of tests and readings, I turn to you to seek for advice.
    Here is my problem:
    I am trying to upgrade a new Mac Mini (Late 2014 model) from it's original mechanical HDD to a Vertex 2 SSD I have been using for a few years with no problems to report, great product.
    First 1 cloned my HDD onto the Vertex 2 SSD using SuperDuper, all went well.
    I then switched disks and set the SSD in the SATA III slot inside the Mac Mini and reboot... the disk would boot, the recovery system and the disk utility would not see the disk (or it would see it just long enough to try to make a disk verification and then would disappear).
    Here is what I have already tried:
    - Boot from Linux LiveCD, I can see the Vertex SSD, I can see all it's file and browse them
    - Reformat the disk, in HFS+ with GUID partition table
    - Clean PRAM
    - Perform a Hardware Check - all good
    - Boot from the original HDD connected through a SATA-to-USB adapter - all good, i can boot the system, but i don't see the SSD drive (or only for a moment then as soon as i try some action on it (like a disk verification) it stalls and then disappears)
    - Try to OCZ toolbox to make a security erase and start fresh. I had here a major issue, the OCZ toolbox would not start, it froze after a lot of complaints a "Scanning for hard disk partitions and creating /etc/fstab" and wouldn't move.
    - Dissassembled the Mac Mini, removed the SSD, put it in a Macbook Pro, use OCZ Toolbox on it, this time, it loaded perfectly, identified the disk, i did a firmware update to the latest (1.37) and performed a security erase. All went perfectly. For verificiation I rebooted in recovery mode from the Macbook with the SSD and formatted properly the disk using the Apple Disk Utility (GUIP partition table+ HFS+ partition) and the system neatly identified it as a good host for system install. Then i removed the Vertex 2 SSD from the Macbook pro, put it back in the Mac Mini (reassembled it - god, that's a big pain !) and boot it again in recovery, only to see... nothing, the disk is still not recognized by the system.
    Voilà... now I'm out of idea, It could be some low level hardware incompatibility, or anything else, i read about TRIM and Yosemite sometime not behaving well, about SATA II and SATA III compatibility problems, but so far, nothing clear.
    I therefore welcome in anticipation your knowledge and hope we can figure this out. For the sake of extending the reach, I will also post this on Anandtech and Apple support forums.

    Well, thank you tbirdvet, but the problem was actually an incompatibility at the controller level.
    To quote the OCZ support :
    The issue is incompatibility between the older SandForce 1222 controller used in the Vertex 2 and the newer Intel Haswell platform used in the Late 2014 Mac Mini.  The incompatibility started with the Intel 8 and now 9 series chipsets and spans across all products that used the controller regardless of manufacturer.  It is expected behavior to be able to connect the Vertex 2 then clone to it, but if you try and cold boot to it the detection will fail.  Unfortunately, the Vertex 2 and the controller it utilized are long EOL and never received a firmware update (if that was even possible) to adjust for the release of these new chipsets.
    So I can stop looking around it simply wont boot, ever. Product being End Of Support, no new firmware will ever fix this.
    So I guess, i'll have to look another SSD.

  • Timeout during allocate of Vertex RFC

    Hi Guys.
    Im facing this odd issue after an offline backup is completed and brings the system.
    As you can see the Vertex RFC is no longer working and displays a timeout issue after a Sales programs tries to reach it.
    Also when testing the RFC is unable to initialize.
    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Gateway on host etgrws01.entegris.com / sapgw20
    M  *  ERROR       timeout during allocate
    M  *
    M  *  TIME        Tue Dec 28 16:43:08 2010
    M  *  RELEASE     640
    M  *  COMPONENT   SAP-Gateway
    M  *  VERSION     2
    M  *  RC          242
    M  *  MODULE      gwr3cpic.c
    M  *  LINE        1854
    M  *  DETAIL      no connect of TP /boltons/D01/vertex/3.3/TransLink/verrfc from
    M  *              host etgrws01.entegris.com after 22 sec
    M  *  COUNTER     6378
    M
    A  RFC 1448  CONVID 40614370
    A   * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPECMINIT
    A  RFC> ABAP Programm: CL_XTAX_RULES_RFC=============CP (Transaction: VA02)
    A  RFC> User: VMESENBR (Client: 200)
    A  RFC> Destination: VERTEX (handle: 3, , )
    A  *** ERROR => RFC ======> CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
    Timeout during connection setup. Please check partner availability
    [abrfcio.c    7933]
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1464
    CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
    Timeout during connection setup. Please check partner availability
    DEST =VERTEX
    HOST =etgrws01
    PROG =/boltons/D01/vertex/3.3/TransLink/verrfc
    [abrfcio.c    7933]
    That /boltons/D01/vertex/3.3/TransLink/verrfc is located on the same server as the SAP application, so i cannnot figure out why is showing partner not available/timeouts, when is pinging a program on the same server.
    I have tried restarting the Dispatcher
    rfc/use_gwstart =1
    Increased CPIC timeout value gw/cpic_timeout =120 (Increased CPIC timeout)
    I have also searched thru these notes but still no luck
    Note 581509 - Reasons for timeout during allocate
    Note 638701 - Starting RFC servers takes too long
    Note 948636 - Starting executables locally using RFC
    The only workaround for this, is restarting the SAP Application, in order to have the RFC working again, but this seems an overkill to fix an RFC Ping Issue.
    All ECC Systems have the same program version and configuration but only Dev system is facing this.
    The whole point of this, is why when the system is shut down in order to perform an offline backup causes this, and the only way to fix this, is shutting down/start up the system again.
    If you have some ideas of what could be causing this, it's would be highly appreciated.
    Martin

    Hi Martin,
    We are experiencing the same issue with SAP/Vertex. Can you let me know how you resolve this? Did you change the SAP gateway timeout parameter? If so, which one is it?
    Your help on this is greatly appreciated.
    Thanks much!
    Best regards,
    Cyanna

  • How can i get my hp dv-7 to stop blue screening with the new ocz vertex 3 ssd

    installed a new ocz vertex 3 ssd on my pavilion DV-7-6b75nr and it will now not stop blue screening.Even took it to a computer shop and they could solve the issue. is this laptop not meant for sata 3 SSD's or do i need a certain one or does hp have to install it? windows7,computer 3 weeks old,I7 processer...using the SSD for my os and main boot drive..Computer shop said i might need to rewrite HPs bios...??

    Hi,
    You can find the list on the following link:
        http://h10025.www1.hp.com/ewfrf/wc/document?docnam​e=c02763358&tmp_task=prodinfoCategory&cc=us&dlc=en​...
    Please install the following list:
    1. Software multimedia
    2. All components of Software solutions
    3. Utilities
    from the following link:
       http://h10025.www1.hp.com/ewfrf/wc/softwareCategor​y?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=5064​...
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • MacBook Pro 11/2007 problem with SSD OCZ Vertex Series 250 GB

    Hi,
    you can read my detailed problem in the OCZ board here:
    http://www.ocztechnologyforum.com/forum/showthread.php?t=64941
    The short version:
    - I bought an OCZ Vertex SSD with 250 GB for my 2 years old MacBook Pro
    - System Details: MacBookPro3,1; Boot Rom: MBP31.0070.B07; CPU: Intel Core 2 Duo 2.4GHz; SMC: 1.18f5
    - The first 250 GB OCZ SSD was an firmware 1.3 and I could install it with Snow Leopard very easy. After 2 days the HDD just disappeared and it also didn't work in an other PC with an internal SATA port and also not with an external disk with sata to FireWire / USB
    - I RMA'ed the disk with OCZ and received a new one with firmware 1.4. I tried to install the computer from scratch and it couldn't write the partition when the SSD was connected to the internal SATA port of the MBP. I used the external SATA to USB and formated the disk with another mac. Then I could install SL from scratch but after some hours the computer began to stall and after the reboot it tried to run fschk and I got the error: "kernel[0]: disk0: I/O error."
    (again: Further details please have a look at the link above)
    - When I boot the system through firewire with the SSD connected through SATA to Firewire it works like a charm but that doesn't make sense (Having a MBP with an external boot drive)
    - I RMA'ed the disk again and last week I received the third one but it had the exact same problem.
    So now OCZ told me to ask apple for a possible solution. Does anybody have an idea what to do?
    I've read two posts about OCZ problems and they wrote about efi 1.7 problem and with efi 1.6 it would work. Didn't try it out yet - should I?
    Thanks for you help!
    --Goetz aka Tankmann

    No ideas?

  • IPC UserExits, Custsomer Account Class, Populate ACCNT_CLS For Vertex

    With reference to our landscape: CRM40 w/ IPC40 SP 07 Patch 26.
    We are in the process of extending our CRM 40 system for consumer use in Canada. We have been running our US implementation since 2005. In the US we have implemented the java PricingUserExits in order to implement our custom routines.
    For Canada however, we have a user exit in R/3 side that contains functionality we need to replicate in our CRM system. This userexit is implemented (based on oss note 302998) in order to populate CH_USER_CHANGED_FIELDS-ACCNT_CLS field. The  userexit name is EXIT_SAPLFYTX_USER_001. Below is the code segment:
      select single gform
             into ch_user_changed_fields-accnt_cls
             from kna1
             where kunnr = ch_user_changed_fields-accnt_no. "Ship-To
    On the r/3 system, the ACCNT_CLS value is passed to Vertex which in turn handles the proper tax determination.
    I have researched OSS, SDN and Web as well as my own trial and error coding in java user exits ItemTaxUserExit and DocumentTaxUserExit in order to bind ACCNT_CLS attribute along with a hard coded value. However the functionality/result I expect is as if Vertex is not receiving or recognizing the value. I can bind the attribute ACCNT_CLS without error. Here is the simple explanation of my enhancement:
    In ItemTaxUserExit.addAttributeBindings  along with some conditional logic, I am invoking the following method calls against object itemUserExitAccess and document
    itemUserExitAccess.addHeaderAttributeBinding("ACCNT_CLS","GW");
    document.addHeaderAttributeBinding("ACCNT_CLS","GW");
    in ItemTaxUserExit.determineRelevantAttributes I have specified the following:
    return new String[] { PricingCustomizingConstants.AttributeNames.product_taxability_type, "ACCNT_CLS" };
    One thing to note is the ACCNT_CLS is not one of the PricingCustomizingConstants.AttributeNames so I have explicitly used ACCNT_CLS.
    I also output the value of this attribute to the log to verify it has been set and contains value. It is successful and has value
    Log.getInstance().log(this,Severity.DEBUG,"accntclsBinding was not null " + accntclsBinding.getName() + " = " + accntclsValue.getValue() ,null);
    I feel I am heading in the right direction but possibly off the beaten path. I have tried to bind bogus attributes and receive a java null pointer exception so binding ACCNT_CLS successfully is a good thing. But why it is not communicated to Vertex.
    I found two oss notes 673222 and 586939. Do you feel these are applicable and an appropriate for resolving my issue?
    Any advise and direction you can provide would be greatly appreciated.

  • Z68A-GD65 (G3) not always finding ocz vertex 3

    Me and a friend just bought identical setups, among them was the Z68A-GD65 (G3) motherboard and OCZ Vertex 3 120GB SSD. Both of us get some random crashes and sometimes when trying to boot the computer the SSD does not show up in BIOS (therefore can't boot from SSD). This also happens after a random crash. This usually gets temporarily fixed if you do a hard reboot. However it is very annoying when the computer freezes randomly (can be days between freezes). When BIOS cant' find the SSD it takes a longer time to show the mobo splash screen thingy.
    It is noteworthy that when doing a "hard reboot" it sometimes takes the computer about 5 seconds to startup after pressing the power button.
    Anyone got an idea how to fix this?
    I don't really know how i would go about solving this as it works most of the time so i don't want to fiddle with things i don't completely understand.
    System spec:
    CPU: i7 2600K, 3.4GHz
    Motherboard: MSI Z68A-GD65 (G3), v 23.1
    RAM: 4xCorsair Vengeance Low Profile 4GB DDR3 PC-12800 1600MHz (16GB total)
    GPU: Sapphire HD6950 1GB
    SSD: OCZ Vertex 3 120GB
    OS: Windows 7 Ultimate
    PSU: 650W Corsair

    Quote from: Henry on 17-October-11, 06:59:47
    Check with OCZ for the latest firmware update and see it that fixes your problem.
    Had to install Linux for that and had alot of trouble, but after some hours i finally updated the firmware.
    We will see if it ever happens again.

  • [Solved][OpenGL]Vertex Buffer Objects - Crash on binding a buffer.

    I am writing a little test application which is more or less just meant for learning and developing some of the underlying classes. I have recently decided to try replacing the immediate mode rendering with Vertex Buffer Objects. Since VBO's have been part of core OpenGL since 1.5, this should be no problem. Unfortunately, it does seem to be a problem, as the program crashes on the call to glBindBuffer. According to the debugger, it's a segmentation fault, which doesn't tell me much. I'm not sure what is going on, but I know my laptop supports well over OpenGL 1.5. ( I have up to OpenGL 2.1 until the Mesa libraries and ATI drivers get updated to allow OpenGL 3.2 on my card )
    I am using SDL 1.2 with OpenGL.
    Some code snippets of the VBO code.
    GLuint *VBOID;
    glGenBuffers(1, VBOID); // Works fine
    glBindBuffer(GL_ARRAY_BUFFER, *VBOID); //Crashes on this line
    Last edited by Katherine1 (2012-07-04 15:27:02)

    GLuint vboid;
    glGenBuffers(1, &vboid);
    glBindBuffer(GL_ARRAY_BUFFER, vboid);
    Your vboid is currently pointer, is it allocated? If it isn't your code makes no sense at all and it's miracle it doesn't crash on gen call.
    Also, gdb will tell you more if you read the documentation
    Last edited by Cloudef (2012-07-04 15:14:02)

  • W520 support for SATA III or 6GB with Vertex 3 240GB SSD

    I need a laptop that supports 16GB memory, HD display (1920 X 1080) and SATA 3 with 6Gb speeds to leverage my existing Vertex 3 240GB SSD.
    Looking up PSREF, I find the W520 specs state SATA 3Gb/s (SATA II?) while the chipset is QM67 which is supposed to support SATA III 6Gb/s.
    So the question is, does the W520 support SATA 3 at 6Gb/s? I need the throughput to leverage the throughput of the Vertex 3 240GB SSD  for multiple VM's on my laptop.
    Thanks and regards
    Sarge Thomas
    Solved!
    Go to Solution.

    Just for the record i been using several SSDs with the W520 including the OCZ Vertex 3 and OCZ Vertex 3 max and they both fit fine with the rubber rails in the W520. Just don't mount the case that is normally around the HDD/SSD. You won't need that case anyway when using the SSD in the W520. Use only the rubber rails and the SSD will fit fine and should be seated fine as well.
    -gan

Maybe you are looking for