SAP Note 15675 - Usage of undocumented ORACLE parameters

Symptom:

See solution

Cause and prerequisites

See solution

Solution
USAGE OF UNDOCUMENTED ORACLE PARAMETERS

With good reason, I must once again stress that so-called undocumented
ORACLE parameters are NOT to be used in customer systems.

In particular, this applies to all '_' parameters.

Using these parameters can lead to fatal consequences for the customer.


Example: If a database is used with _disable_logging and the host
crashes during this time (power failure, disk crash, ...),
the database can normally NOT BE RESTARTED!

In this case, the customer must retrieve a backup.

If you forget to disable this parameter and the Archive mode
activates the database, this leads to an 'Archive Stuck.' In
this case, the database can only be exited using 'Shutdown

abort'. If you then try to start the database with
'_disable_logging', the database may allow itself to be
opened. However, there is a much higher probability that an
ORA 600 error occurs which means that the customer must
retrieve a backup anyway.

This parameter can only be used when restructuring a database
(orabuild).

The usage of this parameter is forbidden by ORACLE and if used, the
customer normally receives NO support.

Juergen Kirschner (ORACLE Germany)

Usage of this parameter is also forbidden by SAP (Exception: in
connection with orabuild).

Hans-Georg Oberhauser (SAP)

Additional key words

ORA-600 [2662]