Link to home
Create AccountLog in
Avatar of Wileciyote
WileciyoteFlag for United States of America

asked on

NetApp SMO ORA-00119 (..Local_Listener..) ORA-00132: syntax error or unresolved network name 'LISTENER_<NAME>

Hi,
 
   I have killed myself on this for days and have searched forum after forum without results. Any help will be greeted with bowing and scraping. (Please see bottom for updated info) Here is the setup:

1) A production Oracle Database running 10.2.0.5 with a Listener running on Port 1690. Solaris 10 Sparc.
2) NetApp Oracle Snap Manager 3.2
3) Two Snap Manager Repository Indexes on a separate binary install of Oracle 10.2.0.5 listening on ports 1521 and 1522.

The commands and issues.

I was able to create the repositories just fine and was able to take snapshots of all three databases. When it came time to run a preview of a Snap Restore, both Repository instances communicated to ports 1521 and 1522 on the other respective database to get a restoration plan. This worked whether the instances were up or down. The Listeners were of course up. Both repositories share the same TNS_ADMIN and ORACLE_HOME - separate spfiles and data-files.

When it came time to preview the restore for the production database, it showed the proper plan, when the database was up. The listener was up and it showed JDBC hitting it once. When the production database was down, the preview attempted to hit the production database three times with JDBC and failed to do a [STARTUP NOMOUNT]. The TNS_ADMIN is not shared with the repository databases. here is the command executed and the error.

smo backup restore -profile NDDB-FULL-SNAP -label F_A_20121107112828CST -complete -controlfiles -recover -alllogs -preview

SMO-13032: Cannot perform operation: Backup Restore Preview.  Root cause: ORACLE-20001: Error trying to change state to STARTED for database instance nddb: ORACLE-00001: Error executing SQL: [STARTUP NOMOUNT;].  The command returned: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_NDDB'

SMO-13048: Backup Restore Preview Operation Status: FAILED
Operation Id [2c9204103ae5e3d5013ae5e3e6950001] failed. Error: SMO-13032: Cannot perform operation: Backup Restore Preview.  Root cause: ORACLE-20001: Error trying to change state to STARTED for database instance nddb: ORACLE-00001: Error executing SQL: [STARTUP NOMOUNT;].  The command returned: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_NDDB'

The production database has been in place for six years so I don't believe it's entirely the problem. It has to be something simple. This works **when** the database is running but not when it is stopped. It should work.

I just found this in an audit file:

nddb@zorak> more nddb_ora_28397_1.aud
Audit file /nddbhome/nddb/Product/10.2.0/rdbms/audit/nddb_ora_28397_1.aud
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
ORACLE_HOME = /nddbhome/nddb/Product/10.2.0
System name:    SunOS
Node name:      zorak
Release:        5.10
Version:        Generic_147440-24
Machine:        sun4u
Instance name: nddb
Redo thread mounted by this instance: 0 <none>
Oracle process number: 0
Unix process pid: 28397, image: oracle@zorak

Fri Nov  9 11:57:42 2012
LENGTH : '156'
ACTION :[7] 'CONNECT'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[4] 'nddb'
CLIENT TERMINAL:[13] 'Not Available'
STATUS:[1] '0'
DBID:[0] ''


Here is an edit that I should have probably put in:

The production database listener.ora;

LISTENER_NDDB = (ADDRESS_LIST =
(ADDRESS= (PROTOCOL=tcp) (HOST=test-nddb) (PORT=1690))
)

SID_LIST_LISTENER_nddb = (SID_LIST=
(SID_DESC=
(SDU=32120)
(TDU=32120)
(SID_NAME=nddb)
(ORACLE_HOME=/nddbhome/nddb/Product/10.2.0)
)
)
PASSWORDS_LISTENER_nddb = test-nddbnddb

SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER_nddb=OFF

# Entry used by applications attaching the database in standalone mode

LISTENER_nddb_IPC = (ADDRESS=(PROTOCOL=ipc)(KEY=nddb))

SID_LIST_LISTENER_nddb_IPC = (SID_LIST=
(SID_DESC=(SID_NAME=nddb)(ORACLE_HOME=/nddbhome/nddb/Product/10.2.0))
)

LOCAL_LISTENER = (ADDRESS_LIST =
(ADDRESS= (PROTOCOL=tcp) (HOST=test-nddb) (PORT=1690))


The Repository DB's tnsnames.ora:

# tnsnames.ora Network Configuration File: /nddbhome/nddb/product/10.2.0/tns/tnsnames.ora
# Generated by Oracle configuration tools.

NDDBRPDB_IPC =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = ipc)(key=nddbrpdb))
(CONNECT_DATA=(SID = nddbrpdb))
)

# Entry used by applications attaching the database in standalone mode

LISTENER_NDDBRPDB =
(ADDRESS = (PROTOCOL = tcp)(HOST = zorak)(PORT = 1521))

ONDDBRPDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = tcp)(HOST = zorak)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = nddbrpdb)
)
)

onddb = (DESCRIPTION=
(SDU=32120)
(TDU=32120)
(ADDRESS=
(PROTOCOL=tcp)
(HOST=test-nddb)
(PORT=1690)
)
(CONNECT_DATA=
(SID=nddb)
)
)

LISTENER_NDDB =
(ADDRESS = (PROTOCOL = tcp)(HOST = test-nddb)(PORT = 1690))

# Entry used by applications attaching the database in standalone mode
nddb_ipc = (DESCRIPTION=
(ADDRESS= (PROTOCOL=ipc)(key=nddb))
(CONNECT_DATA=(SID=nddb))
)

ONDDBRPDB =
(DESCRIPTION =
(SDU = 32120)
(TDU = 32120)
(ADDRESS = (PROTOCOL = tcp)(HOST = zorak)(PORT = 1521))
(CONNECT_DATA =
(SID = nddbrpdb)
)
)

Everything in the tnsnames.ora responds to a tnsping.
ASKER CERTIFIED SOLUTION
Avatar of Wileciyote
Wileciyote
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Wileciyote

ASKER

Resolved in the Oracle Support Forum.