SHUTDOWN: waiting for detached processes to terminate

HI
I have cold backups running every night and before the backup session starts, we have a cronjob 'srvctl stop -p prod' where our db servers are running on RAC.
but starts from last saturday, our backup session for raw device failed. when look at the alert log, it gives as (example on 15th November 2006)
Tue Nov 21 01:33:31 2006
Thread 1 advanced to log sequence 2855
Current log# 1 seq# 2855 mem# 0: /u01/oracle/oradata/prod/redo_1_01_01.log
Current log# 1 seq# 2855 mem# 1: /u01/oracle/oradata/prod/redo_1_01_02.log
Tue Nov 21 02:37:24 2006
Reconfiguration started
List of nodes: 0,
Global Resource Directory frozen
one node partition
Communication channels reestablished
Server queues filtered
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Resources and enqueues cleaned out
Resources remastered 13089
147420 GCS shadows traversed, 0 cancelled, 18306 closed
63793 GCS resources traversed, 0 cancelled
98369 GCS resources on freelist, 162162 on array, 162162 allocated
set master node info
147420 GCS shadows traversed, 0 replayed, 18306 unopened
Submitted all remote-enqueue requests
Update rdomain variables
0 write requests issued in 129114 GCS resources
1 PIs marked suspect, 0 flush PI msgs
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Tue Nov 21 02:37:27 2006
Reconfiguration complete
Tue Nov 21 02:37:28 2006
Instance recovery: looking for dead threads
Instance recovery: lock domain invalid but no dead threads
Tue Nov 21 02:37:29 2006
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 90
Tue Nov 21 02:37:29 2006
ALTER DATABASE CLOSE NORMAL
Tue Nov 21 02:37:29 2006
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Nov 21 02:37:34 2006
Thread 1 closed at log sequence 2855
Tue Nov 21 02:37:38 2006
Completed: ALTER DATABASE CLOSE NORMAL
Tue Nov 21 02:37:38 2006
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
archiving is disabled
Archive process shutdown avoided: 0 active
Tue Nov 21 02:42:49 2006
SHUTDOWN: waiting for detached processes to terminate.Tue Nov 21 07:16:38 2006
Starting ORACLE instance (normal)
Seems like it was hang when 'shutdown immediate' command is issued. can somebody help me? what should i do?
Thanks
Best regards,
Nonie

Hi nonie
Oracle shutdown Problem
If the following message is in the Oracle alert file:
SHUTDOWN: waiting for detached processes to terminate
you should change the SERVER and SRVR parameters from SHARED to DEDICATED in the file <ORACLE_HOME>\network\ADMIN\tnsnames.ora.
http://serviceportal.fujitsu-siemens.com/i/en/support/technics/fgm/unix/nsr40a_en.htm
hope this helps
Taj.

Similar Messages

SHUTDOWN: waiting for active calls to complete.

Hello,
environment is HPUX 11.23, Oracle Version is 9.2.0.5
We had an ORA-600 error yesterday. We reported that error to the support and were suggested to install patch 9.2.0.8.
However i have one question. As you can see from the output in the alert-logfile it took a very long time to shutdown the instance using the immediate option:
Sun Nov 9 17:33:58 2008
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 454
Sun Nov 9 17:39:07 2008
Active call for process 3991 user 'oracle' program 'oracle@xyz (TNS V1-V3)'
SHUTDOWN: waiting for active calls to complete.
Sun Nov 9 17:50:36 2008
ALTER DATABASE CLOSE NORMAL
Is there anything one can do in such a situation to speed up the shutdown of the instance ?

Rajabaskar Thangaraj,
Oracle database has a job facility and a streams/advanced queuing facility.
These facilities are possible by setting up a few ancillary processes.
Those parameters govern the number of processes.
Setting them to 0 will disable the facility completely.
As you alter the parameter in memory, as you as you have bounced the database, it will be back to the value in the spfile and the facilities will work again.
Disabling them is especially useful when you the facilities are frequently used, ie you have a job running every 30 seconds.
In the past, on several databases, this was the only way to allow a shutdown immediate.
Hope this helps,
Sybrand Bakker
Senior Oracle DBA

