Friday, October 17, 2008

LDAP_DIRECTORY_ACCESS

Property

Description

Parameter type

String

Syntax

LDAP_DIRECTORY_ACCESS = { NONE | PASSWORD | SSL }

Default value

NONE

Modifiable

ALTER SYSTEM

Basic

No

LDAP_DIRECTORY_ACCESS specifies whether Oracle refers to Oracle Internet Directory for user authentication information. If directory access is turned on, then this parameter also specifies how users are authenticated.

Values:

· NONE

Oracle does not refer to Oracle Internet Directory for Enterprise User Security information.

· PASSWORD

Oracle tries to connect to the enterprise directory service using the database password stored in the database wallet. If that fails, then the Oracle Internet Directory connection fails and the database will not be able to retrieve enterprise roles and schema mappings upon enterprise user login.

· SSL

Oracle tries to connect to Oracle Internet Directory using SSL.

Note:

1. This parameter was introduced in 10g.

2. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘LDAP_DIRECTORY_ACCESS’;

NAME

VALUE

IS

DEFAULT

ISSES_

MODIFIABLE

ISSYS_

MODIFIABLE

ISINSTANCE_

MODIFIABLE

IS

DEPRECATED

DESCRIPTION

ldap_directory_access

NONE

TRUE

FALSE

IMMEDIATE

TRUE

FALSE

RDBMS's LDAP access option

Oracle initializatoin parameters

LARGE_POOL_SIZE

Property

Description

Parameter type

Big integer

Syntax

LARGE_POOL_SIZE = integer [K | M | G]

Default value

If SGA_TARGET is set, but a value is not specified for LARGE_POOL_SIZE, then the default is 0 (internally determined by the Oracle database). If LARGE_POOL_SIZE is specified, then the user-specified value indicates a minimum value for the memory pool.

If SGA_TARGET is not set, 0 if both of the following are true:

· The pool is not required by parallel execution

· DBWR_IO_SLAVES is not set

Otherwise, derived from the values of PARALLEL_MAX_SERVERS, PARALLEL_THREADS_PER_CPU, CLUSTER_DATABASE_INSTANCES, DISPATCHERS, and DBWR_IO_SLAVES.

Note that a value derived in this way does not take into account the requirements used for Automatic Storage Management files. As a general guideline, you should add 600K to the size of the SGA on a database instance using ASM.

Modifiable

ALTER SYSTEM

Range of values

300 KB to at least 2 GB (actual maximum is operating system-specific)

Basic

No

LARGE_POOL_SIZE specifies (in bytes) the size of the large pool allocation heap. The large pool allocation heap is used in shared server systems for session memory, by parallel execution for message buffers, and by backup processes for disk I/O buffers. Parallel execution allocates buffers out of the large pool only when SGA_TARGET is set.

Caution:

When Oracle derives a default value, it adds 250K for each session for the shared server if DISPATCHERS is configured. The final derived value also includes a port-specific amount of memory for backup I/O buffers. The total derived default value can either be too large to allocate or can cause performance problems. In that case, set LARGE_POOL_SIZE to a number sufficiently small so that the database can start.

You can specify the value of this parameter using a number, optionally followed by K or M to specify kilobytes or megabytes, respectively. If you do not specify K or M, then the number is taken as bytes.

Note:

1. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘LARGE_POOL_SIZE’;

NAME

VALUE

IS

DEFAULT

ISSES_

MODIFIABLE

ISSYS_

MODIFIABLE

ISINSTANCE_

MODIFIABLE

IS

DEPRECATED

DESCRIPTION

large_pool_size

167772160

FALSE

FALSE

IMMEDIATE

TRUE

FALSE

size in bytes of large pool

Oracle initializatoin parameters

JOB_QUEUE_PROCESSES

Thank you for visiting Spatial DBA - Oracle and ArcSDE.

Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.

========================================================================



Property
Description
Parameter type
Integer
Default value
1000
Modifiable
ALTER SYSTEM
Range of values
0 to 1000
Basic
Yes
Real Application Clusters
Multiple instances can have different values.
JOB_QUEUE_PROCESSES specifies the maximum number of processes that can be created for the execution of jobs. It specifies the number of job queue processes per instance (J000, ... J999). Replication uses job queues for data refreshes. Advanced queuing uses job queues for message propagation. You can create user job requests through the DBMS_JOB package.
Some job queue requests are created automatically. An example is refresh support for materialized views. If you wish to have your materialized views updated automatically, you must set JOB_QUEUE_PROCESSES to a value of one or higher.
Note:
1. Query for the current value of the parameter
select name, value, isdefault, isses_modifiable, issys_modifiable,
isinstance_modifiable, isdeprecated, description
from v$parameter
where upper(name) = ‘JOB_QUEUE_PROCESSES’;
NAME
VALUE
IS
DEFAULT
ISSES_
MODIFIABLE
ISSYS_
MODIFIABLE
ISINSTANCE_
MODIFIABLE
IS
DEPRECATED
DESCRIPTION
job_queue_processes
10
FALSE
FALSE
IMMEDIATE
TRUE
FALSE
number of job queue
slave processes

