Hp Pavilion X2 Detachable: Touch Screen And Audio Not Working Any More

Problem

The touch screen and audio of the Hp Pavilion X2 Detachable PC 10 stopped working after Windows 10 update.

Touch Screen Problem

Solution

Go to
https://support.hp.com/us-en/drivers/selfservice/hp-pavilion-10-k000-x2-detachable-pc/7439381/model/7588503?sku=K8L57EA

Download the "Intel Chipset, Graphics, Camera and Audio Driver Pack" as depicted

This driver solved my touch screen issue and the error symbol disappeared from the speaker symbol, but the sound still does not work.

Audio Problem

Go to the same site as before:
https://support.hp.com/us-en/drivers/selfservice/hp-pavilion-10-k000-x2-detachable-pc/7439381/model/7588503?sku=K8L57EA

Download the "Realtek High-Definition (HD) Audio Driver" as depicted

I hope this helps

Mobile Phone No Longer Charges - How To Solve This Problem

English

Suddenly the smartphone no longer charges completely. What to do?

There are many pages that describe possible solutions.
So I won't repeat them.
Here is a description of one of the solutions that is nearly impossible to find.
This one helped me at the end.

If the mobile phone is charging, but only up to a certain level, then this solution could help.

Cause

This behavior indicates that the chip that measures the charge level can no longer correctly determine the "values for empty and full".

Solution

• Discharge the phone completely until it shuts down itself
• Switch on two / three times (without charging), so the device shuts down itself
• Finally charge it FULLY (up to 100%)

Voilà, the problem should be solved by now.

---

Deutsch

Plötzlich lädt das Smartphone nicht mehr vollständig auf. Was tun?

Es gibt viele Seiten, die mögliche Lösungen beschreiben.
Somit werde ich diese Lösungen nicht wiederholen.
Hier wird eine der Lösungen beschrieben, die fast nicht zu finden ist.
Diese hat mir schlussendlich geholfen.

Wenn das Mobile-Phone lädt, aber nur bis zu einem bestimmten Niveau, dann könnte diese Lösung helfen.

Ursache

Dieses Verhalten deutet darauf hin, dass der Chip, der den Ladestand misst, die "Werte für leer und voll" nicht mehr korrekt ermitteln kann.

Lösung

• Das Handy vollständig entladen, bis es sich selbst abschalltet
• Zwei- bis dreimal einschalten (ohne Aufladen), so dass sich das Gerät selbst ausschaltet
• Schlussendlich es VOLLSTÄNDIG (bis 100%) aufladen

Voilà, das Problem sollte jetzt gelöst sein.


Picture by Alexander Andrews
Downloaded from: https://unsplash.com/s/photos/battery

How To Correct Logcat Missing Filter In Android Studio

Before trying to restart the Android Studio in order to make the logcat filter fields re-appear (this did not worked for me the last time), simply try first to change the window size to “Restore Down” and back to “Maximize” or the other way around. (This worked for me on Windows 10).

Here is what I mean:

"Restore Down"

"Maximize"

I hope this helps.

Oracle Data Pump Errors: ORA-31626 and ORA-06512 and ORA-31637 and ORA-31632 and ORA-01422

Problem

While implementing a Data Pump Export script, I started getting the following error stack:

Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

ORA-31626: job does not exist

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79

ORA-06512: at "SYS.KUPV$FT", line 1183

ORA-31637: cannot create job CSEXPDP_01 for user SYS

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95

ORA-06512: at "SYS.KUPV$FT", line 1176

ORA-31632: master table "SYS.CSEXPDP_01" not found, invalid, or inaccessible

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95

ORA-06512: at "SYS.KUPV$FT", line 1167

ORA-01422: exact fetch returns more than requested number of rows

ORA-06512: at "SYS.KUPV$FT_INT", line 2566

ORA-06512: at "SYS.KUPV$FT_INT", line 2556

ORA-06512: at "SYS.KUPV$FT", line 1092

Cause & Solution

In my case the error was caused, because my script used the same name for the Database Directory and the Data Pump Job.

For example:

It created a DB-Directory like this . . .

CREATE OR REPLACE DIRECTORY tmp_auto_dp_01 AS '...';

. . . and specified a DataPump job name like this:

JOB_NAME=tmp_auto_dp_01

DIRECTORY=tmp_auto_dp_01

SCHEMAS=...

DUMPFILE=...

LOGFILE=...

I hope it helps someone

KeePassDroid Fingerprint Sensor Issue

