Oracle Database Discussions

Hi,

I have killed myself on this for days and have searched forum after forum without results. 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. (Same host)

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 databases 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

[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'

[ERROR] 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 and has no problem starting when logging in as sysdba 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.

Edited by: user11377518 on Nov 9, 2012 9:13 AM