---
title: "Uptime Architect (@uptimearchitect) | Hashnode"
description: "Independent, vendor-neutral Oracle reliability & performance — RAC, Data Guard, tuning, OCI/Azure. Read the latest articles by Uptime Architect on Hashnode."
url: "https://hashnode.com/@uptimearchitect"
---

@uptimearchitect

# Uptime Architect

@uptimearchitect · Joined June 2026

Independent, vendor-neutral Oracle reliability & performance — RAC, Data Guard, tuning, OCI/Azure

[Website](https://uptimearchitect.com/)

### [ORA-04068 After a Deploy: The Retry Works. The Package State Is Gone.](https://uptimearchitect.hashnode.dev/ora-04068-after-a-deploy-the-retry-works-the-package-state-is-gone?utm_source=hashnode&utm_medium=feed)

Why ORA-04068 hits once per connection after a PL/SQL deploy, which packages raise it, and how SERIALLY\_REUSABLE and EBR avoid it. Lab-proven.

16 min read · [uptimearchitect.hashnode.dev](https://uptimearchitect.hashnode.dev/ora-04068-after-a-deploy-the-retry-works-the-package-state-is-gone?utm_source=hashnode&utm_medium=feed)

[23h ago](https://hashnode.com/posts/ora-04068-after-a-deploy-the-retry-works-the-package-state-is-gone/6afe10a4127a3bb7a61be601)

### [ORA-00054 Resource Busy: Find the Session, and Know Which DDL Will Wait](https://uptimearchitect.hashnode.dev/ora-00054-resource-busy-find-the-session-and-know-which-ddl-will-wait?utm_source=hashnode&utm_medium=feed)

Find the idle session behind ORA-00054, see which DDL waits instead of failing, and why DDL\_LOCK\_TIMEOUT stalls every writer. With a free lab.

14 min read · [uptimearchitect.hashnode.dev](https://uptimearchitect.hashnode.dev/ora-00054-resource-busy-find-the-session-and-know-which-ddl-will-wait?utm_source=hashnode&utm_medium=feed)

[2d ago](https://hashnode.com/posts/ora-00054-resource-busy-find-the-session-and-know-which-ddl-will-wait/6afc686b1077fdff1dba87f9)

### [ORA-03113 After the Connection Sat Idle: The Firewall Forgot It](https://uptimearchitect.hashnode.dev/ora-03113-after-the-connection-sat-idle-the-firewall-forgot-it?utm_source=hashnode&utm_medium=feed)

Why idle pooled Oracle connections fail with ORA-03113 or ORA-03135 behind a firewall or load balancer, and the SQLNET.EXPIRE\_TIME fix.

14 min read · [uptimearchitect.hashnode.dev](https://uptimearchitect.hashnode.dev/ora-03113-after-the-connection-sat-idle-the-firewall-forgot-it?utm_source=hashnode&utm_medium=feed)

[5d ago](https://hashnode.com/posts/ora-03113-after-the-connection-sat-idle-the-firewall-forgot-it/6af878095d514f5227f9ebb5)

### [ORA-01000 Maximum Open Cursors Exceeded: Don't Raise the Limit, Find the Leak](https://uptimearchitect.hashnode.dev/ora-01000-maximum-open-cursors-exceeded-don-t-raise-the-limit-find-the-leak?utm_source=hashnode&utm_medium=feed)

ORA-01000 is a per-session cursor leak, not a low limit. Find the session and the statement, skip the cached-cursor trap, and see why a raise fails.

14 min read · [uptimearchitect.hashnode.dev](https://uptimearchitect.hashnode.dev/ora-01000-maximum-open-cursors-exceeded-don-t-raise-the-limit-find-the-leak?utm_source=hashnode&utm_medium=feed)

[Nov 11](https://hashnode.com/posts/ora-01000-maximum-open-cursors-exceeded-don-t-raise-the-limit-find-the-leak/6af4a7f6fe352d7842e53720)

### [SYSDATE Is Hours Off After the Move to the Cloud. Nothing Errors.](https://uptimearchitect.hashnode.dev/sysdate-is-hours-off-after-the-move-to-the-cloud-nothing-errors?utm_source=hashnode&utm_medium=feed)

After a move to a UTC cloud host, Oracle SYSDATE is hours off with no error. Why DBTIMEZONE doesn't fix it, and the two fixes that do.

13 min read · [uptimearchitect.hashnode.dev](https://uptimearchitect.hashnode.dev/sysdate-is-hours-off-after-the-move-to-the-cloud-nothing-errors?utm_source=hashnode&utm_medium=feed)

[Nov 8](https://hashnode.com/posts/sysdate-is-hours-off-after-the-move-to-the-cloud-nothing-errors/6af08810ac2f991d14545f32)
