Re: Regarding abrupt exit during Updation ofworkspace

Question

On Fri, 12 Sep 1997 15:39:37 +0530, G. Ramesh Kumar Reddy wrote:
Hi,
Could any one diagonise the problem reported. A snapshot of the error
message displayed has been enclosed. I am unable to update my workspace. An
early reply to the effect is appreciated.
Thanx
ERROR: TMgr.RunThread: task wsmgr.display terminated -escaped exception:
FATAL ERROR: System segmentation/access violation caught.
Class: qqos_SystemException
Error #: [101, 321]
Detected at: qqos_MainExFilter at 1
Last TOOL statement: method wsmgr.compileAllUnconditionally
Error Time: Fri Sep 12 15:36:01
Exception occurred (locally) on partition "Forte_cl0_Client", (partitionId
= 9BF77B64-0A62-11D1-BD48-8BB2B251AA77:0x5d3:0x1, taskId =
[9BF77B64-0A62-11D1-BD48-8BB2B251AA77:0x5d3:0x1.8]) in application
"Forte_cl0", pid 176 on node GRKR in environment centrale.I've seen this problem happen before, once when attempting to update a
workspace and several times when trying to force a compile of all
projects in the workspace (selecting "Utilities / Force Compile / All
Projects" from the menus). I don't know what causes it, but what has
always worked for me is to select each user project one at a time and
force a compile on that project alone ("Utilities / Force Compile /
Selected Project"). Once you've done this on all your projects, the
update workspace or the forced compile of all projects should be OK
again.
Hope this helps.
Dale V. Georg
Indus Consultancy Services
[email protected]
Dale V. Georg
Indus Consultancy Services
[email protected]

Answer 1

Hi user781131,
What happens if I invoke the script, the backup session starts and then there is abrupt termination of the RMAN session either because of losing the db
connection or receiving an interrupt signal or a kill signal or some other weird reason?The backup set which rman was creating is not commited due to the abnormal termination but all succesfull backup sets can be used.
What if I re-invoke my script? Will it start from the point where it was stopped earlier or would it start from the point where we had last successful Level 1 backup
completed?In your backup script you do not use the < NOT BACKED UP SINCE TIME > clause so it will again do a level 1 backup off all datafiles.
See:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1017236
This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up. If AS BACKUPSET is set, then this feature is only useful if RMAN generates multiple backup sets during the backup.
Regards,
Tycho
Edited by: tychos on 28-jan-2010 15:21