If KeePassDroid shows a message, that there is a problem with the fingerprint sensor:

1. Go to the Android App Sessings => Apps => KeePassDroid => Data 
1. => empty the cache
2. If this doesn't help.
   Make a backup of your KeePass data file
   and do the same as on 1. and delete all the data (instead of a.).

I could solve this problem on my Samsung Galaxy S9 already one month ago and only could take my time now to write this down. That's why I do not remember exactly which method I used.

If this helped you, please give me a feedback, so that I can update this blog entry.

(I know, this is a trivial hint and it is almost embarrassing to admit, but it took me a some time to get the this idea.)

Oracle Enterprise Manager / Cloud Control: Historical Data Not Showing Issue

Problem Description

Last week after one of Oracle Database hosts had to be rebooted because of memory problem. I had the issue with Oracle Enterprise Manager / Cloud Control that historical data of this DB (only for this DB) was not showing any more:

• In "Performance" => "Performance Home" => "View Data: Historical"
  Error Message
  Data Not Available. Statspack data is not available for this database instance. Make sure that Statspack is installed on the target instance.

• In "Performance" => "Top Activity"  => "View Data: Historical"
  Error Message
  (No Data Available)

• In: "Performance"  => "ASH Analytics" in "Top Activity"
  Error
  No useful data was showing

Possible Solution

Completely logout of Enterprise Manager (not only from the DB) and logon back.

ASM: Queries Hanging (v$asm_disk)

Solved Problem When ASM Queries on v$asm_disk Hang / Block 

Wenn trying to display ASM information, Oracle Cloud Control (Enterprise Manager) displays nothing.

Also when trying to perform some queries on ASM, they "hang" and no answer is returned.

(For example: SELECT * FROM v$asm_disk; hangs)

Commands with the ASM tool asmcmdh still work:

oracle@<Host>:~/ [+ASM] asmcmdh

ASMCMD> lsdsk -p

Group_Num  Disk_Num      Incarn  Mount_Stat  Header_Stat  Mode_Stat  State   Path

        1         0  2526484498  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/grid

        2         6  2526484516  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u01_07

        2         7  2526484517  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u01_08

        2         8  2526484518  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u01_09

        2         9  2526484519  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u01_10

        3         0  2526484503  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u02_01

        3         1  2526484505  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u02_02

        3         2  2526484504  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u02_03

        3         3  2526484507  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u02_04

        3         4  2526484506  CACHED      MEMBER       ONLINE     NORMAL  /dev/ASM/u02_05

The Metalink Doc ID 8786114.8 suggests to verify / correct the ASM discovery string in order to exclude "invalid devices"

like /dev/kmem or other devices that should not be scanned by the ASM disk discovery.

