Thursday, March 12, 2026

How to switch/connect with other database (demo)?

postgres=#

postgres=# \c demo

You are now connected to database "demo" as user "postgres".

demo=#

demo=# \l demo

How to create database in PostgreSQL ?

postgres=#

postgres=# create database demo;

CREATE DATABASE

postgres=#

postgres=# \l

postgres=#

PostgreSQL : 'more' is not recognized as an internal or external command, operable program or batch file.

postgres=#

postgres=# \l

'more' is not recognized as an internal or external command,

operable program or batch file.

postgres=#

postgres=# \l

'more' is not recognized as an internal or external command,

operable program or batch file.

postgres=#

This happens in psql on Windows when the MORE command is missing or overridden in the system PATH.

psql uses the system pager (more) to display long output like \l, \dt, etc.

postgres=#

postgres=# \pset pager off

Pager usage is off.

postgres=#

postgres=# \l

List of databases

-----------+----------+----------+-----------------+--------------------+--------------------+--------+-----------+-----------------------

(3 rows)

postgres=#

Wednesday, March 11, 2026

Important Oracle Database License Audit Checklist

Oracle Database License Audit Checklist

1. Perform a Comprehensive Oracle Environment Inventory (On‑Prem & Cloud)

Catalog every Oracle database deployment, including production, development, testing, and disaster‑recovery environments.
Include all infrastructure types: physical servers, virtual machines, containers, and cloud-hosted databases.
Record the database edition (Standard Edition, Enterprise Edition) and version (e.g.11g,19c, 21c).

2. Verify License Entitlements and Agreements

Map each deployment to its corresponding license type (NUP, Processor‑based).
Use Oracle’s Core Factor Table to correctly calculate processor requirements.
Review legacy contracts, existing ULAs, and any embedded licensing rights that may impact compliance.

3. Assess Feature and Option Usage

Use automated tools/scripts to detect usage of chargeable features such as RAC, Partitioning, Advanced Compression, etc.
Confirm that all enabled features are properly licensed or disable those not in use.

4. Evaluate Virtualization and Cloud Architectures

Track virtual machine movement across hypervisors (e.g. VMware vSphere, Nutanix ).
Ensure hard partitioning or affinity rules are documented and enforced where required.
Review Oracle workloads running on public cloud IaaS platforms like AWS, Azure, or OCI to confirm licensing alignment.

5. Prepare an Accurate and Audit‑Ready Data Package

Validate all data generated by LMS (License Management Services) scripts before sharing externally.
Avoid running Oracle‑provided audit scripts without expert review.
Document all licensing interpretations, configuration decisions, and control measures for audit transparency.

Note :-

We have to very careful run any script in environment before review with experts ......

Monday, February 16, 2026

Use Cases of Oracle Grid Control

Oracle Grid Control was designed for centralized management of on‑premise Oracle IT infrastructure, especially when organizations had many databases, middleware servers, and hosts.

1. Centralized Monitoring of Large On‑Prem Environments

Grid Control provides a single-window solution for monitoring multiple Oracle databases, WebLogic servers, hosts, and even some non-Oracle technologies (IBM WebSphere, SQL Server, etc.) in one place.

2. End-to-End Application & Service Monitoring

It includes service-level management, real user monitoring, and deep diagnostics for multi-tier applications—ideal for environments needing SLA visibility.

3. Database Performance Diagnostics (11g Features)

For Oracle Database 11g Release 2, Grid Control provides:

Enhanced performance pages
ADDM integration
Real-time SQL monitoring
Parallel SQL tuning

4. Real Application Clusters (RAC) & High Availability Management

Use cases include:

Managing policy-managed RAC databases
Auto-discovery of RAC nodes
Monitoring Oracle Clusterware and Grid Infrastructure

5. Configuration, Provisioning, and Lifecycle Management

Grid Control supports configuration management, provisioning, and patching in on‑prem environments.

6. Modeling IT Environment & Service-Level Management

Advanced use cases include:

Modeling composite services
Service-level agreements (SLAs)
Root-cause analysis for service failures

