Database restart

Hi all,
DB:Oracle 10.2.0.4
OS:windows server 2003
Recently i am facing oracle database seervices restart every friday night (same time every week) in my windows host.
i have checked, there is no scheduled tasks..like backups...etc
where can i find out why restart happening...
thanks,
dbc.

thanks kohli for your quick reply...
please find the alert logfile content while restarting.....
Shutting down instance: further logons disabled
Fri May 04 17:00:12 2012
Stopping background process QMNC
Fri May 04 17:00:13 2012
Stopping background process CJQ0
Fri May 04 17:00:14 2012
Stopping background process MMNL
Fri May 04 17:00:15 2012
Stopping background process MMON
Fri May 04 17:00:16 2012
Shutting down instance (immediate)
License high water mark = 46
Fri May 04 17:00:16 2012
Stopping Job queue slave processes
Fri May 04 17:00:16 2012
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Fri May 04 17:00:30 2012
ALTER DATABASE CLOSE NORMAL
Fri May 04 17:00:30 2012
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri May 04 17:00:31 2012
Shutting down archive processes
Archiving is disabled
Fri May 04 17:00:36 2012
ARCH shutting down
ARC1: Archival stopped
Fri May 04 17:00:41 2012
ARCH shutting down
ARC0: Archival stopped
Fri May 04 17:00:42 2012
Thread 1 closed at log sequence 22084
Successful close of redo thread 1
Fri May 04 17:00:43 2012
Completed: ALTER DATABASE CLOSE NORMAL
Fri May 04 17:00:43 2012
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Fri May 04 17:00:45 2012
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Fri May 04 17:00:45 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
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 = 150
__shared_pool_size = 113246208
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
sga_target = 612368384
control_files = D:\ORADATA\ODDP\CONTROL01.CTL, D:\ORADATA\ODDP\CONTROL02.CTL
db_block_size = 8192
__db_cache_size = 482344960
compatible = 10.2.0.3.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\ORADATA\flash_recovery_area
db_recovery_file_dest_size= 21474836480
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=ODDPXDB)
utl_file_dir = *
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ODDP\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ODDP\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ODDP\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ODDP\CDUMP
db_name = ODDP
open_cursors = 300
pga_aggregate_target = 203423744
PMON started with pid=2, OS id=9156
PSP0 started with pid=6, OS id=9248
MMAN started with pid=10, OS id=9072
DBW0 started with pid=14, OS id=10204
DBW1 started with pid=18, OS id=8664
DBW2 started with pid=22, OS id=9952
DBW3 started with pid=26, OS id=8264
LGWR started with pid=30, OS id=8732
CKPT started with pid=34, OS id=1664
SMON started with pid=38, OS id=640
RECO started with pid=42, OS id=6236
CJQ0 started with pid=46, OS id=1704
MMON started with pid=50, OS id=9340
MMNL started with pid=54, OS id=2140
Fri May 04 17:00:47 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Fri May 04 17:00:47 2012
starting up 1 shared server(s) ...
Fri May 04 17:00:47 2012
ALTER DATABASE MOUNT
Fri May 04 17:00:51 2012
Setting recovery target incarnation to 2
Fri May 04 17:00:51 2012
Successful mount of redo thread 1, with mount id 1681645503
Fri May 04 17:00:51 2012
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri May 04 17:15:52 2012
db_recovery_file_dest_size of 20480 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 May 04 17:17:53 2012
alter database open
Fri May 04 17:17:53 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=66, OS id=8996
Fri May 04 17:17:53 2012
ARC0: Archival started
Fri May 04 17:17:53 2012
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 22084
Fri May 04 17:17:53 2012
ARC0: Becoming the 'no FAL' ARCH
Fri May 04 17:17:53 2012
ARC0: Becoming the 'no SRL' ARCH
ARC1 started with pid=74, OS id=8712
Fri May 04 17:17:54 2012
ARC1: Becoming the heartbeat ARCH
Fri May 04 17:17:54 2012
Current log# 1 seq# 22084 mem# 0: D:\ORADATA\ODDP\REDO01B.ORA
Fri May 04 17:17:54 2012
Current log# 1 seq# 22084 mem# 1: C:\ORADATA\ODDP\REDO01A.LOG
Successful open of redo thread 1
Fri May 04 17:17:54 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri May 04 17:17:54 2012
SMON: enabling cache recovery
Fri May 04 17:17:55 2012
Successfully onlined Undo Tablespace 1.
Fri May 04 17:17:55 2012
SMON: enabling tx recovery
Fri May 04 17:17:55 2012
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=78, OS id=9056
Fri May 04 17:17:59 2012
Completed: alter database open

