Random server reboots caused by _mdnsresponder

I have a customer running 10.5.7 server. The server has an issue where it seemingly reboots at random without a user causing it. The system log shows entries like this:
Oct 13 15:54:03 server shutdown[88813]: reboot by openbase:
Oct 13 15:54:03 server shutdown[88813]: SHUTDOWN_TIME: 1255463643 856709
Oct 13 17:09:38 server shutdown[703]: reboot by _mdnsresponder:
Oct 13 17:09:38 server shutdown[703]: SHUTDOWN_TIME: 1255468178 405753
The users openbase and _mdnsresponder are non-interactive users that exist for services running on the server. Two questions arise:
1. Are these log messages indicating that a reboot is initiated by these non-interactive users?
If so,
2. How does a non-interactive user reboot the server?
I know they're running OpenBase as the backend for a Daylite install we don't support, so I'm more interested to know how the _mdnsresponder user is causing a reboot, if indeed that's the case.

Similar Messages

SQL server service reboot cause the Buffer Data to flush

Could someone please let me know if I just reboot SQL service on Production SQL Server that Causes to remove all Data cached in Buffer cache ? Is reboot SQL service also flush Procedure cache ?
Thank you for in advance for your help .
Daizy

Hi Daizy,
Restart of SQL Server Service is the similar with restarting of the applications. All your caches will be flushed.
Usually, you would not experience any data loss (transaction log records are hardened on the disk synchronously) with exception of transactions with delayed durability in SQL Server 2014. However, all your uncommitted transactions would be rolled back.
Do not forget that reboot would cause performance degradation (data and plans are not cached), database restarts and a few other things. It could be more efficient to use one of the DBCC
commands to cleanup specific cache rather than reboot the service.
Thank you!
Dmitri V. Korotkevitch (MVP, MCM, MCPD)
My blog: http://aboutsqlserver.com

NFS: server reboot - client problem with "file handle" - no unmont

Hello,
when I restart a NFS-server and a client has a NFS-share on it still mounted, that NFS-share becomes unusable on the client: everything causes the client complain about an old "file handle", even trying to unmount that share!
So my question is: How to deal gracefully with a NFS-server reboot and avoiding this file handle problem?
Apart from going to each client and unmount the NFS-share by hand?
Thanks!

Do I need to Give these values manually again as they are moved from Env to other?
When we transport ID objects, the values stored in the channel get lost and have to be manually enetered......it happens even for DEV --> QA environment.
Now your channel should reflect PROD-related data.
2- Why my Receiver communiation channel coimg as
Communication Channel | PRD_400 | RFC_QA3_Receiver:
The channel name does not depend on the environment it is present....verify the name once again!
Regards,
Abhishek.

Unexpected Server Reboot on Windows Server 2012 Standard

Hi All,
I have received unexpected reboot on Windows Server 2012 Standard . After searching on the internet I found one
hotfix for this, but it is applicable for Windows 2008 R2. Link to download Windows 2008 R2
hotfix -
http://support.microsoft.com/kb/2732595/en-US
Can someone guide me to get a same
hotfix for Windows Server 2012 Standard.
Log Name:      System
Source:        User32
Date:          2/27/2014 7:27:17 AM
Event ID:      1074
Task Category: None
Level:         Information
Keywords:      Classic
User:          SYSTEM
Computer:      Server1.test.com
Description:
The process wininit.exe has initiated the restart of computer "Server1" on behalf of
user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
Thank you.
Regards,
Mahesh Arban.

Hi Mahesh Arban,
Sorry for my delay.
I can’t find the same hotfix for Windows Server 2012 Standard. So, we may need to do some troubleshootings
to narrow down this issue and solve it.
Please let me confirm if you have installed all updates for this Windows Server 2012 Standard. Meanwhile, please
use Sfc command to scans and verifies the integrity of all protected system files.
In addition, this issue caused to unexpected server reboot. So, please configure and then collect the dump
file to analysis. It may help us to find the root cause of this issue.
How to read the small memory dump file that is created by Windows if a crash occurs
http://support.microsoft.com/kb/315263/en-us
By the way, can you find any error messages in application log (such as Event ID 1000 or others) after this
issue occurred?
Hope this helps.
Best regards,
Justin Gu

Cube Databases Are Deleted with Server Reboot

We have deployed two small cubes in our SQL 2012 SSAS environment running on Windows Server 2012. Every time the server is rebooted, the cube databases are deleted. The database files deleted are in the default directory. We have added
exclusions for these directories in the AV software running on the server. We even added NetStop commands to stop the SSAS, SQL Agent and SQL Server services before the reboot occurs to make sure SQL Server is stopped before reboot. Has anyone
encountered this? If so, do you have a fix for this issue?
Thanks in advance for your assistance.