Getting java to wait for a process to end

I have an application running Javac i need it to wait for this process to end before it does anything else.
I have tried using theProc.waitFor() (the Process i have created), but this hangs my application. I know there is nothing wrong with the class paths and java itself. I have checked the process list and Javac is still in it. WHY?
Can someone suggest anything.

http://www.javaworld.com/javaworld/jw-12-2000/jw-1229-traps.html

Timed out waiting for Business process

Hi,
I created a web application using evision in JCAPS 512. It works properly. But some times i am getting an error message as
"Timed out waiting for business process" when i try to access the web page usign url.
But if i invoke page again then application works properly.
I have increased server response timeout value also. But couldn't get
the reason when it will occur.
Please let me know what is the reason for this problem. If this error occurs please let me know is it possible to show some other page instead of displaying error to user.
Regards
Venkatesh.S

Good day.
I have a similar problem and I have managed to pinpoint when it fails but unfortunately I don't know how to fix it yet.
In my scenario, I have 2 separate processes:
the first process reads data from a Seebeyond SRE instance and stores it on a local Java CAPS queue.
The second process is an EVision process that reads the data from this queue and displays it on a page.
Whenever I am not connected to the network linking my Java CAPS instance to the Seebeyond SRE instance (first process cannot connect ) I get this problem on the EVision side every second time I request a page. This means I can view the first message on the queue and then I have to restart the Logical Host
This doesn't make sense to me, since The EVision process is a completely separate process, deployed in it's own WAR file.

Thread not waiting for DOS process

Hi
In program I am using Threads. Here all threads will start and execute one DOS command. My problem is that all those thread needs to wait for DOS command to finish its process and then only thread should return.
I have created ThreadGroup and added all threds. And I am checking it by using
ThreadGroupVar.activeCount()!=0 so that I can come to know all thread processing is over or not.
Threads are coming back to main process as soon as they start DOS command ..they are just not waiting it to be finish DOS job.
Please guide me on this
Regards,
Niraj

Create a collection of the Threads then iterate through it using join() on each one. When you have iterated though all the Threads they will all have completed.

Waiting for Sub Process to complete

Hi,
Below mentioned is my requirement:
1. Main process begins
2. Copy a tar file from a source directory to target directory.
3. Call a sub-process to untar the file (using MKS tool kit utility from command prompt).
4. sub-process ends
5. Work on the folders (untared) by applying rules.
6. Main process ends.
When I call sub-process like
main() // main method
// calling sub-process
Process p = Runtime.getRuntime().exec(tar -xvf C:\\Source\\ -C C:\\Target);
p.waitFor();
// calling rules
rule("C:\\Target"); // private method to perform validation on the untared files located in Target folder.
//main method ends
The program gets stuck up here.
The file size to untar is small (1MB). But, after some time, when I kill the main process, I could see sub-process completing its task.
Can you any one suggest me to know the sub-process completion, so that I could call my rules()

I f you read the documentation for exec() and Process carefully you will find that when you an exec() a process, pipes are created back to the main process for the stdout and sterr of the sub-process. Those pipes have a finite size and when full the sub-process will block, hence waitFor() will wait forever.
You need to create threads to drain stdout/stderr of the sub-process, or else re-direct the subprocess output (start a shell to run the actual command) so that the pipes won't get full and block.

WaitFor() doesn't wait for my process to complete?

Hi all,
I'm launching a browser from my java program to display a text file, and when this is done i want to delete that text file from the server, so i tell the process that launches the browser to wait, then i make a call to delete the file from the server
my code goes something like this:
Process browserProc = Runtime.getRuntime().exec(<command to launch browser>);
browserProc.waitFor();
//here i call an external process to delete the file
this works sometimes, but others the file is deleted before the browser gets to display it. what am i doing wrong?! if this is due to subprocesses being spawned is there any solution? any help is greatly appreciated!
thanks and regards,
emh3

This is from some legacy code..urlToPointTo is the url
of my file - does this fall into that category?Apparently it does. And it should, too. I can see the designers thinking "Should this command wait until the GUI is closed? No. Of course not. Obviously the user of this command only wants to launch the GUI. Why on earth would they want to wait until it is closed?"
When you are having so much trouble doing something so simple, that's a good indication that you're doing something that isn't a good idea. Can you explain why you need to delete the remote file after it's displayed? Maybe that was your idea of how to implement some other requirement.

