The connections to Linux server got disconnected with message “timed out waiting for input: auto-logout”.
It is an unhappy thing when you are run some kind of long running scripts or database SQLs.
The issue is coming from the variable ‘TMOUT’ in Linux environment.
$ cat /etc/profile.d/autologout.sh export TMOUT=36000 $ grep TMOUT /etc/profile TMOUT=14400 $ echo $SHELL /bin/bash $ cat /etc/bashrc|grep TMOUT TMOUT=3600
If you want to disable timeout, then reset variable TMOUT=0
$ export TMOUT=0
For some reason, a client has to reinstall OEM central agents in a multi-OMS Oracle Enterprise Manager Cloud Control environment. Certainly the agent has been installed on the same server as the OMS.
First keep a record of the plugins deployed onto the agent already.
$emctl listplugins agent
Then uninstall the agent cleanly as per How to Deinstall OEM Agents in Oracle Enterprise Manager 13C
The next is to install the agent with required plugins deployed.
Now we need discover all WebLogic Domain targes based on the following instructions, and then all those targets will be monitored by the central agent.
Read more of this content when you subscribe today.
The following messages appear in alert.log:
...
..
.
2021-10-26 6:34:11.701 [CRSD(56455)]CRS-2878: Failed to restart resource 'ora.net1.network'
2021-10-26 6:34:11.705 [CRSD(56455)]CRS-2769: Unable to failover resource 'ora.net1.network'.
2021-10-26 6:34:11.807 [CRSD(56455)]CRS-2878: Failed to restart resource 'ora.net1.network'
2021-10-26 6:34:11.880 [CRSD(56455)]CRS-2769: Unable to failover resource 'ora.net1.network'.
...
..
.
In the mean time, there are other resources failure from scan listeners, VIPs and local listeners, etc.
Read more of this content when you subscribe today.
The following messages appear in CRS alert.log of ExaCC or Exadata:
2021-10-24 05:10:52.584 [CLSECHO(189590)]AFD-0654: AFD is not supported on Exadata systems 2021-10-24 11:10:53.734 [CLSECHO(288932)]AFD-0654: AFD is not supported on Exadata systems 2021-10-24 17:10:56.450 [CLSECHO(398661)]AFD-0654: AFD is not supported on Exadata systems 2021-10-24 23:10:55.077 [CLSECHO(92820)]AFD-0654: AFD is not supported on Exadata systems 2021-10-25 05:10:54.274 [CLSECHO(195018)]AFD-0654: AFD is not supported on Exadata systems 2021-10-25 11:10:53.935 [CLSECHO(268638)]AFD-0654: AFD is not supported on Exadata systems 2021-10-25 17:10:52.051 [CLSECHO(361889)]AFD-0654: AFD is not supported on Exadata systems 2021-10-25 23:10:52.858 [CLSECHO(37352)]AFD-0654: AFD is not supported on Exadata systems 2021-10-26 05:10:56.178 [CLSECHO(135982)]AFD-0654: AFD is not supported on Exadata systems
AFD protects from unauthorized processes over write to the asm claimed disks
in raw disk environment which is not applicable to exadata disks (non-oracle processes could not recognize / write to exadata disks).
so the message “FD-0654: AFD is not supported on Exadata systems” in alert.log can be ignored.
The following posts demonstrated how to check fragmentations in PostgreSQL:
How to Identify Fragmentation in PostgreSQL RDS
Code to Report Table Index Schema or Database Fragmentation in PostgreSQL
This post will show how to check table and index fragmentations in Oracle database.
Read more of this content when you subscribe today.
Make DBA Life Easy 