Similar Messages

Database restarting daily, why?

My RDBMS is Enterprise Edition Release 11.2.0.3.0 - 64bit Production running on RHEL 6 x86_64 running on a virtual server. Each morning at 05:58 the database restarts. Looking at the various trace files generated at that time I see messages as follows -
CELL communication is configured to use 0 interface(s):
kcrfwy: minimum sleep is 9974 usecs (overhead is 8974 usecs)
kgfmIsAppliance=0 (due to init)
There is a vktm trace file:
VKTM running at (1)millisec precision with DBRM quantum (100)ms
[Start] HighResTick = 1383573491638525
kstmrmtickcnt = 0 : ksudbrmseccnt[0] = 1383573491
kwqmnich: current time:: 13: 58: 21: 0
kwqmnich: instance no 0 repartition flag 1
kwqmnich: initialized job cache structure
*** 2013-11-04 05:58:23.677
kwqinfy: Call kwqrNondurSubInstTsk
PQQ: Skipping service checks
kgsksysstop: blocking mode (2) timestamp: 1383573500394276
kgsksysstop: successful
kgsksysresume: successful
*** 2013-11-04 05:59:14.924
PQQ: Active Services changed
PQQ: Old service table
SvcIdx SvcId Active ActDop
PQQ: New service table
SvcIdx SvcId Active ActDop
     1      1      1      0
     2      2      1      0
     3      3      1      0
     4      4      1      0
Control file enqueue hold time tracking dump at time: 1470029
1: 1140ms (rw) file: kct.c line: 2522 count: 140733193388033 total: 1140ms time: 1469406
The alert log shows the shutdown/startup and all looks normal. The audit trail file shows a connection as sysdba at this time (that is to be expected I suppose).
The vktm trace file indicates to me that the problem may be due to the virtual keeper of the time and I wondered if it is perhaps getting out of sync with the time clock on the virtual server. I spoke with one of the system administrators who suggested some checks. One is that the entry tinker panic 0 be in the /etc/ntp.conf file but I don't find that entry. The VM tools appear to be in place -
-bash-3.2$ grep "buildNr =" /usr/bin/vmware-config-tools.pl
$buildNr = '8.6.11 build-1180212';
-bash-3.2$ /sbin/lsmod | grep vm
vmmemctl 46424 0
vmci            83804 1 vsock
vmxnet                55556 0
vmxnet3               88544 0
At this point I am stuck and not sure what else to look at. I have done a bit of searching but have not found anything which seems to fit my situation. If anyone has encountered this or has any suggestions I would be most grateful.
Thank you.
Bill Wagman

I understand your desire to 'plan' and why that might normally make sense but if planning is needed before your org can change their most important passwords then you have a large, gaping security hole.
One of the key tasks that ANY organization must be able to perform AT A MOMENTS NOTICE is changing key passwords. Implicit in that task is the requisite documentation that shows the EXACT steps the need to be taken and clearly identifies ALL possible impacts (i.e. other password changes needed, batch process impacts, etc).
The IT manager, or lead DBA, should be able to put their hands on security documentation that identifies that process and the steps to implement it.
As part of the process of resolving your current issue I suggest you broach that LARGER deficiency to your management and make immediate plans to address it.

Queuing fails after database restart

Hi All
Currently we are on a test run of our application invloving advance queuing. The application involves queueing between 2 databases over a dblink.
when we create queue tables ,create queues, start queues, add subscribers, enable propogation on both db's . it works fine. but why doesnt queuing withstand a database restart.
The propogation to queues over dblinks fails , the moment i restart the databases. What could be the error .
I have to recreate all queue tables, queues, add subscribers , enable propagation all over again if i restart the db's.
My enqueuing process is initated on a trigger in a table with visibility on commit.
And i have dequeuing process on dbms_aq.listen.
kindly respond
Regards
Sushant