Hi Jbud55,
In your description, you said that the SQL Server Analysis Services cubes were deleted after the server reboot, right? We cannot reproduce this issue in our local environment. In order to narrow down this issue, please apply the latest Cumulative Update
and Services Pack.
Besides, does this issue occur when you restart the services manually? As per my understanding, the issue can be caused by the server reboot. Are there any error message on the log? Under C:\Program Files\Microsoft SQL Server\MSAS11.\OLAP\Log (this could
be different for your server), there are 3 log files that are generated:
msmdrrv.log
FlightRecorderCurrent.trc
FightRecorderBack.trc
The msmdrrv.log simply points to the other two logs. There might be some detail information for this error.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Post server reboot , instance 1 crashes on starting the second one

Hi ,
We had a server reboot ( Solaris SPARC 64 bit) and had to shutdown the application running on RAC system on 2 servers.
now post the activity , we are trying to bring up the instances but whenever one comes up the other goes down.
If we try to start the second one , first goes down.
Oracle database version : 10.2.0.3.0
Alert logs for both have been mentioned below :
instance1:
Mon Jul 23 16:17:22 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 bge3 10.0.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 bge0 58.2.35.0 configured from OCR for use as a public interface
Interface type 1 bge1 58.2.35.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/orainf/product/10.2.0/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes                = 400
__shared_pool_size       = 956301312
shared_pool_size         = 201326592
__large_pool_size        = 16777216
__java_pool_size         = 150994944
java_pool_size           = 150994944
__streams_pool_size      = 16777216
streams_pool_size        = 16777216
sga_target               = 1610612736
control_files            = /db01/asdb/asdb/control01.ctl, /db01/asdb/asdb/control02.ctl, /db01/asdb/asdb/control03.ctl
db_block_size            = 8192
__db_cache_size          = 452984832
db_cache_size            = 167772160
compatible               = 10.2.0.3.0
db_file_multiblock_read_count= 16
cluster_database         = TRUE
cluster_database_instances= 2
thread                   = 1
instance_number          = 1
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
ldap_directory_access    = PASSWORD
remote_login_passwordfile= EXCLUSIVE
db_domain                = intranet.genpact.com
remote_listener          = LISTENERS_ASDB
job_queue_processes      = 10
background_dump_dest     = /u01/app/orainf/admin/asdb/bdump
user_dump_dest           = /u01/app/orainf/admin/asdb/udump
core_dump_dest           = /u01/app/orainf/admin/asdb/cdump
audit_file_dest          = /u01/app/orainf/admin/asdb/adump
db_name                  = asdb
open_cursors             = 300
pga_aggregate_target     = 848297984
aq_tm_processes          = 1
Mon Jul 23 16:17:24 2012
Oracle instance running with ODM: Veritas 5.0.30.00 ODM Library, Version 1.1
cluster interconnect IPC version:
        VERITAS IPC '5.0MP3' 07:30:15 Jul 29 2008
IPC Vendor 86 proto 76
Version 1.0
PMON started with pid=2, OS id=17279
DIAG started with pid=3, OS id=17281
Mon Jul 23 16:17:24 2012
Errors in file /u01/app/orainf/admin/asdb/bdump/asdb1_diag_17281.trc:
ORA-07445: exception encountered: core dump [_kill()+8] [SIGIOT] [unknown code] [0x438100000000] [] []
PSP0 started with pid=4, OS id=17283
LMON started with pid=5, OS id=17285
LMD0 started with pid=6, OS id=17287
LMS0 started with pid=7, OS id=17289
LMS1 started with pid=8, OS id=17293
MMAN started with pid=9, OS id=17297
DBW0 started with pid=10, OS id=17299
LGWR started with pid=11, OS id=17301
CKPT started with pid=12, OS id=17303
SMON started with pid=13, OS id=17333
RECO started with pid=14, OS id=17338
CJQ0 started with pid=15, OS id=17340
MMON started with pid=16, OS id=17342
MMNL started with pid=17, OS id=17344
Mon Jul 23 16:17:26 2012
Errors in file /u01/app/orainf/admin/asdb/bdump/asdb1_lmon_17285.trc:
ORA-27550: Target ID protocol check failed. tid vers=%d, type=%d, remote instance number=%d, local instance number=%d
Mon Jul 23 16:17:26 2012
LMON: terminating instance due to error 27550
Instance terminated by LMON, pid = 17285
Mon Jul 23 16:18:33 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 bge3 10.0.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 bge0 58.2.35.0 configured from OCR for use as a public interface
Interface type 1 bge1 58.2.35.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/orainf/product/10.2.0/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes                = 400
__shared_pool_size       = 956301312
shared_pool_size         = 201326592
__large_pool_size        = 16777216
__java_pool_size         = 150994944
java_pool_size           = 150994944
__streams_pool_size      = 16777216
streams_pool_size        = 16777216
sga_target               = 1610612736
control_files            = /db01/asdb/asdb/control01.ctl, /db01/asdb/asdb/control02.ctl, /db01/asdb/asdb/control03.ctl
db_block_size            = 8192
__db_cache_size          = 452984832
db_cache_size            = 167772160
compatible               = 10.2.0.3.0
db_file_multiblock_read_count= 16
cluster_database         = TRUE
cluster_database_instances= 2
thread                   = 1
instance_number          = 1
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain                = intranet.genpact.com
job_queue_processes      = 10
background_dump_dest     = /u01/app/orainf/admin/asdb/bdump
user_dump_dest           = /u01/app/orainf/admin/asdb/udump
core_dump_dest           = /u01/app/orainf/admin/asdb/cdump
audit_file_dest          = /u01/app/orainf/admin/asdb/adump
db_name                  = asdb
open_cursors             = 300
pga_aggregate_target     = 848297984
aq_tm_processes          = 1
Mon Jul 23 16:18:35 2012
Oracle instance running with ODM: Veritas 5.0.30.00 ODM Library, Version 1.1
cluster interconnect IPC version:
        VERITAS IPC '5.0MP3' 07:30:15 Jul 29 2008
