Blackberry curve 8900 app error 523 and os 5.x

Introduction

Yes, yes, yes, me also. Put my device into the charger for bedtime and what? nope, no clock screen, instead found some (blue)white screen replacement having the following message being right centered:

app error 523 / reset

Great! The following is a log of what i tried and what really helped and a short contemplation what actually saved my day in terms of phone settings, contacts, calendar, installed software and all this. That is, reinstalling (flashing) a device is just one side of the medal, going productive with contacts, phone log, web bookmarks and so on is quite another. By the way, i do not run that device in an enterprise environment, all the device management is up to me.

Simulating and resolving a dataguard archivelog gap

I was wondering what will happen iff some archivelog gap really happens in a dataguard environment. How to resolve it? What has to be done manually and what happens automatically due to the remote file service (fal), for example.

Well, my attempt in producing the problem goes like this:

• verify normal operation by doing manual log switches on primary and watching the alert.log on primary and standby what happens
• defering the remote log destination (usually #2) on primary
• doing another manual log switches on primary that do now, don’t get shipped to standby
• backup primary with removing all backed up archive logs from the recovery destination
• bounce primary and standby
• activating the remote log destination (usually #2) on primary again, doing another manual log switches on primary, watching the alert.log on primary and standby what happens

Ok, let’s follow the alert.log on primary and standby …

Uncataloging a backupset from the rman repository

Ever seen this error message?

RMAN-06122: CHANGE .. UNCATALOG not supported for BACKUPSET

Seems you’re trying the get clean of backup sets that still exists on disk or tape but should no longer be regarded as a part of this database. What for? Well, this is quite a common requirement for rman-cloned or -duplicated databases where the rman repository (controlfile copy) originates from a seed database. Think of a standby database creation for example.