The IGNORE_SESSION_SET_PARAM_ERRORS parameter allows you to change the outcome of the following scenario:

1. An Oracle database uses PDB lockdown profiles to prevent certain initialization parameters from being modified with the ALTER SESSION statement.
2. A database client attempts to modify one of those parameters with the ALTER SESSION statement. The client has no knowledge that the parameter is locked down.
3. The database returns an error to the client.

To prevent the database from returning an error in the preceding scenario, set the value of IGNORE_SESSION_SET_PARAM_ERRORS to a comma-separated list of locked down initialization parameters. Thereafter, if a client attempts to modify one of those parameters with the ALTER SESSION statement, the database will ignore the modification attempt and indicate to the client that the operation was successful.

You can set the IGNORE_SESSION_SET_PARAM_ERRORS parameter while connected to a specific PDB, or you can apply it to all PDBs by setting it in the CDB root.

Example

The CURSOR_INVALIDATION and CURSOR_SHARING parameters are locked down in one of the PDBs in your database. If a client application attempts to modify either of these parameters, you want the database to ignore the request and allow the application to continue running without incurring an error. To achieve this, you can connect to the PDB and set the IGNORE_SESSION_SET_PARAM_ERRORS parameter. For example:

ALTER SYSTEM SET IGNORE_SESSION_SET_PARAM_ERRORS = CURSOR_INVALIDATION, CURSOR_SHARING;