Check this thread:
Message Bridge - consumer count Increasing

Connection pool testing for dealing with database restarts

How do you configure the app server to test JDBC connections before handing them to the application? The app server needs to accomodate database restarts while the app is running.
We have an EAR file built with ANT (we use Eclipse 3.x to develop the app) and we use the deploy tool for getting it installed on the engine at 6.40 SP15. We have setup a datasource in the project options but I don't see how to configure it so that the engine tests JDBC connections before giving them to the application. We need to guard against database restarts and other app servers that I have used have an option that takes care of this detail. I cannot get the deploy tool help to appear due to an invalid URL being requested by the tool.

Craig,
you are right, in visual admin, it appears, any options to test a poll served connection are absent.
Remedy: In tab additional
- check expiration control and set
- connection lifetime to say 60 (seconds) and
- cleanup thread to say 30
This way, you can't fully avoid, but diminish the likelihood to catch a bad connection.
Regards
Gregor

OEM Repository Database Restarts Daily

Greetings,
I am running OEM 12.1.0.3.0 on a VM running Linux x86_64. The repository is Oracle 11.2.0.3.0 running on a separate VM host also running Linux x86_64.
On a daily basis at 05:57:21 (give or take a few seconds) my OEM repository is restarted -
Shutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
<remaining shutdown steps displayed in the alert logs>
and it immediately restarts. I am unable to determine why. The host is not restarted. I have looked at dba_jobs in the repository and see nothing running which would do this. I have looked at OEM jobs and don't see anything scheduled there which would do this. I am at a loss to explain this and am wondering if anyone else has encountered this or has an explanation. Is this expected behavior or is my setup an anomaly?
Thank you.
Bill Wagman

Bill,
This would not be an expected behaviour. If your Repository DB re-starts, then there are chances that the OMS will also re-start if it cannot access the repository DB for a long duration. This will affect console usage.
Do you not see any other errors before this shutdown?
You could also check if there are any DB trace files created around the same time.
Recommend posting this in the Database forum for further investigation.
Regards,
Smitha.

How to handle a (Oracle) database restart

Hi,
For a cold backup we stop and start the database.
When using Toplink for database access I've a problem when the database is restarted: "500 Internal Server Error: Exception [TOPLINK-4002] ... oracle.toplink.exceptions.DatabaseException ... Broken Pipe ... etc"
I there a simple solution? (Restarting J2EE App solves the problem but is not our prefered way)
How is this handled when we use BC4J?
Thanks,
Stephan van Hoof

Stephan,
Can you post the configuration you are using (e.g. app server with TL, Java Objects or EJB CMP, version of TL, with out without JDev etc.) and the steps to reproduce the issue?
Thanks,
Anuj Jain

Database Restarting

