Install RAC 11g2 : DBCA error with listener

Question

I get this error while create database with DBCA in RAC 11g2 installation.
ORA-00119: invalid specification for system parameter REMOTE_LISTENER
ORA-00132: syntax error or unresolved network name 'rac-scan.edu.vn:1521'
My scan listener :
[oracle@vm01 admin]$ srvctl config scan_listener
SCAN Listener LISTENER_SCAN1 exists. Port: TCP:1521
SCAN Listener LISTENER_SCAN2 exists. Port: TCP:1521
[oracle@vm01 admin]$ srvctl status scan_listener
SCAN Listener LISTENER_SCAN1 is enabled
SCAN listener LISTENER_SCAN1 is running on node vm02
SCAN Listener LISTENER_SCAN2 is enabled
SCAN listener LISTENER_SCAN2 is running on node vm01
[oracle@vm01 admin]$ srvctl status scan
SCAN VIP scan1 is enabled
SCAN VIP scan1 is running on node vm02
SCAN VIP scan2 is enabled
SCAN VIP scan2 is running on node vm01
[oracle@vm01 admin]$ srvctl config scan
SCAN name: rac-scan.edu.vn, Network: 1/10.10.10.0/255.255.255.0/eth2
SCAN VIP name: scan1, IP: /rac-scan.edu.vn/10.10.10.250
SCAN VIP name: scan2, IP: /rac-scan.edu.vn/10.10.10.251
So thanks
Chuong

Answer 1

I've had a very similar problem with DBCA and creation of an 11.2.0.3 database and this ORA-00119:Invalid specification for system parameter REMOTE_LISTENER ORA-00132: syntax error or unresolved network name 'orapscan:1521'.
The solution to my problem was that on the host (a production host) that I was trying to execute DBCA from if I did a 'tnsping orapscan' it did not resolve.
On our development host a 'tnsping oradscan' (oradscan is the scan equivalent in dev for our production equivalent orapscan) it resolves ok.
ie.
13:22:15[oracle@euxq10 [eu11d] ~]$tnsping oradscan
TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 08-APR-2013 13:22:20
Copyright (c) 1997, 2011, Oracle. All rights reserved.
Used parameter files:
/apps/oracle/network/sqlnet.ora
Used EZCONNECT adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=TCP)(HOST=10.3.55.34)(POR..... etc.....
In this case, it is resolved from EZCONNECT.
This then led us to look at the sqlnet.ora on both our development and production environments, and this is where we found a difference.
In our development environment in sqlnet.ora, we had -
NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, EZCONNECT)
But in our production environment in sqlnet.ora we had -
NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES)
Thus when we changed our sqlnet.ora in our production environment to include EZCONNECT - ie.
NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, EZCONNECT)
Then when we retried the DBCA create, we did not receive this ORA-00119 / ORA-00132 error with parameter REMOTE_LISTENER.
Anyway, this was the solution to my problem. Hope it helps others.
Regards,
Roger