Schema is a user where there will be Objects present

application User is a user were there will not be any objects present, but will
have permissions on schema objects

login as SYSTEM
create user prdmmis identified by password;
grant connect, resource to prdmmis;
------------------------------

To check if an Oracle database server is running, you can use the following
methods:
Check the console, Open Oracle Instance Manager

------------------------------

Instance
Service
PDB
SID vs Service Name
PDB Service
Listener
Admin tools

------------------------------
Database: a collection of physical operating system files on disk
Instance: A set of oracle background processes/threads and a shared memory area.
Which is memory that is shared across those threads/processes running on a single
computer.

An instance can mount and open at most one database in its life. We must discard
this instance and create a new one in order to open this or any other database.

To recap

An instance is a set of O/s background processes and shared memory. These processes
can operate on a single database
A database is a collection of files(datafiles, temp files, redo log files and
control files)
At any time an instance will have only one set of files (one database) associated
with it.
A database will have only one instance working on it. in special cases as Oracle
Real Application Cluster (RAC), an option of oracle allows it to function on many
computers in a clustered envirnment. We may have many instances simultaneously
mounting and opening this one database which resides on a set of shared physical
disk. This gives us access to this single database from many different computers at
the same time. Oracle RAC provides for extremely highly available systems and
provides extremely scalable solutions.
An instance can mount and open only a single database ever.
A database may be mounted and opened by one or more isntances (using RAC)

As noted earlier there is, in most cases, a one-to-one relationship between an

instance and a database. This is probably how the confusion surroundign the terms
arises. In most peoples experience, an database is an instance and an instance is a
database.

In many test environments, this is not the case, on my desk,i might have five
seperate databases. On the test machine, at any point in time there is only one
instance of oracle running, but the database it is accessing may be different from
day to day, hour to hour depending on my needs. By simply having many different
configuration files, i can mount and open any one of these databases, here i have
one instance at a time but many databases, only one of which is accessible at any
point in time.

SQL> select name from v$datafile;

NAME
--------------------------------------------------------------------------------
/home/ora10g/dbs/dbs1ora10g.dbf
/home/ora10g/dbs/dbx1ora10g.dbf

SQL> select member from v$logfile;

MEMBER
--------------------------------------------------------------------------------
/home/ora10g/dbs/log1ora10g.dbf
/home/ora10g/dbs/log2ora10g.dbf

SQL> select name from v$controlfile;

NAME
--------------------------------------------------------------------------------
/home/ora10g/dbs/cntrlora10g.dbf

SQL>

----------------------------------------------

When we say sqlplus / as sysdba; -- it connects to CDB (or depending on

ORACLE_PDB_SID setting). / indicates OS authentication

---------------------------------

select instance_name from v$instance; -- Shows instance name

Which DB is connected when i say SYS as sysdba; - it connects to default database

stored in registry, you can override that by setting ORACLE_SID in the environment
too.

Every running oracle database is associated with atleast one Oracle database
instance
Because an instance exists in memory and a database exists on disk, an instance can
exist without a database and a database can exist without an instance (data files
in os)

An instance is associated with one and only one database EVER. An instance comes
into being with startup - and goes away with shutdown. In between startup and
shutdown - that instance can mount and open exactly ONE database - ever.

A database however, can be open by one or more instances - with real application
clusters. In that environment - you can run as many instances as you like on
different machines and all can mount and open the same set of database files.

A listener is completely detached from an instance - you need one listener per host
- regardless of the number of instances running on the host. In fact - a listener
doesn't even have to run on the same machine as the instance!
You typically run ONE listener on a host and let all of the instances on that host
register with it.

------------------------------------

From Gemini

Oracle Server : This is the hardware, the physical computer (or vitual machine)
where the oracle server software resides. It can host multiple instances.

Oracle Instance: This is the software, set of Oracle software processes running on
the server
Its key components are :
System Global Area (SGA) : Shared Memory area used by the instance to cache data,
control blocks and other information
Program Global Area (PGA) : Memory allocated to each user process connecting to the
instance
Database Association : An instance typically manages a single database, but
multiple instances can access the same database in some congigurations

Oracle Database :
Data collection: A collection of related data organized and stored according to a
specific model (usually relational)
Files: Resides on the server storage(disk) as a set of OS files
Instance Relationship : Managed by Oracle Instance

Oracle Listener:
Process: A dedicated process that listens for incoming client connection requests
Role:
Receives connection requests from clients (Applications)
Determines the target Oracle instance for the connection
Establishes a connection between the client and the target instance

In Summary:

The server is the physical machine.

The instance is the software running on the server that manages the database.
The database is the actual collection of data.
The listener is the process that facilitates connections between clients and the
database instance

-----------------------------------

From Ramkumar Swaminathan Youtube Channel - THE BEST EXPLANATION FOR ORACLE
ARCHITECTURE (NON-CDB)

Computing architecture of Oracle - Ramkumar Swaminathan

https://www.youtube.com/watch?v=EqYB7mp_U3I&list=PL3Hc8S1SG2AQnk6Nu57m2JLkWxorMAsmE