HI,
Oracle database version 9.2.0.4:
O/S Version :SuSE Linux Enterprise Server 9 (x86_64)
Around last week the database was restarting and it was showing in the log file that "Restarting background process QMN0". So what i did was I changed the AQ_TM_PROCESSES value to 0 instead of 1. Thought this would solve the problem. I had done a lot of investigation on this and only then I changed the value. Even then the issue still persits and it has made no change to the database.
Please Advice.
Successful mount of redo thread 1, with mount id 910022969
Sat Dec 12 10:23:57 2009
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Sat Dec 12 10:23:58 2009
alter database backup controlfile to trace
Sat Dec 12 10:23:58 2009
Completed: alter database backup controlfile to trace
Sat Dec 12 10:45:48 2009
alter database open
Sat Dec 12 10:45:48 2009
Thread 1 opened at log sequence 3127
Current log# 1 seq# 3127 mem# 0: /u01/app/oracle/oradata/UUM/redo_uum_01.log
Successful open of redo thread 1
Sat Dec 12 10:45:48 2009
LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
Sat Dec 12 10:45:48 2009
SMON: enabling cache recovery
Sat Dec 12 10:45:50 2009
Successfully onlined Undo Tablespace 1.
Sat Dec 12 10:45:50 2009
SMON: enabling tx recovery
Sat Dec 12 10:45:50 2009
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 17
Waiting for dispatcher 'D000' to shutdown
Waiting for shared server 'S000' to die
All dispatchers and shared servers shutdown
Tue Dec 15 12:40:50 2009
ALTER DATABASE CLOSE NORMAL
Tue Dec 15 12:40:51 2009
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Dec 15 12:40:52 2009
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 3127
Successful close of redo thread 1
Tue Dec 15 12:40:53 2009
Completed: ALTER DATABASE CLOSE NORMAL
Tue Dec 15 12:40:53 2009
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 Dec 15 12:41:00 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 1
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.6.0.
System parameters with non-default values:
processes = 600
sessions = 665
timed_statistics = TRUE
shared_pool_size = 100663296
large_pool_size = 16777216
java_pool_size = 33554432
control_files = /u01/app/oracle/oradata/UUM/UUM01.ctl, /opt/oracle/admin/UUM/UUM02.ctl, /u01/app/oracle/oradata/UUM/UUM03.ctl
db_block_size = 8192
db_cache_size = 50331648
compatible = 9.2.0.0.0
log_checkpoint_interval = 10000
db_file_multiblock_read_count= 16
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 900
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = UUM
dispatchers = (PROTOCOL=TCP) (SERVICE=UUMXDB)
job_queue_processes = 1
hash_join_enabled = TRUE
background_dump_dest = /opt/oracle/admin/UUM/bdump
user_dump_dest = /opt/oracle/admin/UUM/udump
core_dump_dest = /opt/oracle/admin/UUM/cdump
sort_area_size = 1048576
db_name = UUM
open_cursors = 300
star_transformation_enabled= FALSE
optimizer_index_cost_adj = 10
optimizer_index_caching = 80
query_rewrite_enabled = FALSE
pga_aggregate_target = 59768832
aq_tm_processes = 0
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
RECO started with pid=7
SMON started with pid=6
Tue Dec 15 12:41:01 2009
starting up 1 shared server(s) ...
CJQ0 started with pid=8
Tue Dec 15 12:41:02 2009
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Dec 15 12:41:02 2009
ALTER DATABASE MOUNT
Tue Dec 15 12:41:06 2009
Successful mount of redo thread 1, with mount id 910318558
Tue Dec 15 12:41:06 2009
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Tue Dec 15 12:41:08 2009
alter database backup controlfile to trace
Tue Dec 15 12:41:08 2009
Completed: alter database backup controlfile to trace
Tue Dec 15 16:42:35 2009
alter database open
Tue Dec 15 16:42:36 2009
Thread 1 opened at log sequence 3127
Current log# 1 seq# 3127 mem# 0: /u01/app/oracle/oradata/UUM/redo_uum_01.log
Successful open of redo thread 1
Tue Dec 15 16:42:36 2009
LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
Tue Dec 15 16:42:36 2009
SMON: enabling cache recovery
Tue Dec 15 16:42:39 2009
Successfully onlined Undo Tablespace 1.
Tue Dec 15 16:42:39 2009
SMON: enabling tx recovery
Tue Dec 15 16:42:39 2009
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Thanks

Are there any messages in os logs(/var/messages) or even in background process logs.

Restart on primary database restarts the recovery process on standby

We have a dataguar broker configuration running in maximum perfromance mode.
Every time we start the primary database, the recovery process on standby gets restarted.
I can consistently reproduce teh problem. Looks like expected behaviour.
Even if standby is in read only mode and restart the primary database it bring the database back in recovery mode.
Any explanation why oracle needs to do it?

Neil_Arul wrote:
We have a dataguar broker configuration running in maximum perfromance mode.
Every time we start the primary database, the recovery process on standby gets restarted.
I can consistently reproduce teh problem. Looks like expected behaviour.
Even if standby is in read only mode and restart the primary database it bring the database back in recovery mode.
Any explanation why oracle needs to do it?Yes, When you enable broker it very common behaviour.
When ever you bounce the database also MRP process will be started automatically.
By disabling broker you can avoid automatic startup, BTW Standby should be in recovery mode, i think no need to worry on this.
If you want to disable as per time, you can disable it as below
ALTER SYSTEM SET DG_BROKER_START=FALSE ;
Total Questions: 3 (3 unresolved)
Close the threads when you feel its answered, Keep the forum clean.
Edited by: CKPT on Feb 15, 2012 12:57 PM

