394 Chapter 10
Tuning, Troubleshooting, Security, and Maintenance
Troubleshooting: Specific Problems
Problem Could not connect to Oracle when using SQL*Net, with following error
message:
Database error: ORA-12158: (Cnct err, can’t get err txt
See Servr Msgs & Codes Manual) (OpC50-15)
Description ITO connects as user opc_op to the database. For this reason, the
current directory (the directory where you started ITO) must be readable
by user opc_op
Solution Allow read and execute access to all users to the directory from which you
normally start ITO or change the directory to a directory accessible by
opc_op before starting ITO
Problem Cannot start Oracle database
Description The Oracle database cannot be started because the Oracle resources are
already in use.
Solution Check that Oracle is not already running. Check whether some
inter-process communication facilities are not freed by the Oracle
processes: ipcs | grep oracle. If there are some IPC facilities left,
clean them up using: ipcrm. Check whether the Oracle SGA definition
file, ${ORACLE_HOME}/dbs/sgadef${ORACLE_SID}.dbf still exists,
and if so, remove it.
If other instances of Oracle are running on the same system, shut down
these instances before clearing semaphores and shared-memory using
ipcrm(1M).
Problem Cannot create Oracle database. opcdbsetup exits with following error:
insufficient privileges, not connected
Description Connect internal requires that the primary group of the DBA user is
dbaA. The default DBA user is the UNIX user oracle.
Solution Correct the Oracle DBA user using SAM and assign him the group dba