IPC Vendor 86 proto 76
Version 1.0
PMON started with pid=2, OS id=19523
DIAG started with pid=3, OS id=19525
Mon Jul 23 16:18:36 2012
Errors in file /u01/app/orainf/admin/asdb/bdump/asdb1_diag_19525.trc:
ORA-07445: exception encountered: core dump [_kill()+8] [SIGIOT] [unknown code] [0x4C4500000000] [] []
PSP0 started with pid=4, OS id=19527
LMON started with pid=5, OS id=19529
LMD0 started with pid=6, OS id=19531
LMS0 started with pid=7, OS id=19533
LMS1 started with pid=8, OS id=19537
MMAN started with pid=9, OS id=19557
DBW0 started with pid=10, OS id=19573
LGWR started with pid=11, OS id=19576
CKPT started with pid=12, OS id=19578
SMON started with pid=13, OS id=19580
RECO started with pid=14, OS id=19582
CJQ0 started with pid=15, OS id=19584
MMON started with pid=16, OS id=19586
MMNL started with pid=17, OS id=19588
Mon Jul 23 16:18:37 2012
Errors in file /u01/app/orainf/admin/asdb/bdump/asdb1_lmon_19529.trc:
ORA-27550: Target ID protocol check failed. tid vers=%d, type=%d, remote instance number=%d, local instance number=%d
Mon Jul 23 16:18:37 2012
LMON: terminating instance due to error 27550
Instance terminated by LMON, pid = 19529
Mon Jul 23 16:20:16 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 bge3 10.0.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 bge0 58.2.35.0 configured from OCR for use as a public interface
Interface type 1 bge1 58.2.35.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/orainf/product/10.2.0/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes                = 400
__shared_pool_size       = 956301312
shared_pool_size         = 201326592
__large_pool_size        = 16777216
__java_pool_size         = 150994944
java_pool_size           = 150994944
__streams_pool_size      = 16777216
streams_pool_size        = 16777216
sga_target               = 1610612736
control_files            = /db01/asdb/asdb/control01.ctl, /db01/asdb/asdb/control02.ctl, /db01/asdb/asdb/control03.ctl
db_block_size            = 8192
__db_cache_size          = 452984832
db_cache_size            = 167772160
compatible               = 10.2.0.3.0
db_file_multiblock_read_count= 16
cluster_database         = TRUE
cluster_database_instances= 2
thread                   = 1
instance_number          = 1
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
db_domain                = intranet.genpact.com
job_queue_processes      = 10
background_dump_dest     = /u01/app/orainf/admin/asdb/bdump
user_dump_dest           = /u01/app/orainf/admin/asdb/udump
core_dump_dest           = /u01/app/orainf/admin/asdb/cdump
audit_file_dest          = /u01/app/orainf/admin/asdb/adump
db_name                  = asdb
open_cursors             = 300
pga_aggregate_target     = 848297984
Mon Jul 23 16:20:18 2012
Oracle instance running with ODM: Veritas 5.0.30.00 ODM Library, Version 1.1
cluster interconnect IPC version:
        VERITAS IPC '5.0MP3' 07:30:15 Jul 29 2008
