Problem Description:
1:oracle database connection suddenly becomes very slow when landing; Sqldeveloper link database is slow;
2:kettle-spoon ETL Program Access database, task execution times: Database connection IO error: Socket Time out error.
Solve:
1:lsnrctl status uses commands to view the status of Oracle listening, and after the command executes, the results are displayed for a long time (normal and quick display);
2: Analyze whether the listening log is too large. Find the log path from the rendering results of the above command:
Listener Parameter file/u01/app/oracle/product/11.1.0/network/admin/listener.ora Listener Log File / U01/app/oracle/diag/tnslsnr/devdb/listener/alert/log.xml
The log is not large, and it is displayed by day.
3: Restart the monitor try: Lsnrctl stop lsnrctl Start, or you can use Lsnrctl reload, or very slow
4: Suspected Kettle-spoon database connection pool problem, the ETL program connection changed to Jndi shared database connection, and set up a connection pool.
Do the following:
1. Add the JDBC connection information to the data-integration\simple-jndi\jdbc.properties.
Like what:
############ ORACLE ################
Ora/type=javax.sql.datasource
Ora/driver=oracle.jdbc.driver.oracledriver
Ora/url=jdbc:oracle:thin:@127.0.0.1:1521:orcl
Ora/user=system
Ora/password=system
############ MSSQL ################
Mssql/type=javax.sql.datasource
Mssql/driver=net.sourceforge.jtds.jdbc.driver
Mssql/url=jdbc:jtds:sqlserver://127.0.0.1:1433;databasename=test; Selectmethod=cursor Mssql/user=test
Mssql/password=test
Note that the kettle used by the MSSQL driver is: driver=net.sourceforge.jtds.jdbc.driver
2. In the Database connection edit interface Select
Access=jndi
JNDI name fill in the previous configuration file '/' in front of the name, such as "mssql/password=test" here to fill "MSSQL"
Set the above two steps, click on the Test button, if the connection is OK, if you want to configure the connection pool, click on the list on the left of the above interface "pooling" item.
5: View Oracle's Listener.ora and Tnsnames.ora files. Ensure that host (IP) is consistent in Listener.ora and Tnsnames.ora.
It's still very slow.
6: From the landing report IO error, it may be connected to the database login, the database to write the listening log to the server. There may be a problem with the database server IO. Decide to set the listening log to off state to try.
1:LSNRCTL Login Monitor Operation interface
2:set Log_status off------------the ability to turn off the Write log (set log_status on-------------------turn on the ability to listen for write logs)
3:save_config------Save Configuration
4:exit
5:lsnrctl stop--Turn off monitoring
6:lsnrctl Start--Start monitoring
Test again, problem solved. Conclusion: There may be a problem with the database server IO. Or there is a problem with the disk.
Oracle database logon connection is slow; Kettle Connection Oracle Report IO error, socket time out problem resolution record