out of memory HP-UX Error: 12: Not enough space
ORA-30019: Illegal rollback Segment operation in Automatic Undo mode
ORA-30036: unable to extend segment by 1024 in undo tablespace 'UNDOTBS1'
TNS-12500
.... system resource depletion, means that the system memory allocated to the oracle exhausted. Although we have 4G of physical memory, but the system under normal circumstances can only be assigned to the oracle 2G of memory, 2G memory, including all memory SGA, PGA, etc. need to use oracle. In exclusive mode, a session for each of the right and left separate memory allocation 2M. In the present embodiment, the SGA allocated about 600M, every user is assigned a 2M memory calculation, when the number of connections 750, the total allocated memory has reached 2G, will not increase the number of new connections. To solve this problem, under the premise of no major adjustment, either reduce the SGA size, or reduced to the size of the memory allocation for each session in order to be able to connect more users.
Resolution process:
1 Reset init.ora parameter file, tuning parameters following four values:
....short_area_size
....hash_area_size
....bitmap_merge_area_size
....create_bitmap_area_seze
....open_cursone
2 small size of the transfer of SGA
Reducing the number of queues oracle Job 3 (Job_queue_processes) and the number of concurrent queue (PARALLEL_MAX_SERVERS)
4 reset and reducing the Session / thread stack size used
The oracle model to 5 mts
6 Use of ESMA intel hardware support, namely the use of large memory
..1) Use / 3G system switches on the intel
.. 2) Use PSE36 memory
1 TNS-12154 Error ORA-12154 or
Wherein: SQL * NET connection string is not found or alias
Reason 1: (1) TNSNAMES.ORA file is not found, the default path to the file is:
Windows 95/98 client
SQL*Net 2.x - ORAWIN95NETWORKADMIN
Net8 - ORAWIN95NET80admin
Net8i - ORACLEORA81NETWORKADMIN
Windows NT client
SQL*Net 2.x - ORANTNETWORKADMIN
Net8 - ORANTNET80ADMIN
Net8i - ORACLEORA81NETWORKADMIN
UNIX Client
$ORACLE_HOME/NETWORK/ADMIN
or /etc
or /var/opt/oracle
In the client settings TNS_ADMIN
Set TNS_ADMIN. TNS_ADMIN points TNSNAMES.ORA file location in the registry HKEY_LOCAL_MACHINESoftwareOracle
Action: Check the file location above description
Reason 2: (2) TNSNAMES.ORA file format not content
Action: Check the file format, the standard format is as follows:
DEV1.WORLD =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (Host = 145.45.78.56) (Port = 1521) ) )
(CONNECT_DATA = (SID = ORCL) ) )
Reason 3: (3) TNSNAMES.ORA inconsistent with SQLNET.ORA
Measures: SQLNET.ORA format is as follows:
TRACE_LEVEL_CLIENT = OFF
SQLNET.AUTHENTICATION_SERVICES = (NONE)
NAMES.DIRECTORY_PATH = (TNSNAMES)
AUTOMATIC_IPC = OFF
Because there is no NAMES.DEFAULT_DOMAIN = world, so DEV1.WORLD connection string can not be connected, it can be increased in TNSNAMES.ORA
DEV1 =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (Host = 145.45.78.56) (Port = 1521) ) )
(CONNECT_DATA = (SID = ORCL) ) )
In this case it can be connected.
2 NL-00462 Error or ORA-00462
Features: listener can not start
The reason: LISTENER.ORA file content errors, such as mismatched parentheses, parameter name errors, extra spaces and so on.
Action: Re-edit file
3 NL-00405 Error or ORA-00405
Characteristics: LISTENER.ORA file is unreadable or can not be found
The reason: LISTENER.ORA file content errors, such as mismatched parentheses, parameter name errors, extra spaces and so on.
Action: Make sure the file location in the default directory $ ORACLE_HOME / Network / ADMIN , or set the environment variable TNS_ADMIN points to the location of this file is located.
4 TNS-01155 Error or ORA-01155
Characteristics: LISTENER.ORA file SID_LIST_LISTENER variable assignment does not
The reason: LISTENER.ORA file content errors, SID_LIST_LISTENER variable assignment wrong.
Action: Be sure the correct assignment file, $ ORACLE_HOME / Network / ADMIN / the Samples have sample files directory for reference.
5 TNS-12537 、TNS-12560、TNS-00507 Error
Characteristics: LISTENER.ORA file references an invalid protocol adaptation program
The reason: LISTENER.ORA file PROCOTOL variable assignment wrong.
Action: Make sure the file in the correct assignment, usually with TCP protocol, $ ORACLE_HOME / Network / ADMIN / the Samples have sample files directory for reference. With adapters tnslsnr inspection program agreement
6 TNS-12203 Error
Wherein: the target can not be connected to the
The reason: the listener whether to start; alias is configured
Action: Check whether the listener is started, for example lsnrctl Status ; check TNSNAMES.ORA alias configuration
7 TNS-12533 Error
Wherein: the target can not be connected to the
Cause: Illegal address parameters,
Remedy: Check TNSNAMES.ORA the ADDRESS parameters
1 ORA-12571 , ORA-03113 , ORA-03114 , ORA-01041
Characteristics: The client (proxy or application server) Times have such disconnection error
The reason: If the occasional once, it may abort the reasons for the network or the user, if compared with the client and server-side character set often inconsistent.
Action: If occasional, may file server protocol configuration of PROTOCOL.ORA increase in a row
TCP.NODELAY=YES；
If you often have, for the client and server-side character set is inconsistent or network reasons.
The client's character set definition in the registry: HKEY__LOCAL__MACHINE / SOFTWARE / ORACLE / NLS__LANG
In the client registry TCP setup parameters item TCPMAXDATARETRANSMITIONS = 20 .
2 ORA-01000
Features: cursor reaches the maximum number of sessions allowed
The reason: the cursor reaches the maximum number of sessions allowed
Action: There are two solutions:
( 1 ) in the initialization file INIT <SID> .ORA increases file OPEN_CURSORS amount, generally require more than 200 .
( 2 ) at the application level, and development-related tools, such as setting MAXOPEN_CURSORS like.
3 ORA-01545
Features: a rollback segment unavailable
Cause :( 1 ) when the rollback ONLINE , the rollback but unavailable, e.g. rollback table space where the OFFLINE;
( 2 ) when the rollback ONLINE time, but has rollback ONLINE , e.g. rollback is used twice, as typical case OPS time mode, rollback is not public ;
( 3 ) When you delete a rollback, rollback segments have active transaction;
Measures :( 1 ) ensure that the rollback can
( 2 ) from the initialization file INIT <SID> .ORA parameter ROLLBACK) SEGMENTS remove the specified rollback.
( 3 ) rollback table space where you can delete, cancel UNDO affairs
4 ORA-0165x
Wherein: the table space is not enough space for distribution
Reason: table is full; storage parameters is unreasonable, the NEXT is too small; no continuous section
Action: If the table is full, you need to increase table space file; if the storage parameters is unreasonable, you need to increase INITIAL and the NEXT ; if there is no continuous interval need to merge free table space.
View space debris with DBA_FREE_SPACE
5 ORA-01555
Features: The current session can not read data from a previous version
The reason: many reasons, the main reasons are the following: rollback segment is too small, too little; rollback conflict; cross submission (FETCH_ACROSS)
Action: Increase the number of rollback;
6 ORA-04031
Features: shared memory pool area is not enough memory, or memory fragmentation
Reason: when trying to load a large package or a large storage execution process, no shared pool contiguous memory space.
Action: If this is not enough memory, increase SHARE) pool_size ;
If memory fragmentation, execute alter system flush share_pool
7 ORA-04091
Features: Trigger is not working properly
Reason: when a line change is triggered to read or modify a table (being modified, insertion), such an error is generated.
Action: Check the trigger scripts to ensure referential integrity
8 ORA-01242 , ORA-01113
Wherein: a media failure database downtime
The reason: media failure.
Action: Check hardware failure; modify dbshut script, which will be the STARTUP command is amended as follows:
Startup open recover
Alter database open