No database users
It reads Oracle inventory from the OS and instance configuration — it never logs in to create a monitoring account inside your databases.
The Data Collector
Discovery with a smaller blast radius.
One file. Zero dependencies. Every host.
A temporary privileged shell, a set of AES-256 encrypted output files, and no persistent credentials left behind on any host.
The collector is a single self-contained bash program that discovers Oracle software across the estate without installing an agent, creating a database user, or opening a listening port. Copy it, run it, take the encrypted output with you.
Why it's different
Discovery that respects your security model
Most tools need broad, permanent access. The collector needs only a temporary, privileged shell — and it works even when no single machine can reach the whole estate.
Encrypted by default (AES-256)
Output files are sealed with AES-256 before they ever leave the host. Transport method is your choice.
Segmented networks + least privilege
Designed for estates where no single workstation can reach every server. Run it per zone under a temporary privileged shell.
No agent, no listener
Nothing is installed and no port is opened. The collector is a script that runs, produces encrypted files, and exits.
Platform native
Linux, AIX, HP-UX, Solaris and Windows via Cygwin, using only functions already present on the host.
Optional real-time WRT daemon
A daemon mode streams DB, FMW and OS workload metrics so analysis isn't limited to a single snapshot.
Run modes
Snapshot or stream
A sealed, point-in-time snapshot
Produce an encryption-sealed inventory for a renewal or an audit — one command, no configuration on the host.
- One command
- AES-256 output
- No host changes
# ./LMSCloud collect ALL ALL
# ./LMSCloud uploadContinuous compliance
Stream workload metrics so drift, under-licensing and unused entitlements surface continuously instead of once a year.
- DB · FMW · OS metrics
- Configurable frequency
- Trend over time
# ./LMSCloud daemon start
# ./LMSCloud daemon status
# ./LMSCloud daemon stopAccess & privilege
Run under a temporary privileged shell. Root auto-detects new software owners; sudo keeps tighter, explicit control. Nothing persists when the run ends.
- Root or sudo
- Per-owner grouping
- No persistent credentials
# sudo ./LMSCloud collect ALL ALL
# ./LMSCloud daemon stopCollect everything, once
A complete inventory of Oracle Database, Fusion Middleware and OS/CPU data in a single pass — ideal before an audit or a renewal.
- DB instances & options
- Middleware deployments
- Servers, sockets & cores
- Encrypted output
# mkdir /lmscloud
# cp LMSCloud /lmscloud/
# cd /lmscloud/
# ./LMSCloud collect ALL ALL
# ./LMSCloud uploadStream workload over time
Run the collector as a daemon to feed Workload Real-Time metrics into the dashboard — the same data behind “how much work is this system actually doing?”
- DB · FMW · OS metrics
- Configurable frequency
- Time-series analysis
# ./LMSCloud daemon start
# ./LMSCloud daemon status
# ./LMSCloud daemon stopRoot vs sudo
As root, the collector automatically detects any new Oracle software owner and adds their software without further interaction. As a non-root / sudo user you keep tighter control, at the cost of extra work each time a new owner appears.
- Root detection
- Per-owner grouping
- No persistent credentials
Home directory layout
/lmscloud/
├── LMSCloud the collector
├── custom_location.conf map hosts to locations
├── libs/ optional helpers
├── logs/ run logs
└── output/ encrypted result files
Coverage
Supported platforms
No runtime, no package manager, no compiler. If the host has a POSIX shell and standard utilities, the collector runs.
| Platform | How it runs | Requirements | Operational impact |
|---|---|---|---|
| Linux | Native bash, root or sudo | None — built-in utilities only | No install, no change ticket |
| AIX | Native shell, root or sudo | None | Nothing to patch |
| HP-UX | Native shell, root or sudo | None | Nothing to patch |
| Solaris | Native shell, root or sudo | None | Nothing to patch |
| Windows | Via Cygwin | Cygwin base | Runs inside existing Cygwin |
Evidence
From encrypted output to analytics
One sealed output file carries everything the business needs for an audit and everything the engine needs to compute cost and coverage.
What's in the encrypted output
- AESSealed output — every file encrypted with AES-256 before it leaves the host.
- DBDatabase inventory — instances, editions, options and effective cores.
- FMWMiddleware inventory — Fusion Middleware deployments and versions.
- OSServer detail — sockets, cores, virtualisation and core factor.
- WRTOptional metrics — real-time DB, FMW and OS workload series.
- SHAChain of custody — checksum for verification and replay.
Collector output
LMSCloudDB · FMW · OS inventory
WRT daemonreal-time metrics
↓
Ingest
mdb() · mfmw() · mos() · m_opl()validate + alerts
↓
SMART-DB · PostgreSQL
dbworkload · fmwworkload · osworkload_realtimeraw tables
db_view · fmw_viewnormalised views
rdb() · rfmw()cost & coverage
Start from the audit checklist.
Audit-ready inventory, without touching the estate.
Walk your security and compliance team through exactly what the collector reads, what it produces and what it leaves behind.
Run the collector against a zone, upload the encrypted results, and let the SMART-DB engine do the rest.