IPC Vendor 86 proto 76
Version 1.0
PMON started with pid=2, OS id=22860
DIAG started with pid=3, OS id=22870
Mon Jul 23 16:20:18 2012
Errors in file /u01/app/orainf/admin/asdb/bdump/asdb1_diag_22870.trc:
ORA-07445: exception encountered: core dump [_kill()+8] [SIGIOT] [unknown code] [0x595600000000] [] []
PSP0 started with pid=4, OS id=22888
LMON started with pid=5, OS id=22892
LMD0 started with pid=6, OS id=22899
LMS0 started with pid=7, OS id=22901
LMS1 started with pid=8, OS id=22905
MMAN started with pid=9, OS id=22909
DBW0 started with pid=10, OS id=22911
LGWR started with pid=11, OS id=22913
CKPT started with pid=12, OS id=22915
SMON started with pid=13, OS id=22917
RECO started with pid=14, OS id=22919
CJQ0 started with pid=15, OS id=22921
MMON started with pid=16, OS id=22923
MMNL started with pid=17, OS id=22933
Mon Jul 23 16:20:20 2012
Errors in file /u01/app/orainf/admin/asdb/bdump/asdb1_lmon_22892.trc:
ORA-27550: Target ID protocol check failed. tid vers=%d, type=%d, remote instance number=%d, local instance number=%d
Mon Jul 23 16:20:20 2012
LMON: terminating instance due to error 27550
Instance terminated by LMON, pid = 22892instance 2:
Mon Jul 23 16:20:30 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 bge3 10.0.0.0 configured from OCR for use as a cluster interconnect
WARNING 10.0.0.0 could not be translated to a network address error 1
Interface type 1 bge0 58.2.35.0 configured from OCR for use as a public interface
Interface type 1 bge1 58.2.35.0 configured from OCR for use as a public interface
WARNING: No cluster interconnect has been specified. Depending on
           the communication driver configured Oracle cluster traffic
           may be directed to the public interface of this machine.
           Oracle recommends that RAC clustered databases be configured
           with a private interconnect for enhanced security and
           performance.
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/orainf/product/10.2.0/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes                = 400
__shared_pool_size       = 721420288
shared_pool_size         = 201326592
__large_pool_size        = 16777216
__java_pool_size         = 150994944
java_pool_size           = 150994944
__streams_pool_size      = 16777216
streams_pool_size        = 16777216
spfile                   = /db01/asdb/asdb/spfileasdb.ora
sga_target               = 1610612736
control_files            = /db01/asdb/asdb/control01.ctl, /db01/asdb/asdb/control02.ctl, /db01/asdb/asdb/control03.ctl
db_block_size            = 8192
__db_cache_size          = 687865856
db_cache_size            = 167772160
compatible               = 10.2.0.3.0
db_file_multiblock_read_count= 16
cluster_database         = TRUE
cluster_database_instances= 2
thread                   = 2
instance_number          = 2
undo_management          = AUTO
undo_tablespace          = UNDOTBS2
ldap_directory_access    = PASSWORD
remote_login_passwordfile= EXCLUSIVE
db_domain                = intranet.genpact.com
dispatchers              = (PROTOCOL=TCP) (SERVICE=asdbXDB)
remote_listener          = LISTENERS_ASDB
job_queue_processes      = 10
background_dump_dest     = /u01/app/orainf/admin/asdb/bdump
user_dump_dest           = /u01/app/orainf/admin/asdb/udump
core_dump_dest           = /u01/app/orainf/admin/asdb/cdump
audit_file_dest          = /u01/app/orainf/admin/asdb/adump
db_name                  = asdb
open_cursors             = 300
pga_aggregate_target     = 848297984
aq_tm_processes          = 1
Cluster communication is configured to use the following interface(s) for this instance
58.2.35.93
Mon Jul 23 16:20:32 2012
Oracle instance running with ODM: Veritas 5.0.30.00 ODM Library, Version 1.1
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=28537
DIAG started with pid=3, OS id=28539
PSP0 started with pid=4, OS id=28541
LMON started with pid=5, OS id=28543
Mon Jul 23 16:20:33 2012
WARNING: Failed to set buffer limit on IPC interconnect socket
Oracle requires that the SocketReceive buffer size be tunable upto 1MB
Please make sure the kernel parameterwhich limits SO_RCVBUF value set by
applications is atleast 1MB
LMD0 started with pid=6, OS id=28545
LMS0 started with pid=7, OS id=28547
LMS1 started with pid=8, OS id=28551
MMAN started with pid=9, OS id=28555
DBW0 started with pid=10, OS id=28557
LGWR started with pid=11, OS id=28567
CKPT started with pid=12, OS id=28587
SMON started with pid=13, OS id=28594
RECO started with pid=14, OS id=28596
CJQ0 started with pid=15, OS id=28599
MMON started with pid=16, OS id=28605
MMNL started with pid=17, OS id=28608
Mon Jul 23 16:20:34 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Mon Jul 23 16:20:34 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Mon Jul 23 16:20:35 2012
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Mon Jul 23 16:20:35 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Mon Jul 23 16:20:35 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Mon Jul 23 16:20:35 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Mon Jul 23 16:20:35 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Mon Jul 23 16:20:35 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=28770
Mon Jul 23 16:20:36 2012
ALTER DATABASE   MOUNT
Mon Jul 23 16:20:36 2012
This instance was first to mount
Setting recovery target incarnation to 2
Mon Jul 23 16:20:40 2012
Successful mount of redo thread 2, with mount id 2392310356
Mon Jul 23 16:20:40 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE   MOUNT
Mon Jul 23 16:20:40 2012
ALTER DATABASE OPEN
This instance was first to open
Mon Jul 23 16:20:40 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Mon Jul 23 16:20:41 2012
Started redo scan
Mon Jul 23 16:20:41 2012
Completed redo scan
509 redo blocks read, 149 data blocks need recovery
Mon Jul 23 16:20:41 2012
Started redo application at
Thread 2: logseq 1492, block 3
Mon Jul 23 16:20:41 2012
Recovery of Online Redo Log: Thread 2 Group 7 Seq 1492 Reading mem 0
Mem# 0: /db01/asdb/asdb/redo07a.log
Mem# 1: /db01/asdb/asdb/redo07b.log
Mon Jul 23 16:20:41 2012
Completed redo application
Mon Jul 23 16:20:41 2012
Completed crash recovery at
Thread 2: logseq 1492, block 512, scn 10435264045528
149 data blocks read, 149 data blocks written, 509 redo blocks read
Picked broadcast on commit scheme to generate SCNs
Mon Jul 23 16:20:42 2012
Thread 2 advanced to log sequence 1493
Thread 2 opened at log sequence 1493
Current log# 8 seq# 1493 mem# 0: /db01/asdb/asdb/redo08a.log
Current log# 8 seq# 1493 mem# 1: /db01/asdb/asdb/redo08b.log
Successful open of redo thread 2
Mon Jul 23 16:20:42 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jul 23 16:20:42 2012
SMON: enabling cache recovery
Mon Jul 23 16:20:42 2012
Successfully onlined Undo Tablespace 5.
Mon Jul 23 16:20:42 2012
SMON: enabling tx recovery
Mon Jul 23 16:20:43 2012
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=24, OS id=29088
Mon Jul 23 16:20:46 2012
Completed: ALTER DATABASE OPENPlease suggest
Regards
KK

