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.)

ORA-65011 Pluggable database ... does not exist

PROBLEM: ORA-65011 Pluggable database ... does not exist

If trying to start the DB service ...

OS> srvctl start service -s MY_DB_SERVICE -d MY_CDB_UNIQUE_NAME -pdb MY_PDB_SID

... you get the following error ORA-65011 ...

PRCD-1084 : Failed to start service MY_DB_SERVICE

PRCR-1079 : Failed to start resource ora. MY_CDB_UNIQUE_NAME.MY_DB_SERVICE.svc

ORA-65011: Pluggable database MY_CDB_UNIQUE_NAME does not exist.

CRS-5017: The resource action "ora. MY_CDB_UNIQUE_NAME.MY_DB_SERVICE.svc start" encountered the following error:

ORA-65011: Pluggable database MY_PDB_SD does not exist.

. For details refer to "(:CLSN00107:)" in "/u00/app/oracle/diag/crs/my_host/crs/trace/ohasd_oraagent_oracle.trc".

CRS-2674: Start of 'ora.CDB_UNIQUE_NAME.MY_DB_SERVICE.svc' on 'my_host' failed

(Since I has just created the DB using RMAN dupplicate and skipping some tablespaces, I though that my PDB (pluggable DB) had problems because of missing tablespaces.)

... but, as the error says, there is no PDB with the given name:

OS> oerr ORA 65011

65011, 00000, "Pluggable database %s does not exist."

// *Cause:  User attempted to specify a pluggable database

//          that does not exist.

// *Action: Check DBA_PDBS to see if it exists.

SOLUTION

Check how the service has been configured ...

I remarked that the name of my PDB (MY_PDB_SID)
was misspelled (MY_PDB_SD <= missing "I")

OS> srvctl config service -s MY_DB_SERVICE -db MY_CDB_UNIQUE_NAME

Service name: MY_DB_SERVICE

Cardinality: SINGLETON

Service role: PRIMARY

. . .

Runtime Load Balancing Goal: NONE

TAF policy specification: NONE

Edition:

Pluggable database name: MY_PDB_SD

Maximum lag time: ANY

SQL Translation Profile:

. . .

GSM Flags: 0

Service is enabled

... and re-create the DB service, using the correct PDB name

(So I re-created my MY_DB_SERVICE)

OS> srvctl remove service -s MY_DB_SERVICE -db MY_CDB_UNIQUE_NAME

OS> srvctl add service -service MY_DB_SERVICE -db MY_CDB_UNIQUE_NAME -pdb MY_PDB_SID -l primary/u00/app/oracle

Then it worked

OS> srvctl start service -s MY_DB_SERVICE -db MY_CDB_UNIQUE_NAME

OS> srvctl status service -s MY_DB_SERVICE -db MY_CDB_UNIQUE_NAME

Service MY_DB_SERVICE is running

Oracle Database: How To "Shrink" the UNDO Tablespace

-- Create "temporary" undo tablespace and make it the default undo tablespace

create undo tablespace UNDO_TMP datafile '+U01' size 2G AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED;

alter system set undo_tablespace=UNDO_TMP;

-- Drop the original undo tablespace

drop tablespace UNDOTS including contents and datafiles;

-- Recreate the old undo tablespace (smaler) and make it the default undo tablespace again

create undo tablespace UNDOTS datafile '+U01' size 2G AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED;

alter system set undo_tablespace=UNDOTS;

-- Drop the "temporary" undo tablespace

drop tablespace UNDO_TMP including contents and datafiles;

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.