Waiting for another Process??

hello all,
I need a little help. when my application starts i need to be able to launch another process(another java application) and then kill my current one. The way i am doing it now is i fire off the other application and then do a system.exit(0). Well, this works when i test, but when a launcher is built with InstallAnywhere, it does not. When i call the system.exit to kill the current process, everything gets killed, the second app never gets launched. So, im guessing it just doesnt have enough time to start teh new process. I wanted to put some code in to wait and make sure this new process has been started before killing this current process. I am not sure how to do this. I know it is possible to get some process information using JNI, but we can not use it do to portability issues
thanks!

I beg your pardon?
You want to get a reference to the program that some code is running in? And when that program ends, you want some code in that program to do something? Regardless of the fact that the program already ended and that code doesn't exist any more?

Waiting for a process kicked off by servlet

I am kicking off a script on a Unix machine from my servlet on os390 using,
Process p = rt.exec("full_path/script");
How do I know when the process is complete so that I can show the xml page that the process is creating?
Justin Mennen
[email protected]

there is a method waitFor() in Process meant for that purpose

How to wait for a Process to complete without using wait,notify methods

I have created a new Process using run.exec() method using a cmdline String array in the format "java, class name, 4 command line arguments" to be passed to the main method of that class. But I have a maximum limit of the no. of processes to be created e.g. 5. So whenever I create a process, I use a static semaphore class to decrease the count, and increase it again when the process ends; so when the 6th process wants to start it will be suspended until another process is complete. My problem is how do I communicate to the calling class that the process has ended. I don't want to create any threads as that will defeat the purpose of creating separate processes. I have tried Process.waitFor() method but it doesn't work.

you could add a iamfinished method to the class where you store the counter and thread calls it if it is finished.

GUI Login to System "Waiting for Response"

Dear all,
I´ve installed a new SAP-System with ABAP and JAVA.
The installation was successfull, but when I want to login to the System
the GUI write "Waiting for Response". That´s all.
Can anyone help me?

The disp_dev writes:
trc file: "dev_disp", trc level: 1, release: "700"
sysno      01
sid        CCC
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    111
intno      20050900
make:      multithreaded, Unicode, optimized
pid        3732
Sat Aug 16 09:45:36 2008
kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (01 3732) [dpxxdisp.c   1239]
     shared lib "dw_xml.dll" version 111 successfully loaded
     shared lib "dw_xtc.dll" version 111 successfully loaded
     shared lib "dw_stl.dll" version 111 successfully loaded
     shared lib "dw_gui.dll" version 111 successfully loaded
     shared lib "dw_mdm.dll" version 111 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3901