Hi ,
I have used the command ifconfig -a
below is the output :
chaning the original IP's with alphabets for security concerns
instance 1:
bash-2.05$ ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet XY.M.CD.93 netmask ffffff00 broadcast XY.M.CD.255
        groupname orapub
bge0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
        inet XY.M.CD.94 netmask ffffff00 broadcast XY.M.CD.255
bge0:3: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 2
        inet XY.M.CD.151 netmask ffffff00 broadcast XY.M.CD.255
bge1: flags=39040803<UP,BROADCAST,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED,STANDBY> mtu 1500 index 3
        inet XY.M.CD.95 netmask ffffff00 broadcast XY.M.CD.255
        groupname orapub
bge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
        inet ZZ.0.0.1 netmask ff000000 broadcast ZZ.255.255.255
bge3: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
        inet 0.0.0.0 netmask 0instance 2:
bash-2.05$ ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet XY.M.CD.96 netmask ffffff00 broadcast XY.M.CD.255
        groupname orapub
bge0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
        inet XY.M.CD.97 netmask ffffff00 broadcast XY.M.CD.255
bge0:2: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 2
        inet XY.M.CD.152 netmask ffffff00 broadcast XY.M.CD.255
bge1: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 1500 index 3
        inet XY.M.CD.98 netmask ffffff00 broadcast XY.M.CD.255
        groupname orapub
bge3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
        inet 0.0.0.0 netmask ff000000
bge3:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
        inet 10.0.0.3 netmask ff000000 broadcast ZZ.255.255.255Regards

RE: NT Server Reboot and Forte Partitions[Ref:C943460]

