RE: dbca and ASM
- From: "Herring Dave - dherri" <Dave.Herring@xxxxxxxxxx>
- To: "Rajeev Prabhakar" <rprabha01@xxxxxxxxx>
- Date: Fri, 28 Sep 2007 16:22:18 -0500
Yup, saw that one. Not an issue:
% cat $ORA_ASM_HOME/network/admin/sqlnet.ora:
# sqlnet.ora.NODE1 Network Configuration File:
/u01/app/oracle/product/10.2.0/asm/network/admin/sqlnet.ora.NODE1
# Generated by Oracle configuration tools.
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
NAMES.DEFAULT_DOMAIN = corp.acxiom.net
Dave
___________________________________
David C. Herring, DBA | A c x i o m Delivery Center Organization
630-944-4762 office | 630-430-5988 wireless | 630-944-4989 fax
________________________________________
From: Rajeev Prabhakar [mailto:rprabha01@xxxxxxxxx]
Sent: Friday, September 28, 2007 4:18 PM
To: Herring Dave - dherri
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: dbca and ASM
Did you review metalink note 365428.1 ?
The Problem lies with Oracle Net configuration. If either of the following
parameters are set to anything other
than the default of "accepted" ,DBCA cannot communicate with the ASM instance.
SQLNET.ENCRYPTION_SERVER = accepted
SQLNET.ENCRYPTION_CLIENT = accepted
The problem was with encryption type of "DES40".
After removing "DES40" from both SQLNET.ENCRYPTION_TYPES_CLIENT and
SQLNET.ENCRYPTION_TYPES_SERVER communication between DBCA and ASM was
re-established.
The problem is that DES40 was specified as one of the encryption algorithms
and it doesn't play well with the jdbc
drivers. Per sections 5.1.2 of the 10.2 ASO guide, DES40 is not supported for
jdbc clients
Pasted below is the solution that it suggests..
------------------------------------------------------------------------------------------------------------------------------------------------------
Remove DES40 from Encryption Types
Old settings:
SQLNET.ENCRYPTION_TYPES_CLIENT= (DES40, RC4_40, RC4_56, 3DES112, 3DES168,
AES256)
SQLNET.ENCRYPTION_TYPES_SERVER= (DES40, RC4_40, RC4_56, 3DES112, 3DES168,
AES256)
New settings that work:
SQLNET.ENCRYPTION_TYPES_CLIENT= (RC4_40, RC4_56, 3DES112, 3DES168, AES256)
SQLNET.ENCRYPTION_TYPES_SERVER= (RC4_40, RC4_56, 3DES112, 3DES168, AES256)
------------------------------------------------------------------------------------------------------------------------------------------------------
Rajeev
On 9/28/07, Herring Dave - dherri <Dave.Herring@xxxxxxxxxx> wrote:
Folks,
I'm trying to create a database on my RAC cluster with ASM. This is on
10.2.0.3 and RHEL4 64bit. ASM is up and running on both nodes (only 2-node
cluster) and I've got valid diskgroups in each. Checking crsstat it shows all
services are up, as in ASM, LISTENER, gsd, ons, vip on both nodes.
Now for creating a database. I thought dbca would be the way. But in the
process, I believe step 7, I'm asked for the storage to use. I pick ASM, then
"next". At this point I get the message: "DBCA could not startup the ASM
instance configured on this node. To proceed with database creation using ASM
you ...".
I can't figure out why dbca can't see my ASM instance. I've tried setting
ORACLE_SID=, ORACLE_SID=+ASM, ORACLE_SID=+ASM1 (local instance on this server
of ASM), all run out of $ORACLE_HOME/bin, not $ORA_ASM_HOME/bin. Each try
gives me the same error.
Any clue how to get dbca see your existing ASM instances? Is there any way to
find out what exactly is failing behind the scenes? I've set tracing for dbca
(-DTRACING.ENABLED=true -DTRACING.LEVEL=2 in the last line of dbca), but that
doesn't output anything after first starting up.
Any help would be GREATLY appreciated. Thanks.
Dave
___________________________________
David C. Herring, DBA| A c x i o m Delivery Center Organization
630-944-4762office |630-430-5988 wireless|630-944-4989 fax
*************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be
legally privileged.
If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.
If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.
Thank you.
*************************************************************************
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
