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

 

postgres=#

postgres=#

postgres=#

postgres=# \c demo

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

demo=#

demo=#

demo=# \l demo

 demo | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           |

How to create database in PostgreSQL ?

 

postgres=#

postgres=#

postgres=# create database demo;

CREATE DATABASE

postgres=#

postgres=# \l

 demo      | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           |

 postgres  | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           |

 template0 | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           | =c/postgres          +

           |          |          |                 |                    |                    |        |           | postgres=CTc/postgres

 template1 | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           | =c/postgres          +

           |          |          |                 |                    |                    |        |           | postgres=CTc/postgres

postgres=#

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

 postgres=#

postgres=#

postgres=#

postgres=# \l

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

operable program or batch file.

postgres=#

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

   Name    |  Owner   | Encoding | Locale Provider |      Collate       |       Ctype        | Locale | ICU Rules |   Access privileges

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

 postgres  | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           |

 template0 | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           | =c/postgres          +

           |          |          |                 |                    |                    |        |           | postgres=CTc/postgres

 template1 | postgres | UTF8     | libc            | English_India.1252 | English_India.1252 |        |           | =c/postgres          +

           |          |          |                 |                    |                    |        |           | postgres=CTc/postgres

(3 rows)

postgres=#

postgres=#

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 ......