Problem: only the machine users connected to the black screen of access database, application and other connection tool cannot connect to the oracle, PLSQL snagged the user name password is not correct display connection fails, also can't connection has been no response; Black screen restart listen, slow to fail!
Problem: because the oracle server to monitor has never changed, suddenly can not access the database, therefore ruled out configuration errors, network connection is normal, also finally found to monitor log files to about 20 g, deleted after listening log files, all return to normal

Conclusion: first encountered this problem, since this problem is hidden and difficult to find the problem!

CodePudding user response:

Because listening log big? Not because listening log large file system where burst?

CodePudding user response:

If it is early Windows file's largest 4 G, after will not be able to connect,
Light delete useless, if you don't want to restart the monitor, can set log_status way switch, give you a script,
Clean up listening log

CodePudding user response:

reference 1st floor minsic78 response:

because listening log big? Not because listening log large file system where burst?

Specific haven't further processing, production environment, temporary treatment, further repair this month

CodePudding user response:

refer to the second floor oracle_awen response:

early Windows file if it is the largest 4 G, unable to connect to the then,
Light delete useless, if you don't want to restart the monitor, can set log_status way switch, give you a script,
Clean up listening log

This script is equivalent to replace operations manual deletion log

CodePudding user response:

Mark the

CodePudding user response:

references the flying fish, 4/f, 1993 response:

Quote: refer to the second floor oracle_awen response:

if it is early Windows file's largest 4 G, unable to connect to the then,
Light delete useless, if you don't want to restart the monitor, can set log_status way switch, give you a script,
Clean up listening log

This script is equivalent to replace operations manual deletion log on

Yes, this is the point of a DBA daily inspection,