3.1.3.12 Customized Options

Table of Contents Previous Next



In previous releases of Advanced Server, the custom_variable_classes was required by those parameters not normally known to be added by add-on modules (such as procedural languages).
The custom_variable_classes parameter is deprecated in Advanced Server 9.2; parameters that previously depended on this parameter no longer require its support.
Range: 0 to 500
Range: 30 Kb to 256 Kb
Range: {true | false}
Provides the capability to temporarily suspend Index Advisor in an EDB-PSQL or PSQL session. The Index Advisor plugin, index_advisor, must be loaded in the EDB-PSQL or PSQL session in order to use the index_advisor.enabled configuration parameter.
Use the SET command to change the parameter setting to control whether or not Index Advisor generates an alternative query plan as shown by the following example:
Range: {true | false}
Range: {learn | passive | active}
The edb_sql_protect.level configuration parameter can be set to one of the following values to use either learn mode, passive mode, or active mode:
learn. Tracks the activities of protected roles and records the relations used by the roles. This is used when initially configuring SQL/Protect so the expected behaviors of the protected applications are learned.
passive. Issues warnings if protected roles are breaking the defined rules, but does not stop any SQL statements from executing. This is the next step after SQL/Protect has learned the expected behavior of the protected roles. This essentially behaves in intrusion detection mode and can be run in production when properly monitored.
active. Stops all invalid statements for a protected role. This behaves as a SQL firewall preventing dangerous queries from running. This is particularly effective against early penetration testing when the attacker is trying to determine the vulnerability point and the type of database behind the application. Not only does SQL/Protect close those vulnerability points, but it tracks the blocked queries allowing administrators to be alerted before the attacker finds an alternate method of penetrating the system.
Range: 1 to 2147483647
If the server is started when edb_sql_protect.max_protected_relations is set to a value outside of the valid range (for example, a value of 2,147,483,648), then a warning message is logged in the database server log file:
The database server starts successfully, but with edb_sql_protect.max_protected_relations set to the default value of 1024.
Range: 1 to 2147483647
Every protected role consumes space in shared memory. Please note that the server will reserve space for the number of protected roles times the number of protected relations (edb_sql_protect.max_protected_relations). The space for the maximum possible protected roles is reserved during database server startup.
If the database server is started when edb_sql_protect.max_protected_roles is set to a value outside of the valid range (for example, a value of 2,147,483,648), then a warning message is logged in the database server log file:
The database server starts successfully, but with edb_sql_protect.max_protected_roles set to the default value of 64.
Range: 100 to 2147483647
If the database server is started when edb_sql_protect.max_queries_to_save is set to a value outside of the valid range (for example, a value of 10), then a warning message is logged in the database server log file:
The database server starts successfully, but with edb_sql_protect.max_queries_to_save set to the default value of 5000.
Range: {NULL | empty_string | pgsql}
Use the edbldr.empty_csv_field parameter to specify how EDB*Loader will treat an empty string. The valid values for the edbldr.empty_csv_field parameter are:
An empty field is treated as a NULL if it does not contain quotes and as an empty string if it contains quotes.
For more information about the edbldr.empty_csv_field parameter in EDB*Loader, see the Database Compatibility Guide for Oracle Developers.
Range: {true | false}
When set to TRUE, Advanced Server’s UTL_ENCODE.UUDECODE function can decode uuencoded data that was created by the Oracle implementation of the UTL_ENCODE.UUENCODE function.
When set to the default setting of FALSE, Advanced Server’s UTL_ENCODE.UUDECODE function can decode uuencoded data created by Advanced Server’s UTL_ENCODE.UUENCODE function.
3.1.3.12.12 utl_file.umask
Range: Octal digits for umask settings
The utl_file.umask parameter sets the file mode creation mask or simply, the mask, in a manner similar to the Linux umask command. This is for usage only within the Advanced Server UTL_FILE package.
Note: The utl_file.umask parameter is not supported on Windows systems.
The value specified for utl_file.umask is a 3 or 4-character octal string that would be valid for the Linux umask command. The setting determines the permissions on files created by the UTL_FILE functions and procedures. (Refer to any information source regarding Linux or Unix systems for information on file permissions and the usage of the umask command.)
The following shows the results of the default utl_file.umask setting of 0077. Note that all permissions are denied on users belonging to the enterprisedb group as well as all other users. Only user enterprisedb has read and write permissions on the file.


Table of Contents Previous Next