Single Query suddenly goes slow until database restart or query change

Hello all,
Configuration I'm using is Oracle 10g EE 10.1.0.4.0 on Windows 2003 Server
I have performance issue with one single query. The query is called using dbExpress from Delphi application.
Since a month, almost every week this query starts going VERY slow. Usually it executes in a 0.5-1 second, but when it's slowed down, it takes approx. 4-5 minutes to execute.
The query runs on a single table (~4 000 000 rows) and runs on primary index. The index itself consists of 5 fields - the query uses the first 4 of them. I know it's not a good design but restructuring the table/index is out of question, AFAIK.
Until now, I figured out two ways to speed things up. The first and obvious is to restart the server or shut/start the database. It works. For a week. Then we're back at first square.
The second way is some kind of a mystery to me: If I change the query a little bit, never mind how - for example, adding 'and (1=1)' in the clause, after deploying the application, it starts running fast. Again for a week or so.
I've attached an jpeg showing the explain plans on slow and fast executing queries. They look almost the same.
I'm running out of ideas for now. It's very annoying (and unsafe) to restart the machine on a week basis. Thus any help is greatly appreciated.
Things I've done so far:
- installed last service packs from Oracle and Microsoft.
- tried different versions of dbexpora.dll.
- Regularly gathered and estimated statistics and analyzings.
- Made sure that the server is not under heavy load (antiviruses, firewalls, archive loggers are stopped or uninstalled for a while).
- made sure that there is enough free space on hard disks.
- the disk array itself is in good health - defragmented, HDD tools doesn't find anything suspicious.
Final thoughts: Maybe the sql cache is going overloaded and someway stops executing the query. That's why when I restart the machine or change the query clause insignificantly, it starts running fast. I took a peek on v$sql and v$sqlarea but there is nothing special, and honestly, I'm not very familiar reading the values in this view - I'm just comparing the values returned by this query with the others - they look similar.
Anyway, if someone could help, it would be great.
Regards,
Ivan
Screenshots showing the explain plans for slow and fast query:
Image: !http://img254.imageshack.us/img254/6674/queryr.jpg!

Sorry for the incomplete information. I tried to gather the mentioned in your second link additional data. Unfortunately, I cannot find the TKPROF utility - it's not in the bin directory, neither in any other folder. Guess it's not installed at all.
About rewriting the query, suggested in the first link you gave: it's so simple and clear that it should not be rewriten. As I mentioned before, every time I change the query even a little bit, it starts running well for a couple of days.
Anyway, here are the stats I've just gathered. Unfortunately, now the query performs well and I'm not able to give you stats, showing the slowed down query.
These are the parameters relevant to the optimizer:
SQL> show parameter optimizer
NAME TYPE VALUE
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 10.1.0.4
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
SQL> show parameter db_file_multi
NAME TYPE VALUE
db_file_multiblock_read_count integer 32
SQL> show parameter db_block_size
NAME TYPE VALUE
db_block_size integer 8192
SQL> show parameter cursor_sharing
NAME TYPE VALUE
cursor_sharing string EXACT
Screenshots of explain plan is posted in my first post - both for fast and slow executed query.
output of SQL_Plus AUTOTRACE including the TIMING information:
SQL> set autotrace traceonly arraysize 1000
SQL> SELECT * FROM "AOPERITEM"
WHERE (FOPER = 201)
AND (FCLIENT = 1)
AND (FDATEOPER = '2009-10-28')
AND (FNUMOPER = 95532)
Execution Plan
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)|
| 0 | SELECT STATEMENT | | 1 | 132 | 5 (0)|
| 1 | TABLE ACCESS BY INDEX ROWID| AOPERITEM | 1 | 132 | 5 (0)|
| 2 | INDEX RANGE SCAN | AOPERITEM_IDX | 1 | | 4 (0)|
Note
- 'PLAN_TABLE' is old version
Statistics
1 recursive calls
0 db block gets
9 consistent gets
0 physical reads
0 redo size
3098 bytes sent via SQL*Net to client
369 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
4 rows processed
The DBMS_XPLAN.DISPLAY_CURSOR output:
SQL> select /*+ gather_plan_statistics */
* FROM "AOPERITEM"
WHERE (FOPER = 201)
AND (FCLIENT = 1)
AND (FDATEOPER = '2009-10-28')
AND (FNUMOPER = 95532)
Execution Plan
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)|
| 0 | SELECT STATEMENT | | 1 | 132 | 5 (0)|
| 1 | TABLE ACCESS BY INDEX ROWID| AOPERITEM | 1 | 132 | 5 (0)|
| 2 | INDEX RANGE SCAN | AOPERITEM_IDX | 1 | | 4 (0)|
Note
- 'PLAN_TABLE' is old version
Statistics
0 recursive calls
0 db block gets
9 consistent gets
4 physical reads
0 redo size
2937 bytes sent via SQL*Net to client
369 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
4 rows processed
PS: I'm not a DBA myself, I'm just trying to find a solution to this problem.
Thanks in advance.

