Oracle® Database Administrator's Reference 10g Release 2 (10.2) for hp OpenVMS Part Number B25416-02 |
|
|
View PDF |
This appendix covers Oracle Database 10g messages, codes, and actions. The information in this appendix supplements Oracle Database Error Messages Guide. Refer to this guide for a complete list of messages and detailed information about Oracle messages and codes.
All messages between 07500 and 07999 are specific to the OpenVMS operating system.
$ INSORACLE
Privileges to use the CONNECT /
command depend on whether or not:
An ORA_
sid
_DBA
identifier is in the OpenVMS rights database
The account has the process rights identifier ORA_DBA
, ORA_
sid
_DBA
, or both
These identifiers are added by running the OpenVMS AUTHORIZE
utility. The following cases identify process rights identifiers and your subsequent privileges:
If the identifier, ORA_
sid_x
_DBA
, exists in the OpenVMS rights database for instance sid_x
, then your account must have been granted the process rights identifier ORA_
sid_x
_DBA
to control instance sid_x
.
If the identifier ORA_
sid_x
_DBA
exists in the OpenVMS rights database for instance sid_x
and your account does not have the process rights identifier ORA_
sid_x
_DBA
but it does have ORA_DBA
, then your account does not have sufficient privileges to control instance sid_x
. However, it may control all other instances that do not have ORA_
sid_x
_DBA
identifiers defined for them.
If the identifier ORA_
sid_x
_DBA
does not exist in the OpenVMS rights database for instance sid_x
and you have the process rights identifier to ORA_DBA
, then your account has sufficient privileges to control instance sid_x
and all other instances that do not have ORA_
sid
_DBA
identifiers defined for them.
SYSGEN
parameter MAXSYSGROUP
poses a security risk.MAXSYSGROUP
.SYSGEN
parameter MAXSYSGROUP poses a security risk.MAXSYSGROUP
SYSGEN
parameter. If any valid Oracle files exist with such ownership conditions, then you must change their ownership before attempting to run the REUSE
command on them.SYSGEN
parameter MAXSYSGROUP
poses a security risk.MAXSYSGROUP
.SYSGEN
parameter MAXSYSGROUP
poses a security risk.SYSGEN
parameter MAXSYSGROUP
. If any valid Oracle files exist with such ownership conditions, then you must change their ownership before attempting to open them.SYSGEN
parameter MAXSYSGROUP
poses a security risk.SYSGEN
parameter MAXSYSGROUP
. If any valid Oracle files exist with such ownership conditions, then you must change their ownership before attempting to REUSE them. Likewise, if you attempt to create a file that will inherit an invalid ownership from the parent directory, then you should create it in a different location, or take other steps to avoid this situation.ORACLE_SID
that is exceptionally long or defined circularly. If none, then report as a bug.DB_BLOCK_SIZE
in the parameter file to conform to these limits.The error is caused when there are not enough contiguous global pages available to create the SGA. For example, the SGA created by the distributed INIT.ORA
file requires 390000 contiguous global pages. In addition, remember that contiguous global pages are consumed by the installation of the Oracle sharable image, and any Oracle Database Client applications installed by INSUTILITY.COM.
To show the maximum number of contiguous global pages, use the following lexical function:
$ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES")
To show the number of global pages available, use the following lexical function:
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")
If the available global pages are fragmented, then restart the system after increasing the SYSGEN
parameter, GBLPAGES
(global page limit). This parameter cannot be dynamically increased. You need to restart the system for these changes to take effect. If the available global pages are merely fragmented, but their number is sufficient and restarting the system is enough. In such a case, there is no need to increase the SYSGEN
parameter, GBLPAGES
.
$MGBLSC
failed. The usual reason is that Oracle Database 10g has not been started up.