Database is hang during shutdown abort (Urgent Production Issue)

Hi Gurus
In my production system while shutdown immediate , database was hang.
When we logged in system and gave shutdown abort its again hang.
Pls suggest me what could be the reason and how it can be solved
Thanks

Tue Oct 21 05:01:09 2008
Shutting down instance: further logons disabled
Tue Oct 21 05:45:19 2008
ksvcreate: Process(q005) creation failed
Tue Oct 21 05:45:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:45:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:45:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:49:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:49:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:49:24 2008
Shutting down instance (abort)
License high water mark = 26
Termination issued to instance processes. Waiting for the processes to exit
Tue Oct 21 05:49:35 2008
Instance termination failed to kill one or more processes
Tue Oct 21 06:06:43 2008
Instance terminated by USER, pid = 20613

Similar Messages

System hangs during shutdown, blue screen with gear spinning.

My MBP gets stuck during shutdown/restart process.
The system acts like it is shutting down, exits the the desktop, goes to a blue screen with a spining gear then never turns off. It seems the screen falls aslep if you leave it awhile but the system itself won't actually shutdown. If you move the mouse the screen lights back up. but still shos the "death gear"! happens on both shutdowns or restarts. System must be turned off by holding the power switch for 10 secs.
Please help!
Chris

Seems like a odd thing. If youve downloaded torrents of hacked programs or things like that may have been the cause by the uploader hacking and doinng this. I would bring the Macbook Pro to the apple store and see what they can do. If they cant do anything about it I would backup all the important programs and get rid of anything that seems suspicious. Then upload the stuff back onto the computer after you restore it. Thats the best solution.

Os x lion hangs during shutdown

System hangs showing white screen with status wheel. I have to power cycle the box to get it going again. I just upgraded to Lion before this occured.

