User`s guide
Oracle Error Messages for BS2000/OSD A-5
Action: Ensure that the
ORASID
definition is correct and re-run the program.
ORA-05032: bad name parse
Cause: The translation of a file name, or other name containing variable parts,
failed. The error may be caused by a wrong specification in the
ORAENV
file.
Action: Ensure that the
ORAENV
variable assignments are correct. If you cannot
identify the cause of the problem, then contact your Oracle Support Services
Representative.
ORA-05033: bad environment values
Cause: One or more of the values specified in the
ORAENV
file are invalid.
Action: Ensure that you specified legal values in the
ORAENV
file (Refer to
Appendix B, "Oracle Environment Variables" for further information).
ORA-05034: bad seal
Cause: Internal error. An internal file control structure is found to be corrupt.
Action: Contact your Oracle Support Services Representative.
ORA-05035: host command not executed
Cause: A BS2000 command, argument of a
HOST
or
#HOST
command, is invalid or
too long.
Action: Enter a valid
HOST
command.
ORA-05036: bad user id (length)
Cause: Internal buffer overflow while building a file name from variable
components.
Action: Ensure that the
ORAUID
value specified in the
ORAENV
file is correct. If you
cannot identify the cause of the problem, then contact your Oracle Support
Services Representative.
ORA-05037: /CANCEL command not executed
Cause: A background job could not be canceled. The background task may have
already been terminated.
Action: If you cannot identify the cause of the problem, then contact your Oracle
Support Services Representative.
ORA-05038: SID has illegal length
Cause: The system identifier specified in either the
ORAENV
file or as part of a
connect string exceeds 4 characters in length.
Action: Specify a correct value.
ORA-05039: Recursive entry to ssodrv
Cause: The Oracle Database kernel has been re-entered at the top. This should not
happen.
Action: Make sure that your user program does not incorrectly call Oracle
Database functions from within an interrupt handling routine (signal routine,
contingency). If you cannot identify the cause of the problem, then contact your
Oracle Support Services Representative.
ORA-05040: no more dynamic memory
Cause: Request memory failed in file-management components. This is probably
caused by a user address space that is too small.