Site Content

Running: The process is currently executing or running.
Sleeping: The process is waiting for an event or resource to become available. This state can be further classified into several sub-states, such as interruptible sleep, uninterruptible sleep, and stopped.
Zombie: The process has completed its execution, but its parent process has not yet called the wait() system call to collect its exit status.
Stopped: The process has been stopped either by the user or by a signal.
Dead: The process has completed its execution, and its resources have been released by the operating system.

SIGHUP (1): Hangup signal, used to indicate that a controlling terminal has been closed or that a process should reload its configuration.
SIGINT (2): Interrupt signal, typically generated by pressing Ctrl+C on the terminal, used to request that a process terminate.
SIGQUIT (3): Quit signal, similar to SIGINT but produces a core dump of the process.
SIGKILL (9): Kill signal, used to forcibly terminate a process.
SIGTERM (15): Termination signal, used to request that a process terminate gracefully.
SIGSTOP (17): Stop signal, used to temporarily stop a process.
SIGCONT (19): Continue signal, used to resume a previously stopped process.
SIGUSR1 (30): User-defined signal 1, which can be used by a process for its own purposes.
SIGUSR2 (31): User-defined signal 2, which can be used by a process for its own purposes.
SIGPIPE (13): Pipe signal, generated when a process attempts to write to a pipe that has been closed or to a socket that has been disconnected.

SYN: The process starts when the client device sends a synchronization (SYN) request to the server. This request contains a sequence number that helps to ensure the ordered delivery of data.
SYN-ACK: Upon receiving the SYN request, the server sends back a SYN-ACK (synchronization-acknowledgment) message to the client. This message acknowledges receipt of the client's SYN request and includes a sequence number that is used to establish the connection.
ACK: Finally, the client sends an acknowledgement (ACK) message back to the server to confirm the receipt of the SYN-ACK message. At this point, the connection is established, and data can be exchanged between the two devices.

Log file sync: A wait event that occurs when the database is waiting for a redo log file to be written to disk.
db file sequential read: A wait event that occurs when the database is waiting for a single block to be read from a data file on disk.
db file scattered read: A wait event that occurs when the database is waiting for multiple blocks to be read from a data file on disk.
direct path read/write: A wait event that occurs when the database is performing a direct path read or write operation, which bypasses the buffer cache.
SQL*Net message from client: A wait event that occurs when the database is waiting for a message to be received from a client over the network.
CPU time: A wait event that occurs when a process is waiting for CPU resources to become available.

General Purpose (SSD): This storage class is designed for a wide range of database workloads that require balanced performance, good I/O throughput, and low latency. It is suitable for small-to-medium-sized databases and supports up to 10,000 IOPS.
Provisioned IOPS (SSD): This storage class is designed for database workloads that require high I/O performance and low latency, such as online transaction processing (OLTP) and data warehousing. It provides a guaranteed level of IOPS (input/output operations per second) and is suitable for large databases that require high-performance storage.
Magnetic: This storage class is designed for database workloads that have lower I/O requirements and can tolerate higher latencies, such as test and development environments or backup and archival storage. It provides a low-cost storage option for databases that are not latency-sensitive.
Throughput Optimized (HDD): This storage class is designed for database workloads that require high sequential I/O throughput, such as data warehousing and batch processing. It provides a high-capacity, low-cost storage option for large databases that have moderate IOPS requirements.
Cold Storage (HDD): This storage class is designed for databases that require infrequent access to their data and can tolerate higher latencies, such as backups, archives, and disaster recovery. It provides a low-cost storage option for databases that are rarely accessed.