I had the same rpoblem since installing 10.7 - and 10.7.1 fixed nothing.
i rang Applecare but the guy seemed unconcerned (i had other more pressing Wifi Problems he did solve by getting rid of my Airport network and building a new one)..
So I deliberately quit all apps and shutdown hard, then examined the console on restart (I had previously repaired permissions, zapped the PRAM and reset the SMC anyway for the Wifi issue....so it should have been a clean system.
Lo and behold, I found a reference in the console log to an SD card I had left plugged into my iMac.
So I ejected the SD card, and did a restart to test...and Hey presto- it worked like magic!
I hoep this helps you guys.
Now for the remaining mystery - rearranged desktop icons on startup...i.e. some but not all, and not always....Apple should be doing this debugging not me!

!!!Very Urgent-Production Issue -Please help

Hello IDMers,
We are facing an issue in production, we updated the AD Process form yesterday. Two fields- Employee Type and Employee ID field in AD User Process form got refreshed for all existing users. Those two fields are empty now for all users.
But these fields have appropriate value in the Xellerate User Table for all users. Now I need to some how populate the Employee Type and Employee ID field for all employees from User Table to AD Process form.
for example: Consider an Employee called Peter- His emp type is Full Time and Emp ID is 100; which i have it in OIM User Table, but this user is provisioned with AD and now i will have to update his AD Process form so that these two fields are populated. I need to do this for all users in OIM. I guess the prepop adapter triggers only when the form is created for the first time. Please suggest me some ideas.
Is there a easy way to do this task?
What my thinking is, I need to have a scheduled task that basically loops through all users and updates their employee type and id field in AD User Form from Xellerate User Table.
Please help me with this as it is highly important.
Thanks again every one for your support all the while.
Regards,
~VSN

hey,
i was doing lots of migration from one OIM box to another during our last release. I guess something would have gone wrong while doing an import/export from one OIM system to another.
What I learned was while doing an import the vulnerable object is AD USER (or any resource of OIM) Object (both Process form and process definition), because those are the two objects which you need to import fully no matter how big a change you have done.
So when you do an import watch out for USER DEFINED FIELDS in the process form because for me the two fields which disappeared were user defined/custom created by me. So make sure you export the latest version;even if you didnt make any changes to them better create a new version copy of the form and then export it.
Hope that helps.
~VSN

IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

Dear Folks,
Here we are implementing MIRROR sytem for data extraction in to BIW.
I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
These are following steps I had performed in BW production
1. Using RSADMIN transcation- Assigned one user as a Debugging user.
2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
 In data selection tab, I given date as from 2002 to 2003
 In Update tab, I selected update mode as Initialize Delta process- without data transfer and Uncheck Update Data in master system immediately
 In schedule tab I selected option Start Data load immediately then Start extraction.
3.Data was requested and It was intialized properly with green status 1 from 1 Records.
4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option IDOC list in Source sytem, here also it is not showing any IDOCs.
Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
Points is Assured for all replies.

Hi,
- check you RFC destination (normal test + authorization test)
- Check you partner profiles in WE20 and its ports WE21
- from the source system tree (RSA13) right click your source system and perform a check
- the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
hope this helps,
Olivier.

Database get hang please help to resolved the issue.

Hi,
we are getting below error at that time db not allowed user to connect database.please help to resolved the issue.
db version is 10.2.0.3
Errors in file /oracle/oradata/bdump/pmspr_j002_1593486.trc:
ORA-12012: error on auto execute of job 42597
ORA-27468: "EXFSYS.RLM$SCHDNEGACTION" is locked by another process
Tue Jan 3 10:21:55 2012
Errors in file /oracle/oradata/bdump/pmspr_j003_1347686.trc:
ORA-12012: error on auto execute of job 42596
ORA-27468: "EXFSYS.RLM$EVTCLEANUP" is locked by another process
Tue Jan 3 10:21:55 2012
Errors in file /oracle/oradata/bdump/pmspr_j004_1995004.trc:
ORA-12012: error on auto execute of job 42596
ORA-27468: "EXFSYS.RLM$EVTCLEANUP" is locked by another process
Tue Jan 3 10:21:55 2012
Process OS id : 2064550 alive after kill
Errors in file /oracle/oradata/udump/pmspr_ora_1572972.trc
Tue Jan 3 10:21:55 2012
Errors in file /oracle/oradata/bdump/pmspr_j005_1617988.trc:
ORA-12012: error on auto execute of job 42597
ORA-27468: "EXFSYS.RLM$SCHDNEGACTION" is locked by another process
Tue Jan 3 10:21:55 2012
Errors in file /oracle/oradata/bdump/pmspr_j007_1523820.trc:
ORA-12012: error on auto execute of job 42596
ORA-27468: "EXFSYS.RLM$EVTCLEANUP" is locked by another process
Tue Jan 3 10:21:55 2012
Errors in file /oracle/oradata/bdump/pmspr_j009_1933354.trc:
ORA-12012: error on auto execute of job 42596
ORA-27468: "EXFSYS.RLM$EVTCLEANUP" is locked by another process
Tue Jan 3 10:21:55 2012
Errors in file /oracle/oradata/bdump/pmspr_j006_1536044.trc:
ORA-12012: error on auto execute of job 42597
ORA-27468: "EXFSYS.RLM$SCHDNEGACTION" is locked by another process
Thanks

I think the following Oracle two note looks interesting:
Note: 330725.1 Scheduler Job has Been Locked For Days Ora-27468
Note: 731678.1 Scheduled jobs do not run as expected after 10.2 upgrades
HTH -- Mark D Powell --

URGENT Production issue BPEL P.M. 10.1.3.1Failed to load callback message

Hi,
Any one come accross this. I have onMessage call. In my production system for same bpel process I have 4 task instance. Out of 4 it worked for 2 and for 2 I got following error in domain.log file. I have serial approver human workflow.
I will appreciate if any one have any clue to resolve this. Or any one came accross this.
Regards,
Jigar
<default.collaxa.cube.engine.delivery> <DeliveryService::resolveCallback> Failed to load callback message, msgGuid=1198126fd96a20de:-2bd93846:116466e5c21:-7a93 ... may have been consumed by subscriber

Hi ,
I am getting following error only in production. I have same process running in development and test. Both in development and test I am not getting this error.
error
DeliveryLogger.debug("DeliveryService", "resolveCallback", "Failed to load callback message, msgGuid=", messageGUID, " ... may have been consumed by subscriber");
CallbackInfo result = (CallbackInfo)mCache.get(messageGUID); line of code is the issue. Can any one tell me what is going on here.
Regards,
Jigar
public IMessage resolveCallback(String conversationId, String messageGUID, int conversationType, DomainAuth auth)
throws ServerException
Exception exception;
ICubeContext ctx = null;
com.collaxa.cube.engine.dispatch.message.BatchMessage batchmessage;
try
ctx = createContext(auth);
IDeliveryService ds = getDeliveryService(ctx);
startDeliveryRequest(ctx);
ds.resolveCallback(conversationType, conversationId, messageGUID, ctx);
endDeliveryRequest(ctx);
batchmessage = DispatchHelper.getMessage(ctx);
catch(ServerException se)
logError(se);
setTransactionRollback();
throw checkIfFatalConnectionError(se, ctx);
finally
destroyContext(ctx);
destroyContext(ctx);
return batchmessage;
throw exception;
public void resolveCallback(int conversationType, String conversationId, String messageGUID, ICubeContext ctx)
throws CubeException
StopWatch sw = CubeContextHelper.getStopWatch(ctx);
sw.start("ds-resolve-callback");
DeliveryLogger.debug("DeliveryService", "resolveCallback", "Resolving subscribers for convId ", conversationId, ", msgGuid=", messageGUID);
CallbackInfo info = DeliveryPersistenceMgr.loadCallback(messageGUID, ctx);
if(info == null)
DeliveryLogger.debug("DeliveryService", "resolveCallback", "Failed to load callback message, msgGuid=", messageGUID, " ... may have been consumed by subscriber");
sw.stop("ds-resolve-callback");
return;
IProtocolHandler handler = getProtocolHandler(info.getConversationType());
SubscriptionInfo sis[] = handler.resolveCallback(info, ctx);
if(sis != null && sis.length > 0)
int i = 0;
for(int n = sis.length; i < n; i++)
SubscriptionInfo si = sis;
String subscriberId = si.getSubscriberId();
if(!si.isRecurrent())
si.markAsResolved();
CorrelationId cId = new CorrelationId(subscriberId);
com.oracle.bpel.client.auth.DomainAuth auth = CubeContextHelper.getDomainAuth(ctx);
CallbackDeliveryMessage cm = new CallbackDeliveryMessage(si.getProcessGUID(), si.getProcessId().getProcessId(), si.getProcessId().getRevisionTag(), info.getMessageGUID(), info.getConversationId(), si.getSubscriberId(), new WorkItemKey(cId.getKey()), auth);
cm.setConversationType(info.getConversationType());
DispatchHelper.addMessage(cm, ctx);
DeliveryLogger.debug("DeliveryService", "resolveCallback", "Resolved subscriber ", subscriberId, " for message ", info.getMessageGUID(), " for conversation ", conversationId);
if(!info.isRecurrent())
info.markAsResolved();
info.setResolvedProcessGUID(sis[sis.length - 1].getProcessGUID());
info.setResolvedSubscriberId(sis[sis.length - 1].getSubscriberId());
DeliveryPersistenceMgr.update(info, ctx);
DeliveryPersistenceMgr.updateBatchState(sis, ctx);
} else
DeliveryLogger.debug("DeliveryService", "resolveCallback", "No subscribers found for message ", info.getMessageGUID(), " for conversation ", conversationId);
sw.stop("ds-resolve-callback");
public static CallbackInfo loadCallback(String messageGUID, ICubeContext ctx)
throws CubeException
return PersistenceAdaptorRegistry.getDeliveryAdaptor(ctx).loadCallback(messageGUID, ctx);
public static IDeliveryPersistenceAdaptor getDeliveryAdaptor(ICubeContext ctx)
throws CubeException
return getPersistenceAdaptorRegistry(ctx).m_dlPA;
public CallbackInfo loadCallback(String messageGUID, ICubeContext ctx)
throws CubeException
CallbackCache cache = (CallbackCache)ctx.lookup("__callback-cache");
CallbackInfo info = cache.get(messageGUID, ctx);
if(info != null && info.getPayload().size() > 0)
return info;
StopWatch sw = CubeContextHelper.getStopWatch(ctx);
sw.start("callback-load");
if(info == null)
info = __loadCallback(messageGUID, ctx);
sw.stop("callback-load");
return info;
public final CallbackInfo get(String messageGUID, ICubeContext ctx)
CallbackInfo result = (CallbackInfo)mCache.get(messageGUID);
if(result == null)
nMisses++;
} else
nHits++;
return result;
public synchronized Map getStatistics()
Map map = new HashMap();
map.put("name", "callback");
map.put("policy", "map");
map.put("count", String.valueOf(getSize()));
map.put("size", String.valueOf(getSize()));
map.put("hwm", "N/A");
map.put("lwm", "N/A");
map.put("units", "");
map.put("puts", String.valueOf(nPuts));
map.put("hits", String.valueOf(nHits));
map.put("misses", String.valueOf(nMisses));
return map;

Hang during VI loading - possible version issue

I've got a VI with many sub-VIs that when I try to open it the Loading dialog box eventually gets stuck in a loop where it goes back and forth between loading 2 different VI's.
This VI was written in an older version of LabVIEW, I think 7.1. I'm trying to open it in 8.5. I don't have the 7.1 disks anymore.
When I try to open the VI, the dialog box pops up that says: "Loading: <filename>.vi" and it goes through several files before getting stuck as described above. It'll hang forever so I never get any error message. I tried mass compiling but that eventually hangs as well. I attached the log from the mass compile. It doesn't always get stuck on the same VI so I haven't been able to narrow it down to a particular file or files.
I copied and pasted all the files from a different computer and the same VI works on there (with Labview 7.1). Any suggestions about how I could fix the problem would be helpful.
-Scott
Attachments:
log2.txt ‏24 KB

Hi Scott,
Can you perhaps provide some screenshots of what you see when trying to load that VI?
Also, are you able to load a single VI instead of your application? That would be a good way to conclude that the problem exists within your application. Perhaps you can create a very simple VI in 7.1 and try loading it 8.5 and see if you experience the same thing. You can also try loading some of your SubVI's separately and see if some of them can load but others cannot.
Did you change the location of some of these VIs?
Tejinder Gill
National Instruments
Applications Engineer
Visit ni.com/gettingstarted for step-by-step help in setting up your system.

Urgent production issue

Hi sap gurus,
In sale order delivery date is 25/3/2008, but when i check the schedule line the system is giving 4.4. 2008 as default.
stock is displaying as 0 on 25/3/2008 in availablity check at item level ,system confirms stock only at 4/4/2008.
but stock is there on the particular date .
i can save the order and delivery.
but when i do pgi ,it is displaying error as deficit of stock.
kindly suggest me the solution.

Dear divya nair
As you said though stock is available on 25/03/08, you will not be able to post the goods issue, bcoz delivery for some other order has been created and saved without doing PGI. You can check in MD04 where the delivery reference will flow else, check in MMBE where there is a tab "schedule for delivery". Either you can cancel that delivery or wait till 4/4/08.
thanks
G. Lakshmipathi

**URGENT** - PRODUCTION ISSUE with Planning Layout

Hi,
we've a manual planning layout that uses both macros SAPAFTERDATAPUT and SAPBEFOREDATAGET with custom code developed in these 2 macros to switch data between "SEM-BPS 1" and "New" sheet.
Layout has 11 characteristics in lead columns and around 40 keyfigures in data columns (dynamic).
Using macros, we are formatting SEM-BPS 1 sheet to display all dynamic data coumns in a single page of New sheet.
for this, our custom macro formats each row of SEM-BPS1 into 10 rows of New sheet by reducing 40 columns into 4 (columns is what matters for our users but not rows).
We tried this for 40 rows of data. (means, 40 rows 40 columns). Our Custom macro formed 400 rows and 4 columns into New Sheet and even switched data between "SEM-BPS 1" and "New" sheet as per our macro coding. here, we can execute all planning functions. fine till this point
Now, we have a problem when dealing with 100 rows. (means, 100 rows 40 columns). Our custom macro had formed 1000 rows and 4 columns as expected with accurare data. 
at this point, When we started running any planning function or even when we just click on check button (check button runs both SAP macros, I assume), system is freezing up doing nothing. each time, we had to kill the process. when we looked into CPU usage, we can see that excel.exe process is using 99% of CPU.
Appreciate if any one can share experinces on this.
Note: 
1. By disabling custom macros, we executed 100 rows 40 columns w/o any issues.
2. when executed custom macros outside of SAP for 1000 rows 4 columns, both macros took just 2 seconds to switch data between sheets.

