The current summary of the statement, in view of the data connection is very useful, after writing the program while testing the code side to see the release of database connections to help optimize the analysis of a robust system program.
1. SQL code
Select COUNT (*) from v$process
Select COUNT (*) from v$process--current number of database connections
2. SQL code
Select value from v$parameter where name = ' processes '
Select value from v$parameter where name = ' processes '--the maximum number of connections allowed for the database
3. SQL code
alter system SET processes = + scope = SPFile;
alter system SET processes = spfile;--Modify the maximum number of connections:
4. SQL code
1.shutdown immediate;
2.startup; Shutdown immediate; startup;--restarting the database
5. SQL code
SELECT Osuser, a.username,cpu_time/executions/1000000| | ' S ', B.sql_text,machine
From V$session A, V$sqlarea b
where a.sql_address =b.address order by cpu_time/executions Desc; SELECT Osuser, a.username,cpu_time/executions/1000000| | ' S ', b.sql_text,machine from V$session A, V$sqlarea b where a.sql_address =b.address order by cpu_time/executions Desc; --See which users are currently using the data
6. SQL code
Select COUNT (*) from v$session
Select COUNT (*) from V$session --current session connection number
7. SQL code
Select COUNT (*) from v$session where status= ' ACTIVE '
Select COUNT (*) from v$session where status= ' ACTIVE '--Number of concurrent connections
8. SQL code
Show parameter processes show parameter processes --Maximum connection
9. SQL code
alter system SET processes = value scope = SPFile;
Oracle views information such as the maximum number of connections allowed and the current number of connections