Sat Aug 16 09:45:41 2008
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5361]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >solman_CCC_01                           <
DpShMCreate: sizeof(wp_adm)          18672     (1436)
DpShMCreate: sizeof(tm_adm)          4232256     (21056)
DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
DpShMCreate: sizeof(comm_adm)          528064     (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1536)
DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 06420040, size: 4892312)
DpShMCreate: allocated sys_adm at 06420040
DpShMCreate: allocated wp_adm at 06422090
DpShMCreate: allocated tm_adm_list at 06426980
DpShMCreate: allocated tm_adm at 064269B0
DpShMCreate: allocated wp_ca_adm at 0682FDF0
DpShMCreate: allocated appc_ca_adm at 06835BB0
DpShMCreate: allocated comm_adm at 06837AF0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 068B89B0
DpShMCreate: allocated gw_adm at 068B89F0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 068B8A20
DpShMCreate: allocated wall_adm at 068B8A28
MBUF state OFF
DpCommInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
J2EE server info
start = TRUE
state = STARTED
pid = 4056
argv[0] = C:\usr\sap\CCC\DVEBMGS01\exe\jcontrol.EXE
argv[1] = C:\usr\sap\CCC\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=C:\usr\sap\CCC\SYS\profile\CCC_DVEBMGS01_solman
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1127
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=CCC
argv[7] = -DSAPMYNAME=solman_CCC_01
argv[8] = -DSAPPROFILE=C:\usr\sap\CCC\SYS\profile\CCC_DVEBMGS01_solman
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
Sat Aug 16 09:45:42 2008
DpJ2eeStart: j2ee state = STARTED
Sat Aug 16 09:45:44 2008
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1629]
***LOG Q0K=> DpMsAttach, mscon ( solman) [dpxxdisp.c   11753]
DpStartStopMsg: send start message (myname is >solman_CCC_01                           <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 111
Release check o.K.
Sat Aug 16 09:45:46 2008
DpJ2eeLogin: j2ee state = CONNECTED
Sat Aug 16 09:46:08 2008
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Sat Aug 16 09:46:16 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Sat Aug 16 09:46:53 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Sat Aug 16 09:47:13 2008
SoftCancel request for T14 U15 M0 received from IC_MAN
SoftCancel request for T13 U14 M0 received from IC_MAN
Sat Aug 16 09:52:24 2008
WARNING => DpEnvCheck: no answer from msg server since 20 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:52:44 2008
WARNING => DpEnvCheck: no answer from msg server since 40 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:53:04 2008
WARNING => DpEnvCheck: no answer from msg server since 60 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:53:24 2008
WARNING => DpEnvCheck: no answer from msg server since 80 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:53:44 2008
WARNING => DpEnvCheck: no answer from msg server since 100 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:54:04 2008
WARNING => DpEnvCheck: no answer from msg server since 120 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:54:24 2008
WARNING => DpEnvCheck: no answer from msg server since 140 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:59:46 2008
J2EE server info
start = TRUE
state = ACTIVE
pid = 4056
http = 50100
https = 50101
load balance = 1
start_lazy = 0
start_control = SAP J2EE startup framework
Mon Aug 18 08:24:32 2008
DpSigQuit: caught signal 3
Mon Aug 18 08:24:45 2008
DpModState: change server state from ACTIVE to SHUTDOWN
Softshutdown of server...
send softshutdown to gateway
there are still entries in queues: 2
Mon Aug 18 08:25:05 2008
Softshutdown of server...
send softshutdown to gateway
DpHalt: shutdown server >solman_CCC_01                           < (normal)
Mon Aug 18 08:25:06 2008
Stop work processes
Mon Aug 18 08:25:07 2008
Stop gateway
Stop icman
Terminate gui connections
wait for end of work processes
waiting for termination of work processes ...
Mon Aug 18 08:25:08 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:09 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:11 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:12 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:13 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:14 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:15 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:16 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:17 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:18 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:19 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:20 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:21 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:23 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:24 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:25 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:26 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:27 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:28 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:29 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:30 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:31 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:32 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:33 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:34 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:35 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:36 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:37 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:38 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:39 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:40 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:41 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:42 2008
wait for end of gateway
wait for end of icman
DpHalt: disconnect j2ee listener
DpHalt: wait for end of j2ee server
waiting for termination of J2EE server ...
Mon Aug 18 08:25:43 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:44 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:46 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:47 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:48 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:49 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:50 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:51 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:52 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:53 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:54 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:55 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:56 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:57 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:58 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:59 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:00 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:01 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:02 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:03 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:04 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:05 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:06 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:07 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:08 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:09 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:10 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:11 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:12 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:13 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:14 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:15 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:16 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:17 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:18 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:19 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:20 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:21 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:22 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:23 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:24 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:25 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:26 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:27 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:28 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:29 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:30 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:31 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:32 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:33 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:34 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:35 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:36 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:37 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:38 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:39 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:40 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:41 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:42 2008
ERROR => DpHalt: J2EE (pid 4056) still alive ... [dpxxdisp.c   10223]
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=4056)
DpIJ2eeShutdown: j2ee state = SHUTDOWN
waiting for termination of J2EE server ...
Mon Aug 18 08:26:43 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:44 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:45 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:46 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:47 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:48 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:49 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:50 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:51 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:52 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:53 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:54 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:55 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:56 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:57 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:58 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:59 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:00 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:01 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:02 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:03 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:04 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:05 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:06 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:07 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:08 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:09 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:10 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:11 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:12 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:13 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:14 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:15 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:16 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:17 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:18 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:19 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:20 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:21 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:22 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:23 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:24 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:25 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:26 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:27 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:28 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:29 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:30 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:31 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:32 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:33 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:34 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:35 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:36 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:37 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:38 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:39 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:40 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:41 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:42 2008
ERROR => DpHalt: J2EE (pid 4056) still alive [dpxxdisp.c   10255]
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
DpJ2eeEmergencyShutdown: try to kill SAP J2EE startup framework (pid=4056)
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:43 2008
DpStartStopMsg: send stop message (myname is >solman_CCC_01                           <)
DpStartStopMsg: stop msg sent
Mon Aug 18 08:27:44 2008
DpHalt: sync with message server o.k.
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   12099]
MBUF state OFF
MBUF component DOWN
cleanup EM
Mon Aug 18 08:27:45 2008
***LOG Q05=> DpHalt, DPStop ( 3732) [dpxxdisp.c   10371]
Can you understand, what this means?

