We have a Cache Battery failure on 550boxes, will it affect?

1005 pts.
AS/400 hardware
Cache battery
Cache Battery Failure
IBM System i 550
We have a Cache Battery failure on 550boxes, and the disks attached to the disk controller seem to show degrade in performance, and to replace it we might need to IPL to DST, but our customer has not agreed for a downtime till 20 more days to come. WIll it cause a problem or is it OK to run with the degraded disks? Thanks in advance

Answer Wiki

Thanks. We'll let you know when a new response is added.

Are you sure the battery can’t be replaced concurrently? Most of them can. If you are seeing performance degredation in performance data, then it is real, so it just depends on what your customer would rather risk, degraded performance or the risk of concurrent replacement.

We have had cache battery failures before but our users hardly notice degraded performance, but of course, they need to replaced sometime. The system will warn you about 90 days before they actually fail. From my experience, the system needs to be down for about 1 1/2 hours because our battery packs have never been concurrently maintainable. IBM recommends that you replace the batteries before you receive failure messages, so the way to view when you will get warning and then failure messages (and mark it on your calendar) is this:

Go into SST (STRSST) and take options 1, 4, 1, 2, 14 (Start a service tool, Display/Alter/Dump, Display/Alter storage, Licensed Internal Code (LIC) data, Advanced Analysis). Type a 1 to select BATTERYINFO and then enter -INFO -ALL on the Option parameter. It will show you the estimated number of days that the system will issue a warning followed by the estimated numbers of days until failure. Just below that it will tell you if your battery pack is concurrently maintainable.

Good luck.

Discuss This Question: 6  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • WoodEngineer
    The cache battery effects on your disk controller card. When the battery is out, the system requires confirmation of a disk write before allowing processing to continue. This is what slows the system. We had to shut down our 520 to replace the battery. The kicker was that IBM strongly recommended an Option 21 Save before replacing the battery. That was the real time killer. It seems like a whole lot of CYA but that is the way IBM likes to do things. The save is your option. A battery typically lasts about three years.
    8,225 pointsBadges:
  • Batman47
    There is a natural fear from some people when you see cache battery packs fail. I've been administrating the iSeries since it came out in 1988. The system has never crashed despite these cache battery packs running out of life and IBM never recommended performing a save before replacing them since they are obviously aware of the system's design.
    1,050 pointsBadges:
  • DanD
    I agree, and of late have been letting IBM replace the batteries concurrently, but several yrs ago a CE wiped out my ASP when he initialized a cache battery before replacing it. Fortunately we had done a save lib immediately before he went to work killing my system, but I had to wait for the last savsys to be sent from Iron Mountain, and ened up working straight through for 32 hours restoring the system. If you have the time, it is better to do the save first and replace the battery(s) from DST.
    2,865 pointsBadges:
  • mcl
    Some of the newer systems are set up so the batteries can be replaced concurrently. Most of the others are easy to do, but the system has to be down. We have a 570 that required about 4 hours to replace the batteries on the controller in the 570 chassis - but most of the others are 1 to 1 1/2 hours. Most of that time is powering the system down and back up - if the IBM CE knows what to do. Yeah, you could do a save first - it all depends on your backup strategy as to what you might need to save - and when you did a full backup last. I highyly recommend checking the battery status periodically using STRSST. The number of days to warning and error are estimates. System IPL's will tend to change those values. You can run for a while with a battery error state. We ran for two months with a battery error on our development box because purchasing had not renewed the service contract and wouldn't pay for a service call. I did a lot of grumbling during that time... Regards Mike
    2,740 pointsBadges:
  • harisudhan21
    There was a decline in the performance and we had critical overnight jobs running all through the day as a result of this during the Quarter end process. So we had to change the battery asap and there was a considerable difference in the system speed! Thanks all for the discussion! Hari
    1,005 pointsBadges:
  • Splat
    This happened to us a year or so ago. I/O performance was noticeably degraded, but per my CE nothing was at risk. We took the system (a 525) down for the battery replacement - the CE wasn't keen on the idea of hot-swapping that part. If you do drop the system for the replacement, use the *CNTRLD option on your ENDSBS - this tells the system to clear the cache, preventing data loss.
    12,865 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: