XE Database Dead?
Hello. I'm not very knowledgeable when it comes to DBA work, but I've hit a snag and would appreciate a little advice. I have an Oracle XE install on my home computer for keeping track of business receipts and such. Recently I couldn't connect to APEX and started looking into it. When I tried to connect with SQL+, I would get the message:
ERROR:
OR-01033: ORACLE initialization or shutdown in progress
So I stopped and started the DB, checked to see the listener service was going, and still have the issue. I checked my alert_xe.log file, and it's... huge. Attached at the bottom, I included a fragment of my log file that consists of the last recent timestamp.
I do have a script that runs on my computer that does an EXP every night on my schema, but if I try an IMP, I get the same message (which makes sense since my DB apparently isn't running).
What would be your suggestions? I wanted some advice before I uninstalled and re-installed then imported my dmp backups.
Thanks to any necromancers who can help me bring this back from the dead!
Kerry.
Dump file e:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Thu Oct 29 20:40:40 2009
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 2
CPU : 1 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:211M/511M, Ph+PgF:1012M/1247M, VA:1945M/2047M
Thu Oct 29 20:40:40 2009
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 =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Thu Oct 29 20:40:52 2009
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 104857600
__large_pool_size = 8388608
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = E:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 146800640
control_files = E:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 25165824
compatible = 10.2.0.1.0
db_recovery_file_dest = E:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
job_queue_processes = 4
audit_file_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 41943040
PSP0 started with pid=3, OS id=2988
MMAN started with pid=4, OS id=2992
PMON started with pid=2, OS id=2984
DBW0 started with pid=5, OS id=3004
LGWR started with pid=6, OS id=3008
CKPT started with pid=7, OS id=3012
SMON started with pid=8, OS id=3016
RECO started with pid=9, OS id=3020
CJQ0 started with pid=10, OS id=3024
MMON started with pid=11, OS id=3028
MMNL started with pid=12, OS id=3032
Thu Oct 29 20:40:55 2009
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Thu Oct 29 20:41:00 2009
alter database mount exclusive
Thu Oct 29 20:41:05 2009
Setting recovery target incarnation to 2
Thu Oct 29 20:41:05 2009
Successful mount of redo thread 1, with mount id 2582644764
Thu Oct 29 20:41:05 2009
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Thu Oct 29 20:41:05 2009
alter database open
Thu Oct 29 20:41:06 2009
Beginning crash recovery of 1 threads
Thu Oct 29 20:41:06 2009
Started redo scan
Thu Oct 29 20:41:07 2009
Completed redo scan
9180 redo blocks read, 514 data blocks need recovery
Thu Oct 29 20:41:07 2009
Started redo application at
Thread 1: logseq 797, block 5520
Thu Oct 29 20:41:09 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 797 Reading mem 0
Mem# 0 errs 0: E:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_2MXYQN2G_.LOG
RECOVERY OF THREAD 1 STUCK AT BLOCK 28 OF FILE 2
Thu Oct 29 20:41:11 2009
Aborting crash recovery due to error 1172
Thu Oct 29 20:41:11 2009
Errors in file e:\oraclexe\app\oracle\admin\xe\udump\xe_ora_3080.trc:
ORA-01172: recovery of thread 1 stuck at block 28 of file 2
ORA-01151: use media recovery to recover block, restore backup if needed
ORA-1172 signalled during: alter database open...
Thu Oct 29 20:55:05 2009
db_recovery_file_dest_size of 10240 MB is 0.98% 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.
Thu Oct 29 22:50:17 2009
WARNING: inbound connection timed out (ORA-3136)
Billy Verreynne wrote:
Kamran Agayev A. wrote:
Let it be a lesson for you to take RMAN backup of your database and to be able to recover your database from almost any situation you areOn XE.. by an end-user with very little to no Oracle experience, never mind DBA experience!? Come on! That is a totally unrealistic expectation on your part.
Rather think how you can assist an end-user with an XE database to make regular backups of his database in case of a problem. Be constructive instead of pointing a finger and go "+lesson must be learned+".
What do you think he should be doing for backups? Run schema exports? If so, how does he backup APEX applications? DB exports? Rman? Run the database in archive log mode?
Remember, that XE is fully an end-user environment. That is the market that Oracle choose to aim XE at.. and that is the market that our "solutions" offered here should be aimed at.Hi Billy
As it's written in doc which Forstmann has suggested, it's possible to use RMAN in XE database. You're right, may be it's not so simple to make backups directly from RMAN utility, but it's possible:
In Oracle Database XE, the database backup and recovery facility is based upon the Recovery Manager (RMAN) utility that is integrated into the database. Although there is an RMAN command line client similar to SQL Command Line, you do not need to interact with it directly to back up or restore your database. Oracle Database XE includes backup and restore scripts that you access using menu choices on your desktop. These scripts perform a full backup and restore of the entire database, and store backup files in the flash recovery area
Just my 2 cents
P.S.By google-ing I've found a blog post for backing up XE and APEX. Hope this article might be helpful for OP
http://beyondoracle.wordpress.com/2008/06/19/basic-oraclexe-apex-backup/
Edited by: Kamran Agayev A. on Oct 30, 2009 12:16 PM
Similar Messages
-
Hello guys
I have oracle 8i databse under windows NT.It suddenly stop responding!!!!.I'm obliged to restart server.
Any idea what can cause such problem.Like Os or lack of space.I check log file find nothing informative.
any idea
regardsIf the volume that contains the log or archive logs is full, the database will halt until space becomes available.
-
How to clean the dead sessions in the database?
Hi,
sqlldr user/passwd@dbtns DIRECT=TRUE SKIP_UNUSABLE_INDEXES=TRUE SKIP_INDEX_MAINTENANCE=FALSE control="test.ctl"
3M records
The OS shutdown when i sqlldr, and start another sqlldr into the same table
but the table is locked.
sqlldr failed
SQL*Loader-951: Error calling once/load initialization
ORA-00604: error occurred at recursive SQL level 1
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
how to use ORACLE system maintenance procedure to clear the database dead session?
Which procedure?
I don't want to use the solution:
alter system kill sessionHI..
What is the status of the session in V$sesison view.Does the session exist.
COLUMN username FORMAT A15
col osuser for a15
col module for a15
COLUMN machine FORMAT A30
col program for a20
COLUMN logon_time FORMAT A20
SELECT NVL(s.username, '(oracle)') AS username,
s.osuser,
s.sid,
s.serial#,
p.spid,
s.status,
s.module,
s.terminal,
s.machine,
s.program,
TO_CHAR(s.logon_Time,'DD-MON-YYYY HH24:MI:SS') AS logon_time
FROM v$session s,
v$process p
WHERE s.paddr = p.addr
and AND s.status = 'ACTIVE'
ORDER BY s.username, s.osuser;Anand -
Is the JIRA bug database dead/EOLd?
I'm unable to comment on existing bugs.
is this a sign that adobe doesn't care about bug reports from their users? is this a sign that they're planning on killing the flash platform?https://bugbase.adobe.com
-
NON-transactional session bean access entity bean
We are currently profiling our product using Borland OptmizeIt tool, and we
found some interesting issues. Due to our design, we have many session beans which
are non transactional, and these session beans will access entity beans to do
the reading operations, such as getWeight, getRate, since it's read only, there
is no need to do transaction commit stuff which really takes time, this could
be seen through the profile. I know weblogic support readonly entity bean, but
it seems that it only has benefit on ejbLoad call, my test program shows that
weblogic still creates local transaction even I specified it as transaction not
supported, and Transaction.commit() will always be called in postInvoke(), from
the profile, we got that for a single method call, such as getRate(), 80% time
spent on postInvoke(), any suggestion on this? BTW, most of our entity beans are
using Exclusive lock, that's the reason that we use non-transactional session
bean to avoid dead lock problem.
ThanksSlava,
Thanks for the link, actually I read it before, and following is what I extracted
it from the doc:
<weblogic-doc>
Do not set db-is-shared to "false" if you set the entity bean's concurrency
strategy to the "Database" option. If you do, WebLogic Server will ignore the
db-is-shared setting.
</weblogic-doc>
Thanks
"Slava Imeshev" <[email protected]> wrote:
Hi Jinsong,
You may want to read this to get more detailed explanation
on db-is-shared (cache-between-transactions for 7.0):
http://e-docs.bea.com/wls/docs61/ejb/EJB_environment.html#1127563
Let me know if you have any questions.
Regards,
Slava Imeshev
"Jinsong HU" <[email protected]> wrote in message
news:[email protected]...
Thanks.
But it's still not clear to me in db-is-shared setting, if I specifiedentity
lock as database lock, I assumed db-is-shared is useless, because foreach
new
transaction, entity bean will reload data anyway. Correct me if I amwrong.
Jinsong
"Slava Imeshev" <[email protected]> wrote:
Jinsong,
See my answers inline.
"Jinsong Hu" <[email protected]> wrote in message
news:[email protected]...
Hi Slava,
Thanks for your reply, actually, I agree with you, we need to
review
our db
schema and seperate business logic to avoid db lock. I can not say,guys,
we need
to change this and that, since it's a big application and developedsince
EJB1.0
spec, I think they are afraid to do such a big change.Total rewrite is the worst thing that can happen to an app. The
better aproach would be identifying the most critical piece and
make a surgery on it.
Following are questions in my mind:
(1) I think there should be many companies using weblogic serverto
develop
large enterprise applications, I am just wondering what's the maintransaction/lock
mechanism that is used? Transional session / database lock,
db-is-shared
entity
I can't say for the whole community, as for my experience the standard
usage patthern is session fasades calling Entity EJBs while having
Required TX attribute plus plain transacted JDBC calls for bulk
reads or inserts.
is the dominant one? It seems that if you speficy database lock,
the
db-is-shared
should be true, right?Basically it's not true. One will need db-is-shared only if thereare
changes
to the database done from outside of the app server.
(2) For RO bean, if I specify read-idle-timeout to 0, it shouldonly
load
once at the first use time, right?I assume read-timeout-seconds was meant. That's right, but if
an application constantly reads new RO data, RO beans will be
constantly dropped from cache and new ones will be loaded.
You may want to looks at server console to see if there's a lot
of passivation for RO beans.
(3) For clustering part, have anyone use it in real enterpriseapplication?
My concern, since database lock is the only way to choose, how aboutthe
affect
of ejbLoad to performance, since most transactions are short live,if high
volume
transactions are in processing, I am just scared to death about
the
ejbLoad overhead.
ejbLoad is a part of bean's lifecycle, how would you be scared ofit?
If ejbLoads take too much time, it could be a good idea to profile
used SQLs. Right index optimization can make huge difference.
Also you may want cosider using CMP beans to let weblogic
take care about load optimization.
(4) If using Optimization lock, all the ejbStore need to do
version
check
or timestamp check, right? How about this overhead?As for optimistic concurrency, it performs quite well as you can
use lighter isolation levels.
HTH,
Slava Imeshev
"Jinsong Hu" <[email protected]> wrote in message
news:[email protected]...
We are using Exclusive Lock for entity bean, because of we do
not
want
to
load
data in each new transaction. If we use Database lock, that means
we
dedicate
data access calls to database, if database deadlock happens,
it's
hard
to
detect,
while using Exclusive lock, we could detect this dead lock in
container
level.
The problem is, using Exclusive concurrency mode you serialize
access to data represented by the bean. This aproach has negative
effect on ablity of application to process concurrent requests.As
a
result the app may have performance problems under load.
Actually, at the beginnning, we did use database lock and usingtransactional
The fact that you had database deadlocking issues tells that
application logic / database schema may need some review.
Normally to avoid deadlocking it's good to group database
operations mixing in updattes and inserts into one place so
that db locking sequence is not spreaded in time. Moving to
forced serialized data access just hides design/implementation
problems.
session bean, but the database dead lock and frequent ejbLoad
really
kill
us,
so we decided to move to use Exclusive lock and to avoid dead
lock,
we
change
some session bean to non-transactional.Making session beans non-transactions makes container
creating short-living transactions for each call to entity bean
methods. It's a costly process and it puts additional load to
both container and database.
We could use ReadOnly lock for some entity beans, but since weblogicserver will
always create local transaction for entity bean, and we found
transaction
commit
is expensive, I am arguing why do we need create container leveltransaction for
read only bean.First, read-only beans still need to load data. Also, you may seeRO
beans
contanly loading data if db-is-shared set to true. Other reason
can
be
that
RO semantics is not applicable the data presented by RO bean (forinstance,
you have a reporting engine that constantly produces "RO" data,
while
application-consumer of that data retrieves only new data and neverasks
for "old" data). RO beans are good when there is a relatively stable
data
accessed repeatedly for read only access.
You may want to tell us more about your app, we may be of help.
Regards,
Slava Imeshev
I will post the performance data, let's see how costful
transaction.commit
is.
"Cameron Purdy" <[email protected]> wrote:
We are currently profiling our product using Borland
OptmizeIt
tool,
and we
found some interesting issues. Due to our design, we have
many
session
beans which
are non transactional, and these session beans will access
entity
beans
to
do
the reading operations, such as getWeight, getRate, since
it's
read
only,
there
is no need to do transaction commit stuff which really takes
time,
this
could
be seen through the profile. I know weblogic support readonly
entity
bean,
but
it seems that it only has benefit on ejbLoad call, my test
program
shows
that
weblogic still creates local transaction even I specified
it
as
transaction not
supported, and Transaction.commit() will always be called
in
postInvoke(),
from
the profile, we got that for a single method call, such as
getRate(),
80%
time
spent on postInvoke(), any suggestion on this? BTW, most of
our
entity
beans are
using Exclusive lock, that's the reason that we use
non-transactional
session
bean to avoid dead lock problem.I am worried that you have made some decisions based on an improper
understand of what WebLogic is doing.
First, you say "non transactional", but from your description
you
should
have those marked as tx REQUIRED to avoid multiple transactions
(since
non-transactional just means that the database operation becomesits
own
little transaction).
Second, you say you are using exclusive lock, which you shouldonly
use
if
you are absolutely sure that you need it, (and note that it
does
not
work in
a cluster).
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Jinsong Hu" <[email protected]> wrote in message
news:[email protected]...
> -
Implementation oF messageQ in java web services
Hi All,
Can any one tell me how one can implement MSMQ in java for handling web service request and response.
Thanks in Advance
HarshalI am really thankful, for your response.
Ans
1) Web services are implementted in java using apache cxf 2.2.3 framework and It is running on weblogic werver 10.3 and 10.3.4.
2) No, I know your according to call back service concept but instead of this we are having WSDL URL where we need to send response back.
3) Yes, currently we are processing in thread based processing (i.e. for each request we are creating one thread which will process it completely), Which may causes database dead lock, so to remove this we are willing to process requests sequentially.(using MessageQ)
For my knowledge, I am having little confusion that Is MessageQ and JMS are same?
Thanks,
Harshal -
CiscoSecure ACS 4.1(1) Build 23 Patch 5 :database replication fails; possibly short timeout or dead
Hi,
Since some time we are struggling to get database replication working.
On the primary server it is reporting the following on "Database Replication active.csv""
07/21/2010
14:22:58
SZ0910
WARNING
ACS 'SZ0920' not replied to replication request - possibly short timeout or dead
07/21/2010
14:12:08
SZ0910
INFO
Outbound replication cycle starting...
In CSMon.log following is logged:
CSMon 07/21/2010 14:12:11 A 1544 13760 Pausing the monitoring of CSAuth for duration 600
CSMon 07/21/2010 14:12:11 A 1544 11640 Pausing the monitoring of CSLog for duration -1
CSMon 07/21/2010 14:12:14 A 1544 13788 Pausing the monitoring of CSRadius for duration -1
CSMon 07/21/2010 14:12:18 A 0641 3248 CSAuth: Paused State 0 6 Event Detected Level:2 Message:Service CSAuth has been suspended for a configured function to proceed. Monitoring will suspend until the service is restarted
CSMon 07/21/2010 14:12:18 A 0641 3248 CSLog: Stopped State 0 6 Event Detected Level:2 Message:Service CSLog has been stopped or paused by the system. Monitoring will suspend until the service is restarted
CSMon 07/21/2010 14:12:18 A 0641 3248 CSRadius: Stopped State 0 3 Event Detected Level:2 Message:Service CSRadius has been stopped or paused by the system. Monitoring will suspend until the service is restarted
CSMon 07/21/2010 14:12:18 A 1544 7716 Pausing the monitoring of CSTacacs for duration -1
CSMon 07/21/2010 14:12:28 A 0904 3248 Analysis: Level 2 'Service CSAuth has been suspended for a configured function to proceed. Monitoring will suspend until the service is restarted. Service CSLog has been stopped or paused by the system. Monitoring will suspend until the service is restarted. Service CSRadius has been stopped or paused by the system. Monitoring will suspend until the service is restarted. '
CSMon 07/21/2010 14:12:33 E 0351 3248 Failed to log accounting packet to logger localCSLog
CSMon 07/21/2010 14:12:33 A 0641 3248 CSTacacs: Stopped State 0 2 Event Detected Level:2 Message:Service CSTacacs has been stopped or paused by the system. Monitoring will suspend until the service is restarted
CSMon 07/21/2010 14:12:43 A 0904 3248 Analysis: Level 2 'Service CSTacacs has been stopped or paused by the system. Monitoring will suspend until the service is restarted. '
CSMon 07/21/2010 14:12:48 E 0351 3248 Failed to log accounting packet to logger localCSLog
CSMon 07/21/2010 14:22:18 A 0641 3248 CSAuth: State 0 6 Event Detected Level:4 Message:Service pause timed out. Please check the timeout settings for Replication and Backup
I have followed this checklist: https://supportforums.cisco.com/docs/DOC-8795 to make sure configs are ok.
But still replication fails.
There is no firewall in between.
Both ACS servers running on MS Windows Server 2003, SP2.
Can anybody help me in the right direction what could be possible cause of this or where else I can look for logging for further troubleshooting?
Thanks in advance for your help.Hi,
Since some time we are struggling to get database replication working.
On the primary server it is reporting the following on "Database Replication active.csv""
07/21/2010
14:22:58
SZ0910
WARNING
ACS 'SZ0920' not replied to replication request - possibly short timeout or dead
07/21/2010
14:12:08
SZ0910
INFO
Outbound replication cycle starting...
In CSMon.log following is logged:
CSMon 07/21/2010 14:12:11 A 1544 13760 Pausing the monitoring of CSAuth for duration 600
CSMon 07/21/2010 14:12:11 A 1544 11640 Pausing the monitoring of CSLog for duration -1
CSMon 07/21/2010 14:12:14 A 1544 13788 Pausing the monitoring of CSRadius for duration -1
CSMon
07/21/2010 14:12:18 A 0641 3248 CSAuth: Paused State 0 6 Event Detected
Level:2 Message:Service CSAuth has been suspended for a configured
function to proceed. Monitoring will suspend until the service is
restarted
CSMon 07/21/2010 14:12:18 A 0641 3248 CSLog: Stopped State
0 6 Event Detected Level:2 Message:Service CSLog has been stopped or
paused by the system. Monitoring will suspend until the service is
restarted
CSMon 07/21/2010 14:12:18 A 0641 3248 CSRadius: Stopped
State 0 3 Event Detected Level:2 Message:Service CSRadius has been
stopped or paused by the system. Monitoring will suspend until the
service is restarted
CSMon 07/21/2010 14:12:18 A 1544 7716 Pausing the monitoring of CSTacacs for duration -1
CSMon
07/21/2010 14:12:28 A 0904 3248 Analysis: Level 2 'Service CSAuth has
been suspended for a configured function to proceed. Monitoring will
suspend until the service is restarted. Service CSLog has been stopped
or paused by the system. Monitoring will suspend until the service is
restarted. Service CSRadius has been stopped or paused by the system.
Monitoring will suspend until the service is restarted. '
CSMon 07/21/2010 14:12:33 E 0351 3248 Failed to log accounting packet to logger localCSLog
CSMon
07/21/2010 14:12:33 A 0641 3248 CSTacacs: Stopped State 0 2 Event
Detected Level:2 Message:Service CSTacacs has been stopped or paused by
the system. Monitoring will suspend until the service is restarted
CSMon
07/21/2010 14:12:43 A 0904 3248 Analysis: Level 2 'Service CSTacacs has
been stopped or paused by the system. Monitoring will suspend until the
service is restarted. '
CSMon 07/21/2010 14:12:48 E 0351 3248 Failed to log accounting packet to logger localCSLog
CSMon
07/21/2010 14:22:18 A 0641 3248 CSAuth: State 0 6 Event Detected
Level:4 Message:Service pause timed out. Please check the timeout
settings for Replication and Backup
I have followed this checklist: https://supportforums.cisco.com/docs/DOC-8795 to make sure configs are ok.
But still replication fails.
There is no firewall in between.
Both ACS servers running on MS Windows Server 2003, SP2.
Can
anybody help me in the right direction what could be possible cause of
this or where else I can look for logging for further troubleshooting?
Thanks in advance for your help.
Hi,
Also check the port number TCP 2000 this is the replication port which needs to be opened between the primary and secondary ACS.
Hope to Help !!
Ganesh.H -
ORA-00060 dead lock happen on R12 demo database
We have EBS R12 (12.0.4) on Redhat Linux system when I check alert.log file and found demo database (VIS) have ORA-00060 dead lock. The dead lock happen on statement:
UPDATE FND_CONCURRENT_REQUESTS SET PP_END_DATE = SYSDATE, POST_REQUEST_STATUS = 'E' WHERE REQUEST_ID = :B1
Do I need do anthing relate to this ORA- error or just ignore it?
Thanks.Thank you for answer. I checked CM log and did NOT find any error.
I also read document 153717.1 and compare FND_CONCURRENT_REQUESTS table definition. The initial number of trnasaction is 10 and max is 255. I try to use OEM to change "initial transaction number" and it don't allow to.
Any ideal??? -
How can I know a database link target DB is dead?
Hi,
I have a question about using database link.
If I create a public database link linkB from DB A to DB B. Then the DB B's storage fail and DB B is dead.
When I use select * from tableB@linkB in one package with exception handler, it just hang and didn't jump to exception. How can I set a timeout value (like 15 secs) to this database link ??? or is there any method to detect the database link if alive then run the sql statement????
Anyone knows??? thanks!!
Regards,
Miki.Thanks to NKU's answer.
But, the inbond_connect_timeout seems to set in DB server, for a client to connect with the database server and provide the necessary authentication information.
In my case, I don't know the target DB B is dead and my AP hang because it execute a query through DB link from DB A to DB B.
If I can set a timeout value to DB link (create in DB A) or something else, I can have exception handler to process it not just wait a long time period. ^_^
Best Regards,
Miki. -
Site is very slow-Dead lock in database?
Hi Friends,
DB version:10.2.0.1
OS:RHEL
I have a table whose structure is as below
SQL>desc prod
Name Null? Type
ID NOT NULL VARCHAR2(40)
TITLE VARCHAR2(500)
VALUE VARCHAR2(2000)
Column ID has two contarints primary key constraint and check constraint.
Actual problem:
================
One of our site is very slow and as a i DBA i have checked the alert log file of the database and found the error
Wed Jul 7 01:26:50 2010
ORA-00060: Deadlock detected. More info in file /u01/app/oracle/admin/PUBDB01/udump/pubdb01_ora_25844.trc.
I checked the trace file and found the information as below.
DEADLOCK DETECTED
[Transaction Deadlock]
Current SQL statement for this session:
DELETE FROM prod WHERE id = :1
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Now i want to know the reason behind the slowness of the site is because of the deadlock which i have found in the database or some thing else. If the reason is because of the deadlock then what i have to do that SQL statement inorder to perform it optimally.
Please need your help and suggestions.Get statspack/AWR running at regular intervals.
Deadlocks are resolved instantaneously by Oracle itself - I don't think that could cause the entire site to slow down. -
Saving the data from a dead library
So I've given up trying to rebuild my library (see here: http://discussions.apple.com/thread.jspa?messageID=11544400�) and was wondering if anyone had any thoughts on how I could extract the projects from an Aperture 3 library.
In an Aperture 2 library you could view the package contents and each project was bundled into a package along with all setting, versions, etc. This is not the case with A3. If you view the package contents of and A3 library everything is spread out. Masters, Projects, Folders and Version are separate from one another.
Any thoughts?
I've many of my projects backed up but recent work that consisted of a lot of image processing is now lost in the dead library.I think I have recovered my library. I'm in the process of checking the projects to see if they are all intact.
Here is what I did:
1: Created a new empty library
2: Quit Aperture
3: Viewed the contents of the package of the new library and viewed the contents of the old damaged library
4: Moved the "Masters" folder from the old to the new library
5: Moved the "Aperture.aplib" folder from the old to the new library
6: Moved the "ApertureData.xml" file from the old to the new library
7: I then opened the "Database" folder in the old library and copied the following folders: "Albums", "Folders" and "Versions"
Everything else I left behind.
I then launched Aperture by doubleclicking on the new library while holding the Command and Alt keys and selected "Rebuild Library" from the Library First Aid panel.
Aperture then began processing all the content. 10900 images later Aperture launched showing all projects and images.
Looks good so far... -
Database is not starting after RAC installation
Hi All,
I have installed 10g R2 2-node RAC on RHEL4 without any problem. But after the installation the database is not starting and i'm not able to connect. It is showing the below error..
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
Can anybody help what might be the problem?
Thanks,
PraveenHi,
I'm giving the contents of alter log file from the first node...
Mon Feb 19 16:45:59 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =36
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.2.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 1073741824
sga_target = 1073741824
db_block_size = 8192
compatible = 10.2.0.2.0
log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
log_archive_format = %t_%s_%r.dbf
db_file_multiblock_read_count= 16
cluster_database_instances= 1
db_create_file_dest = +ORCL_DATA1
instance_number = 1
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
remote_listener = LISTENERS_BSAPROD
job_queue_processes = 10
background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
db_name = bsaprod
open_cursors = 300
pga_aggregate_target = 262144000
Cluster communication is configured to use the following interface(s) for this instance
10.250.90.107
Mon Feb 19 16:46:00 2007
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=31282
DIAG started with pid=3, OS id=31284
PSP0 started with pid=4, OS id=31286
LMON started with pid=5, OS id=31300
LMD0 started with pid=6, OS id=31315
MMAN started with pid=7, OS id=31317
DBW0 started with pid=8, OS id=31319
LGWR started with pid=9, OS id=31321
CKPT started with pid=10, OS id=31323
SMON started with pid=11, OS id=31325
RECO started with pid=12, OS id=31327
CJQ0 started with pid=13, OS id=31329
MMON started with pid=14, OS id=31331
Mon Feb 19 16:46:00 2007
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=15, OS id=31333
Mon Feb 19 16:46:00 2007
starting up 1 shared server(s) ...
Mon Feb 19 16:46:00 2007
lmon registered with NM - instance id 1 (internal mem no 0)
Mon Feb 19 16:46:01 2007
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
0
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Resources and enqueues cleaned out
Resources remastered 0
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
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Reconfiguration complete
Mon Feb 19 16:46:01 2007
CREATE DATABASE "bsaprod"
MAXINSTANCES 32
MAXLOGHISTORY 1
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
DATAFILE SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL
SYSAUX DATAFILE SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
SMALLFILE UNDO TABLESPACE "UNDOTBS1" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET WE8ISO8859P1
NATIONAL CHARACTER SET AL16UTF16
LOGFILE GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K
USER SYS IDENTIFIED BY *USER SYSTEM IDENTIFIED BY
Mon Feb 19 16:46:01 2007
Starting background process ASMB
ASMB started with pid=19, OS id=31365
Starting background process RBAL
RBAL started with pid=20, OS id=31369
Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
Mon Feb 19 16:46:05 2007
SUCCESS: diskgroup ORCL_DATA1 was mounted
SUCCESS: diskgroup ORCL_DATA1 was dismounted
Mon Feb 19 16:46:06 2007
SUCCESS: diskgroup ORCL_DATA1 was mounted
Mon Feb 19 16:46:06 2007
Database mounted in Exclusive Mode
Mon Feb 19 16:46:09 2007
Successful mount of redo thread 1, with mount id 3309011657
Assigning activation ID 3309011657 (0xc53b82c9)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Successful open of redo thread 1
Mon Feb 19 16:46:09 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Feb 19 16:46:09 2007
SMON: enabling cache recovery
Mon Feb 19 16:46:09 2007
create tablespace SYSTEM datafile SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL online
Mon Feb 19 16:46:20 2007
Completed: create tablespace SYSTEM datafile SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL online
Mon Feb 19 16:46:20 2007
create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Completed: create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Mon Feb 19 16:46:24 2007
CREATE SMALLFILE UNDO TABLESPACE UNDOTBS1 DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
Mon Feb 19 16:46:31 2007
Successfully onlined Undo Tablespace 1.
Completed: CREATE SMALLFILE UNDO TABLESPACE UNDOTBS1 DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
Mon Feb 19 16:46:31 2007
create tablespace SYSAUX datafile SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online
Completed: create tablespace SYSAUX datafile SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online
Mon Feb 19 16:46:36 2007
CREATE SMALLFILE TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
Completed: CREATE SMALLFILE TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
Mon Feb 19 16:46:36 2007
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP
Completed: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP
Mon Feb 19 16:46:36 2007
ALTER DATABASE DEFAULT TABLESPACE SYSTEM
Completed: ALTER DATABASE DEFAULT TABLESPACE SYSTEM
Mon Feb 19 16:46:38 2007
SMON: enabling tx recovery
Mon Feb 19 16:46:39 2007
Threshold validation cannot be done before catproc is loaded.
Threshold validation cannot be done before catproc is loaded.
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=22, OS id=32303
Mon Feb 19 16:46:39 2007
Completed: CREATE DATABASE "bsaprod"
MAXINSTANCES 32
MAXLOGHISTORY 1
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
DATAFILE SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL
SYSAUX DATAFILE SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
SMALLFILE UNDO TABLESPACE "UNDOTBS1" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET WE8ISO8859P1
NATIONAL CHARACTER SET AL16UTF16
LOGFILE GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K
USER SYS IDENTIFIED BY *USER SYSTEM IDENTIFIED BY
Mon Feb 19 16:46:39 2007
CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS2" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
Completed: CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS2" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
Mon Feb 19 16:46:46 2007
CREATE SMALLFILE TABLESPACE "USERS" LOGGING DATAFILE SIZE 5M AUTOEXTEND ON NEXT 1280K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
Completed: CREATE SMALLFILE TABLESPACE "USERS" LOGGING DATAFILE SIZE 5M AUTOEXTEND ON NEXT 1280K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
Mon Feb 19 16:46:46 2007
ALTER DATABASE DEFAULT TABLESPACE "USERS"
Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
Mon Feb 19 16:47:05 2007
Thread 1 advanced to log sequence 2
Current log# 2 seq# 2 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 16:47:34 2007
Thread 1 cannot allocate new log, sequence 3
Checkpoint not complete
Current log# 2 seq# 2 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 3
Current log# 1 seq# 3 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 16:48:10 2007
Thread 1 cannot allocate new log, sequence 4
Checkpoint not complete
Current log# 1 seq# 3 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 4
Current log# 2 seq# 4 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 16:49:05 2007
Thread 1 cannot allocate new log, sequence 5
Checkpoint not complete
Current log# 2 seq# 4 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 5
Current log# 1 seq# 5 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 16:50:19 2007
Thread 1 cannot allocate new log, sequence 6
Checkpoint not complete
Current log# 1 seq# 5 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 6
Current log# 2 seq# 6 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 16:51:00 2007
Thread 1 cannot allocate new log, sequence 7
Checkpoint not complete
Current log# 2 seq# 6 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 7
Current log# 1 seq# 7 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 16:51:54 2007
Thread 1 cannot allocate new log, sequence 8
Checkpoint not complete
Current log# 1 seq# 7 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 8
Current log# 2 seq# 8 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 16:55:32 2007
Thread 1 cannot allocate new log, sequence 9
Checkpoint not complete
Current log# 2 seq# 8 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 9
Current log# 1 seq# 9 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 16:56:35 2007
Thread 1 cannot allocate new log, sequence 10
Checkpoint not complete
Current log# 1 seq# 9 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 10
Current log# 2 seq# 10 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 16:56:52 2007
Thread 1 cannot allocate new log, sequence 11
Checkpoint not complete
Current log# 2 seq# 10 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 11
Current log# 1 seq# 11 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 16:57:04 2007
Thread 1 cannot allocate new log, sequence 12
Checkpoint not complete
Current log# 1 seq# 11 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 12
Current log# 2 seq# 12 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 16:57:14 2007
Thread 1 cannot allocate new log, sequence 13
Checkpoint not complete
Current log# 2 seq# 12 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 13
Current log# 1 seq# 13 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 16:57:31 2007
Thread 1 cannot allocate new log, sequence 14
Checkpoint not complete
Current log# 1 seq# 13 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 14
Current log# 2 seq# 14 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 16:58:13 2007
Thread 1 cannot allocate new log, sequence 15
Checkpoint not complete
Current log# 2 seq# 14 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 15
Current log# 1 seq# 15 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 16:59:42 2007
Thread 1 cannot allocate new log, sequence 16
Checkpoint not complete
Current log# 1 seq# 15 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 16
Current log# 2 seq# 16 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:00:33 2007
Thread 1 cannot allocate new log, sequence 17
Checkpoint not complete
Current log# 2 seq# 16 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 17
Current log# 1 seq# 17 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:01:49 2007
Thread 1 cannot allocate new log, sequence 18
Checkpoint not complete
Current log# 1 seq# 17 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 18
Current log# 2 seq# 18 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:02:23 2007
Thread 1 cannot allocate new log, sequence 19
Checkpoint not complete
Current log# 2 seq# 18 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 19
Current log# 1 seq# 19 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:04:06 2007
Thread 1 cannot allocate new log, sequence 20
Checkpoint not complete
Current log# 1 seq# 19 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 20
Current log# 2 seq# 20 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:05:22 2007
Thread 1 cannot allocate new log, sequence 21
Checkpoint not complete
Current log# 2 seq# 20 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 21
Current log# 1 seq# 21 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:06:22 2007
Thread 1 cannot allocate new log, sequence 22
Checkpoint not complete
Current log# 1 seq# 21 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 22
Current log# 2 seq# 22 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:08:42 2007
Thread 1 cannot allocate new log, sequence 23
Checkpoint not complete
Current log# 2 seq# 22 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 23
Current log# 1 seq# 23 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:09:43 2007
Thread 1 cannot allocate new log, sequence 24
Checkpoint not complete
Current log# 1 seq# 23 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 24
Current log# 2 seq# 24 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:10:42 2007
Thread 1 cannot allocate new log, sequence 25
Checkpoint not complete
Current log# 2 seq# 24 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 25
Current log# 1 seq# 25 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:11:31 2007
Thread 1 cannot allocate new log, sequence 26
Checkpoint not complete
Current log# 1 seq# 25 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 26
Current log# 2 seq# 26 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:12:01 2007
Thread 1 cannot allocate new log, sequence 27
Checkpoint not complete
Current log# 2 seq# 26 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 27
Current log# 1 seq# 27 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:13:12 2007
Thread 1 cannot allocate new log, sequence 28
Checkpoint not complete
Current log# 1 seq# 27 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 28
Current log# 2 seq# 28 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:14:05 2007
Thread 1 cannot allocate new log, sequence 29
Checkpoint not complete
Current log# 2 seq# 28 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 29
Current log# 1 seq# 29 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:14:57 2007
Thread 1 cannot allocate new log, sequence 30
Checkpoint not complete
Current log# 1 seq# 29 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Thread 1 advanced to log sequence 30
Current log# 2 seq# 30 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Mon Feb 19 17:16:29 2007
Thread 1 cannot allocate new log, sequence 31
Checkpoint not complete
Current log# 2 seq# 30 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_2.258.614969167
Thread 1 advanced to log sequence 31
Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Mon Feb 19 17:17:54 2007
Starting background process EMN0
EMN0 started with pid=25, OS id=15651
Mon Feb 19 17:17:54 2007
Shutting down instance: further logons disabled
Mon Feb 19 17:17:55 2007
Stopping background process QMNC
Mon Feb 19 17:17:55 2007
Stopping background process CJQ0
Mon Feb 19 17:17:57 2007
Stopping background process MMNL
Mon Feb 19 17:17:58 2007
Stopping background process MMON
Mon Feb 19 17:17:59 2007
Shutting down instance (immediate)
License high water mark = 1
Mon Feb 19 17:17:59 2007
Stopping Job queue slave processes
Mon Feb 19 17:17:59 2007
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Mon Feb 19 17:18:01 2007
ALTER DATABASE CLOSE NORMAL
Mon Feb 19 17:18:01 2007
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Feb 19 17:18:03 2007
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 31
Successful close of redo thread 1
Mon Feb 19 17:18:04 2007
Completed: ALTER DATABASE CLOSE NORMAL
Mon Feb 19 17:18:04 2007
ALTER DATABASE DISMOUNT
Mon Feb 19 17:18:04 2007
SUCCESS: diskgroup ORCL_DATA1 was dismounted
Mon Feb 19 17:18:04 2007
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
Mon Feb 19 17:18:09 2007
freeing rdom 0
Mon Feb 19 17:18:12 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =36
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.2.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 1073741824
sga_target = 1073741824
control_files = +ORCL_DATA1/bsaprod/controlfile/current.256.614969167
db_block_size = 8192
compatible = 10.2.0.2.0
log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
log_archive_format = %t_%s_%r.dbf
db_file_multiblock_read_count= 16
cluster_database_instances= 1
db_create_file_dest = +ORCL_DATA1
instance_number = 1
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
remote_listener = LISTENERS_BSAPROD
job_queue_processes = 10
background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
db_name = bsaprod
open_cursors = 300
pga_aggregate_target = 262144000
Cluster communication is configured to use the following interface(s) for this instance
10.250.90.107
Mon Feb 19 17:18:13 2007
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=16124
DIAG started with pid=3, OS id=16126
PSP0 started with pid=4, OS id=16128
LMON started with pid=5, OS id=16130
LMD0 started with pid=6, OS id=16132
MMAN started with pid=7, OS id=16134
DBW0 started with pid=8, OS id=16136
LGWR started with pid=9, OS id=16138
CKPT started with pid=10, OS id=16140
SMON started with pid=11, OS id=16142
RECO started with pid=12, OS id=16144
CJQ0 started with pid=13, OS id=16146
MMON started with pid=14, OS id=16148
Mon Feb 19 17:18:13 2007
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=15, OS id=16150
Mon Feb 19 17:18:13 2007
starting up 1 shared server(s) ...
Mon Feb 19 17:18:13 2007
lmon registered with NM - instance id 1 (internal mem no 0)
Mon Feb 19 17:18:14 2007
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
0
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Resources and enqueues cleaned out
Resources remastered 0
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
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Reconfiguration complete
Mon Feb 19 17:18:14 2007
ALTER DATABASE MOUNT
Mon Feb 19 17:18:14 2007
Starting background process ASMB
ASMB started with pid=19, OS id=16182
Starting background process RBAL
RBAL started with pid=20, OS id=16186
Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
Mon Feb 19 17:18:18 2007
SUCCESS: diskgroup ORCL_DATA1 was mounted
Mon Feb 19 17:18:23 2007
Setting recovery target incarnation to 1
Mon Feb 19 17:18:23 2007
Successful mount of redo thread 1, with mount id 3309012054
Mon Feb 19 17:18:23 2007
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Feb 19 17:18:23 2007
alter database archivelog
Completed: alter database archivelog
Mon Feb 19 17:18:23 2007
alter database open
Mon Feb 19 17:18:23 2007
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=22, OS id=16393
Mon Feb 19 17:18:23 2007
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=23, OS id=16395
Mon Feb 19 17:18:23 2007
Thread 1 opened at log sequence 31
Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Successful open of redo thread 1
Mon Feb 19 17:18:23 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Feb 19 17:18:23 2007
SMON: enabling cache recovery
Mon Feb 19 17:18:23 2007
ARC0: STARTING ARCH PROCESSES
Mon Feb 19 17:18:23 2007
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Feb 19 17:18:23 2007
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
ARC2 started with pid=24, OS id=16422
Mon Feb 19 17:18:23 2007
Successfully onlined Undo Tablespace 1.
Mon Feb 19 17:18:23 2007
SMON: enabling tx recovery
Mon Feb 19 17:18:23 2007
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=25, OS id=16449
Mon Feb 19 17:18:25 2007
Completed: alter database open
Mon Feb 19 17:18:25 2007
ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 3 SIZE 51200K,
GROUP 4 SIZE 51200K
Completed: ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 3 SIZE 51200K,
GROUP 4 SIZE 51200K
Mon Feb 19 17:18:28 2007
ALTER DATABASE ENABLE PUBLIC THREAD 2
Completed: ALTER DATABASE ENABLE PUBLIC THREAD 2
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
Mon Feb 19 17:18:29 2007
Starting background process EMN0
EMN0 started with pid=26, OS id=16564
Mon Feb 19 17:18:29 2007
Shutting down instance: further logons disabled
Mon Feb 19 17:18:29 2007
Stopping background process QMNC
Mon Feb 19 17:18:29 2007
Stopping background process CJQ0
Mon Feb 19 17:18:30 2007
Stopping background process MMNL
Mon Feb 19 17:18:31 2007
Stopping background process MMON
Mon Feb 19 17:18:32 2007
Shutting down instance (immediate)
License high water mark = 3
Mon Feb 19 17:18:32 2007
Stopping Job queue slave processes
Mon Feb 19 17:18:32 2007
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Mon Feb 19 17:18:34 2007
ALTER DATABASE CLOSE NORMAL
Mon Feb 19 17:18:34 2007
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Feb 19 17:18:34 2007
Shutting down archive processes
Archiving is disabled
Mon Feb 19 17:18:39 2007
ARCH shutting down
ARC2: Archival stopped
Mon Feb 19 17:18:44 2007
ARCH shutting down
ARC1: Archival stopped
Mon Feb 19 17:18:49 2007
ARCH shutting down
ARC0: Archival stopped
Mon Feb 19 17:18:50 2007
Thread 1 closed at log sequence 31
Successful close of redo thread 1
Mon Feb 19 17:18:51 2007
Completed: ALTER DATABASE CLOSE NORMAL
Mon Feb 19 17:18:51 2007
ALTER DATABASE DISMOUNT
Mon Feb 19 17:18:51 2007
SUCCESS: diskgroup ORCL_DATA1 was dismounted
Mon Feb 19 17:18:51 2007
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
Mon Feb 19 17:18:56 2007
freeing rdom 0
Mon Feb 19 17:18:59 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
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.2.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 1073741824
spfile = +BSA_DATA1/bsaprod/spfilebsaprod.ora
sga_target = 1073741824
control_files = +ORCL_DATA1/bsaprod/controlfile/current.256.614969167
db_block_size = 8192
compatible = 10.2.0.2.0
log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
log_archive_format = %t_%s_%r.dbf
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +ORCL_DATA1
thread = 1
instance_number = 1
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
remote_listener = LISTENERS_BSAPROD
job_queue_processes = 10
background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
db_name = bsaprod
open_cursors = 300
pga_aggregate_target = 262144000
Cluster communication is configured to use the following interface(s) for this instance
10.250.90.107
Mon Feb 19 17:19:00 2007
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=17373
DIAG started with pid=3, OS id=17375
PSP0 started with pid=4, OS id=17377
LMON started with pid=5, OS id=17379
LMD0 started with pid=6, OS id=17381
LMS0 started with pid=7, OS id=17383
LMS1 started with pid=8, OS id=17387
MMAN started with pid=9, OS id=17391
DBW0 started with pid=10, OS id=17393
LGWR started with pid=11, OS id=17395
CKPT started with pid=12, OS id=17397
SMON started with pid=13, OS id=17399
RECO started with pid=14, OS id=17412
CJQ0 started with pid=15, OS id=17428
MMON started with pid=16, OS id=17430
Mon Feb 19 17:19:00 2007
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=17432
Mon Feb 19 17:19:00 2007
starting up 1 shared server(s) ...
Mon Feb 19 17:19:01 2007
lmon registered with NM - instance id 1 (internal mem no 0)
Mon Feb 19 17:19:01 2007
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
0
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 Feb 19 17:19:01 2007
LMS 1: 0 GCS shadows cancelled, 0 closed
Mon Feb 19 17:19:01 2007
LMS 0: 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 Feb 19 17:19:01 2007
LMS 1: 0 GCS shadows traversed, 0 replayed
Mon Feb 19 17:19:01 2007
LMS 0: 0 GCS shadows traversed, 0 replayed
Mon Feb 19 17:19:01 2007
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=17460
Mon Feb 19 17:19:02 2007
ALTER DATABASE MOUNT
Mon Feb 19 17:19:02 2007
This instance was first to mount
Mon Feb 19 17:19:02 2007
Starting background process ASMB
ASMB started with pid=22, OS id=17466
Starting background process RBAL
RBAL started with pid=23, OS id=17470
Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
Mon Feb 19 17:19:06 2007
SUCCESS: diskgroup ORCL_DATA1 was mounted
Mon Feb 19 17:19:09 2007
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
Mon Feb 19 17:19:10 2007
Setting recovery target incarnation to 1
Mon Feb 19 17:19:10 2007
Successful mount of redo thread 1, with mount id 3308997510
Mon Feb 19 17:19:10 2007
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE MOUNT
Mon Feb 19 17:19:11 2007
ALTER DATABASE OPEN
This instance was first to open
Picked broadcast on commit scheme to generate SCNs
Mon Feb 19 17:19:11 2007
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=26, OS id=17679
Mon Feb 19 17:19:11 2007
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=27, OS id=17706
Mon Feb 19 17:19:11 2007
Thread 1 opened at log sequence 31
Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Successful open of redo thread 1
Mon Feb 19 17:19:11 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Feb 19 17:19:11 2007
ARC0: STARTING ARCH PROCESSES
Mon Feb 19 17:19:11 2007
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Feb 19 17:19:11 2007
SMON: enabling cache recovery
Mon Feb 19 17:19:11 2007
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
ARC2 started with pid=28, OS id=17708
Mon Feb 19 17:19:11 2007
Successfully onlined Undo Tablespace 1.
Mon Feb 19 17:19:11 2007
SMON: enabling tx recovery
Mon Feb 19 17:19:11 2007
Database Characterset is WE8ISO8859P1
Mon Feb 19 17:19:11 2007
Instance recovery: looking for dead threads
Instance recovery: lock domain invalid but no dead threads
Mon Feb 19 17:19:12 2007
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
Mon Feb 19 17:19:12 2007
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=29, OS id=17735
Mon Feb 19 17:19:13 2007
Completed: ALTER DATABASE OPEN
Mon Feb 19 17:20:11 2007
Shutting down archive processes
Mon Feb 19 17:20:16 2007
ARCH shutting down
ARC2: Archival stopped
Mon Feb 19 17:23:35 2007
Starting background process EMN0
EMN0 started with pid=74, OS id=28350
Mon Feb 19 17:23:35 2007
Shutting down instance: further logons disabled
Mon Feb 19 17:23:36 2007
Stopping background process QMNC
Mon Feb 19 17:23:36 2007
Stopping background process CJQ0
Mon Feb 19 17:23:38 2007
Stopping background process MMNL
Mon Feb 19 17:23:39 2007
Stopping background process MMON
Mon Feb 19 17:23:40 2007
Shutting down instance (immediate)
License high water mark = 34
Mon Feb 19 17:23:40 2007
Stopping Job queue slave processes
Mon Feb 19 17:23:40 2007
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Mon Feb 19 17:24:07 2007
ALTER DATABASE CLOSE NORMAL
Mon Feb 19 17:24:07 2007
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Feb 19 17:24:08 2007
Shutting down archive processes
Archiving is disabled
Mon Feb 19 17:24:18 2007
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC1: Archiving disabled
ARCH shutting down
Mon Feb 19 17:24:18 2007
ARC1: Archival stopped
Mon Feb 19 17:24:18 2007
ARC0: Becoming the heartbeat ARCH
Mon Feb 19 17:24:18 2007
ARC0: Archiving disabled
ARCH shutting down
ARC0: Archival stopped
Mon Feb 19 17:24:19 2007
Thread 1 closed at log sequence 31
Successful close of redo thread 1
Mon Feb 19 17:24:19 2007
Completed: ALTER DATABASE CLOSE NORMAL
Mon Feb 19 17:24:19 2007
ALTER DATABASE DISMOUNT
Mon Feb 19 17:24:19 2007
SUCCESS: diskgroup ORCL_DATA1 was dismounted
Mon Feb 19 17:24:19 2007
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
Mon Feb 19 17:24:25 2007
freeing rdom 0
Mon Feb 19 17:24:35 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth1 10.250.90.0 configured from OCR for use as a cluster interconnect
Interface type 1 eth0 10.250.90.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
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.2.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 1073741824
__shared_pool_size = 255852544
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = +BSA_DATA1/bsaprod/spfilebsaprod.ora
sga_target = 1073741824
control_files = +ORCL_DATA1/bsaprod/controlfile/current.256.614969167
db_block_size = 8192
__db_cache_size = 801112064
compatible = 10.2.0.2.0
log_archive_dest_1 = LOCATION=+BSA_DATA1/bsaprod/
log_archive_format = %t_%s_%r.dbf
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +ORCL_DATA1
thread = 1
instance_number = 1
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=bsaprodXDB)
remote_listener = LISTENERS_BSAPROD
job_queue_processes = 10
background_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/bdump
user_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/udump
core_dump_dest = /u01/app/oracle/oracle/admin/bsaprod/cdump
audit_file_dest = /u01/app/oracle/oracle/admin/bsaprod/adump
db_name = bsaprod
open_cursors = 300
pga_aggregate_target = 262144000
Cluster communication is configured to use the following interface(s) for this instance
10.250.90.107
Mon Feb 19 17:24:35 2007
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=29950
DIAG started with pid=3, OS id=29952
PSP0 started with pid=4, OS id=29954
LMON started with pid=5, OS id=29956
LMD0 started with pid=6, OS id=29958
LMS0 started with pid=7, OS id=29960
LMS1 started with pid=8, OS id=29964
MMAN started with pid=9, OS id=29968
DBW0 started with pid=10, OS id=29970
LGWR started with pid=11, OS id=29972
CKPT started with pid=12, OS id=29974
SMON started with pid=13, OS id=29976
RECO started with pid=14, OS id=29978
CJQ0 started with pid=15, OS id=29980
MMON started with pid=16, OS id=29982
Mon Feb 19 17:24:36 2007
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=29984
Mon Feb 19 17:24:36 2007
starting up 1 shared server(s) ...
Mon Feb 19 17:24:36 2007
lmon registered with NM - instance id 1 (internal mem no 0)
Mon Feb 19 17:24:39 2007
Reconfiguration started (old inc 0, new inc 4)
List of nodes:
0 1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
* domain 0 not valid according to instance 1
* domain 0 valid = 0 according to instance 1
Mon Feb 19 17:24:39 2007
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Mon Feb 19 17:24:39 2007
LMS 1: 0 GCS shadows cancelled, 0 closed
Mon Feb 19 17:24:39 2007
LMS 0: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Mon Feb 19 17:24:39 2007
LMS 0: 0 GCS shadows traversed, 0 replayed
Mon Feb 19 17:24:39 2007
LMS 1: 0 GCS shadows traversed, 0 replayed
Mon Feb 19 17:24:39 2007
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=30069
Mon Feb 19 17:24:40 2007
ALTER DATABASE MOUNT
Mon Feb 19 17:24:41 2007
Starting background process ASMB
ASMB started with pid=22, OS id=30121
Starting background process RBAL
RBAL started with pid=23, OS id=30125
Loaded ASM Library - Generic Linux, version 2.0.2 (KABI_V2) library for asmlib interface
Mon Feb 19 17:24:45 2007
SUCCESS: diskgroup ORCL_DATA1 was mounted
Mon Feb 19 17:24:49 2007
Setting recovery target incarnation to 1
Mon Feb 19 17:24:49 2007
Successful mount of redo thread 1, with mount id 3309017062
Mon Feb 19 17:24:49 2007
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Mon Feb 19 17:24:51 2007
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
SUCCESS: diskgroup BSA_DATA1 was mounted
SUCCESS: diskgroup BSA_DATA1 was dismounted
Mon Feb 19 17:24:52 2007
Completed: ALTER DATABASE MOUNT
Mon Feb 19 17:24:52 2007
ALTER DATABASE OPEN
Picked broadcast on commit scheme to generate SCNs
Mon Feb 19 17:24:52 2007
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=25, OS id=30406
Mon Feb 19 17:24:53 2007
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=26, OS id=30422
Mon Feb 19 17:24:53 2007
Thread 1 opened at log sequence 31
Current log# 1 seq# 31 mem# 0: +ORCL_DATA1/bsaprod/onlinelog/group_1.257.614969167
Successful open of redo thread 1
Mon Feb 19 17:24:53 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Feb 19 17:24:53 2007
ARC0: STARTING ARCH PROCESSES
Mon Feb 19 17:24:53 2007
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Feb 19 17:24:53 2007
SMON: enabling cache recovery
Mon Feb 19 17:24:53 2007
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
ARC2 started with pid=27, OS id=30436
Mon Feb 19 17:25:07 2007
Successfully onlined Undo Tablespace 1.
Mon Feb 19 17:25:07 2007
SMON: enabling tx recovery
Mon Feb 19 17:25:07 2007
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=29, OS id=30882
Mon Feb 19 17:26:31 2007
Completed: ALTER DATABASE OPEN
Mon Feb 19 17:26:38 2007
ALTER SYSTEM SET service_names='bsaprod','bsatest' SCOPE=MEMORY SID='bsaprod1';
Mon Feb 19 17:26:53 2007
Shutting down archive processes
Mon Feb 19 17:26:58 2007
ARCH shutting down
ARC2: Archival stopped
Mon Feb 19 17:32:16 2007
Error: KGXGN aborts the instance (6)
Mon Feb 19 17:32:16 2007
Errors in file /u01/app/oracle/oracle/admin/bsaprod/bdump/bsaprod1_lmon_29956.trc:
ORA-29702: error occurred in Cluster Group Service operation
LMON: terminating instance due to error 29702
Mon Feb 19 17:32:17 2007
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/oracle/admin/bsaprod/bdump/bsaprod1_diag_29952.trc
Mon Feb 19 17:32:18 2007
Trace dumping is performing id=[cdmp_20070219173217]
Mon Feb 19 17:32:21 2007
Instance terminated by LMON, pid = 29956
and also the output of crs_stat -t in first node is....
Name Type Target State Host
ora....d1.inst application ONLINE OFFLINE
ora....d2.inst application ONLINE OFFLINE
ora....od1.srv application ONLINE OFFLINE
ora....od2.srv application ONLINE OFFLINE
ora....test.cs application ONLINE OFFLINE
ora.bsaprod.db application ONLINE OFFLINE
ora....SM1.asm application ONLINE UNKNOWN dsrvbd003
ora....ER.lsnr application ONLINE UNKNOWN dsrvbd003
ora....03.lsnr application ONLINE UNKNOWN dsrvbd003
ora....003.gsd application ONLINE UNKNOWN dsrvbd003
ora....003.ons application ONLINE UNKNOWN dsrvbd003
ora....003.vip application ONLINE ONLINE dsrvbd003
ora....SM2.asm application ONLINE OFFLINE
ora....04.lsnr application ONLINE OFFLINE
ora....004.gsd application ONLINE OFFLINE
ora....004.ons application ONLINE OFFLINE
ora....004.vip application ONLINE OFFLINE -
Not able to connect to Database
My SQL.NET entry is
# Copyright (c) 1996, 2003, Oracle Corporation. All rights reserved.
# NAME
# sqlnet.ora
# FUNCTION
# Oracle Network Client startup parameter file example
# NOTES
# This file contains examples and instructions for defining all
# - ONames Client ----------------------------------------------------
#names.default_domain = world
#Syntax: domain-name
#Default: NULL
# Indicates the domain from which the client most often requests names. When
# this parameter is set the default domain name (for example, US.ACME), the
# domain name will be automatically appended to any unqualified name in an
# ONAmes request (query, register, deregister, etc). Any name which contains
# an unescaped dot ('.') will not have the default domain appended. Simple
# names may be qualified with a trailing dot (for example 'rootserver.').
#names.initial_retry_timeout = 30
#Syntax: 1-600 seconds
#Default: 15 (OSD)
# Determines how long a client will wait for a response from a Names Server
# before reiterating the request to the next server in the preferred_servers
# list.
#names.message_pool_start_size = 10
#Syntax: 3-256
#Default: 10
# Determines the initial number of messages allocated in the client's message
# pool. This pool provides the client with pre-allocated messages to be used
# for requests to ONames servers. Messages which are in the pool and unused
# may be reused. If a message is needed and no free messages are available in
# the pool more will be allocated.
#names.preferred_servers = (address_list =
# (address=(protocol=ipc)(key=n23))
# (address=(protocol=tcp)(host=nineva)(port=1383))
# (address=(protocol=tcp)(host=cicada)(port=1575))
#Syntax: ADDR_LIST
#Default: Well-Known (OSD)
# Specifies a list of ONames servers in the client's region; requests will be
# sent to each ADDRESS in the list until a response is recieved, or the list
# (and number of retries) is exhausted.
# Addresses of the following form specify that messages to the ONames server
# should use Oracle Remote Operations (RPC):
# (description =
# (address=(protocol=tcp)(host=nineva)(port=1383))
# (connect_data=(rpc=on))
#names.request_retries = 2
#Syntax: 1-5
#Default: 1
# Specifies the number of times the client should try each server in the list
# of preferred_servers before allowing the operation to fail.
#names.directory_path
#Syntax: <adapter-name>
#Default: TNSNAMES,ONAMES,HOSTNAME
# Sets the (ordered) list of naming adaptors to use in resolving a name.
# The default is as shown for 3.0.2 of sqlnet onwards. The default was
# (TNSNAMES, ONAMES) before that. The value can be presented without
# parentheses if only a single entry is being specified. The parameter is
# recognized from version 2.3.2 of sqlnet onward. Acceptable values include:
# TNSNAMES -- tnsnames.ora lookup
# ONAMES -- Oracle Names
# HOSTNAME -- use the hostname (or an alias of the hostname)
# NIS -- NIS (also known as "yp")
# CDS -- OSF DCE's Cell Directory Service
# NDS -- Novell's Netware Directory Service
# - Client Cache (ONRSD) ---------------------------------------------
#names.addresses = (ADDRESS=(PROTOCOL=IPC)(KEY=ONAMES))
#Syntax: ADDR
#Default: (ADDRESS=(PROTOCOL=IPC)(KEY=ONAMES))
# Address on which the client cache listens (is available to clients).
# Any valid TNS address is allowed. The default should be used if at
# all possible; clients have this entry hardwired as the first line
# of their server-list file (sdns.ora). If the address is set to a
# non-default value the client's preferred_servers parameter should
# be set to include the client-cache address first.
#names.authority_required = False
#Syntax: T/F
#Default: False
# Determines whether system querys (for the root etc) require Authoritative
# answers.
#names.auto_refresh_expire = 259200
#Syntax: Number of seconds, 60-1209600
#Default: 259200
# This is the amount of time (in seconds) the server will cache the addresses
# of servers listed in server-list file (sdns.ora). When this time expires the
# server will issue another query to the servers in those regions to refresh
# the data.
#names.auto_refresh_retry = 180
#Syntax: Number of seconds, 60-3600
#Default: sec. 180
# This set how often the server will retry when the auto_refresh query fails.
#names.cache_checkpoint_file = cache.ckp
#Syntax: filename
#Default: $ORACLE_HOME/network/names/ckpcch.ora
# Specifies the name of the operating system file to which the Names Server
# writes its foreign data cache.
#names.cache_checkpoint_interval = 7200
#Syntax: Number of seconds, 10-259200
#Default: 0 (off)
# Indicates the interval at which a Names Server writes a checkpoint of its
# data cache to the checkpoint file.
#names.default_forwarders=
# (FORWARDER_LIST=
# (FORWARDER=
# (NAME= rootserv1.world)
# (ADDRESS=(PROTOCOL=tcp)(PORT=42100)(HOST=roothost))))
#Syntax: Name-Value/address_list
#Default: NULL
# A list (in NV form) of the addresses of other servers which should be used to
# forward querys while in default_forwarder (slave) mode. NAME is the global
# names for the server to which forwards whould be directed, and ADDRESS is its
# address.
#names.default_forwarders_only = True
#Syntax: T/F
#Default: False
# When set to true this server will use the servers listed in default_forwarders
# to forward all operations which involve data in foreign regions. Otherwise it
# will use the servers defined in the server-list file (sdns.ora) in addition
# to any defined in the default_forwarders parameter.
#names.log_directory = /oracle/network/log
#Syntax: directory
#Default: $ORACLE_HOME/network/log
# Indicates the name of the directory where the log file for Names Server
# operational events are written.
#names.log_file = names.log
#Syntax: filename
#Default: names.log
# The name of the output file to which Names Server operational events are
# written.
#names.log_stats_interval = 3600
#Syntax: Number of seconds, 10-ub4max
#Default: sec. 0 (off)
#Specifies the number of seconds between statistical entries in log file.
#names.log_unique = False
#Syntax: T/F
#Default: False
# If set to true the server will guarantee that the log file will have a unique
# name which will not overwrite any existing files (note that log files are
# appended to, so log information will not be lost if log_unique is not true).
#names.max_open_connections = 10
#Syntax: 3-64
#Default: 10
# Specifies the number of connections that the Names Server can have open at any
# given time. The value is generated as the value 10 or the sum of one
# connection for listening, five for clients, plus one for each foreign domain
# defined in the local administrative region, whichever is greater. Any
# operation which requires the server to open a network connection will use
# an already open connection if it is available, or will open a connection
# if not. Higher settings will save time and cost network resources; lower
# settings save network resources, cost time.
#names.max_reforwards = 2
#Syntax: 1-15
#Default: 2
# The maximum number of times the server will attempt to forward a certain
# operation.
#names.message_pool_start_size = 24
#Syntax: 3-256
#Default: 10
# Determines the initial number of messages allocated in the server's message
# pool. This pool provides the server with pre-allocated messages to be used
# for incoming or outgoing messages (forwards). Messages which are in the pool
#names.trace_file = names.trc
#Syntax: filename
#Default: names.trc
# Indicates the name of the output file from a Names Server trace session.
#names.trace_func # NA
#Syntax: T/F
#Default: False
# Internal mechanism to control tracing by function name.
#names.trace_level = ADMIN
#Syntax: T/F
#Default: False
#Syntax: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
# Indicates the level at which the Names Server is to be traced.
# Available Values:
# 0 or OFF - No trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - WorldWide Customer Support trace information
#names.trace_mask = (200,201,202,203,205,206,207)
#namesctl.trace_unique = True
#Syntax: T/F
#Default: False
# Indicates whether each trace file has a unique name, allowing multiple trace
# files to coexist. If the value is set to ON, a process identifier is appended
# to the name of each trace file generated.
#namesctl.no_initial_server = False
#Syntax: T/F
#Default: False
# If set to TRUE namesctl will suppress any error messages when namesctl is
# unable to connect to a default names server.
#namesctl.internal_use = True
#Syntax: T/F
#Default: False
# If set to true namesctl will enable a set of internal undocumented commands.
# All internal commands are preceded by an underscore ('_') in order to
# distinguish them as internal. Without going into details, the commands
# enabled are:
# _max_reforwards _modify_ops_enabled
# _next_cache_checkpoint _next_cache_flush
# _next_stat_log _next_stat_reset
# _reload _request_delay
# _restart _shutdown
#namesctl.noconfirm = True
#Syntax: T/F
#Default: False
# When set to TRUE namesctl will suppress the confirmation prompt when
# sensitive operations (stop, restart, reload) are requested. This is
# quite helpful when using namesctl scripts.
#namesctl.server_password = mangler
#Syntax: string
#Default: NULL
# Automatically sets the password for the names server in order to perform
#Default: /.:/subsys/oracle/names
#Specifies the DCE cell (prefix) to use for name lookup.
#names.nds.name_context = personnel.acme
#Syntax: NDS name
#Default: (OSD?)
# Specifies the default NDS name context in which to look for the name to
# be resolved.
#names.nis.meta_map # NA
# Syntax: filename
# The acceptable difference in the number of seconds between when a
# credential was sent and when it was received.
#sqlnet.kerberos5_clockskew=600
#sqlnet.kerberos5_conf
# Syntax: Any valid pathname.
# Default: /krb5/krb.conf
# The Kerberos configuration pathname.
#sqlnet.kerberos5_conf=/tmp/mykrb.conf
#sqlnet.kerberos5_realms
# Syntax: Any valid pathname
# Default: /krb5/krb.realms
# The Kerberos host name to realm translation file.
#sqlnet.kerberos5_realms=/tmp/mykrb.realms
#sqlnet.kerberos5_keytab
# Syntax: Any valid pathname.
# Default: /etc/v5srvtab
# The Kerberos secret key file.
## Parameters used with Radius adapter
# Need to specify the location of the Radius server
#sqlnet.radius_authentication = localhost
# Need to specify the port address of the Radius server
#sqlnet.radius_authentication_port = 1654
# If your radius server support accounting, you can enable it
#sqlnet.radius_accounting = off
# Turn on/off challenge response
#sqlnet.radius_challenge_response = off
# Keyword to request a challenge from Radius server.
# If you use activcard, enter activcard
# If you use something else, enter challenge
#sqlnet.radius_challenge_keyword = challenge
# Enter the name of the client interface you want to use for challenge response
#sqlnet.radius_authentication_interface = DefaultRadiusInterface
# Where is the secret file locate
#sqlnet.radius_secret = $ORACLE_HOME/security/radius.key
# ACCEPTED The service will be active if the other side of the
# connection specifies "REQUESTED" or REQUIRED" and
# there is a compatible algorithm available on the other
# side; it will be inactive otherwise.
# REJECTED The service must not be active, and the connection
# will fail if the other side specifies "REQUIRED".
# REQUESTED The service will be active if the other side specifies
# "ACCEPTED", "REQUESTED", or "REQUIRED" and there is a
# compatible algorithm available on the other side; it
# will be inactive otherwise.
# REQUIRED The service must be active, and the connection will
# fail if the other side specifies "REJECTED" or if there
# is no compatible algorithm on the other side.
#sqlnet.crypto_checksum_types_client
#sqlnet.crypto_checksum_types_server
#sqlnet.encryption_types_client
#sqlnet.encryption_types_server
# These parameters control which algorithms will be made available for
#ssl_server_dn_match
# Systax: ON/OFF
# Default: OFF
# The ssl_server_dn_match parameter determines SSL behavior when the
# server's distinguished name does not match the service name. When
# set to ON, the names must match for a connection to be established.
# Leaving the parameter on OFF allows connection to servers where
# the names do not match. However, this may potentially allow servers
# to fake their identity.
#ssl_client_authentication
# Syntax: TRUE/FALSE
# Default: TRUE
# The ssl_client_authentication parameter controls whether the client
# is authenticated using SSL. This parameter should be set to FALSE if
# using a cipher suite that contains Diffie-Hellman anonymous
# authentication (DH_anon) or if using other non-SSL authentication
# methods.
#ssl_cipher_suites
# Syntax: (SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_SHA,
# SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_DES_CBC_SHA,
# SSL_DH_anon_WITH_3DES_EDE_CBC_SHA, SSL_DH_anon_WITH_RC4_128_MD5,
# SSL_DH_anon_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5,
# SSL_RSA_EXPORT_WITH_DES40_CBC_SHA,
# SSL_DH_anon_EXPORT_WITH_RC4_40_MD5,
# SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA)
# Default: All cipher suites enabled
# ssl_cipher_suites defines a list of cipher suites used to negotiate
# an SSL connection in order of priority. The cipher suites selected for
# a server must be compatible with those required by the client.
#ssl_version
# Syntax: 0/2.0/3.0
# Default: 0 (impiles 3.0)
# The ssl_version parameter defines the version of SSL that must
# run on the systems with which the client communicates.
# - SSL ---------------------------------------------------------------------
#my_wallet
# Syntax: A properly formatted NLNV list.
# Default: Platform specific. Unix: $HOME/oracle/oss
# The method for retrieving and storing my identity.
#my_wallet
# =(source
# =(method=file)
# (method_data=/dve/asriniva/oss/wallet)
# - Sqlnet(v2.x) and Net3.0 Client ------------------------------------------
# In the following descriptions, the term "client program" could mean
# either sqlplus, svrmgrl or any other OCI programs written by users
#trace_level_client = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the client program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#trace_directory_client = /oracle/network/trace
#Possible values: Any valid directory path with write permission
#Default: $ORACLE_HOME/network/trace ($ORACLE_HOME=/oracle at customer
# site)
#Purpose: Indicates the name of the directory to which trace files from
# the client execution are written.
#Supported since: v2.0
#trace_file_client = /oracle/network/trace/cli.trc
#Possible values: Any valid file name
#Default: $ORACLE_HOME/network/trace/cli.trc ($ORACLE_HOME =
# /oracle at customer site)
#Purpose: Indicates the name of the file to which the execution trace
# of the client is written to.
#Supported since: v2.0
#trace_unique_client = ON
#Possible values: {ON, OFF}
#Default: OFF
#Purpose: Used to make each client trace file have a unique name to
# prevent each trace file from being overwritten by successive
# runs of the client program
#Supported since: v2.0
#log_directory_client = /oracle/network/log
#Possible values: Any valid directory pathname
#Default: $ORACLE_HOME/network/log ($ORACLE_HOME = /oracle at customer
# site)
#Purpose: Indicates the name of the directory to which the client log file
# is written to.
#Supported since: v2.0
#log_file_client = /oracle/network/log/sqlnet.log
#Possible values: This is a default value, u cannot change this
#Default: $ORACLE_HOME/network/log/sqlnet.log ($ORACLE_HOME=/oracle in
# customer site)
#Purpose: Indicates the name of the log file from a client program
#Supported since: v2.0
#log_directory_server = /oracle/network/trace
#Possible values: Any valid diretcory path with write permission
#Default: $ORACLE_HOME/network/trace ( $ORACLE_HOME=/oracle at customer
# site)
#Purpose: Indicates the name of the directory to which log files from the
# server are written
#Supported since: v2.0
#trace_directory_server = /oracle/network/trace
#Possible values: Any valid directory path with write permission
#Default: $ORACLE_HOME/network_trace ( $ORACLE_HOME=/oracle at customer
# site)
#Purpose: Indicates the name of the directory to which trace files from
# the server are written
#Supported since: v2.0
#trace_file_server = /orace/network/trace/svr_<pid>.trc
#Possible values: Any valid filename
#Default: $ORACLE_HOME/network/trace/svr_<pid>.trc where <pid? stands for
# the process id of the server on UNIX systems
#Purpose: Indicates the name of the file to which the execution trace of
# the server program is written to.
#Supported since: v2.0
#trace_level_server = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the server program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#use_dedicated_server = ON
#Possible values: {OFF,ON}
#Default: OFF
#Purpose: Forces the listener to spawn a dedicated server process for
# sessions from this client program.
#Supported since: v2.0
#use_cman = TRUE
#Possible values: {TRUE, FALSE}
#Default: FALSE
#Purpose:
#Supported since: v3.0
#tnsping.trace_directory = /oracle/network/trace
#Possible values: Any valid directory pathname
#Default: $ORACLE_HOME/network/trace ($ORACLE_HOME=/oracle at customer
# site)
#Purpose: Indicates the directory to which the execution trace from
# the tnsping program is to be written to.
#Supported since: v2.0
#tnsping.trace_level = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the server program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#sqlnet.expire_time = 10
#Possible values: 0-any valid positive integer! (in minutes)
#Default: 0 minutes
#Recommended value: 10 minutes
#Purpose: Indicates the time interval to send a probe to verify the
# client session is alive (this is used to reclaim watseful
# resources on a dead client)
#Supported since: v2.1
#sqlnet.client_registration = <unique_id>
#Possible values:
#Default: OFF
#Purpose: Sets a unique identifier for the client machine. This
# identifier is then passed to the listener with any connection
# request and will be included in the Audit Trail. The identifier
# can be any alphanumeric string up to 128 characters long.
#Supported since: v2.3.2
#bequeath_detach = YES
#Possible values: {YES,NO}
#Default: NO
#Purpose: Turns off signal handling on UNIX systems. If signal handling
# were not turned off and if client programs written by users make
# use of signal handling they could interfere with Sqlnet/Net3.
#Supported since: v2.3.3
#automatic_ipc = OFF
#Possible values: {ON,OFF}
#Default: OFF
#Purpose: Force a session to use or not to use IPC addresses on the
# client's node.
#Supported since: v2.0
#disable_oob = ON
#Possible values: {ON,OFF}
#Default: OFF
#Purpose: If the underlying transport protocol (TCP, DECnet,...) does
# not support Out-of-band breaks, then disable out-of-band
# breaks
#Supported since: v2.0
#sqlnet.inbound_connect_timeout = 3
#Possible values: 0-any valid positive integer (in seconds)
#Default: 0
#Recommended value: 3 seconds (note: this is highly application dependent)
#Purpose: Indicates the time interval within which database authentication
# for a client must be completed. If the client fails to complete
# authentication within the given time period, then the database
# server will drop the client connection. This can be used to
# counter Denial of Service attacks in which malicious clients may
# cause numerous servers to be spawn without fully establishing DB
# sessions.
# A value of 0 turns off the timeout feature. If a spurious
# timeout error occurs (e.g. due to a slow network/system),
# reconfigure this parameter to a larger value.
#Supported since: v9.2
{code}
and my tns file entry is
{code}
# This file contains the syntax information for
# the entries to be put in any tnsnames.ora file
# The entries in this file are need based.
# There are no defaults for entries in this file
# that Sqlnet/Net3 use that need to be overridden
# Typically you could have two tnsnames.ora files
# in the system, one that is set for the entire system
# and is called the system tnsnames.ora file, and a
# second file that is used by each user locally so that
# he can override the definitions dictated by the system
# tnsnames.ora file.
# The entries in tnsnames.ora are an alternative to using
# the names server with the onames adapter.
# They are a collection of aliases for the addresses that
# the listener(s) is(are) listening for a database or
# several databases.
# The following is the general syntax for any entry in
# a tnsnames.ora file. There could be several such entries
# tailored to the user's needs.
<alias>= [ (DESCRIPTION_LIST = # Optional depending on whether u have
# one or more descriptions
# If there is just one description, unnecessary ]
(DESCRIPTION=
[ (SDU=2048) ] # Optional, defaults to 2048
# Can take values between 512 and 32K
[ (ADDRESS_LIST= # Optional depending on whether u have
# one or more addresses
# If there is just one address, unnecessary ]
(ADDRESS=
[ (COMMUNITY=<community_name>) ]
(PROTOCOL=tcp)
(HOST=<hostname>)
(PORT=<portnumber (1521 is a standard port used)>)
[ (ADDRESS=
(PROTOCOL=ipc)
(KEY=<ipckey (PNPKEY is a standard key used)>)
[ (ADDRESS=
[ (COMMUNITY=<community_name>) ]
(PROTOCOL=decnet)
(NODE=<nodename>)
(OBJECT=<objectname>)
... # More addresses
[ ) ] # Optional depending on whether ADDRESS_LIST is used or not
[ (CONNECT_DATA=
(SID=<oracle_sid>)
[ (GLOBAL_NAME=<global_database_name>) ]
[ (SOURCE_ROUTE=yes) ]
(DESCRIPTION=
[ (SDU=2048) ] # Optional, defaults to 2048
# Can take values between 512 and 32K
[ (ADDRESS_LIST= ] # Optional depending on whether u have more
# than one address or not
# If there is just one address, unnecessary
(ADDRESS
[ (COMMUNITY=<community_name>) ]
(PROTOCOL=tcp)
(HOST=<hostname>)
(PORT=<portnumber (1521 is a standard port used)>)
[ (ADDRESS=
(PROTOCOL=ipc)
(KEY=<ipckey (PNPKEY is a standard key used)>)
... # More addresses
[ ) ] # Optional depending on whether ADDRESS_LIST
# is being used
[ (CONNECT_DATA=
(SID=<oracle_sid>)
[ (GLOBAL_NAME=<global_database_name>) ]
[ (SOURCE_ROUTE=yes) ]
[ (CONNECT_DATA=
(SID=<oracle_sid>)
[ (GLOBAL_NAME=<global_database_name>) ]
... # More descriptions
[ ) ] # Optional depending on whether DESCRIPTION_LIST is used or not
{code}
DATABASE-10G CLIENTHi Rahul,
this question does not seem to be related to SQL and PL/SQL forum.
I guess you could use {forum:id=64} or {forum:id=61} forums.
Regards.
Al -
Unable to create database due to ORA-12560, TNS protocol adapter error
Hello,
I'm trying to create an 8.1.7.0 database on a W2k server, but it is failing because as soon as svrmgrl is launched, I get an ORA-12560, TNS: protocol adapter error:
D:\oracle\db_creation_scripts>D:\oracle\ora81\bin\svrmgrl @D:\oracle\db_creation_scripts\mterm62run.sql
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
ORA-12560: TNS:protocol adapter errorEcho ON
SVRMGR> connect INTERNAL/manager
ORA-12560: TNS:protocol adapter error
SVRMGR> startup nomount pfile="D:\oracle\admin\mterm62\pfile\initmterm62.ora"
LCC-00161: Message 161 not found; product=RDBMS; facility=MGR
My ORACLE_HOME, ORACLE_SID, and TNS_ADMIN environmental variables are correctly set, and I'm able to tnsping the listener.
I've enabled tracing, and my client trace file is:
--- TRACE CONFIGURATION INFORMATION FOLLOWS ---
New trace stream is d:\trace\client_trace.log_2084_9.trc
New trace level is 6
--- TRACE CONFIGURATION INFORMATION ENDS ---
--- PARAMETER SOURCE INFORMATION FOLLOWS ---
Attempted load of system pfile source d:\oracle\ora81\network\admin\sqlnet.ora
Parameter source loaded successfully
Attempted load of local pfile source D:\oracle\db_creation_scripts\sqlnet.ora
Parameter source was not loaded
-> PARAMETER TABLE LOAD RESULTS FOLLOW <-
Successful parameter table load
-> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <-
TRACE_DIRECTORY_SERVER = d:\trace
TRACE_DIRECTORY_CLIENT = d:\trace
NAMES.DIRECTORY_PATH = (TNSNAMES, HOSTNAME)
SQLNET.CRYPTO_SEED = 4fhfguweotcadsfdsafjkdsfqp5f201p45mxskdlfdasf
TRACE_FILE_CLIENT = client_trace.log
TRACE_FILE_SERVER = server_trace.log
SQLNET.AUTHENTICATION_SERVICES = (NTS)
TRACE_UNIQUE_CLIENT = on
TRACE_LEVEL_CLIENT = ADMIN
TRACE_LEVEL_SERVER = ADMIN
--- PARAMETER SOURCE INFORMATION ENDS ---
--- LOG CONFIGURATION INFORMATION FOLLOWS ---
Log stream will be "D:\oracle\db_creation_scripts\sqlnet.log"
Log stream validation not requested
--- LOG CONFIGURATION INFORMATION ENDS ---
nigini: entry
nigini: Count in NI global area now: 1
nigini: Count in NI global area now: 1
nrigbi: entry
nrigbni: entry
nrigbni: Unable to get data from navigation file tnsnav.ora
nrigbni: exit
nrigbi: exit
nigini: exit
niqname: Hst is already an NVstring.
niqname: Inserting CID.
niotns: entry
niotns: niotns: setting up interrupt handler...
niotns: Not trying to enable dead connection detection.
niotns: Calling address: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleMTERM62)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=MTERM62)(CID=(PROGRAM=D:\oracle\ora81\bin\SVRMGRL.EXE)(HOST=SERV0354)(USER=tarisa))))
nsmal: 140 bytes at 0x12493f0
nscall: connecting...
nladini: entry
nladini: exit
nladget: entry
nladget: exit
nlpcaini: entry
nlpcaini: prg =
nlpcaini: arg[0] =
nlpcaini: arg[1] =
nlpcaini: exit
nsmal: 420 bytes at 0x12542f0
nsmal: 1712 bytes at 0x12572f0
nsopen: opening transport...
ntpcon: entry
ntpcon: toc = 1
sntpcall: entry
snlpcss: entry
ntpcon: exit
nserror: nsres: id=0, op=65, ns=12560, ns2=0; nt[0]=530, nt[1]=2, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
nsopen: unable to open transport
nsmfr: 1712 bytes at 0x12572f0
nsmfr: 420 bytes at 0x12542f0
nladget: entry
nladget: exit
nsmfr: 140 bytes at 0x12493f0
nladtrm: entry
nladtrm: exit
nioqper: error from nscall
nioqper: nr err code: 0
nioqper: ns main err code: 12560
nioqper: ns (2) err code: 0
nioqper: nt main err code: 530
nioqper: nt (2) err code: 2
nioqper: nt OS err code: 0
niomapnserror: entry
niqme: entry
niqme: reporting NS-12560 error as ORA-12560
niqme: exit
niomapnserror: returning error 12560
niomapnserror: exit
niotns: Couldn't connect, returning 12560
niotns: exit
nigtrm: Count in the NI global area is now 0
nnfgdei: entry
nrigbd: entry
nrigbd: exit
nigtrm: Count in the NL global area is now 0
My tnsnames, listener and sqlnet.ora files are very simple:
## BEGIN TNSNAMES.ORA
# TNSNAMES.ORA Network Configuration File: D:\oracle\ora81\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
MTERM62 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.3.1.75)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = mterm62)
(INSTANCE_NAME = mterm62)
INST1_HTTP =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.3.1.75)(PORT = 1521))
(CONNECT_DATA =
(SERVER = SHARED)
(SERVICE_NAME = mterm62)
(PRESENTATION = http://admin)
# LISTENER.ORA Network Configuration File: D:\oracle\ora81\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = serv0354)(PORT = 1521))
SID_LIST_LISTENER =
(SID_DESC =
(ORACLE_HOME = D:\oracle\ora81)
(SID_NAME = mterm62)
TRACE_LEVEL_LISTENER = ADMIN
# SQLNET.ORA Network Configuration File: D:\oracle\ora81\NETWORK\ADMIN\sqlnet.ora
# Generated by Oracle configuration tools.
TRACE_DIRECTORY_CLIENT = d:\trace
TRACE_UNIQUE_CLIENT = on
TRACE_DIRECTORY_SERVER = d:\trace
SQLNET.AUTHENTICATION_SERVICES= (NTS)
TRACE_FILE_CLIENT = client_trace.log
TRACE_FILE_SERVER = server_trace.log
TRACE_LEVEL_CLIENT = ADMIN
TRACE_LEVEL_SERVER = ADMIN
NAMES.DIRECTORY_PATH= (TNSNAMES, HOSTNAME)
SQLNET.CRYPTO_SEED = 4fhfguweotcadsfdsafjkdsfqp5f201p45mxskdlfdasf
Does anyone have any ideas what else I can check. I'm a Unix person, not a Windows person, which is making it even more complicated. If I was on Unix, I'd just blow everything away and start again from scratch, but since I'm not sure how to remove all traces from the registry, etc., I don't want to try that on this machine. There was already one other database created, but it's not goign to be used.
Any help would be greatly appreciated.
regards,
Tarisa.hi,
thanks for the info. the problem, as it turns out, was that I was connected to the db server via a terminal service (Microsoft Management Console), which for some reason caused probelms with TNS. After I connected directly to the machine using VNC, I was able to create the database with no problems. strange but true.
regards,
Tarisa. -
Unable to open database connection after applicaiton is running for several days.
Has anyone experienced a similar error to this:
After about 3 days of use our application starts to report errors opening
the database connection. By that time we've had thousands of transactions
happen. Oracle is only showing a few open connections to our iAS host so
the error seems to indicate the connection pool. I'm configured for 64
connections (the default). We are using the Oracle native driver on iAS
SP3, Solaris.
The iAS ksvradmin monitor gives errors when trying to see how many open
connections it has (verified bug in SP3), so I can't get any info from iAS
on the connection pool.
Thanks in advance,
Rodger Ball
Sr. Engineer
Business WireiAS6 SP3 and earlier cannot detect dead connections. If connections become
stale, iAS does not detect this and will hand out these stale connections.
I don't know enough about your problem, but you can check for this.
hope this helps,
-James
"Rodger Ball" <[email protected]> wrote in message
news:9suucb$[email protected]..
Has anyone experienced a similar error to this:
After about 3 days of use our application starts to report errors opening
the database connection. By that time we've had thousands of transactions
happen. Oracle is only showing a few open connections to our iAS host so
the error seems to indicate the connection pool. I'm configured for 64
connections (the default). We are using the Oracle native driver on iAS
SP3, Solaris.
The iAS ksvradmin monitor gives errors when trying to see how many open
connections it has (verified bug in SP3), so I can't get any info from iAS
on the connection pool.
Thanks in advance,
Rodger Ball
Sr. Engineer
Business Wire
Maybe you are looking for
-
Sending groups of variable records in one e-mail to separate recipients.
I have a table that includes rows of pending actions pointing to duplicate e-mail addresses. I would like to send the addressees their respective action items in one e-mail to each person. The CFMail sends the pending action items to each in separate
-
How to Recover RPD in 10g Urgent
Hi Gurus, I was using my OBIEE 10g RPD and i created some columns and i click on Check Global consistence it work does not have any errors. Then when i click on Save button the RPD is not responding. I dont have any backup of the Code and today is th
-
Quicktime has broken iTunes - HELP!
Earlier today I opened iTunes and was about to buys some videos for my iPod. There was a notice at the top of the itunes store screen that said I needed to update Quicktime & iTunes in order to play & buy the videos. I clicked and followed the on scr
-
HT1311 I have done all the steps and it keeps saying my security code is invalid?
Not sure why it keeps saying my security code is invalid?? I have all the correct information
-
My I phone no power but charge totally out
My iPhone no power