Database hangs in shutdown immediate for cold backup

Dear experts ,
we have scheduled cold backup for our database.
is there any solution to resolve below mentioned errors other than RMAN hot backup or shutdown abort ?
Sat Jan 26 00:20:55 2013
Active call for process 3939 user 'oracle' program '[email protected]'
SHUTDOWN: waiting for active calls to complete.
Sat Jan 26 01:15:59 2013
SHUTDOWN: Active sessions prevent database close operation
Instance shutdown aborted

Hi,
should we daily kill these processes with LOCAL=NO
what is proposed solution in such cases ?
is it not harmful for OS or database to kill these processes daily ?Yon can create shell script to find kill session only when you find active calls in your database alert log. You need not have to kill it on daily basis.
Refer MOS tech notes for more details:
*Alert Log: Shutdown Waiting for Active Calls to Complete [ID 1039389.6]*
*What Is The Fastest Way To Cleanly Shutdown An Oracle Database? [ID 386408.1]*
thanks,
X A H E E R

Wait for Intel G5 or buy power mac pro intel now????

This is for video and multimedia processing and i know Qaud g5 is best on the market right now but i need somnething within a few months with fast processing power with intel because that will be the newest tech. that wont go out of date anytime soon. So what do I do Wait for power mac G5 Intel which i predict in year or just buy the mac book pro but scared it won't process as fast as i think it will. I just absolutly cant handle when using multiple layers and when I edit them waiting for the process time to make each of the changes. WHAT SHOULD I DO!!!!!!

You're not even comparing apples to apples here. The MBP is faster than the G4 Powerbooks, but it will in no way compete with a Quad G5! Not to mention, the MBP maxxes out at 2GB memory, which although good, is not nearly enough for serious mutimedia processing like you mentioned. If I didn't already have a D2.5, I'd buy a Quad now - why wait.

[Solved] systemd does not wait for the unit to finish

My problem is described in the title. I have made a test by enabling the following unit:
[Unit]
Description=/etc/rc.local Compatibility
[Service]
Type=forking
ExecStart=/bin/sleep 1000
TimeoutSec=0
RemainAfterExit=yes
After=network.target
[Install]
WantedBy=multi-user.target
The unit is well started (a process sleep 1000 exists). But with a type=forking, systemd is supposed to hang in this case. Instead, the graphical.target is launched, systemctl list-units mention it as dead, but the display manager is started before the sleep 1000 completes. Ho can I force systemd to wait?
Last edited by olive (2015-03-16 16:49:34)

