Database Management Systems

A Hibernate Session obtains a JDBC connection lazily - only when it's actually needed for an operation. This improves efficiency by avoiding unnecessary database connections. The session doesn't grab a connection at creation time.

To enable the query cache in Hibernate, you must set the configuration property hibernate.cache.use_query_cache to true in the configuration file. The option hibernate.cache.query_cache is incorrect because it is not a valid Hibernate configuration property name.

Setting hibernate.cache.use_query_cache to true enables two cache regions: StandardQueryCache for storing query results and UpdateTimestampsCache for tracking timestamp information. This allows Hibernate to cache query results and invalidate them appropriately when underlying data changes. The UpdateTimestampsCache is essential for maintaining cache consistency.

When sizing undo tablespace, you need to consider: the undo block size (determines space efficiency per transaction), the UNDO_RETENTION parameter (how long undo data must be kept for flashback/consistency), and the rate of undo blocks generated per second (transaction workload). Redo log files and buffer cache size don't directly determine undo tablespace requirements.

Flashback Technology can recover DROP TABLE and DROP USER operations using Flashback Drop (recyclebin feature). DROP TABLESPACE and DROP PARTITION cannot be flashed back. ALTER TABLE DROP COLUMN also cannot be recovered with Flashback - you'd need point-in-time recovery or restore from backup. Flashback Drop works at the schema object level, not for structural changes within objects.

In NOARCHIVELOG mode, database structural modifications such as adding a new tablespace or dropping a datafile alter the control file's structure. Backing up the control file immediately after these operations is critical since transactions are not archived, making recovery of structural changes impossible without a recent control file backup.

PGA (Program Global Area) is created when a dedicated server process starts and contains data and information specific to that server process. SGA (System Global Area) is shared by all processes. Streams Pool and Shared Pool are components within the SGA, not separate memory areas for dedicated processes. PGA is private to each process.

Oracle Database 10g Release 2 introduced significant enhancements to Automatic Storage Management (ASM), Flashback technologies, Data Guard, and the Flash Recovery Area (now Fast Recovery Area). Tivoli Data Protection is a third-party IBM product and not an Oracle database component.

The ORACLE_HOME environment variable points to the directory where the Oracle database software executable binaries, libraries, and helper files are installed. It does not dictate the directory for Oracle Managed Files or database files, which are managed by parameter configuration files.

RMAN backup can back up only used data blocks (skip empty blocks in datafiles) - this is called unused block compression. Archived redo log files can and should be backed up with RMAN. Online redo log files are NOT backed up by RMAN (they're managed through log switches/archiving). RMAN can backup in both ARCHIVELOG and NOARCHIVELOG mode, though some features require ARCHIVELOG.

For remote SYSDBA authentication, Oracle uses a password file to authenticate administrative users. The password file stores usernames and password hashes for users with SYSDBA, SYSOPER, or SYSASM privileges. Control files contain database structure information, not authentication data. Listener configuration files manage connection requests, not authentication.

The alert log file is automatically recreated by the Oracle instance if it's deleted. There's no manual action required - the instance will create a new file on the next startup or when it needs to write to the alert log. You don't need to recover from backup or change initialization parameters. The BACKGROUND_DUMP_DEST parameter (or DIAGNOSTIC_DEST in newer versions) determines the location but doesn't affect automatic creation.

Roles in Oracle can contain both system privileges (like CREATE TABLE) and object privileges (like SELECT on a table). Roles can be granted to other roles, enabling privilege hierarchies. Roles cannot be granted to themselves (circular reference). Roles are not owned by SYS specifically - they're schema-independent objects. External authentication can be assigned to roles.

When creating a new listener through Enterprise Manager, you must specify: the protocol (TCP, TCPS, etc.), the server/hostname where the listener runs, and the port number it listens on. Database services register dynamically with the listener. Log and trace file locations use default values or are configured later. These three parameters are the minimum required for listener creation and basic operation.

Automatic segment space management uses bitmaps to track free and used space within segments instead of freelists. When you specify automatic segment space management for a tablespace, Oracle uses bitmaps to manage space allocation, which is more efficient than the manual freelists method. Freelists (A and D) are used in manual segment space management, while data dictionary (B) management is an older, deprecated approach.