Sqlplus freezing [message #674331] |
Mon, 21 January 2019 11:28 |
|
Adryana87
Messages: 4 Registered: January 2019
|
Junior Member |
|
|
Hello !
I have installed Oracle EBS with an oracle database vers. 11.1.0.7. I have a server for the application and a different one for the database. Both servers are in a virtual infrastructure.
Since the install, my database machine does not work from 8.00 am until 12.00 pm. Meaning:
- I start the database in open mode
- after that, if the time is before 12.00 pm then it freezes ... meaning that any new connection is pending indefinetely ...
- if the time is after 12.00 pm then everything works perfect
I have tried to
- look in the alert log
- use oradebug to debug the pending process
But nothing seems to work ... it still remains i sqlplus / as sysdba ... until 12.00 pm.
Even if I change the date ... still it does not work.
Do you have any possible explanation for this ?
Or what should I do to correct the problem ?
On the database machine ... I only have the database installed ... nothjng else.
Thanks !
|
|
|
|
|
|
|
|
Re: Sqlplus freezing [message #674525 is a reply to message #674487] |
Thu, 31 January 2019 04:30 |
|
Adryana87
Messages: 4 Registered: January 2019
|
Junior Member |
|
|
<code>
ALTER DATABASE MOUNT
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 357612571
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Tue Jan 29 09:23:52 2019
OS Pid: 27932 executed alter system set events '10046 trace name context forever, level 8'
alter database open
Beginning crash recovery of 1 threads
parallel recovery started with 8 processes
Started redo scan
Completed redo scan
5 redo blocks read, 2 data blocks need recovery
Started redo application at
Thread 1: logseq 76, block 486330
Recovery of Online Redo Log: Thread 1 Group 2 Seq 76 Reading mem 0
Mem# 0: /u01/app/oracle/SERVER/db/apps_st/data/log02a.dbf
Mem# 1: /u01/app/oracle/SERVER/db/apps_st/data/log02b.dbf
Completed redo application of 0.00MB
Completed crash recovery at
Thread 1: logseq 76, block 486335, scn 5965140940293
2 data blocks read, 2 data blocks written, 5 redo blocks read
Tue Jan 29 09:24:01 2019
Thread 1 advanced to log sequence 77 (thread open)
Thread 1 opened at log sequence 77
Current log# 1 seq# 77 mem# 0: /u01/app/oracle/SERVER/db/apps_st/data/log01a.dbf
Current log# 1 seq# 77 mem# 1: /u01/app/oracle/SERVER/db/apps_st/data/log01b.dbf
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Jan 29 09:24:01 2019
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 368.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
Opening with internal Resource Manager plan : on 2 X 0 NUMA system
Starting background process FBDA
Tue Jan 29 09:24:01 2019
FBDA started with pid=40, OS id=27968
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Tue Jan 29 09:24:01 2019
QMNC started with pid=42, OS id=27976
Tue Jan 29 09:24:02 2019
Completed: alter database open
Tue Jan 29 09:24:03 2019
Incremental checkpoint up to RBA [0x4d.3.0], current log tail at RBA [0x4d.81.0]
Tue Jan 29 09:24:04 2019
Starting background process CJQ0
Tue Jan 29 09:24:04 2019
CJQ0 started with pid=44, OS id=28004
OS Pid: 27932 executed alter system set events '10046 trace name context forever, level 8'
Setting Resource Manager plan SCHEDULER[0x72F77]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Tue Jan 29 09:29:02 2019
Starting background process SMCO
Tue Jan 29 09:29:02 2019
SMCO started with pid=32, OS id=28033
</code>
|
|
|
Re: Sqlplus freezing [message #674528 is a reply to message #674525] |
Thu, 31 January 2019 06:33 |
|
EdStevens
Messages: 1376 Registered: September 2013
|
Senior Member |
|
|
Adryana87 wrote on Thu, 31 January 2019 04:30
<code>
ALTER DATABASE MOUNT
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 357612571
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Tue Jan 29 09:23:52 2019
OS Pid: 27932 executed alter system set events '10046 trace name context forever, level 8'
alter database open
Beginning crash recovery of 1 threads
parallel recovery started with 8 processes
Started redo scan
Completed redo scan
5 redo blocks read, 2 data blocks need recovery
Started redo application at
Thread 1: logseq 76, block 486330
Recovery of Online Redo Log: Thread 1 Group 2 Seq 76 Reading mem 0
Mem# 0: /u01/app/oracle/SERVER/db/apps_st/data/log02a.dbf
Mem# 1: /u01/app/oracle/SERVER/db/apps_st/data/log02b.dbf
Completed redo application of 0.00MB
Completed crash recovery at
</code>
So your startup did a crash recovery. Why did the database crash? Why are you having to restart it during normal business hours?
Perhaps we should see the last several lines of the alert log prior to your restarting the db.
[Updated on: Thu, 31 January 2019 06:34] Report message to a moderator
|
|
|
Re: Sqlplus freezing [message #674529 is a reply to message #674528] |
Thu, 31 January 2019 08:30 |
joy_division
Messages: 4963 Registered: February 2005 Location: East Coast USA
|
Senior Member |
|
|
Maybe he is shutting the database daily and when I say shutting, I mean hard stopping it it by pulling out the plug or something.
|
|
|
Re: Sqlplus freezing [message #674555 is a reply to message #674529] |
Fri, 01 February 2019 08:25 |
|
EdStevens
Messages: 1376 Registered: September 2013
|
Senior Member |
|
|
joy_division wrote on Thu, 31 January 2019 08:30Maybe he is shutting the database daily and when I say shutting, I mean hard stopping it it by pulling out the plug or something.
Or every night the cleaning lady is plugging her vacuum cleaner into a spare socket on the UPS . . . ("At Farmers, we know a lot because we've seen a lot")
|
|
|