Blog

PGAdmin GUI Server Group Connections List Repository

A client opens PGAdmin GUI with the following messages:

{"success":0,"errormsg":"(sqlite3.OperationalError) no such table: user\n[SQL: SELECT anon_1.user_id AS anon_1_user_id, anon_1.user_email AS anon_1_user_email, anon_1.user_username AS anon_1_user_username, anon_1.user_password AS anon_1_user_password, anon_1.user_active AS anon_1_user_active, anon_1.user_confirmed_at AS anon_1_user_confirmed_at, anon_1.user_masterpass_check AS anon_1_user_masterpass_check, anon_1.user_auth_source AS anon_1_user_auth_source, role_1.id AS role_1_id, role_1.name AS role_1_name, role_1.description AS role_1_description \nFROM (SELECT user.id AS user_id, user.email AS user_email, user.username AS user_username, user.password AS user_password, user.active AS user_active, user.confirmed_at AS user_confirmed_at, user.masterpass_check AS user_masterpass_check, user.auth_source AS user_auth_source \nFROM user \nWHERE user.id = ?\n LIMIT ? OFFSET ?) AS anon_1 LEFT OUTER JOIN (roles_users AS roles_users_1 JOIN role AS role_1 ON role_1.id = roles_users_1.role_id) ON anon_1.user_id = roles_users_1.user_id]\n[parameters: ('1', 1, 0)]\n(Background on this error at: http://sqlalche.me/e/13/e3q8)","info":"","result":null,"data":null}

This message means the repository of PostgreSQL database connections details including credentials of Server Group is unavailable for PGAdmin.

The repository of PostgreSQL database connections details including credentials of Server Group is stored in SQLLite 3 format under “%UserProfile%\AppData\Roaming\pgAdmin\pgadmin4.db”.

It is strongly suggested to backup this file frequently if you have a long list of Server Group connections.

How to Resolve OEM Agent ‘Availability Evaluation Error’

The following commands helped a client to resolve OEM agent “Availability Evaluation Error”. Just run them in sequence until the issue is resolved.

$ ping omshost
$ nslookup omshost
$ emctl pingOMS
$ emctl config agent addinternaltargets
$ emctl secure agent
$ emctl config agent listtargets
$ emctl clearstate agent

$ emctl upload agent
$ emctl reload agent

The agent should show UP now, otherwise continues the following steps:

$ emctl stop agent
$ emctl secure agent
$ emctl clearstate agent
$ emctl secure agent
$ emctl start agent
$ emctl upload agent 
$ emctl reload agent

$ emctl pingOMS 
$ emctl status agent

timed out waiting for input: auto-logout

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

How to Reinstall and Configure OEM Cloud Control 13c Central Agent 

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.

Subscribe to get access

Read more of this content when you subscribe today.

CRS-2878: Failed to restart resource ‘ora.net1.network’ CRS-2769: Unable to failover resource ‘ora.net1.network’

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.

Subscribe to get access

Read more of this content when you subscribe today.