Search results

Does each client connect to all these databases? Is ipurchprod the first database the clients connect to?

src/web/objects/web-disp.p is a standard program but your application calls it from $DLC/src. It can be a customized version. tptstart-new.p is a part of application.

The probability that the cause is rcode corruption is, IMHO, very low. Upgrade your Progress version first.

There are many articles about error # 1179.

You know the rcode's names

Or rcode corruption, for example. Protraces point out that the same rcode and the same statement in rcode was running while the errors were issued. But the best choice is to upgrade your Progress version first.

So BFP locks are zeroes - as expected. So it's not expected for latchId 18 to be mentioned in the errors.

You only get stats for the first 15 latches. You need to press ENTER one more time.

It's statistics since db startup. Type S to get statistics for a sampling interval.

Enter <return> for more.

Type: debghb Press ENTER Screen will stay unchanged Type: 6 Press ENTER and you will get This menu is not here Menu

promon R&D debghb - in V11.7 you need to enter a secret password; 6 - a hidden menu ("This menu is not here Menu"); 11. Latch Counts

Example: 07/01/26 Activity: Latch Counts 15:51:15 07/01/26 15:41 to 07/01/26 15:51 (10 min 1 sec) ----- Locks ----- ------ Busy ------ Naps ---------- Spins ----------- ----- Nap Max ----- Owner Total /Sec /Sec...

When db will be up and running again check promon / Activity: Latch Counts Does BFP latch (latchId 18) activity is zero for intervals when backup is not running? It's HIGHLY recommended [2026/07/18@12:46:29.000+0000] P-6251 T-139917056815360 I WSAGENT 0: (49) SYSTEM ERROR: Memory violation...

It's very difficult to answer these questions for memory violation errors. Strictly speaking, it's not an error, but a consequence of an error. The bug caused an access to an invalid address. As a result, the code received or modified invalid data. This will continue until the invalid address...

In other words, transaction activity continued after the memory violation errors. Latches 14 and 18 were not permanently locked. Hence the corresponding error messages are not part of the root cause.

prodb empty empty rfutil empty -C aimage truncate -aiblocksize <your-db-ai-blocksize> rfutil empty -C aimage scan verbose -a <ai-name> > scan.txt > APW/AIW later reported lock stack corrupt/underflow and broker initiated abnormal shutdown code 2. The structures in shared memory were already...

[2026/07/13@06:19:46.015-0500] P-17611 T-140394007668160 I AIMGT 22: (3778) This is after-image file number 213817 since the last AIMAGE BEGIN [2026/07/13@06:19:51.016-0500] P-17611 T-140394007668160 I AIMGT 22: (13199) After-image extent /ai/prod/ipurch/ipurchprod.a6 has been copied to...

Did you check the protrace files? /apps/ipurchase/work/webspeed/agents/protrace.12422 /apps/ipurchase/work/webspeed/agents/protrace.11762 /apps/ipurchase/work/webspeed/agents/protrace.17354 /apps/ipurchase/work/webspeed/agents/protrace.17338 > [2026/07/13@06:35:46.082-0500] P-17618...