Oracle initializatoin parameters

Thursday, October 16, 2008

V$WAITSTAT

V$WAITSTAT displays block contention statistics. This table is only updated when timed statistics are enabled.

Column

Datatype

Description

CLASS

VARCHAR2(18)

Class of the block

COUNT

NUMBER

Number of waits by this OPERATION for this CLASS of block

TIME

NUMBER

Sum of all wait times for all the waits by this OPERATION for this CLASS of block

Note:

1.

select * from V$WAITSTAT;

CLASS

COUNT

TIME

data block

847238

382988

sort block

0

0

save undo block

0

0

segment header

1635

245

save undo header

0

0

free list

0

0

extent map

0

0

1st level bmb

31

23

2nd level bmb

24

14

3rd level bmb

0

0

bitmap block

0

0

bitmap index block

0

0

file header block

1116

17

unused

0

0

system undo header

0

0

system undo block

0

0

undo header

4604

133

undo block

701312

21200

Oracle data dictionary views

Oracle dynamic performance views

Tuesday, October 14, 2008

V$RMAN_CONFIGURATION

V$RMAN_CONFIGURATION lists information about RMAN persistent configuration settings.

Column

Datatype

Description

CONF#

NUMBER

A unique key identifying this configuration record within the target database that owns it.

NAME

VARCHAR2(65)

The type of configuration. All options of the CONFIGURE command are valid types except:

· CONFIGURE EXCLUDE (described in RC_TABLESPACE)

· CONFIGURE AUXNAME (described in RC_DATAFILE)

· CONFIGURE SNAPSHOT CONTROLFILE (stored only in control file)

VALUE

VARCHAR2(1025)

The CONFIGURE command setting. Example: RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS

Note:

1.

select * from V$RMAN_CONFIGURATION;

CONF#

NAME

VALUE

1

RETENTION POLICY

TO RECOVERY WINDOW OF 92 DAYS

2

DEFAULT DEVICE TYPE TO

'SBT_TAPE'

Oracle data dictionary views

Oracle dynamic performance views

V$RMAN_COMPRESSION_ALGORITHM

V$RMAN_COMPRESSION_ALGORITHM provides descriptions of supported compression algorithms. It is used by the RMAN client.

Column

Datatype

Description

ALGORITHM_ID

NUMBER

Algorithm ID

ALGORITHM_NAME

VARCHAR2(64)

Name of the algorithm (for example, BZIP2 or ZLIB)

ALGORITHM_DESCRIPTION

VARCHAR2(64)

Description of the algorithm

ALGORITHM_COMPATIBILITY

VARCHAR2(18)

The required database compatibility level in order for the algorithm to work (for example, 11.0.0 for ZLIB)

DATABASE_COMPATIBILITY

VARCHAR2(18)

Current database compatibility

IS_VALID

VARCHAR2(3)

Whether or not the algorithm is valid with regard to the compatibility setting. Value is YES if ALGORITHM_COMPATIBILITY<=DATABASE_COMPATIBILITY.

IS_DEFAULT

VARCHAR2(3)

Whether or not this is the default algorithm

Oracle data dictionary views

Oracle dynamic performance views

V$RMAN_BACKUP_TYPE

V$RMAN_BACKUP_TYPE displays information about RMAN backup types.

Column

Datatype

Description

WEIGHT

NUMBER

Used to set precedence order of different backup types in reports.

INPUT_TYPE

VARCHAR2(13)

Used to represent possible filters used in creating various reporting screens.

Note:

1.

select * from V$RMAN_BACKUP_TYPE;

WEIGHT

INPUT_TYPE

1

BACKUPSET

2

SPFILE

3

CONTROLFILE

4

ARCHIVELOG

5

DATAFILE INCR

6

DATAFILE FULL

7

DB INCR

8

RECVR AREA

9

DB FULL

Oracle data dictionary views

Oracle dynamic performance views