Oracle Streams not working after database restart

Hi,
I am new at this so hope that somebody out there can give me some guidance.. I have managed to setup the streams properly on both my 10g database as per the scripts given in StreamsAdminConfig.sql and StreamsSetup.sql.. It worked beautifully on both direction.
However when i restarted DB1.. suddenly the replication become just one directional only, namely from DB1 -> DB2. I have tried to do DBMS_STREAMS_ADM.STOP_APPLY, STOP_CAPTURE, START_APPLY, START_CAPTURE many times on both DB1 and DB2 but still it works only in one direction.
Later I tried to restart both databases and not it does not work at all (both direction).. Tried restarting the apply and capture process many times too but get no success. Any idea what I could check or try to find out what when wrong. Thanks.
regards,
thamch

trying viewing the status and error messages in views
dba_apply, dba_apply_error, dba_capture and dba_propagation at both databases.

Error in reports after database restart

Hi,
I am making reports using OBI with oracle 10.1.0 . I made some charts, pivot tables
and some graphs. these are working fine until i restart the database. when i restart the
data base the tables are show again at dash board but all pictorial type reports not work
untill i make them again.
it gives me error like
No connection could be made because the target machine actively refused it. [Socket:888]while table by the same query is giving result. only graphical thing give error even after i
redraw them.
Thanks

Step 1: Create Cachepurge.txt file with following command.
call SAPurgeAllCache();
Step 2: Tranfer this Cachepurge.txt file to this path (It can copy to
anywhere)
D:\oracleBI\server\Bin
Step 3:
Go to Command Prompt
cd D:\oracleBI\server\Bin
nqcmd -d Analyticsweb -u Administrator -p Administrator -s D:\oracleBI\server\Bin\Cachepurge.txt -o D:\output.txt
-u --> User
-p --> Password
If you install OBIEE in C: please replace D: with C:
Thanks,
Chandra

Reconnect to portal database after database restart

Hi,
After having seen a 24/7 EP system in production for a while, there is one contributing factor which is causing more downtime than we would like (even though the downtime is very small).
When ever the portal database is restarted or we loose the network connection, the SAP J2EE (and hence EP) is not able to reconnect to the database (as you would expect from such a mature product). The forces us to take down the entire cluster (yes the cluster is big and takes a lot of time to restart) and then take it up again.
An OSS has been open (and been through development) and the verdict is that it cannot be done.
However, I don't believe them. Some of you SAP expert here must know of some very cleaver hack to get this working.
If you have any ideas or experience with this, please do not hesitate to post it.

