When the table space /database in hot backup mode what will happens ?

The datafile headers which contain the SCN of the last completed checkpoint are
NOT updated while a file is in hot backup mode.
Most DBAs assume that since the header is frozen, the dirty blocks would
not be written to the datafile instead recorded in the redo log buffer and onwards
written to the log file due to which there is a huge redo log information generated.
Also, many assume that these archives would be used to write the transactions to
the datafile of the tablespace once the tablespace is removed from the backup
mode. This assumption is false.
DBWn as usual keeps writing the modified blocks to the datafile irrespective
of tablespace being in backup mode. The reason for Oracle to freeze the datafile
header is that the checkpoint SCN at which the header was frozen marks the SCN
from which the recovery needs to be performed when the datafiles that were
backed up (using OS copy) will be restored.
How to find out CPU utilization in Linux?
The top command provides dynamic view of CPU utilization. It displays
system information as well as list of tasks currently managed by kernel. Is also
displays uptime, average load, physical and swap memory utilization.
Syntax of top command is as follows:
$ top
What are the errors occur frequently in your environment oracle dba ?
ORA-12505
SID could not be resolved.
Check listener.ora on the server or run lsnrctl status to make sure a listener is
running for the specified SID.
ORA-12154
The service name could not be found in tnsnames.ora.
Check the service name.
ORA-12162
The connection description has an error.
Check tnanames.ora for syntax, especially mismatched parentheses
ORA-12163
The connection description is too long.

Correct the problem by shortening the connection description.

ORA-01652: unable to extend temp segment by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for a
temporary segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD TEMPFILE statement to add one or more files
to the tablespace indicated.

ORA-00257: archiver error. Connect internal only, until freed.

Cause: The archiver process received an error while trying to archive a redo log. If
the problem is not resolved soon, the database will stop executing transactions. The
most likely cause of this message is the destination device is out of space to store
the redo log file.

Action: Check archiver trace file for a detailed description of the problem. Also
verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST
is set up properly for archiving.

ORA-01031: insufficient privileges

Cause: An attempt was made to change the current username or password without
the appropriate privilege. This error also occurs if attempting to install a database
without the necessary operating system privileges. This error may occur if the user
was granted the necessary privilege at a higher label than the current login.

Action: Ask the database administrator to perform the operation or grant the
required privileges. For Trusted Oracle users getting this error although granted the
the appropriate privilege at a higher label, ask the database administrator to
regrant the privilege at the appropriate label.