ORA-06315: IPA: Invalid connect string
Cause: The connect string is malformed.
Action: Check and correct.
Cause: The connect string is malformed.
Action: Check and correct.
Friday 3 February 2012
ORA-06314: IPA: Event set up failure
ORA-06314: IPA: Event set up failure
Cause: Fatal interprocess communication error.
Action: Contact your system manager.
Cause: Fatal interprocess communication error.
Action: Contact your system manager.
ORA-06313: IPA: Shared memory failed to initialise
ORA-06313: IPA: Shared memory failed to initialise
Cause: The shared memory has not been set up correctly.
Action: Contact your system manager.
Cause: The shared memory has not been set up correctly.
Action: Contact your system manager.
ORA-06312: IPA: Incorrect outgoing service name supplied
ORA-06312: IPA: Incorrect outgoing service name supplied
Cause: Incorrect outgoing service name supplied.
Action: Check and correct the service name.
Cause: Incorrect outgoing service name supplied.
Action: Check and correct the service name.
ORA-06311: IPA: Maximum number of servers reached
ORA-06311: IPA: Maximum number of servers reached
Cause: Maximum number of servers reached.
Action: Shutdown and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start up enough servers to support database links.
Cause: Maximum number of servers reached.
Action: Shutdown and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start up enough servers to support database links.
ORA-06310: IPA: Environment variable(s) not set
ORA-06310: IPA: Environment variable(s) not set
Cause: Environment variable(s) not set correctly.
Action: Check and correct.
Cause: Environment variable(s) not set correctly.
Action: Check and correct.
ORA-06309: IPA: No message queue available
ORA-06309: IPA: No message queue available
Cause: The SQL*Net IPA servers have not been started.
Action: Run ipactl.
Cause: The SQL*Net IPA servers have not been started.
Action: Run ipactl.
ORA-06308: IPA: No more connections available
ORA-06308: IPA: No more connections available
Cause: You have exhausted all your connections.
Action: Try again when some of the current users have logged off.
Cause: You have exhausted all your connections.
Action: Try again when some of the current users have logged off.
ORA-06307: IPA: Cannot reset connection
ORA-06307: IPA: Cannot reset connection
Cause: A fatal error occurred during the resetting of the connection.
Action: Contact your customer support representative.
Cause: A fatal error occurred during the resetting of the connection.
Action: Contact your customer support representative.
ORA-06306: IPA: Message write length error
ORA-06306: IPA: Message write length error
Cause: The IPA driver tried to write a message in the queue that was too big for the queue.
Action: Contact your customer support representative.
Cause: The IPA driver tried to write a message in the queue that was too big for the queue.
Action: Contact your customer support representative.
ORA-06305: IPA: Illegal message type
ORA-06305: IPA: Illegal message type
Cause: The communication between user and ORACLE is out of synchronization. This message should not normally be issued.
Action: Contact your customer support representative.
Cause: The communication between user and ORACLE is out of synchronization. This message should not normally be issued.
Action: Contact your customer support representative.
ORA-06304: IPA: Message receive error
ORA-06304: IPA: Message receive error
Cause: The SQL*Net IPA driver could not read a message from the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
Cause: The SQL*Net IPA driver could not read a message from the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
ORA-06303: IPA: Message send error
ORA-06303: IPA: Message send error
Cause: The SQL*Net IPA driver could not write the message into the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
Cause: The SQL*Net IPA driver could not write the message into the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
ORA-06302: IPA: Cannot connect to remote host
ORA-06302: IPA: Cannot connect to remote host
Cause: found.
Action: Check sequentially for the above causes and eliminate the actual
Cause: found.
Action: Check sequentially for the above causes and eliminate the actual
ORA-06301: IPA: Cannot allocate driver context
ORA-06301: IPA: Cannot allocate driver context
Cause: The memory pool is exhausted.
Action: Check the circumstances and try to allocate less memory in your program or adjust the init parameters in your INIT.ORA file and retry.
Cause: The memory pool is exhausted.
Action: Check the circumstances and try to allocate less memory in your program or adjust the init parameters in your INIT.ORA file and retry.
ORA-06300: IPA: Disconnect failure
ORA-06300: IPA: Disconnect failure
Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.
Action: If there is no message queue, restart the SQL*Net IPA servers using ipactl. Otherwise contact your customer support representative.
Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.
Action: If there is no message queue, restart the SQL*Net IPA servers using ipactl. Otherwise contact your customer support representative.
ORA-06268: NETNTT: cannot read or etc or oratab
ORA-06268: NETNTT: cannot read or etc or oratab
Cause: The NTT two-task driver could not read configuration information from or etc or oratab.
Action: Make sure or etc or oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory.
Cause: The NTT two-task driver could not read configuration information from or etc or oratab.
Action: Make sure or etc or oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory.
ORA-06267: NETNTT: bad state
ORA-06267: NETNTT: bad state
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact your customer support representative.
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact your customer support representative.
ORA-06266: NETNTT: bad write length
ORA-06266: NETNTT: bad write length
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact your customer support representative.
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact your customer support representative.
ORA-06265: NETNTT: break protocol error
ORA-06265: NETNTT: break protocol error
Cause: The NTT two-task driver received an unexpected message type.
Action: Contact your customer support representative.
Cause: The NTT two-task driver received an unexpected message type.
Action: Contact your customer support representative.
ORA-06264: NETNTT: data protocol error
ORA-06264: NETNTT: data protocol error
Cause: The NTT two-task driver received an unexpected message type.
Action: Contact your customer support representative.
Cause: The NTT two-task driver received an unexpected message type.
Action: Contact your customer support representative.
ORA-06263: NETNTT: out of memory in pi_connect
ORA-06263: NETNTT: out of memory in pi_connect
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
ORA-06262: NETNTT: nfconn() failed
ORA-06262: NETNTT: nfconn() failed
Cause: The call to nfconn() failed while attempting to establish a connection.
Action: Contact your customer support representative.
Cause: The call to nfconn() failed while attempting to establish a connection.
Action: Contact your customer support representative.
ORA-06261: NETNTT: nrange() failed
ORA-06261: NETNTT: nrange() failed
Cause: The call to nrange() failed while attempting to establish a connection.
Action: Contact your customer support representative.
Cause: The call to nrange() failed while attempting to establish a connection.
Action: Contact your customer support representative.
ORA-06260: NETNTT: cannot write to remote process
ORA-06260: NETNTT: cannot write to remote process
Cause: An error occurred while writing the NTT communications linke.
Action: Contact your customer support representative.
Cause: An error occurred while writing the NTT communications linke.
Action: Contact your customer support representative.
ORA-06259: NETNTT: cannot read from remote process
ORA-06259: NETNTT: cannot read from remote process
Cause: An error occurred while reading the NTT communications link.
Action: Contact your customer support representative.
Cause: An error occurred while reading the NTT communications link.
Action: Contact your customer support representative.
ORA-06258: NETNTT: cannot allocate context area
ORA-06258: NETNTT: cannot allocate context area
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
ORA-06257: NETNTT: cannot send command line to shadow process
ORA-06257: NETNTT: cannot send command line to shadow process
Cause: An error occurred while writing the NTT communications link.
Action: Contact your customer support representative.
Cause: An error occurred while writing the NTT communications link.
Action: Contact your customer support representative.
ORA-06256: NETNTT: remote fork failed
ORA-06256: NETNTT: remote fork failed
Cause: The Oracle listener process on the cube could not fork off a shadow process.
Action: The instance you are trying to connect to probably doesn t have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance.
Cause: The Oracle listener process on the cube could not fork off a shadow process.
Action: The instance you are trying to connect to probably doesn t have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance.
ORA-06255: NETNTT: cannot read pid of remote process
ORA-06255: NETNTT: cannot read pid of remote process
Cause: An error occurred while reading the NTT communications link.
Action: Contact your customer support representative.
Cause: An error occurred while reading the NTT communications link.
Action: Contact your customer support representative.
ORA-06254: NETNTT: cannot share connection to cube
ORA-06254: NETNTT: cannot share connection to cube
Cause: The NTT two-task driver could not share a connection to the cube.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: The NTT two-task driver could not share a connection to the cube.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
ORA-06253: NETNTT: cannot read arguments from address file
ORA-06253: NETNTT: cannot read arguments from address file
Cause: The NTT two-task driver could not read addressing information from its addressing file.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: The NTT two-task driver could not read addressing information from its addressing file.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
ORA-06252: NETNTT: cannot open address file
ORA-06252: NETNTT: cannot open address file
Cause: The NTT two-task driver could not open a file containing address information.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: The NTT two-task driver could not open a file containing address information.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
ORA-06251: NETNTT: cannot translate address file name
ORA-06251: NETNTT: cannot translate address file name
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
ORA-06250: NETNTT: cannot allocate send and receive buffers
ORA-06250: NETNTT: cannot allocate send and receive buffers
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
ORA-06145: NETTCP: unable to start ORASRV: images not installed
ORA-06145: NETTCP: unable to start ORASRV: images not installed
Cause: The host s SQL*Net TCP or IP server was unable to start the ORACLE server process because the ORACLE protected images were not installed.
Action: Install the images.
Cause: The host s SQL*Net TCP or IP server was unable to start the ORACLE server process because the ORACLE protected images were not installed.
Action: Install the images.
ORA-06144: NETTCP: SID (database) is unavailable
ORA-06144: NETTCP: SID (database) is unavailable
Cause: The database administrator on the host has varied the SID offline.
Action: Wait for it to be varied back on-line.
Cause: The database administrator on the host has varied the SID offline.
Action: Wait for it to be varied back on-line.
ORA-06143: NETTCP: maximum connections exceeded
ORA-06143: NETTCP: maximum connections exceeded
Cause: The connect failed because the maximum conncurrent connections supported by the host s SQL*Net TCP or IP server has already been reached.
Action: Wait for a short period and re-try.
Cause: The connect failed because the maximum conncurrent connections supported by the host s SQL*Net TCP or IP server has already been reached.
Action: Wait for a short period and re-try.
ORA-06142: NETTCP: error getting user information
ORA-06142: NETTCP: error getting user information
Cause: A proxy login connect attempt failed because the SQL*Net TCP or IP server was unable to access the proxy account. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: A proxy login connect attempt failed because the SQL*Net TCP or IP server was unable to access the proxy account. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06141: NETTCP: no privilege for user
ORA-06141: NETTCP: no privilege for user
Cause: A proxy login connect attempt failed because the SQL*Net TCP or IP server had insufficient privileges to access the proxy account.
Action: Change account protection; change server privilges.
Cause: A proxy login connect attempt failed because the SQL*Net TCP or IP server had insufficient privileges to access the proxy account.
Action: Change account protection; change server privilges.
ORA-06140: NETTCP: no such user
ORA-06140: NETTCP: no such user
Cause: A proxy login connect attempt failed because the client username has no counterpart on the host.
Action: none
Cause: A proxy login connect attempt failed because the client username has no counterpart on the host.
Action: none
ORA-06138: NETTCP: error during connection handshake
ORA-06138: NETTCP: error during connection handshake
Cause: Network I or O failure occurred while communicating with the host s SQL*Net TCP or IP server. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: Network I or O failure occurred while communicating with the host s SQL*Net TCP or IP server. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06137: NETTCP: error during connection handshake
ORA-06137: NETTCP: error during connection handshake
Cause: Network I or O failure occurred while communicating with the host s SQL*Net TCP or IP server. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: Network I or O failure occurred while communicating with the host s SQL*Net TCP or IP server. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06136: NETTCP: error during connection handshake
ORA-06136: NETTCP: error during connection handshake
Cause: Network I or O failure occurred while communicating with the host s SQL*Net TCP or IP server. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: Network I or O failure occurred while communicating with the host s SQL*Net TCP or IP server. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06135: NETTCP: connection rejected; server is stopping
ORA-06135: NETTCP: connection rejected; server is stopping
Cause: The host s SQL*Net TCP or IP server rejected this connection request because it is in the process of stopping.
Action: Re-start SQL*Net TCP or IP server.
Cause: The host s SQL*Net TCP or IP server rejected this connection request because it is in the process of stopping.
Action: Re-start SQL*Net TCP or IP server.
ORA-06134: NETTCP: file access privilege violation
ORA-06134: NETTCP: file access privilege violation
Cause: The host s SQL*Net TCP or IP server did not have READ or EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Change protection on SID mapping file.
Cause: The host s SQL*Net TCP or IP server did not have READ or EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Change protection on SID mapping file.
ORA-06133: NETTCP: file not found
ORA-06133: NETTCP: file not found
Cause: The host s SQL*Net TCP or IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Check CONFIG.ORA for spelling; make correct entry.
Cause: The host s SQL*Net TCP or IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Check CONFIG.ORA for spelling; make correct entry.
ORA-06132: NETTCP: access denied, wrong password
ORA-06132: NETTCP: access denied, wrong password
Cause: The host SQL*Net TCP or IP server rejected this connection request because the client password did not match the host password.
Action: To grant access, get passwords in sync.
Cause: The host SQL*Net TCP or IP server rejected this connection request because the client password did not match the host password.
Action: To grant access, get passwords in sync.
ORA-06131: NETTCP: user access denied
ORA-06131: NETTCP: user access denied
Cause: The host s SQL*Net TCP or IP server rejected this connection request because the client user(name) does not have access privilege - as determined by the contents of the Username Mapping Table (UMT), a component of the host s CONFIG.ORA.
Action: To grant access, add appropriate entry to the host s UMT.
Cause: The host s SQL*Net TCP or IP server rejected this connection request because the client user(name) does not have access privilege - as determined by the contents of the Username Mapping Table (UMT), a component of the host s CONFIG.ORA.
Action: To grant access, add appropriate entry to the host s UMT.
ORA-06130: NETTCP: host access denied
ORA-06130: NETTCP: host access denied
Cause: The host s SQL*Net TCP or IP server rejected this connection request because the client node does not have access privilege - as determined by the contents of the Valid Node Table (VNT), a component of the host s CONFIG.ORA.
Action: To grant access, add appropriate entry to the host s VNT.
Cause: The host s SQL*Net TCP or IP server rejected this connection request because the client node does not have access privilege - as determined by the contents of the Valid Node Table (VNT), a component of the host s CONFIG.ORA.
Action: To grant access, add appropriate entry to the host s VNT.
ORA-06129: NETTCP: unable to transfer socket ownership to ORASRV
ORA-06129: NETTCP: unable to transfer socket ownership to ORASRV
Cause: The host s SQL*Net TCP or IP server was unable to transfer the network communication handle to the ORACLE server process. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host s SQL*Net TCP or IP server was unable to transfer the network communication handle to the ORACLE server process. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06128: NETTCP: unable to create mailbox
ORA-06128: NETTCP: unable to create mailbox
Cause: The host s SQL*Net TCP or IP server was unable to create a mailbox (needed for IPC communication with the ORACLE server process). See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host s SQL*Net TCP or IP server was unable to create a mailbox (needed for IPC communication with the ORACLE server process). See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06127: NETTCP: unable to change username
ORA-06127: NETTCP: unable to change username
Cause: The host s SQL*Net TCP or IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host OS).
Action: Create new user account on host.
Cause: The host s SQL*Net TCP or IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host OS).
Action: Create new user account on host.
ORA-06126: NETTCP: ORASRV unable to open network connection
ORA-06126: NETTCP: ORASRV unable to open network connection
Cause: The ORACLE server process was started but was unable to open the socket passed to it by TCPSRV.
Action: Contact your customer support representative.
Cause: The ORACLE server process was started but was unable to open the socket passed to it by TCPSRV.
Action: Contact your customer support representative.
ORA-06125: NETTCP: ORASRV exited unexpectedly
ORA-06125: NETTCP: ORASRV exited unexpectedly
Cause: The ORACLE server process was started but exited unexpectedly. Possible causes: 1. Insufficient quotas to run ORASRV 2. ORACLE is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_ SRVTnn_lamp;lt;lamp;nbsp;SIDlamp;gt;.OUT
Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative.
Cause: The ORACLE server process was started but exited unexpectedly. Possible causes: 1. Insufficient quotas to run ORASRV 2. ORACLE is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_ SRVTnn_lamp;lt;lamp;nbsp;SIDlamp;gt;.OUT
Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative.
ORA-06124: NETTCP: timeout waiting for ORASRV
ORA-06124: NETTCP: timeout waiting for ORASRV
Cause: The ORACLE server process was started but failed to respond after N secs.
Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = lamp;lt;lamp;nbsp;no. of secslamp;gt; which will come into effect the next time the SQL*Net TCP or IP server is started.
Cause: The ORACLE server process was started but failed to respond after N secs.
Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = lamp;lt;lamp;nbsp;no. of secslamp;gt; which will come into effect the next time the SQL*Net TCP or IP server is started.
ORA-06123: NETTCP: cannot set KEEPALIVE
ORA-06123: NETTCP: cannot set KEEPALIVE
Cause: The host s SQL*Net TCP or IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host s SQL*Net TCP or IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06122: NETTCP: setup failure
ORA-06122: NETTCP: setup failure
Cause: The host s SQL*Net TCP or IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host s SQL*Net TCP or IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06121: NETTCP: access failure
ORA-06121: NETTCP: access failure
Cause: The host s SQL*Net TCP or IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host s SQL*Net TCP or IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP or IP server log file for more details.
Action: Contact your customer support representative.
ORA-06120: NETTCP: network driver not loaded
ORA-06120: NETTCP: network driver not loaded
Cause: The TCP or IP network driver is not loaded.
Action: Check that the TCP or IP driver is loaded correctly.
Cause: The TCP or IP network driver is not loaded.
Action: Check that the TCP or IP driver is loaded correctly.
Subscribe to:
Posts (Atom)