Hi Bradley.
At our customers, we need one of our Forte applications to be running for data
communications to take place. After a reboot, we need this application's
partitions to come online. The way we did this (as you suggested) was to use a
BAT file, and then install this as an NT service (we used a utility that comes
with the NT resource kit - srvany).
This works fine for us. One of the issues we had was that the partitions tried
to come online before Oracle was running - this resulted in the dbsessions
failing and the partitions not coming online. We got round this by preceding
starting the partitions with a loop that polled Oracle until it was up. Needless
to say, piping all output to log files was essential for us to figure out what
was going on.
Hope this helps,
Steve Elvin
Systems Developer
Frontline Ltd.
UK
-----Original Message-----
From: INTERNET [email protected]
Sent: Monday, November 02, 1998 11:04 PM
To: Steve Elvin; X400
p=NET;a=CWMAIL;c=GB;DDA:RFC-822=Forte-Users(a)sagesoln.com;
Subject: NT Server Reboot and Forte Partitions [Ref:C943460]
I have a system administration question for users with NT servers in
their Forte environment. If I have installed Forte partitions on an NT
server which I would like to startup when the server is rebooted, then
what are my options for scripting this to happen automatically?
Currently the only Forte process on the server which starts up
automatically is the Forte node manager, through the installed NT
service. I have been contemplating setting up a BAT file process as an
NT service which would wait for the Forte node manager service to start,
and then execute an fscript file to start the required forte partitions.
How is this situation being handled in other environments? Thanks.
Bradley K Wells
Strong Capital Management, Inc
[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi Brad,
I am not sure if this is the right solution in the long run, but if you
login into NT after reebot you can create a simple client that "pings" your
service objects and put the shortcut into the Startup Group. I think such a
client may also be useful to monitor your Forte server for application
specific parameters, instead of relying only on logs/econsole.
David
At 04:18 PM 11/2/98 -0600, you wrote:
I have a system administration question for users with NT servers in
their Forte environment. If I have installed Forte partitions on an NT
server which I would like to startup when the server is rebooted, then
what are my options for scripting this to happen automatically?
Currently the only Forte process on the server which starts up
automatically is the Forte node manager, through the installed NT
service. I have been contemplating setting up a BAT file process as an
NT service which would wait for the Forte node manager service to start,
and then execute an fscript file to start the required forte partitions.
How is this situation being handled in other environments? Thanks.
Bradley K Wells
Strong Capital Management, Inc
[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

How clusterware restarts on automatically after server reboot in 11g R2

Hi,
I would like to know how the cluster restarts on automatically after the server reboot in 11g R2 RAC . The oracle restart feature in 11g R2 help to restart the components like databases, ASM in case of abnormal failure. But how the clusterware starts on own after the server reboot? can you share any documents or notes is really appreciated.
Thanks,
Robin.

At Grid Infrastructure installation time system configuration is modified so that UNIX init daemon restarts OHASD: http://docs.oracle.com/cd/E11882_01/rac.112/e16794/intro.htm#BABIDEFI. For example with Oracle Linux 5 and Oracle RAC 11.2.0.1 you have following line in /etc/inittab:
h1:35:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1 </dev/nulland:
[root@rac1 ~]# head /etc/init.d/init.ohasd
#!/bin/sh
# Copyright (c) 2001, 2009, Oracle and/or its affiliates. All rights reserved.
# init.ohasd - Control script for the Oracle HA services daemon
# This script is invoked by the init system
ORA_CRS_HOME=/u01/app/11.2.0/grid
export ORA_CRS_HOMEEdited by: P. Forstmann on 11 févr. 2013 18:45

Oracle 10G Db Starts-up After Server Reboot, BUT Goes DOWN After Some Time

Hi All,
I am really puzzled over this one. I have couple of servers running DB on them and I have used scripts to auto-enable them when server(s) reboot.
But there is one server where I see this funny behavior.
The DB comes-up after server reboot.
I can verify that in the startup logs and some more logs that I created.
I can see that LISTENER is able to communicate also.
But after a while, the DB shuts-down....!!
I have checked all the places I could. I have also tried to see the difference between this server and others (I did not install this one), but can not see any difference.
Is there anyway to find out (log) what is shutting down the DB??
Any help will be much appreciated as I am at my wits end.
Following is snap-shot from my logs:
Fri Mar 16 20:42:29 EDT 2007
Running dbstart.
Done with starting all, let's check status...
Fri Mar 16 20:42:42 EDT 2007
LSNRCTL for Solaris: Version 10.2.0.1.0 - Production on 16-MAR-2007 20:42:42
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Solaris: Version 10.2.0.1.0 - Production
Start Date 16-MAR-2007 00:46:56
Uptime 0 days 19 hr. 55 min. 46 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/product/10.2.0/Db_1/network/admin/listener.ora
Listener Log File /oracle/product/10.2.0/Db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.103.253.50)(PORT=1521)))
Services Summary...
Service "orcl" has 2 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orcl_XPT" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully
Current Status:
# date
Fri Mar 16 21:30:40 EDT 2007
# su - oracle -c "lsnrctl status"
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
LSNRCTL for Solaris: Version 10.2.0.1.0 - Production on 16-MAR-2007 21:30:53
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Solaris Error: 146: Connection refused
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.103.253.50)(PORT=1521)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Solaris Error: 146: Connection refused

