Extents would be managed by freelists.

Free space would be managed by data dictionary

The segment would be managed by bitmaps.

The segment would be managed by freelists.

Oracle Net Manager.

Data Pump.

Oracle Universal Installer (OUI).

Oracle Enterprise Manager.

Database Configuration Assistant (DBCA).

Object level.

Row level.

Block level.

Schema level.

Database level.

Loss of the initialization parameter file.

One of the redo log members.

Any data file belonging to the default permanent tablespace

Any archive log file.

Any control file.

It is possible to have tablespaces of different block sizes in a database.

A data block is the smallest unit of I/O for data files.

Multiple tablespaces can share single data file.

Each data block in the database always corresponds to one OS block

Each segment contains one or more extents.

Data files and redo log files can be renamed at the MOUNT stage

Control files are required to bring the database to the NOMOUNT stage.

Data files and online redo log files are checked for consistency while opening the database

Data files and redo log files are made available to users at the OPEN stage.

undef

0

1

2

', 'a', ' ', 'b', ' ', 'c', ' '

', 'a', 'b', 'c', ''

undef, 'a', 'b', 'c', undef

'a', 'b', 'c'

A

AA

Can't locate object method "foo" via package "A"

none of the above

same

different

the code is ill-formed

none of the above

character class

metacharacter

assertion

quantifier

Last access

Inode number

Both of the above

Perl Version ID

sort @a

sort {$1 <=> $2} @a

sort {$a <=> $b} @a

sort {$[0] <=> $[1]} @a

1 2 3

2 3 4

5 6 7

6 7 8

True

False

$string =~ s///g;

$string =~ s///g;

$string =~ s///g;

$string =~ s///g;

interface

class

Object

None of these

set

ConcurrentSkipListSet

Hashmap

Queue

java.io

java.util

javax.xml.stream

java.io.*

Handle with try catch block

Handle with Throwable class

Both of above true

None of above