-
vms database startup problem
Hi All ,
one of our adminstrator copied all binaries , and datafiles from production box to disaster recovery box . but when i was trying to start the database
It is prompting TNS prompting during execution of command itself .
could anybody tell us what we are missing .
[ORACLE8]> svrmgrl
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
ORA-12162: TNS:service name is incorrectly specified
SVRMGR> connect internal
Password:
Password:
ORA-12162: TNS:service name is incorrectly specified
SVRMGR>
-
-
Originally posted by vishal sood
Check ur TNSNAMES.ora
Nope. Nothing to do with tnsnames.ora
The ORA_SID logical is not defined.
Run the correct ORAUSER_.COM file to set up your environment.
If you execute SVRMGRL in order to create a new instance, the ORASRV_BEQ
command file must already exist for this new instance.
The recommended solution to this problem is to run ORACLEINS to create your
new instance and tell it not to create the database files (the last question
it asks), i.e., exit out of ORACLEINS at this point.
This sets up your environment to allow you to go into SVRMGRL.
You have the ORAUSER_.COM file that sets up the environment and the
ORASRV_BEQ command file is created.
It has been 3 years I stopped working on VMS but loved it..
Sanjay G.
Oracle Certified Professional 8i, 9i.
"The degree of normality in a database is inversely proportional to that of its DBA"
-
Originally posted by SANJAY_G
It has been 3 years I stopped working on VMS but loved it..
Yeh! Great stuff! (UNIX with a human interface I always thought. That will get some reaction!) Though I only ever did Rdb on VMS.
-
Finaly started that Thanks Sanjay for your suggestion.
Just for the Benefit of Every one i posting method i adopted
1) took open VMS backup command into tape, all files ( binaries , datafiles).
2) Restored from tape to test machine . keeping instance name
3) modify listener.ora file (to change connect parameter )
4) modify ora_rdbms_sids.dat file to change node name. ( in open vms while automatically starting the database , system looks for this file )
5) run orauser_sid.com file to set environment
6) start orasrv_beq listener
7) svrmgrl
8) connect internal as sysdba
9) startup mount pfile=logical_name_for_path:init.ora
10) alter database open
-
VMS, bah. I'd rather work on Windont.
Jeff Hunter
-
Well, maybe netware, then Windont.
Jeff Hunter
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|