Koperun

 GAS 2026 attendees guide. Guys, if you're staying in the city on Tuesday after the Day 2 event, I have a proposition for you: - Go and eat something tradiotional and regio nal at Śląska Prohibicja ( Home - Śląska Prohibicja ) Book your table in advance!!! Take uber or bus https://maps.app.goo.gl/wHz26XcQqDeiaXiw6 There traidional LOCAL  dishes are: ŻUR  for a soup and ROLADA Z KLUSKAMI for the main course. Traditional Polish dishes are: ROSÓŁ and PIEROGI / KOTLET SCHABOWY Alternatively if you don't want to travel, you can walk to a similar restaurant: Restauracja Tatiana Katowice - Contact us But I strongly recommend the first one! For walks:  go to the 1. Trzy stawy park,  or 2. Kościuszko park,    and take a walk on 3. Mariacka street. And walk around 

The previous post covered replacing a disk in a mirrored rootvg, which is the hard case: boot image, boot list, dump device, and a long stretch where the machine runs on one disk. This is the case you will hit far more often — a failing disk in an ordinary mirrored volume group — and there is a single command for it that a surprising number of AIX administrators have never used. replacepv replacepv hdisk2 hdisk10 That is the whole thing. It moves every physical partition off the failing disk onto the replacement, removes the old disk from the volume group, and leaves the mirror intact the entire time. No unmirrorvg , no reducevg , no window where your data has one copy. It is not a general-purpose tool and that is why people forget it exists. Six conditions have to hold, and if any of them fails you are back to the long procedure. The first one is the killer. replacepv does not work on rootvg, full stop, which is exactly why the previous post is as long as it is. Why it is wor...

A disk in a mirrored rootvg is the one disk you cannot just pull. It holds the boot image, it probably holds the primary dump device, and half of every logical volume on the system lives on it. Pull it without preparation and reducevg refuses, or worse, the machine comes up on nothing after the next reboot. This is the full sequence for a two-disk mirrored rootvg on AIX, replacing hdisk0 . Non-root volume groups are much simpler and I have noted the difference at the end. Decide whether you actually have a problem Disks rarely die cleanly. They complain first, and the complaints show up in the error log: errpt | more 1581762B 0727203502 T H hdisk0 DISK OPERATION ERROR 1581762B 0727203502 P H hdisk0 DISK OPERATION ERROR The third column is the one that matters. T is temporary, P is permanent. A single temporary error on a busy system is noise. A cluster of them over a few hours is a drive on its way out. A permanent error is not a warning, it is a report of ...

Commvault's own documentation covers the Oracle iDataAgent well enough, and it covers Solaris well enough, but it does not walk you through the two together on a text-mode installer where one wrong answer means you reinstall. This is that walkthrough, from a clean Solaris 11.3 box to a working sbt_tape channel in RMAN. All hostnames, addresses and group names in the screenshots are placeholders. Substitute your own. Before you start You need the Commvault Solaris agent package staged somewhere on the machine, the CommServe hostname, and a decision from whoever runs your backup platform about which storage policy this client belongs to. You will be asked for that at the end and you cannot skip it. Oracle is assumed to be installed already, with a known ORACLE_HOME and the usual dba and oinstall groups. 1. Create the backup user Commvault processes that touch the database run as a dedicated user rather than as oracle or root . Create it, give it a password, and put it in t...

A 68,000-line command reference for Solaris, AIX, HP-UX and Linux, converted from a plain text file into navigable Markdown. Download link at the bottom. What it is Albert van der Sel compiled UNIX command examples over years of DBA work — commands for Oracle, DB2 and SQL Server administrators who have to keep the box underneath the database alive. Version 115 is dated 2009. I have been carrying the text file around since, adding to it. The problem with the original is not the content. It is that 2.8 MB of plain text with no structure is only usable through Ctrl+F, and only if you already know the exact string you are looking for. So I converted it. Headings are real headings now, command listings are fenced code blocks, and there is a table of contents with 207 entries at the top. You can scroll it, link into it, and read it on a phone. What is in it Memory, swap and CPU inspection on five platforms, side by side. Mount and NFS. Permissions, sticky bit, SETUID. find , crontab ,...

For about three years, every big AI lab behaved like a teenager with a new car. Look what mine can do. Look at my benchmark. Look at my context window. Every few weeks somebody published a chart where their bar was taller than everybody else's bar, and we all went along with it, because the bars kept getting taller and the models kept getting better and it was fun to watch. Meanwhile China said almost nothing. Then once in a while DeepSeek dropped something that knocked everyone off their feet, everyone spent a week arguing about training costs, and the noise started again. That era is over. It ended in April 2026, and I don't think we noticed how completely. The race we thought we were in The mental model everybody used was Formula 1. Whoever builds the fastest car wins the season. Speed was the whole point, and speed was something you showed off, because showing off is how you raise the next round. Some people preferred the Manhattan Project comparison. I used to think that o...