Managed to find some undocumented command that did the trick.
1. Telnet to the administration console (port 50008 is standard ?)
2. Login as administrator
3. Run the lsc command in order to get the cluster id of an application node
4. Change the active node to an application node
>jump <clusterId>
5. Add the dbpool command set
>add dbpool
6. Close the database pool
>close_pool <poolname> -force
7. Open the database pool
>open_pool <poolname>
From the SAP J2EE administration console in the dbpool there seems to be a functionality for closing and opening the pool, but this doesn't work, at least not in PL21 (maybe it doesn't force the connections to close)
Message was edited by: Dagfinn Parnas

AQ Subscriber not reciving notification after database restart

Hi All,
I am currently working on moving some code from two synchronous processes to be asynchronous (not part of critical code path), to do this I have been using one Advanced Queue with two PLSQL registered subscribers.
when we first moved the code into test it was working fine and the data would be processed from the queue quite quickly.
however we then had to restart the database for another reason and after that I noticed that queue was slowly building up with nothing moving from the "READY" state.
having a look at aq$<queue_table>s the two subscribers are still shown and it appears like the user id still has the correct grants and priviledges. I have also checked to make sure that the aqtm_processes is still > 0 and that the QMNC and EMN0 backgroud processes are in v$bgprocess.
Can anybody else suggest what i might have missed? I do not want to have to drop and recreate the queue and subscribers whenever the database needs to come down.
Also I know if the subscriber was down and then bought back up it would not process the backlog but is there anyway of getting it to do this?
almost forgot to mention we are running:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit
Cheers,
Chris

Hi,
I had not set the paramater the DBA had set it and i think their reasoning was:
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14257/componet.htm#sthref339]
"Oracle strongly recommends that you do NOT set AQ_TM_PROCESSES = 0"
although reading a few lines up from there:
"Oracle recommends, however, that you leave the AQ_TM_PROCESSES parameter unspecified and let the system autotune"
As there is another planned outage this weekend i will try resetting the paramater to see if the queues are still dequeueing correctly:
alter system reset AQ_TM_PROCESSES scope=spfile sid='*'
If they are not dequeueing I will try stopping and starting them however I would prefer not to have to do this as then whenever a new queue is introduced with subscribers we would need to add to the scripts run after db startup.
I did find out that removing the subscriber and then recreating it will cause the subscribers to work again but i would prefer to not have to do this after every db restart.
Thanks for pointing me to the AQ_TM_PROCESSES and i will see if that helps :)

Refreshing DBCP following database restarts

My DBA needed to restart the database server while I was away on leave. The result of which was a Broken Pipe error being displayed to the users of one my web applications. I believe others have experienced the same problem (http://freeroller.net/comments/founder_chen/Weblog/commons_dbcp_pool_broken_pipe).
Does anyone know a way of being able to recover from this error without having to restart the web application? Is there a way of refreshing the connection pool automatically when this error is encountered?
I am using Tomcat and Oracle via the Oracle JDBC driver.
Thanks,
Pete

Try to add a validation query on your connection pool and to set the testOnBorrw parameter to true.
Haven't test it but it should work...
Hi

System Crash and Database Restart

Hi,
I have a CRM 2007 system with MaxDB 7.7.
The system had an unplanned restart during the night.
Now I have reboot and I am trying to get the database back online.
Any dbbcli command I run such as db_state or db_online such as
dbmcli -n lsadc1 -d DC1 -u SUPERDBA,xxxxxxx db_online
just returns with the message:
"Error! Connection failed to node lsadc1 for database DC1:
Connection broken"
Some dbmcli commands do work such as:
E:\sapdb\DC1\db\pgm>dbmcli version
OK
version,os,dbroot,logon,code,swap
"7.7.02","WIN32","E:\sapdb\DC1\db",True,ASCII,2
Can anyone give an information on this?
Thanks.
Edited by: Peter O'Hara on Oct 30, 2008 2:02 PM
Edited by: Peter O'Hara on Oct 30, 2008 2:03 PM
A bit more information on this.
I have found that if I run Xserver in the foreground and use the dbmcli command with an IP address rather than the server name, Xserver displays the following message:
"18456 ERROR: Could not read from 'teo110_PipeBase::eo110_ReadPipe' pipe, rc = 109"
Thanks again.
Peter

Hi Peter,
as you're a SAP customer, please do open a support message for this.
regards,
Lars

Database restart

Similar Messages

Maybe you are looking for