Flexible DELETE

Problem:

You need to DELETE/MOVE big number of objects (report instances, shortcuts…) scattered all over the system.

It could be millions of objects in hundreds or thousands folders.

Example: 200k users with favorite folders with month/year subfolders with few dozens objects in each which sum up to 14 million shortcuts and it is only in UAT system.

BOBJ Limits don’t always work, as we don’t wont anything be deleted from recent month/year folders and we want to delete everything from outdated folders, including folders.

Solution:

BiWhy provides DELETE functionality, but it currently limited to single WEBI. This restriction is imposed intentionally and can be removed if there will be use cases for it.

We propose a safe way to DETELE objects, instead:

• Flexibly fetch objects that you want to DELETE/MOVE with CMS DBx functionality – standard BOBJ SQL query (use object type, creation/update timestamp, owner, …)

• In the result tree, select objects or folders (to select all objects beneath) and MOVE them to some ARCHIVE folder either preserving full tree path (from objects to root) or sub-path (form objects to selected folder)

• Continue to use your system:

  • If you satisfied with results, you can finally delete objects by just removing ARCHIVE folder.

  • If for some reason you want to restore all/some objects, you can easily find them in tree structure and restore them by moving back with BiWhy or CMC.

WEBI error info

WEBI error info

BiWhy offers a range of convenient tools to efficiently gather, modify, analyze, and present data on your behalf, alleviating the burden of tedious tasks and enabling you to swiftly identify the underlying causes.

In the event that a tool tailored to your specific workflow is absent, simply let us know.

We value your feedback and, if it proves beneficial or you are a valued client, we will promptly incorporate it into BiWhy.

Problem:

If you see a significant number of *.errorinfo (WEBI errrors/dumps) in logs, it indicates something wrong with the system, but what exactly?

Solution:

Collect logs with couple clicks, load them in one click to WEBI analyzer.

Time spend ~5min

Result: just one user with three reports is responsible for 114 dumps.

Let’s go and analyze this broken workflow.

Audit DB

Audit DB is a powerful but rarely used tool.

Apparently was designed with store flexibility (write all possible event types and their measures in just two tables), rather than with performance or report usability, in mind.

So even if you installed Audit Universe and fixed it for your database flavor, installed audit reports and figured out what are they for, or created your own reports, chances are performance will be discouraging for using it or/and you will be providing not compatible event/event details in the prompts.

BiWhy approach:

Connect to Audit DB with BiWhy just by providing a connection string and JDBC driver, the most used ones are shipped with BiWhy for convenience.

With a single click collect Audit DB metadata – available events (Refresh, Logon, Error,…), details (size, duration,…), statuses (successful, failed…), users, servers,...

Retrieve events, filtering by what you need. Double click will insert keys with comments from metadata to SQL query.

Double-click on results to drill down or add an additional window for side investigation.

Pros:

• Quick start

• Better performance – proven in several critical engagements

• More meaningful results – you know your query and avoid not compatible events/details

• Easy get to know and use metadata (what is available, filter for yourself or query)

• Quick query test, for example with TOP 1

• Quick drill down

Cons:

• A bit of technical interface, subject to improvement by request

• Requires basic SQL knowledge

Suggestions:

Check Errors, top Size, and top Duration events

If you have problems with some particular Server, check what is running on it Object Name and who is running it User

Example:

To increase your Audit DB effectiveness and avoid overloading the system with events collection, check what is in it and get rid of objects that you don’t need.

Below is an example of Audit DB (45 days retention) with 1 billion rows in the Details table, among which ~630M rows are just useless overhead information of (User Group Name/ID) which could be turned off just by unchecking one check box.