Hi there
This is the option Jeff was referring to. I see it in my own RoboHelp version 10. As we aren't seeing it in your screen capture, I'm wondering if this was an option that was added via a service release you haven't installed.
I do suppose another possibility would be that you are using RoboHelp for Word and perhaps that isn't an option with that application.
Cheers... Rick

If shutdown immediate hangs database waits one hour for shutdown abort

we have schedules cold backup for our 11g database on redhat 5.3.
there is a shell script written with shutdown immediate command.
If database hangs during shutdown immediate database waits one hour for auto shutdown abort.
but this happens once or twice in a month
can we do this auto shutdown abort earlier than one hour ??

user13376823 wrote:
we have schedules cold backup for our 11g database on redhat 5.3.
Since you're shutting down the database for cold backup so ensure it should be shutdown properly by shutdown or shutdown immediate cmd not by abort cmd.
Consistent backup:-
A backup taken when the database is mounted (but not open) after a normal shutdown. The checkpoint SCNs in the datafile headers match the header information in the control file. None of the datafiles has changes beyond its checkpoint. Consistent backups can be restored without recovery.
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1007616

Urgent- production order error- ERTR status

Dear PP Gurus
i have an urgent production issue, we have full fledged WM implemented and production order components are issued automatically when order is released via a Pick list
Now the problem is that the BOM components are NOt correctly staged during picking
after the order is released , the status shows ERTR- Error in transfer requirements, so how should i solve this error
i have created production supply areas and maintained supply areas in MRP=2 views, i have also created Control Cycles for all the materials
please help and appreciate your valuable expertise on how to solve this urgent issue
thanks in advance
regards
Chakri

Hi Chakri
Check production schedulign profile, Did you maintain WM in that
also check in Control cycle ,staging ind. shd be "1"
Cheers
bala

Loss of all controlfile,database is automatic shutdown abort?

Your database is configured in NOARCHIVELOG mode. All the control files have been lost due to a hard disk failure but the data files are not lost. You have the closed whole database backup available to you. Which two statements are true in this scenario? (Choose two.)
A) The instance aborts.
B) The database cannot be recovered.
C) The database can be recovered by restoring the control files from the backup.
D) The database remains opened and you have to shut it down with the ABORT option.
E) The database can be restored till the point of the last closed whole database backup.
noarchivelog mode , before open database i had rman backup full database;
idle> conn / as sysdba
Connected.
idle> alter database open;
Database altered.
idle> conn anbob/anbob
Connected.
anbob@ANBOB> create table testdelctl(id int);
Table created.
anbob@ANBOB> insert into testdelctl values(999);
1 row created.
anbob@ANBOB> commit;
Commit complete.
anbob@ANBOB> conn system/oracle
Connected.
system@ANBOB> select * from v$controlfile;
STATUS
NAME
IS_ BLOCK_SIZE FILE_SIZE_BLKS
/oracle/oradata/anbob/control01.ctl
NO 16384 430
/oracle/oradata/anbob/control02.ctl
NO 16384 430
/oracle/oradata/anbob/control03.ctl
NO 16384 430
system@ANBOB> !rm /oracle/oradata/anbob/control*.ctl
system@ANBOB> !ls /oracle/oradata/anbob/
redo01.log redo03.log system01.dbf undotbs01.dbf users01.dbf
redo02.log sysaux01.dbf temp01.dbf undotbs2.dbf
system@ANBOB> select open_mode from v$database;
select open_mode from v$database
ERROR at line 1:
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/oracle/oradata/anbob/control01.ctl'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3
system@ANBOB> select status from v$instance;
STATUS
OPEN
sys@ANBOB> conn anbob/anbob
Connected.
anbob@ANBOB> select * from testdelctl;
ID
999
anbob@ANBOB> insert into testdelctl values(0);
1 row created.
anbob@ANBOB> commit;
Commit complete.
anbob@ANBOB> conn / as sysdba
Connected.
sys@ANBOB> alter systme checkpoint;
alter systme checkpoint
ERROR at line 1:
ORA-00940: invalid ALTER command
sys@ANBOB> alter system checkpoint;
System altered.
sys@ANBOB> select status from v$instance;
STATUS
OPEN
sys@ANBOB> select * from v$version where rownum=1
2 ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
sys@ANBOB> shutdown immediate
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/oracle/oradata/anbob/control01.ctl'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3
sys@ANBOB> shutdown abort
ORACLE instance shut down.
sys@ANBOB> startup
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1218316 bytes
Variable Size 96471284 bytes
Database Buffers 67108864 bytes
Redo Buffers 2973696 bytes
ORA-00205: error in identifying control file, check alert log for more info
sys@ANBOB> select status from v$instance;
STATUS
STARTED
[oracle@aix ~]$ rman target/
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Jul 14 22:32:12 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: anbob (not mounted)
RMAN> restore controlfile;
Starting restore at 14-JUL-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/14/2011 22:32:27
RMAN-06563: control file or SPFILE must be restored using FROM AUTOBACKUP
RMAN> restore controlfile from autobackup;
Starting restore at 14-JUL-11
using channel ORA_DISK_1
recovery area destination: /oracle/flash_recovery_area
database name (or database unique name) used for search: ANBOB
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /oracle/flash_recovery_area/ANBOB/autobackup/2011_07_14/o1_mf_s_756511643_71xy4xjm_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/oracle/oradata/anbob/control01.ctl
output filename=/oracle/oradata/anbob/control02.ctl
output filename=/oracle/oradata/anbob/control03.ctl
Finished restore at 14-JUL-11
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/14/2011 22:32:52
ORA-01507: database not mounted
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/14/2011 22:33:12
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/14/2011 22:33:19
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/oradata/anbob/system01.dbf'
RMAN> recover database;
Starting recover at 14-JUL-11
Starting implicit crosscheck backup at 14-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 3 objects
Finished implicit crosscheck backup at 14-JUL-11
Starting implicit crosscheck copy at 14-JUL-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 14-JUL-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /oracle/flash_recovery_area/ANBOB/autobackup/2011_07_14/o1_mf_s_756511643_71xy4xjm_.bkp
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 19 is already on disk as file /oracle/oradata/anbob/redo03.log
archive log thread 1 sequence 20 is already on disk as file /oracle/oradata/anbob/redo01.log
archive log filename=/oracle/oradata/anbob/redo03.log thread=1 sequence=19
archive log filename=/oracle/oradata/anbob/redo01.log thread=1 sequence=20
media recovery complete, elapsed time: 00:00:03
Finished recover at 14-JUL-11
RMAN> alter database open resetlogs;
database opened
RMAN> exit
Recovery Manager complete.
o[oracle@aix ~]$ ora
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Jul 14 22:34:23 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
sys@ANBOB> !ls /oracle/oradata/anbob/
control01.ctl control03.ctl redo02.log sysaux01.dbf temp01.dbf undotbs2.dbf
control02.ctl redo01.log redo03.log system01.dbf undotbs01.dbf users01.dbfconn anbob
sys@ANBOB> conn anbob
Enter password:
Connected.
anbob@ANBOB> select * from tab;
TNAME TABTYPE CLUSTERID
TESTCHAR TABLE
TT TABLE
TESTTRUN TABLE
TESTADDM TABLE
TEST TABLE
TESTFUNIDX TABLE
TEAM TABLE
MEMB TABLE
TESTENC TABLE
TESTREC TABLE
BIN$p/SuvHy7sn7gQKjA9QF/dQ==$0 TABLE
DETP TABLE
TESTDELCTL TABLE
DEPT TABLE
TESTFLS TABLE
15 rows selected.
anbob@ANBOB> select * from testdelctl;
ID
999
0
why,loss of all controlfile,the database not abort?

Satish Kandi wrote:
The files, which are in use by a process, are not actually deleted when one issues rm command.
Its only when the process terminates that the locks are released and file is actually deleted at operating system level.I concur!
This behavior is *NIX only.
Windows explicitly prevents open files from being deleted.
Edited by: sb92075 on Jul 14, 2011 9:18 PM

What happen during shutdown oracle database

Dear All,
i have a questions and i enclosed some suggestions for the answer because I'm confused about the answers :
What happens during shutdown oracle database :
and the suggested answer :
1- When shutdown the database with NORMAL or IMMEDIATE option : the database system writes check point before shutting down the database .
2- when you shutdown the database with the IMMEDIATE , option , open transaction are rolled back before the database is shutdown .
3- shutting down the database with abort always requires an instance recovery at the next startup .
please suggest the right answer .
Regards

Hi Anwar,
When you close a database, Oracle writes all database data and recovery data in the SGA to the datafiles and redo log files, respectively. Next, Oracle closes all online datafiles and redo log files.
When you terminate the instance of an open database/use abort command to close and completely shut down the database the writing of all data in the buffers of the SGA to the datafiles and redo log files is skipped. The subsequent reopening of the database requires recovery, which Oracle performs automatically.
I hope this will help you out to understand the process.

What happen during shutdown database

Dear All,
i have a questions and i enclosed some suggestions for the answer because I'm confused about the answers :
What happens during shutdown oracle database :
and the suggested answer :
1- When shutdown the database with NORMAL or IMMEDIATE option : the database system writes check point before shutting down the database .
2- when you shutdown the database with the IMMEDIATE , option , open transaction are rolled back before the database is shutdown .
3- shutting down the database with abort always requires an instance recovery at the next startup .
please suggest the right answer .
Regards
Anwar

First of all shutdown has 4 options
1.Normal
2.Immediate
3.Transactional
4.Abort
Default is normal
Normal: No new connections are allowed. Database and redo buffers are written into disk.Database is closed.
     Backgroud process are terminated.SGA is deallocated. Until and unless all users disconnect, database wont be closed.
Transactional: No client can start a new transaction. Clients get disconnected once their transactions are completed.
     Database and redo buffers are written into disk.Database is closed.Backgroud process are terminated.SGA is deallocated.
Immediate: Current running SQL are not completed. Oracle does not wait for users to disconnect.
     All active transactions are rolled back.Database and redo buffers are written into disk.
     Database is closed.Backgroud process are terminated.SGA is deallocated.
Abort: All users are disconnected.Database and redo buffers are NOT written into disk.
All background processes are killed instantly and instance is abruptly terminated.

Database is hang during shutdown abort (Urgent Production Issue)

Similar Messages

Maybe you are looking for