I was just looking at that.. Thanks for the tip.
Following is what I see. But not sure what does it tell me?? Please help......
From alert_orcl.log:
<snip>
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Fri Mar 16 20:42:41 2007
Errors in file /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15
Fri Mar 16 20:42:42 2007
Completed: ALTER DATABASE OPEN
From /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
# cat /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
/oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
Oracle Database 10g Release 10.2.0.1.0 - 64bit Production
ORACLE_HOME = /oracle/product/10.2.0/Db_1
System name: SunOS
Node name: gcars0j6
Release: 5.10
Version: Generic_118833-24
Machine: sun4u
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 15
Unix process pid: 7700, image: oracle@gcars0j6 (TNS V1-V3)
*** SERVICE NAME:() 2007-03-16 20:42:37.548
*** SESSION ID:(159.3) 2007-03-16 20:42:37.548
Thread 1 checkpoint: logseq 255, block 2, scn 8602014
cache-low rba: logseq 255, block 3
on-disk rba: logseq 255, block 767, scn 8602399
start recovery at logseq 255, block 3, scn 0
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 382Kb in 0.16s => 2.33 Mb/sec
Total physical reads: 4096Kb
Longest record: 3Kb, moves: 0/1066 (0%)
Change moves: 1/8 (12%), moved: 0Mb
Longest LWN: 308Kb, moves: 0/29 (0%), moved: 0Mb
Last redo scn: 0x0000.0083431e (8602398)
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 1
Average hash chain = 149/149 = 1.0
Max compares per lookup = 1
Avg compares per lookup = 1925/2083 = 0.9
*** 2007-03-16 20:42:37.702
KCRA: start recovery claims for 149 data blocks
*** 2007-03-16 20:42:37.705
KCRA: blocks processed = 149/149, claimed = 149, eliminated = 0
*** 2007-03-16 20:42:37.706
Recovery of Online Redo Log: Thread 1 Group 2 Seq 255 Reading mem 0
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 1
Average hash chain = 149/149 = 1.0
Max compares per lookup = 1
Avg compares per lookup = 2054/2074 = 1.0
Error in executing triggers on database startup
*** 2007-03-16 20:42:41.963
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15

Call park music on hold reverts to default after server reboot

