Licence-aware placement.
Rymvard counts processors the way your rules say — soft partitioning counts the cluster, pinned cores count only what is pinned — before a VM moves, not after.
Oracle hosting
Every Oracle processor counted.Every application, ready to recover.
For providers that host Oracle applications and databases — E-Business Suite, JD Edwards, PeopleSoft, Siebel and Hyperion — and their teams: Rymvard checks whether every application and its database can recover at the second site, counts the processors your licence rules require wherever a VM lands, and plans upgrades and the next landscape against the capacity you really have.
Read-only. New in version 0.27 — the screens show an illustrative example estate, not a customer.
Where a VM lands decides what you owe.
On shared virtualisation one Oracle database can make a whole cluster count. Middleware on the application tier needs its own processors unless the application licence includes it. And the standby that should carry production at the second site is often the one nobody has tried.
Recovery, end to end.
An application is ready to recover only when its application tier fits at the second site and its Data Guard standby can carry production. Rymvard checks both, per system.
Upgrades with a double run.
An E-Business Suite 12.2 upgrade or a new tools release: Rymvard plans the upgrade copy on its target, week by week, and names the week it breaks.
What Rymvard shows
One view of every Oracle landscape.
Systems by product and environment, their tiers and databases, recovery verdicts, support dates and licence positions — each traceable to the record and the moment it was observed.
Applications like SAP systems.
E-Business Suite, JD Edwards, PeopleSoft, Siebel and Hyperion as landscapes per customer and environment — web, application, batch and database tiers on their hosts and VMs.
Middleware licences.
WebLogic Server, Forms & Reports and Tuxedo counted on the hosts that run them, with the restricted-use rights the application licence includes.
Database depth.
Processors by your core factors and partitioning rules, Standard Edition 2 limits and Named User Plus minimums, options in use — and an audit evidence export per customer.
Support dates and upgrades.
Releases leaving Premier Support within 24 months from the dates you enter, and the capacity every upgrade double run needs.
Read-only, from your Oracle estate.
Rymvard reads inventories and observations. It never changes an Oracle system.
- Oracle REST Data Services with a fixed list of read-only queries, Oracle Enterprise Manager targets, or CSV templates and the REST API.
- Licence rules, minimums and entitlements exactly as you enter them — your contract decides, Rymvard counts.
- A standby whose replication evidence is older than one hour is unknown — never ready.
- Detailed records stay in their country; customer names are visible only to the people who need them.
New in 0.27 · Workspaces
Four homes for Oracle teams.
Oracle operations, sales, customer management and lifecycle planning each open Rymvard on their own home — their question, their four figures and only their findings, with AI that explains every number and suggests the next step. See the workspaces
Oracle Applications Operations
Does every Oracle application have room and a working standby?
- Oracle recovery checks failing
- Oracle PRD systems without protection
- Oracle recovery checks unknown
- Oracle recovery checks ready
Oracle Applications Sales
Which Oracle landscape can I offer, where — and from when?
- Oracle site pairs offering the smallest profile
- Oracle application profiles
- Oracle middleware positions short
- Oracle upgrade copies breaking capacity
Oracle Customer Management
Is every customer's Oracle landscape protected and supported?
- Oracle customers with unprotected PRD
- Oracle customers leaving support
- Oracle customers with middleware shortages
- Oracle application customers
Oracle Upgrade & Lifecycle
Which releases leave support, and which upgrades land when?
- Oracle systems past Premier Support
- Oracle systems leaving support within 24 months
- Oracle upgrade copies breaking capacity
- Oracle systems with unknown support dates
Screens from the running product on its example estate. Customer names appear only for planners and admins — findings never name a customer.
Across every vendor
Every licence, one table.
Oracle, Microsoft, Broadcom, Red Hat, SUSE and IBM positions side by side on Licences & Audit — what is short, what is unknown and what goes into this month's reports. Licence-aware placement
Count every processor before the audit does.
One Oracle estate, read-only: which systems can recover, which processors and options are short, where the next landscape fits.