Ideal For:

✔ Large on‑prem Oracle estates
✔ Mixed orchestration environments (DB + WebLogic + Hosts)
✔ Traditional data centers without cloud
✔ RAC-heavy deployments
✔ Organizations needing SLA and service monitoring

✅ Use Cases of Oracle Cloud Control (OEM 12c/13c)

Oracle Cloud Control expands on Grid Control by adding cloud, engineered systems, automation, and lifecycle capabilities.

1. Managing Entire Enterprise + Cloud Infrastructure

Cloud Control is Oracle’s integrated platform for monitoring databases, engineered systems, applications, middleware, hardware, and cloud environments centrally.

2. Hybrid & Cloud Management

It provides capabilities for:

Oracle Cloud (OCI) monitoring
Hybrid deployments (on‑prem + cloud)
Cloud automation, configuration, and provisioning

3. Full Lifecycle Management & Automation

Cloud Control offers automated:

Configuration management
Provisioning
Patch automation
Compliance assessment

4. Engineered Systems (Exadata, ZDLRA) Management

Cloud Control supports Oracle engineered systems for:

Hardware health monitoring
Exadata cell and storage metrics
Database machine-level performance
(Engineered systems management is explicitly part of Cloud Control’s scope.)

5. Deep Diagnostics & Tuning via Licensed Packs

Cloud Control integrates advanced features when packs are enabled:

Diagnostics Pack (AWR/ASH integration)
Tuning Pack
Lifecycle Management Pack

6. Compliance & Security Monitoring

Cloud Control supports compliance frameworks and access control management for enterprise governance—e.g., SOX, security baselines.

7. Managing Large Fleets at Scale

Includes support for:

Fleet Maintenance
Mass agent deployment
Drift analysis
Enterprise-wide policy enforcement

Ideal For:

✔ Multi-datacenter enterprises
✔ Cloud + on‑prem hybrid environments
✔ Exadata and engineered systems
✔ Large fleet automation & compliance
✔ Organizations needing advanced diagnostics and tuning

🆚 Summary: When to Use What

Requirement	Grid Control	Cloud Control
Large on‑prem infrastructure	✔	✔
Hybrid / Cloud environments	❌	✔
Engineered systems (Exadata)	Limited	✔ Full support
Advanced automation & provisioning	Moderate	✔ Extensive
SLA, service modeling	✔	✔ Enhanced
Diagnostics, Tuning Packs	Available	✔ Fully integrated
Modern UI, plugin architecture	Legacy	✔ Modern extensible

🎯 Short Answer

Grid Control → Best for older, fully on‑premises Oracle environments needing centralized monitoring and basic lifecycle management.
Cloud Control → Best for modern enterprises requiring cloud integration, engineered systems support, automation at scale, and advanced diagnostics/compliance.

Database Control vs Grid Control vs Cloud Control (OEM)

🚀 Database Control vs Grid Control vs Cloud Control (OEM)

1. Database Control (DB Control)

Scope: Single database / single host

What it is:

A lightweight management console installed automatically with an Oracle database.
Uses the local DB Control Agent and stores configuration in the database’s own repository.

Best for:
✔ Managing one database
✔ Basic monitoring
✔ Single-server environments

Limitations:
❌ Cannot manage multiple databases centrally
❌ No enterprise monitoring
❌ Feature deprecated since Oracle 12c
❌ Not suitable for HA/DR, Exadata, RAC monitoring at scale

Think of it as:

A local-only admin console for one Oracle DB instance.

2. Grid Control (OEM 10g / 11g)

Scope: Enterprise-level monitoring across multiple servers

What it is:

First enterprise-grade OEM version that gave you central management.
Came with:
- OMS (Oracle Management Server)
- OMR (Oracle Management Repository)
- Agent on each monitored host

Best for:
✔ Monitoring multiple DBs
✔ Managing RAC, ASM
✔ Host & application monitoring
✔ Patch management (PSUs)
✔ SLA dashboards