For example it suggests not to use /dev/* as an ASM disk discovery string.

Querying the DB for the ASM disk discovery string, returns:

SQL> show parameter asm_diskstring
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
asm_diskstring                       string      /dev/ASM

Listing the mount points using the result from above, shows that still some mount points exits (highlighted)

that are not valid any more. (i.e. no storage is mounted on these mount points any more)

(These are not listed be the asmcmdh command from above.)

(This is not directly apparent from the result below. But I knew, that nothing was mounted at these mount points any more.)

oracle@<Host>:~/ [+ASM] ll /dev/ASM*

total 0
drwxr-xr-x  2 root root  360 Jan 24 10:29 .
drwxr-xr-x 12 root root 3660 Mar 26 15:47 ..
lrwxrwxrwx  1 root root    7 Apr 18  2013 grid -> ../xvdf
lrwxrwxrwx  1 root root    7 Apr 18  2013 u01_01 -> ../xvdb
lrwxrwxrwx  1 root root    7 Apr 18  2013 u01_02 -> ../xvdc
lrwxrwxrwx  1 root root    7 Apr 18  2013 u01_03 -> ../xvdd
lrwxrwxrwx  1 root root    7 Apr 18  2013 u01_04 -> ../xvde
lrwxrwxrwx  1 root root    7 Oct  4  2013 u01_05 -> ../xvdllrwxrwxrwx  1 root root    7 Oct  4  2013 u01_06 -> ../xvdm
lrwxrwxrwx  1 root root    7 Jan 24 10:29 u01_07 -> ../xvdn
lrwxrwxrwx  1 root root    7 Jan 24 10:29 u01_08 -> ../xvdo
lrwxrwxrwx  1 root root    7 Jan 24 10:29 u01_09 -> ../xvdp
lrwxrwxrwx  1 root root    7 Jan 24 10:29 u01_10 -> ../xvdq
lrwxrwxrwx  1 root root    7 Apr 18  2013 u02_01 -> ../xvdg
lrwxrwxrwx  1 root root    7 Apr 18  2013 u02_02 -> ../xvdh
lrwxrwxrwx  1 root root    7 Apr 18  2013 u02_03 -> ../xvdi
lrwxrwxrwx  1 root root    7 Apr 18  2013 u02_04 -> ../xvdj
lrwxrwxrwx  1 root root    7 Apr 18  2013 u02_05 -> ../xvdk

Problem Cause

As described in the Metalink-Article from above, the SQL statement and Cloud Control hang,

because the statement tried to query inexistent LUNs with a very long timeout.

Solution

In my case, the solution was to remove the old (invalid) mount points.

I did not need to change the ASM disk discovery string.

Tags: Oracle, ASM, Problems&Solutions, LUN, Hang, blockiert, Publish
May 06, 2014 at 09:21AM

Kubuntu 14.04 black screen after monitor off/on

Whenever I turned my display off and on again after having logged on,  the screen stayed black. After rebooting, the logon screen appeared, but after logon with my user account, the screen got black. Logging with other user accounts had no problem.

This problem occurred using Kubuntu 14.04.  and a Nvidia graphics card connected by a display port cable.

Here is the description how I corrected it. In short Change the first false value of your screen definition file  .kde/share/apps/kscreen/xxxxxxxxxxxxxx from false to true. Than make this file read only. In Detail Start one of the consoles: Ctrl-Alt-F1 Then enter your OS-User name and password. Go to the directory .kde/share/apps/kscreen located in your home directory: cd ~/.kde/share/apps/kscreen Listing the files in this directory (ls -1), should display at least one file, that looks like the one bellow. The files name is a mix of number an letters (seems a long hexadecimal number): ls -1 7134be4579e47853d9bc866485e252fb If you have/had more than one monitors, several files will be listed. This is a text file. Its contents can be displayed with the command cat : cat 7134be4579e47853d9bc866485e252fb [ { "enabled" : false, "id" : "9a9b7a71150d853203babd861f68d8c5", "metadata" : { "fullname" : "xrandr-Dell Inc.-DELL U2515H-9X2VY61E10XL", "name" : "DP-1" }, "mode" : { "refresh" : 59.9506, "size" : { "height" : 1440, "width" : 2560 } }, "pos" : { "x" : 0, "y" : 0 }, "primary" : true, "rotation" : 1 } ] Change the false value after "enabled" (from above) to true. Here I show how to do it using the vi editor, that is available on every Linux system. vi 7134be4579e47853d9bc866485e252fb Go to the beginning of false by using the arrow keys press the key [DEL] until false is completely deleted press the key [i] in order to enter the insert mode (-- INSERT -- will then by displayed at the bottom line) type true press the key [ESC] in order to leave the insert mode (-- INSERT -- disappear from the bottom line) press the keys [:] and [x] (":" starts the command mode and "x" is the command "exit with saving") If you display the contents of your file again, the false should now have been replaced by true Now the Graphical environment can be restarted by entering the command startx. startx

I could avoid that this problem occurs again I made this file read only chmod ugo-w 7134be4579e47853d9bc866485e252fb I hope this helps.

Tags: Problems&Solutions, Kubuntu, Publish, Monitor, Black Screen
August 28, 2016 at 08:52AM

Registering an Oracle DB into the RMAN Catalog

PROBLEM

If the Database ID changed (I described this in a previous post) and the RMAN catalog is used, RMAN will output the following error stack:

RMAN-03002: failure of backup command at 07/05/2016 03:56:13
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database:
RMAN-20001: target database not found in recovery catalog



As the last error line says, the database can not be found in the RMAN catalog, because the DB ID is used in order to identify the catalog records belonging your DB.

SOLUTION

Logon as oracle on your DB host.
Logon with RMAN to your DB and your RMAN catalog (here TNS-Alias RMANCAT):

OS> rman target / catalog /@RMANCAT


Then register your DB into the RMAN catalog:

RMAN> REGISTER DATABASE;

PROBLEM 

If you are trying to register a standby DB and get this error:

RMAN> REGISTER DATABASE;
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog


SOLUTION

First: make sure, that the primary DB is already registered in the RMAN catalog.

Then logon with the standby DB on the RMAN catalog and execute the following statement:

RUN {
  ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
  CROSSCHECK BACKUP;
}