Oracle 10G tablespace movement, all applicable routines of the TNS listener cannot establish a new connection, service_died 12537, c3p0 connection pool parameters,

Oracle 10G tablespace movement, all applicable routines of the TNS listener cannot establish a new connection, service_died 12537, c3p0 connection pool parameters,

One Oracle O & M experience while learning and working, step by step.

A few days ago, after deleting junk data tables and clearing the rollback tablespace, we rebuilt the index again, and felt that oracle's performance was really amazing. The system started to run quickly again.

After the customer experienced this, he proposed to switch the database to the storage and allocated 200 GB.

Start working,

1. Stop oracle first

2. Copy the tablespace file you want to move to the destination. For example, copy data from disk D to disk E.

3. log on to oracle

sqlplus / as sysdba

4. Then execute

startup mount alter database rename file 'D:/xxxxx' to 'E:/xxxxx';alter database open;

OK. Everything is done.

After the successful completion, the system runs for two days. The customer said that the system must be restarted every morning before it can be used. Otherwise, the service will be used. Very confused. Open oracle log view

Warning log: \ oracle \ product \ 10.2.0 \ db_1 \ admin \ orcl \ bdump \ alert_orcl.log listening log: \ oracle \ product \ 10.2.0 \ db_1 \ NETWORK \ log \ listener. log

The volume of listener. log has increased to 140 MB. The following content is found in the opening:

Workman 16: 57:-2014 07:59:42 * service_update * scm *-2014 07:59:47 * (CONNECT_DATA = (CID = (PROGRAM =) (HOST =__ jdbc __) (USER =) (SERVICE_NAME = SCM) * (ADDRESS = (PROTOCOL = tcp) (HOST = 10.11.15.179) (PORT = 2910) * establish * SCM * 12528TNS-12528: TNS: listener: all applicable routines cannot establish a new connection from month 1 to 12-2014 07:59:57 * (CONNECT_DATA = (CID = (PROGRAM =) (HOST =__ jdbc _) (USER = )) (SERVICE_NAME = SCM) * (ADDRESS = (PROTOCOL = tcp) (HOST = 10.11.15.179) (PORT = 2912) * establish * SCM * 12528TNS-12528: TNS: Listener: all applicable routines cannot establish a new connection from month 1 to Month 12 to month 2014 08:00:05 * service_died * scm * 1253701-12-month 2014 08:00:20 * service_register * scm *-2014 08:00:26 * service_update * scm * 0

[Note: The error 12537 has been found to be a vague problem by Du Niang for a long time. Many people say it is a problem with oracle configuration]

After analysis, this should have nothing to do with the configuration, because oracle does not need to be restarted when the restart is performed again. If there is a problem with or1c itself, I am afraid this will not work, and every time it appears at night, this error should be of a large scope.

Therefore, to view the connection status of java, the program uses c3p0 as the database connection pool. Modify its parameters

 

      <property key="c3p0.validate">true</property>        <property key="c3p0.idle_test_period">60</property>  

The connection pool checks whether the connection is normal. Check the listener. log of or1c again in the morning, and everything is back to normal.

Continue monitoring system ....