DB Home

One database’s alerts, Process Scheduler, Integration Broker, sign-ins, projects, and reports on one page.
Categories:

DB Home shows the current state of one PeopleSoft database: its connection, alerts, Process Scheduler and Integration Broker status, sign-ins, recently changed projects, and report activity.

Opening DB Home

  • On the System Overview, click a database’s name or its DB Home button.
  • In the sidebar, click DB Home. It opens the database you used last.
  • Press Ctrl+K and type “DB Home”.

The database switcher next to the name moves between databases. The page address (for example /dbhome?db=HR92DEV) can be bookmarked or shared.

The header shows the connection status, PeopleTools release, database type, when psLens last checked the connection, and uptime over the last 30 days. PIA Login opens the database’s sign-in page. A warning appears when tables psLens reads are not whitelisted, with a link to the list and the SQL to add them.

Health

The same four scores as the database’s System Overview card: Process Scheduler, Integration Broker, Logins (24h), and Active Alerts. The System Overview page explains how each score is calculated.

Active Alerts

Alerts currently firing for this database, critical first, each with its first three items. Muted alerts are listed last. Muting and rechecking happen on the Active Alerts page.

Process Scheduler

  • Servers: every server in PSSERVERSTAT with its status and last heartbeat. A running server whose heartbeat is more than 10 minutes old is marked Stale, the same rule the Process Scheduler Down alert uses.
  • Errors in the last 24 hours: the latest 10 requests that ended in Error, Not Successful, or Unable to Post, with a link to all of them in the Process Monitor.
  • Recent requests: the 15 newest process requests of any status.

Integration Broker

  • Domains: messaging domains in PSAPMSGDOMSTAT and how many are active.
  • Dispatchers: how many report ACT status.
  • Nodes down: nodes listed in PSNODESDOWN, with the number of operations held for each.
  • Sync errors, last 24 hours: synchronous service operations with errors in PSIBLOGHDR, most errors first.

Signed In Now

This card lists the users with a PIA sign-in from the last 12 hours and no sign-out recorded in PSACCESSLOG, newest sign-in first. It shows how many users and open sessions there are, and for each user the number of open sessions and the time of the latest sign-in. Batch, API, and application server sign-ons are left out.

PSACCESSLOG records sign-in and sign-out but no activity in between. A user who closed the browser without signing out still counts until 12 hours have passed.

Sign-in History

This card counts PIA sign-ins per day in PSACCESSLOG for the last 14 full days, ending yesterday. Today is left out because a partial day would read as a drop. The tiles at the top compare yesterday with:

  • the day before
  • the same weekday a week earlier, which avoids weekend swings
  • the average of the 7 days before it

The table lists each day with its count, the average of the 7 days before it, and the change from that average. Changes of 25% or more are shown in color. Days are calendar days in the PeopleSoft server’s time. The count query uses PeopleSoft meta-SQL for its dates, so it runs on Oracle and SQL Server.

Below the counts, the card lists users with failed logins in the last 24 hours.

Whitelisting PSACCESSLOG

Both sign-in cards need PSACCESSLOG. It has no index on sign-in time, so psLens reads the whole table for each card. On a test database with 1.2 million rows a full read took about half a second. Results are cached for 2 minutes. To turn the cards on, whitelist the table:

INSERT INTO PS_CHG_PSLENS_WL (RECNAME) VALUES ('PSACCESSLOG');

Without it, Signed In Now shows the whitelist statement, and Sign-in History shows each user’s last sign-on attempt from PSPTLOGINAUDIT instead of daily counts.

Recent Project Activity

PeopleSoft does not keep a log of project copies. This card lists projects whose definition changed in the last 7 days (PSPROJECTDEFN.LASTUPDDTTM), who changed them, and the compare or copy target database saved on the project, when there is one.

Security Checks

The latest saved run of the Nodes with No Password and PeopleTools Access Audit reports for this database: the number of findings, how many were added or removed since the run before, and when it ran. If a report has never run against this database, the card links to run it. DB Home never runs these reports itself.

Scheduled and Recent Reports

  • Scheduled Reports: enabled report schedules that include this database, with when each runs next. Times use the psLens server’s clock.
  • Recent Reports: the 8 newest report runs for this database, with status and findings count.

Recently Viewed

Objects you opened in this database, newest first.

Loading, Refresh, and Offline Databases

The header, alerts, reports, and recently viewed items come from psLens’s own records and appear immediately. The PeopleSoft sections load after the page appears, each card on its own, so a slow or failing query affects only its card. Results are reused for 2 minutes; Refresh fetches everything again.

When the database is offline or in scheduled downtime, the PeopleSoft cards say so and psLens sends no queries. Alerts, reports, and recently viewed items still show.