Rules Governing Initialization Parameter Files
The following rules govern the specification of parameters in initialization parameter files:
■ An initialization parameter file should contain only parameters and comments. A
pound sign (#) starts a comment line. The rest of the line is ignored.
■ You can specify parameters in any order.
■ Case (upper or lower) in filenames is significant only if case is significant on the
host operating system.
■ To enter several parameters on one line, use spaces between parameter names and
values, as in the following example:
PROCESSES = 100 CPU_COUNT = 1 OPEN_CURSORS = 10
■ Some parameters, such as ROLLBACK_SEGMENTS, accept multiple value entries.
Enter multiple values enclosed in parentheses and separated by commas. For
example:
ROLLBACK_SEGMENTS = (SEG1, SEG2, SEG3, SEG4, SEG5)
Alternatively, you can enter multiple values without parentheses and commas. For
example:
ROLLBACK_SEGMENTS = SEG1 SEG2 SEG3 SEG4 SEG5
Either syntax is valid.
If you enter values for one parameter in multiple entries, then the entries must be
on consecutive lines. If they are not, then the first entry will not be processed
properly. For example, in the following entry the setting for SEG3 and SEG4 will
override the setting for SEG1 and SEG2:
ROLLBACK_SEGMENTS = SEG1 SEG2
OPEN_CURSORS = 10
ROLLBACK_SEGMENTS = SEG3 SEG4
■ A backslash (), also known as an escape character, indicates continuation of the
parameter specification. If a backslash continues a line, then the continued line
must have no leading spaces. For example:
ROLLBACK_SEGMENTS = (SEG1, SEG2,
SEG3, SEG4, SEG5)
■ You can use the IFILE initialization parameter to embed the contents of another
initialization parameter file into the current initialization parameter file.
■ Enclose in quotation marks any parameter values that contain spaces or tabs. You
can use either single or double quotation marks unless otherwise indicated. For
example:
NLS_TERRITORY = 'CZECH REPUBLIC'
■ Enclose in quotation marks any parameter value that contains a special character.[@more@]
■ An initialization parameter file should contain only parameters and comments. A
pound sign (#) starts a comment line. The rest of the line is ignored.
■ You can specify parameters in any order.
■ Case (upper or lower) in filenames is significant only if case is significant on the
host operating system.
■ To enter several parameters on one line, use spaces between parameter names and
values, as in the following example:
PROCESSES = 100 CPU_COUNT = 1 OPEN_CURSORS = 10
■ Some parameters, such as ROLLBACK_SEGMENTS, accept multiple value entries.
Enter multiple values enclosed in parentheses and separated by commas. For
example:
ROLLBACK_SEGMENTS = (SEG1, SEG2, SEG3, SEG4, SEG5)
Alternatively, you can enter multiple values without parentheses and commas. For
example:
ROLLBACK_SEGMENTS = SEG1 SEG2 SEG3 SEG4 SEG5
Either syntax is valid.
If you enter values for one parameter in multiple entries, then the entries must be
on consecutive lines. If they are not, then the first entry will not be processed
properly. For example, in the following entry the setting for SEG3 and SEG4 will
override the setting for SEG1 and SEG2:
ROLLBACK_SEGMENTS = SEG1 SEG2
OPEN_CURSORS = 10
ROLLBACK_SEGMENTS = SEG3 SEG4
■ A backslash (), also known as an escape character, indicates continuation of the
parameter specification. If a backslash continues a line, then the continued line
must have no leading spaces. For example:
ROLLBACK_SEGMENTS = (SEG1, SEG2,
SEG3, SEG4, SEG5)
■ You can use the IFILE initialization parameter to embed the contents of another
initialization parameter file into the current initialization parameter file.
■ Enclose in quotation marks any parameter values that contain spaces or tabs. You
can use either single or double quotation marks unless otherwise indicated. For
example:
NLS_TERRITORY = 'CZECH REPUBLIC'
■ Enclose in quotation marks any parameter value that contains a special character.[@more@]
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10599713/viewspace-1005015/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Initialization Parameter Files and Server Parameter Files (287)Server
- Special Characters in Initialization Parameter Files
- The SPFILE Initialization Parameter
- OPTIMIZER_MODE Initialization Parameter
- Oracle Server Parameter FilesOracleServer
- linux udev Rules files 理解Linuxdev
- DB_NAME Initialization Parameter (87)
- DB_DOMAIN Initialization Parameter (88)AI
- The SGA_TARGET Initialization Parameter (74)
- Step 3: Create the Initialization Parameter File (61)
- DB_BLOCK_SIZE Initialization Parameter (92)BloC
- The SGA_MAX_SIZE Initialization Parameter (72)
- UNDO_MANAGEMENT Initialization Parameter (118)
- Backing Up Server Parameter Files with RMANServer
- DB_CACHE_SIZE Initialization Parameter (109)
- Initialization Parameter Changes from 9i to 10g
- ORA-29707: inconsistent value 2 for initialization parameter cluster_database_Database
- Oracle修改初始化引數(initialization parameter)scope的選項Oracle
- The COMPATIBLE Initialization Parameter and Irreversible Compatibility (119)
- 【MOS】Parameter FILESIZE - Multiple Export Files (文件 ID 290810.1)Export
- Oracle GoldenGate Best Practice - sample parameter files (文件 ID 1321696.1)OracleGo
- oracle goldengate 引數詳解(轉MOS:Oracle GoldenGates ample parameter files)OracleGo
- Initialization
- list initialization
- 初始化 (Initialization)
- Oracle ParameterOracle
- Rules For JavaScript Library AuthorsJavaScript
- Required parameter $xxx follows optional parameter $yyyUI
- Oracle FilesOracle
- SKIP_UNUSABLE_INDEXES InitializationIndex
- Understanding Initialization Parameters (85)
- Other SGA Initialization Parameters (96)
- Java規則引擎 Easy RulesJava
- ElementUi rules表單驗證UI
- Rust中的macro_rulesRustMac
- Sessions & Processes parameterSession
- Import parameter: STATISTICSImport
- Export Parameter : BufferExport