Hello,
We are noticing that if you define Music on hold for the Park service, the call park music on hold reverts to default sound after server reboot. (all systems we've tested do this)
Anyone using park music on hold that can verify one way or the other?
Thanks,
+Say thanks and observe basic forum courtesy:
+If this post answered your question, Mark As Answer
+If this post was helpful, Vote as Helpful
windowspbx blog: my thots/howtos
see/submit Lync suggestions here: simple and public

We have tested it and we have the same result. Hope the next update will resolve this problem.

AV Agent and OS Collector after server reboot

We are using Oracle AV Server and AV Agent on version 10.2.0.3.2 with Bundle Patch #1.
If the target server reboots, both AV agent and OS Aud collector does not come up automatically ?
Is that a normal behavior ? or we have to do some modifications to get it automatically started.
Appreciate your guidance.
Thanks,
Viral

You could put it as a startup script, but there isn't anything already written. I call a cron script every hour to make sure that the collectors and agent is up. We had to setup trusted connections from the avagent -> avserver to start the collectors:
This is on the agent server. We call it every hour from cron.
#!/bin/ksh
export ORACLE_HOME=<you set>
export LD_LIBRARY_PATH_64=<you set>
export LD_LIBRARY_PATH=<you set>
export PATH=/bin:/usr/local/bin:/usr/bin:${ORACLE_HOME}/bin
export collector_info="<yer collector name 1>:<yer source name 1>
<yer collector name 2>:<yer source name 2>"
start_av () {
# See if av agent is running
avctl show_oc4j_status | grep not
export exit_status=${?}
# If it is not running then start it
if [ ${exit_status} -eq 0 ]; then
echo "Starting AV agent"
avctl start_oc4j
else
echo "AV agent is already running"
fi
start_collector () {
export collector_name=$1
export source_name=$2
# The collector needs to be started from the home av box
ssh <yer av server ip> /home/oracle/sh/start_collector.sh ${collector_name} ${source_name}
export exit_status=$?
if [ ${exit_status} -eq 0 ]; then
echo "The collector ${collector_name} for ${source_name} was started"
elif [ ${exit_status} -eq 99 ]; then
echo "The collector ${collector_name} for ${source_name} was already running"
else
echo "The collector ${collector_name} for ${source_name} may have an issue"
fi
start_av
for i in ${collector_info}; do
collector_name=`echo $i | awk '{ FS=":" }{ print $1 }'`
source_name=`echo $i | awk '{ FS=":" }{ print $2 }'`
start_collector ${collector_name} ${source_name}
doneThis is on your av server start_collector.sh
export ORACLE_SID=<yer sid>
export ORAENV_ASK=NO
. /usr/local/bin/oraenv 1>/dev/null 2>/dev/null
export collector_name=$1
export source_name=$2
export exit_collector_already_running=99
start_collector () {
#Check to see if the collector is already running
avctl show_collector_status     \
      -collname $collector_name \
      -srcname $source_name     \
      | grep not
export exit_status=$?
# If the collector is not running then start it
if [ $exit_status -eq 0 ]; then
avctl start_collector           \
        -collname $collector_name \
        -srcname $source_name
else
# Exit with a status that the collector is already running
exit $exit_collector_already_running
fi
start_collector

Automatically start VMs after server reboot

Hello,
I use a OVM server (3.0.3) without clustering, and I'm doing failure simulations before going to production.
When the server reboots after a electrical failure, all VM are in "offline" state, and I need to acknowledge all events before be able to start them (thanks the forum for this information).
I would like to automatically boot the VM after the reboot, is there a way to do this ?
Thanks,
TM

Have you tried to put a symlink to the vm.cfg in /etc/xen/auto? That works independent of VM Manager. I beleive VM Manager will update the machine to running in that situation. If not, at least your machines are running while you sort out the problems with VM Manager.
ln -s /OVS/Repository/<repositoryUUID>/VirtualMachines/<vmUUID>/vm.cfg /etc/xen/auto/<simplename>
Where repositoryUUID (hopefully the only one because the manager doesn't display it)
vmUUID shows as ID on the Info page for the VM
simplename is any name you like. I chose the name that shows as Name on the machine's Info page.
Let us know if the Manager figures it out OK or if you have to jump through some hoops to get it to show "running" for these VMs.

JRE SE v1.4.1_07 crashes when server reboots

Hi All, we have JRE SE v1.4.1_07 and JRE SE v1.4.0_06 installed in Citrix Servers, JRE v1.4.1_07 is required for a web browser based application. Whenever server reboots, we need to reinstall the JRE SE v1.4.1_07 to work the browser application.
is it because of multiple version on the same server or is there any other reasons?
Any help is appreciated..
Thanks.
Manoj

Hi, Thx. for response.
Why do you have to reinstall 07? We have Web Browser application which require JRE 07 as plug in to work. whenever server reboots, the application stops functioning but if reinstall the 07 version, it works fine.
Also, when you say web browser based app. It makes me
wonder why you need a JRE? Or are you saying a web
container that needs it?Yes, the application require to JRE to work.
Thanks.

Listener not starting on server reboot

for securing listener I have done the following steps:
Created a separate account and group at OS level and brought listener.ora,lsnrctl and related files/directories under this account and group.
I have secured listener by setting password (change_password,save_config followed by reload) on Oracle 8.1.7 running on HP Unix 11.11. while giving save_config the listener.ora is automatically brought under its original user and group.But I manually change it back to the account and group I created.
On server reboot listener does not start automatically.
Please help

Here is the error message, please let me know the solution:
LSNRCTL for HPUX: Version 8.1.7.4.0 - Production on 09-SEP-2007 15:17:46
(c) Copyright 1998 Oracle Corporation. All rights reserved.
Starting /....../oracle/v8/8.1.7/bin/tnslsnr: please wait...
TNSLSNR for HPUX: Version 8.1.7.4.0 - Production
System parameter file is /...../oracle/v8/8.1.7/network/admin/listener.ora
Log messages written to /......./oracle/v8/8.1.7/network/log/listener.log
Attempted to listen on: (ADDRESS=(PROTOCOL=IPC)(KEY=.......world))
TNS-12555: TNS:permission denied
TNS-12560: TNS:protocol adapter error
TNS-00525: Insufficient privilege for operation
HPUX Error: 1: Not owner

Node Manager not starting servicess after server reboot

We have WLS 10.1.3.5 with IDM/OAM(two domains in same server as its TEST environment) on Oracle Linux 5(64bit),when ever server reboots node manger is not starting managed servers.
I have enabled CrashRecoveryEnabled=true
Here is nodemanager.properties.
[oracle@oam nodemanager]$ cat nodemanager.properties
#Changed NM Listen Port
#Tue Mar 05 03:12:20 IST 2013
DomainsFile=/u01/Oracle/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
DomainsDirRemoteSharingEnabled=false
PropertiesVersion=10.3
AuthenticationEnabled=true
NodeManagerHome=/u01/Oracle/Middleware/wlserver_10.3/common/nodemanager
javaHome=/u01/Oracle/Middleware/jdk160_24
JavaHome=/u01/Oracle/Middleware/jdk160_24/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
DomainRegistrationEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/u01/Oracle/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
here is my domain information in server.
=========================
[oracle@oam nodemanager]$ cat nodemanager.domains
#Domains and directories created by Configuration Wizard
#Tue Mar 05 05:24:37 IST 2013
OAMDomain=/u01/Oracle/Middleware/user_projects/domains/OAMDomain
IDMDomain=/u01/Oracle/Middleware/user_projects/domains/IDMDomain

Hi,
Entries in nodemanager.properties looks fine, but how are you testing this functionality?
If you will stop servers monitored by nodemanager, stop nodemanager and then reboot physical server, on startup if nodemanager is configured as daemon it will start nm process but will do nothing to managed server process.
To test "CrashRecoveryEnabled=true" kill the managed server pid and then stop/kill nodemanager process. Then perform physical server reboot, now if nm is configured as daemon process server reboot will start nodemanager. Once NM is up first thing it check is the server it was monitoring earlier and if under directory $WL_HOME/servers/<server>/data/nodemanager it finds "pid" and "lck" file it checks if that pid exists and if not then go for a restart of weblogic server instance.
This has worked for me...!
Thanks,
Ranjan
http://www.middlewaresupport.wordpress.com

Random server reboots caused by _mdnsresponder

Similar Messages

Maybe you are looking for