olive, now you're making even less sense. I didn't say the sleep example was stupid and I didn't question your reasons for doing/wanting this.
I suggested you add "Before=display-manager.service" and you respond "I added Before=graphical.target and it didn't change anything."
I also tried to explain why systemd has no reason to delay the display-manager.service. You could have asked for further clarification, as berbae has now done. Let's try a longer explanation.
Service startup
Services can be started in different ways, as configured with Type=. This determines when a service is considered "started" (or when the service's start-up is considered finished). When a service reaches this state (some time after being started), units that are supposed to start After= this service will be started (and no sooner).
With simple systemd has no further information about the start-up process. It launches whatever you specify in ExecStart and this is the main process that continues to run till the service stops. systemd assumes this type of service is started immediately. All the other types have some way for the process to indicate to systemd (either directly or indirectly) when it has finished starting.
Actually oneshot is also a bit special and that is where RemainAfterExit comes in. For oneshot, systemd waits for the process to exit before it starts any follow-up units (and with multiple ExecStarts I assume it waits for all of them). So that automatically leads to the scheme in berbae's last post. However, with RemainAfterExit, the unit remains active even though the process has exited, so this makes it look more like "normal" service with
begin of unit/startup ---- end of startup ------ end of unit
This is the relevant behavior for this thread. First sleep starts, then after 1000 seconds, start-up finishes and follow-up units will be started. Then either the unit dies, or (with RemainAfterExit) it stays "active".
The man page describes how "end of startup" is determined for each Type.
Targets
Targets are meant to group units together, to provide synchronization points (and replace runlevels). When you start a target, all its units will be started (in parallel if possible). The man page says:
Unless DefaultDependencies= is set to false, target units will
implicitly complement all configured dependencies of type Wants=,
Requires=, RequiresOverridable= with dependencies of type After= if the
units in question also have DefaultDependencies=true.
This means that (by default) when a target is requested, all it units are started first. Only after all units have finished starting, the target itself will be started (and since the target doesn't do anything by itself, this startup is basically instantaneous). Without this dependency, the order between the target and its units is unspecified, so in theory the target could finish starting immediately while its units are still being started.
Back to olive
graphical.target has these DefaultDependencies, so it is not started until all its units (like display-manager.service) and other After= dependencies (like multi-user.target) have finished starting. Your sleep service has to be started before multi-user.target starts (again due to default target dependencies). So first display-manager and the sleep service are started and after 1000 seconds, the sleep service finishes starting and then (assuming all other dependencies were quicker) multi-user.target is started and graphical.target as well (assuming display-manager didn't need 1000 seconds).
If you want display-manager.service after the sleep service, add a Before/After line to specify that (this was your original goal and my suggestion).
olive wrote wrote:However, units that are parts of the graphical target are still launched before the graphical target become active. I am still unable to completely delay the starts of the graphical target before a specific unit completes.
It should be clear now how this works. "units that are part of the graphical target" can only mean "units that are wanted/required by the graphical target" but that is basically all the units that are started when you boot your system, because multi-user.target is a part of graphical.target. And your sleep service is a part of multi-user.target, so in fact you're saying you want to delay starting the sleep service until the sleep service completes
What you probably intended was to delay all units that are a part of graphical.target but not of multi-user.target until after the sleep service. I can't think of an easy (or even good) way to do this and this post is already too long, so I'll table that for now.

Waiting for the end of the process

I'm executing a command using the Runtime class and I have to wait until the end of the command to get the results. But, I don't want to sleep the thread for some undeterminated time. I'd like it just to wait until the command ends.
See in this code:
try
String result="";
Process p = Runtime.getRuntime().exec("sh"); //open a new shell
InputStream is = p.getInputStream();
OutputStream os = p.getOutputStream();
os.write("ifconfig -a | grep PROMISC -c\n".getBytes());
os.flush();
try {
Thread.currentThread().sleep(1000);
/*command should take some time to execute so wait for 10 secs .... I don't like this .... I would prefer waiting for the end the command ifconfig*/
catch (InterruptedException eIE) { }
while (is.available() > 0)
result = result + ( (char) is.read());
System.out.println(result);
catch (IOException e) {
System.out.println(e);

AFAIK you can only detect if the shell process has finished, as sub-processes of the shell are not visible to your Java program (without resorting to OS-specific syscalls).
You can write "exit" (or whatever terminates your shell) in the output stream as the last command - this will quit the shell as soon as all commands are finished, and that will be visible to your prog. Note that you should not run ANY of the shell commands in background then, as this could cause the shell to exit before the commands are finished (and, depending on the system, even signal the subprocesses).

SHUTDOWN: waiting for detached processes to terminate

Similar Messages

Maybe you are looking for