AutoArchival?

[Yvonne]

Yes the LD_LIBRARY_PATH is set

LD_LIBRARY_PATH=/usr/openwin/lib:/usr/dt/lib:/usr/java/lib:/app/oracle/product/8.1.7/lib:/app/oracle/product/8.1.7/jdbc/lib

[sambavan]

That is correct. Do a ps -ef|grep your_instance2 and confirm that it had not been started. If it was running, then set your ORACLE_SID to it and connect through the server manager and issue a shutdown immediate. Then try to start the other instance. If that doesn't work,then, folloing the steps mention on A1, can you afford to bounce your server, to startup with?


Before bouncing the server, check /var/opt/oracle/oratab and make sure that the auto start option on the file for all the instance had been set to "N". Then bounce your server.

Then make sure that the

ORACLE_BASE=
ORACLE_HOME=$ORACLE_BASE/product/8.1.7
LD_LIBRARY_PATH=
PATH=$ORACLE_HOME/bin
ORACLE_SID=


Now log into server manager and try to issue the startup mount command. IF it were to come through, then proceed with the others. If not A1.3 or A1.4 and relink the oracle and try starting it in the nomount stage.

Please let me know of the results before doing the relinking. I'm in constant look out for your postings.

Sam



[Edited by sambavan on 05-02-2001 at 05:44 PM]

[gsprince]

can you verify the envoronment variables ORACLE_SID, ORACLE_HOME, LD_LIBRARY_PATH are all set and are having the value you expected.

If not set them. The easiest way to do that is to invoke the oracle_env.sh if one already exists. (usually under "oracle" user's home directory)

now,

% svrmgrl

svrmgrl> connect / as sysdba ;
(or connect internal)

svrmgrl > startup ;

Let us know of any problem u have.

[Yvonne]

yaaay!!

Rebooting the server helped with starting the instance. In all of our conversations I'm not sure what to start next. Should I try to uncomment the log lines in the ora file, shutdown the instance and then restart or try what Sam suggested:
- shutdown instance
- startup nomount
- alter database mount
- alter database open

Yvonne

[gsprince]

uncomment the needed lines

svrmgr> shutdown immediate ;

##u can alter those parameter without even shutting down the instance. Use the "ALter System dada.."

svrmgr> startup ;

[sambavan]

O.K that was a good news. Now as gsprince suggested shutdown your instance as immediate. Forget about the other linking and all for the time being.

Uncomment the archive log options in your initSID.ora, then try to start the instance on the mount stage.


startup nomount
alter database mount;
alter database open;
alter system archive log start;
shutdown immediate;
startup
archive log list;
select * from v$instance;

This should put and confirm your instance to be in the archive log mode.

Let us know if you have any problem.

Good luck,
Sam

[Edited by sambavan on 05-02-2001 at 08:19 PM]

[Yvonne]

Well I uncommented the log lines in the initSID.ora file and stopped and restarted the instance. It came up great!

When will I expect it to begin the archiving. Is there somewhere where a time is set to begin archiving?

Thank you so much for your help Sam and gsprince. I really appreciate it.

Time for a beer!

[sambavan]

you can see the logs that are being archive by

sqlplus sys

SQL> archive log list;

This would show you the log sequence number that is being archived.

You can also go to the archive log destination directory and do an ls and check it.


Have fun
Sam