ORA-32005: error while parsing size specification [string]
Cause: The value specified for an alter operation on a size parameter is not valid
Action: Correct the value and retry the operation
https://support.oracle.com/
http://www.oracle.com/
ORA-32005: error while parsing size specification [string]
Cause: The value specified for an alter operation on a size parameter is not valid
Action: Correct the value and retry the operation
https://support.oracle.com/
http://www.oracle.com/
ORA-32004: obsolete and/or deprecated parameter(s) specified
Cause: One or more obsolete and/or parameters were specified in the SPFILE or the PFILE on the server side
Action: See alert log for a list of parameters that are obsolete. or deprecated. Remove them from the SPFILE or the server side PFILE
https://support.oracle.com/
http://www.oracle.com/
ORA-32003: error occured processing parameter 'string'
Cause: An error occured while parsing the parameter file
Action: See additional errors to determine the root cause
https://support.oracle.com/
http://www.oracle.com/
ORA-32002: cannot create SPFILE already being used by the instance
Cause: A create spfile command is trying to write to an SPFILE that was used to startup the instance
Action: Specify a different SPFILE name
https://support.oracle.com/
http://www.oracle.com/
ORA-32001: write to SPFILE requested but no SPFILE specified at startup
Cause: An alter system command or an internal self tuning mechanism requested a write to the SPFILE but no SPFILE was used to startup the instance
Action: Create an SPFILE and re-start the instance using the SPFILE
https://support.oracle.com/
http://www.oracle.com/
ORA-31901: the current operation was cancelled by the user
Cause: The user requested to cancel current operation
Action: No action is necessary
https://support.oracle.com/
http://www.oracle.com/
ORA-31700: Very long string supplied for AUDIT_SYSLOG_LEVEL parameter
Cause: Very long string supplied for AUDIT_SYSLOG_LEVEL in init.ora
Action: Use a valid facility.level such as "local1.notice" as described in syslog's manual pages
https://support.oracle.com/
http://www.oracle.com/
ORA-31698: Error stack buffer size must be specified and must be greater than 0
Cause: Called get worker exception and either specified NULL or 0 for the error stack size argument
Action: Be sure to specify am error stack buffer size that is big enough to hold the error stack string (e.g. 4096 bytes). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error
https://support.oracle.com/
http://www.oracle.com/
ORA-31697: aborting operation at process order number string
Cause: User asked for it
Action: Don't ask for it
https://support.oracle.com/
http://www.oracle.com/
ORA-31696: unable to export/import string using client specified string method
Cause: Table attributes prevent client specified method for exporting or importing data
Action: Use default 'DATA_ACCESS' parameter value
https://support.oracle.com/
http://www.oracle.com/