Making the initialization parameters private prevents the upload from happening and they do not appear in dynamic performance views.
If, however, you are storing sensitive information like a password in the initialization parameter file, then you may not want it uploaded to the server because the initialization parameters and values are not encrypted when uploaded. Most initialization parameters should not be private. PRIVATE specifies that the initialization parameter should be private to the agent and should not be uploaded to the Oracle database.
Use SET for parameter values that the drivers or non-Oracle system need as environment variables. SET specifies that, in addition to being used as an initialization parameter, the parameter value is set as an environment variable for the agent process. If you do not specify either SET or PRIVATE, the parameter is used only as an initialization parameter for the agent. Most parameters are needed only as initialization parameters, so you usually do not need to use the SET or PRIVATE keywords. You cannot use either as an initialization parameter name. If a backslash precedes any other character then the backslash is ignored.įor example, to enable tracing for an agent, set the HS_FDS_TRACE_LEVEL initialization parameter as follows: HS_FDS_TRACE_LEVEL=ON The following can be used inside a quoted string:Ī backslash at the end of the line continues the string on the next line. An initialization parameter value is either:Ī string of characters that does not contain any backslashes, white space or double quotation marks (")Ī quoted string beginning with a double quotation mark and ending with a double quotation mark. Value is the initialization parameter value. Initialization parameter names are case sensitive. It is a string of characters starting with a letter and consisting of letters, digits and underscores. Parameter is an initialization parameter name. If there is a syntax error in an initialization parameter file, none of the settings take effect. The syntax for the initialization parameter file is as follows:Įach command should start on a separate line.Įnd of line is considered a command terminator (unless escaped with a backslash). Oracle Database Gateway for DRDA Initialization Parameters Oracle Database Gateway for ODBC Initialization Parameters Oracle Database Gateway for SQL Server Initialization Parameters Oracle Database Gateway for Teradata Initialization Parameters
Oracle Database Gateway for Informix Initialization Parameters
Oracle Database Gateway for Sybase Initialization Parameters It also describes the initialization parameter file syntax. This appendix contains a list of the gateway initialization parameters that can be set for each gateway and their description. Changes made to the initialization parameters only take effect in the next gateway session. The gateway initialization parameter file must be available when the gateway is started. Set the gateway parameters in the initialization parameter file using an agent-specific mechanism, or set them in the Oracle data dictionary using the DBMS_HS package. The Oracle database initialization parameters in the init.ora file are distinct from gateway initialization parameters.