Database Management Systems

A PeopleSoft access ID is the database user ID used to establish the connection between the application server and the database. This ID typically has elevated privileges and is used for all database operations after the initial user authentication.

Replication in database systems serves two key purposes: making copies identical (option B) and enabling users across different locations to access current information (option C). A true replica would have the same replication ID, not a different one (option A is false). Therefore option D (Both b and c) is correct.

Archiving in email systems removes older messages from the active mailbox, storing them separately to free up space and improve performance. Unlike replication, archives are typically one-way and do not synchronize changes back to the original database. Archives contain a subset of documents, not all documents and design elements.

LISTENER.ORA is the server-side configuration file that contains network parameters for the Oracle Net Listener, including the listener address, port, service names, and protocol settings. INIT.ORA contains database initialization parameters, SQLNET.ORA is for client-side SQL*Net configuration, and TNSNAMES.ORA is a client-side file for database service name resolution. The listener.ora file is specifically responsible for defining how the listener accepts network connections.

When the Oracle listener is shut down, existing database connections remain unaffected because the listener's role is ONLY to initiate new connections - it doesn't maintain or manage existing connections. Once a connection is established, communication occurs directly between the client and the database instance. The connections won't close immediately, won't close when transactions complete, and will continue operating normally. Only new connection attempts will fail until the listener is restarted.

To use SQLPLUS to connect to a remote Oracle database, you need a TNS (Transparent Network Substrate) entry on the CLIENT side (where SQLPLUS executable resides), not the server side. The TNS entry in tnsnames.ora on the client machine tells SQLPLUS how to reach the remote database - the host, port, service name, and protocol. Without this client-side TNS entry, SQLPLUS doesn't know where to connect. The server's TNS configuration is irrelevant for the client connection attempt.

When SQLPLUS and the database reside on the same server, you don't need a TNS entry. You can connect using the BEQ protocol (bequeath/local connection) with syntax like 'sqlplus / as sysdba' or 'sqlplus username/password'. The BEQ protocol uses inter-process communication directly without going through the network listener or TNS. TNS entries are only required for remote connections across the network. Local connections bypass the TNS layer entirely.

The statement is false. Enterprise users in Oracle DO require database accounts and schema creation in each database they need to access. Enterprise User Security (EUS) provides centralized user management across databases, but each database must still have a schema/user account mapped to the enterprise user. The enterprise user is authenticated centrally (often through LDAP/directory), but authorization (schema access, privileges) requires database-level schema objects. There's no magic way to bypass the need for database accounts entirely.

The statement is false. Even if a user is IDENTIFIED EXTERNALLY (OS authentication), they cannot connect with 'sqlplus -S / as SYSDBA' without being explicitly granted SYSDBA privileges. The '/' syntax allows OS-authenticated users to connect, but only if they have a corresponding database account with appropriate privileges. A user identified externally still needs proper SYSDBA grant to use 'as SYSDBA'. Without this grant, the connection attempt will fail regardless of OS authentication.

USER_SYS_PRIVS shows the system privileges granted specifically to the current user. ALL_SYS_PRIVS would show all system privileges in the database (not filtered for the user). The ROLE_PRIVS views are for role privileges, not system privileges. For user U01 checking their own system privileges, USER_SYS_PRIVS is correct.

Hibernate provides built-in ID generation strategies called generators. Commonly used generators include increment (generates identifiers incrementally), identity (uses database identity column), sequence (uses database sequence), hilo (high/low algorithm), and uuid (generates UUIDs). The other options contain either incorrect names or mix of unrelated terms.

In Hibernate, the Configuration class (org.hibernate.cfg.Configuration) represents the complete set of object-relational mappings between Java types and SQL database tables. It is responsible for reading configuration files (hibernate.cfg.xml or hibernate.properties) and mapping files, creating the SessionFactory. The other options either use incorrect package names or incorrectly add '.Session' suffix.

When connecting to Oracle over a non-secure network connection (without OS authentication support), Oracle uses password file authentication for privileged connections like SYSDBA. The password file stores credentials of users with SYSDBA/SYSOPER privileges. OS authentication works only when the client is on the same host as the database or has a trusted secure connection. Control files store database structure, not authentication data.

Rebuilding an index creates a new index using the existing index as the data source, requiring sufficient temporary disk space to hold both the old and new indexes simultaneously. The new index will not contain deleted entries, and online rebuilds allow concurrent queries.

STARTUP NOMOUNT is used when creating a new database because it starts the instance (SGA and background processes) without mounting a database. At this stage, Oracle reads the parameter file but doesn't look for a control file (which doesn't exist yet for a new database). STARTUP MOUNT requires an existing control file, STARTUP OPEN requires an existing database, and plain STARTUP is equivalent to STARTUP OPEN.