[tmux] How to scroll in history

I thought, it would need magic but acutally it is as simple as

[ctrl][B] and then [PgUp]

[DbVis] Monitor file details lacks database connection section

Locate the correct meta data file (.met) in the Monitors of the settings directory. Locate the

exec.connection

line and set the databse id as found in the active

configXYZ/dbvis.xml

file. Possibly you also need to set a value for

exec.schema

.

[DbVis] DBMS_OUTPUT not working

• Make sure to switch on polling in the DBMS_OUTPUT tab of DbVis
• Make sure to switch on server output of Oracle

  begin
      DBMS_OUTPUT.ENABLE();
  end;
  /

[Debian/Skolelinux/Ubuntu in fact any systemd based distribution] Management of System services/daemons

As expample, PostgreSQL installation of version 11 with cluster main is being used. Replace postgresql@11-main accordingly. Many services might not have clusters or even parallel versions, e.g. the ssh daemon.

Start service

sudo systemctl start postgresql@11-main

Stop service

sudo systemctl stop postgresql@11-main

Reload configuration of service

sudo systemctl reload postgresql@11-main

Restart service

sudo systemctl restart postgresql@11-main

Query status

sudo systemctl status postgresql@11-main

Make services start at boot

sudo systemctl enable postgresql@11-main

Release services from starting at boot

sudo systemctl disable postgresql@11-main

View log

If the viewing user is not in the group adm or systemd-journal, one neeeds to sudo. See also https://linuxhandbook.com/journalctl-command/

journalctl -u postgresql@11-main.service # to see the log entries of the PostgreSQL 11 main cluster
journalctl --follow --unit=ssh.service # to keep tracing the log entries of the ssh daemon

[VMware view on Debian] Athentication works but starting into the actual session ends with getting closed its window

Further symptoms

Starting VMware view on the console reveals:

terminate called after throwing an instance of 'boost::filesystem::filesystem_error'
  what():  boost::filesystem::create_directories: Permission denied: "/tmp/user/vmware-thiemo"

Environment

Product: VMware Horizon Client
Version: 2111
Build: 8.4.0 (build-18957622)
Host-OS: Linux 5.10.0-10-amd64
Gtk+-Version: 3.24.24
Glib-Version: 2.66.8

(Temporal) solution (adapt to your actual user)

The linked directory already existed.

sudo ln -s /tmp/vmware-thiemo /tmp/user/vmware-thiemo

[TortoiseSVN] SSH public key access to repository

I only know this rather tedious variant to connect over ssh with public key authentication.

1.  Install TortoiseSVN and PuTTY.
2. Create a public key/private key pair in ppk format if you have not got one already; best with PuTTYgen. If you have an OpenSSH key pair, you can convert the key to ppk format with PuTTYgen also.
3. Place the public key onto the server. It depends on the server in which format. As I usually work with *nix servers, I have not got to use anything but OpenSSH format key so fer.
4. Create a connection in PuTTY for SSH using public key authentication. Please be aware that the connection name must NOT contain @ as this is a delimiter character for TortoiseSVN (and presumably other software too) separating a user name from the connection name or more general a server name.
5. This should be not needed but in doubt: Have Pageant (part of PuTTY) running with your key having been imported.
6. Call the TortoiseSVN commands from the file explorer context menu, example for "SVN checkout" and SourceForge:
1. The code page provides the following command line statement: svn checkout --username=thiemo svn+ssh://thiemo@svn.code.sf.net/p/pg-scd/svn/ pg-scd-svn
2. Change it to svn+ssh://thiemo_sf/p/pg-scd/svn/ for the URL of repository field of the dialogue.
3. thiemo_sf is the name of the PuTTY connection. If the user of the connection is not the same as one on the server (cannot think of a reason how this could happen, but there you go) prepend other_user_name@, where other_user_name is to be replace by the actual name like john.
   

[DB2 LUW] gathering statistcs

The runstat command is used to gather statistics on tables and indexes in DB2 LUW. However, it is no standard SQL command, not even an IBM extension. It is an IBM specific to be run on their CLI. However, one can still issue from any SQL client it encapsulated in the ADMIN_SYS procedure. For details, check the IBM documentation

Example

call sysproc.admin_cmd('runstats on table MY_SCHEMA.SOME_TABLE use profile');