Database Options
Use the Database Options section to specify environment variables that may improve the performance of the system. These options do not apply to every database.
(Applies only to Oracle databases.). Use this option to enable processes to initiate a local connection to a PeopleSoft database that is running on the same machine. You should use this option for all PeopleSoft Process Scheduler (batch) and application server configurations that are local (on the same server) to the PeopleSoft Oracle instance. This type of connection enables processing to complete significantly quicker.
Enter 1 to enable this option, and enter 0 to disable it.
Note: Using the local Oracle connection disables the Query Kill function.
Required for database-level auditing. How this works varies slightly, depending on the database platform. Use this option to view more information regarding the clients that are connected to a database server through the application server. For instance, with this enabled, you can view the client machine name or user ID that is associated with a particular connection. Without this option enabled, all connections appear somewhat anonymously, as in PSFT or APPSERV.
The default value is 1 (enabled). Enter 0 to disable it.
Note: This parameter isn't supported for DB2 LUW.
Enables you to configure the maximum number of cursors opened at one time. In general, the maximum number of cursors that can be open at one time within PeopleTools is 64,000. However, some database platforms place greater restrictions on the number of cursors that can be open at one time. By default, if no value is provided, the system allows a maximum of 1024 cursors.
To increase or decrease the default value, assign your custom value to this parameter. The value you set should be determined on multiple factors including:
Any predefined limits imposed by your database platform.
Internal testing of your PeopleSoft application(s).
Always refer to your database documentation for the latest recommendations related to maximum cursors settings. The following information can be used as a guideline.
|
Database |
Maximum Cursors Limit |
|---|---|
|
Oracle |
No predefined limit. |
|
IBM DB2 z/OS |
Limited only by available storage. |
|
IBM DB2 LUW |
Limited only by available storage. |
|
Microsoft SQL Server |
No predefined limit. |
Note: When running Application Engine programs or Data Mover scripts you may see the following message in your log files:
Initializing PSDB maximum
cursor = 1024
This is an informational message, not an error.
Enables you to disable or enable the execution of the %UpdateStats meta-SQL function on an Oracle GTT (Global Temporary table).
On the Oracle 11g database, when the %UpdateStats function is executed on an Oracle GTT, it causes performance issues; but this is not the case with the Oracle 12c database. Based on the version of the Oracle database, ensure that you set the parameter correctly.
The default value is 0, that is, the %UpdateStats function is executed on an Oracle GTT.
Enter 1 to disable the execution of the %UpdateStats function when the target table is an Oracle GTT.