Limitations:
❌ Older architecture
❌ Not cloud-ready
❌ No plugin-based extensibility (limited compared to Cloud Control)

Think of it as:

Enterprise monitoring 1.0 — centralized, but still traditional.

3. Cloud Control (OEM 12c → 13c)

Scope: Enterprise + Cloud + Engineered systems

What it is:

Successor to Grid Control.
Plugin-based architecture to support:
- Oracle DB (all versions)
- Middleware (WebLogic)
- Engineered systems (Exadata, ZDLRA)
- Oracle Cloud, OCI
- Non-Oracle technologies (SQL Server, VMware, etc.)

Key capabilities added:

Lifecycle Management
Patching & Provisioning Automation
Fleet Maintenance
Compliance Management (e.g., STIG, CIS)
Cloud & hybrid monitoring
Advanced diagnostics (AWR, ASH, ADDM integrated)

Best for:
✔ Large enterprises
✔ Multi-datacenter environments
✔ Exadata-heavy setups
✔ CI/CD for DB patching (Fleet Maintenance)
✔ Compliance & audit-driven organizations

Think of it as:

Enterprise monitoring 2.0 — scalable, cloud-aware, and automation‑focused.

📌 Quick Comparison Table

Feature	Database Control	Grid Control	Cloud Control
Scope	Single DB	Multi-DB Enterprise	Hybrid Cloud + Enterprise
Repository	Local DB	Central OMR	Central OMR (Enhanced)
Cloud support	❌	❌	✔ OCI, Hybrid
Engineered systems (Exadata)	❌	Limited	✔ Full support
Patch automation	Basic	Better	Best (Fleet Maintenance)
Plugins	❌	Limited	✔ Full plugin system
Status	Deprecated	Legacy	Current (OEM 13c)

🧠 In Simple Terms

Database Control → Local tool for one database
Grid Control → Central tool for many databases
Cloud Control → Enterprise+Cloud management with automation & plugins

https://www.softwareone.com/en/blog/articles/2021/05/31/oracle-enterprise-manager-how-to-avoid-unexpected-licensing-challenges

https://docs.oracle.com/en/database/oracle/oracle-database/19/dblic/Licensing-Information.html#GUID-B6113390-9586-46D7-9008-DCC9EDA45AB4

Wednesday, February 11, 2026

How to pull image in docker and run ? Hello-World image

use : https://hub.docker.com/_/hello-world

anurag@Anurags-MacBook-Air ~ %

anurag@Anurags-MacBook-Air ~ % docker pull hello-world

Using default tag: latest

latest: Pulling from library/hello-world

Digest: sha256:ef54e839ef541993b4e87f25e752f7cf4238fa55f017957c2eb44077083d7a6a

Status: Image is up to date for hello-world:latest

docker.io/library/hello-world:latest

anurag@Anurags-MacBook-Air ~ %

anurag@Anurags-MacBook-Air ~ % docker run hello-world

Hello from Docker!

This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

1. The Docker client contacted the Docker daemon.

2. The Docker daemon pulled the "hello-world" image from the Docker Hub.

(arm64v8)

3. The Docker daemon created a new container from that image which runs the

executable that produces the output you are currently reading.

4. The Docker daemon streamed that output to the Docker client, which sent it

to your terminal.

To try something more ambitious, you can run an Ubuntu container with:

$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:

https://hub.docker.com/

For more examples and ideas, visit:

https://docs.docker.com/get-started/

anurag@Anurags-MacBook-Air ~ % >....

This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

1. The Docker client contacted the Docker daemon.

2. The Docker daemon pulled the "hello-world" image from the Docker Hub.

(arm64v8)

3. The Docker daemon created a new container from that image which runs the

executable that produces the output you are currently reading.

4. The Docker daemon streamed that output to the Docker client, which sent it

to your terminal.

To try something more ambitious, you can run an Ubuntu container with:

$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:

https://hub.docker.com/

For more examples and ideas, visit:

https://docs.docker.com/get-started/

anurag@Anurags-MacBook-Air ~ %

if you see " Hello from Docker! " then all good