Printable View
Hi everyone,
Now this is the environment that i am into. I am creating a database for demo purpose. I have installed Oracle Enterprise Edition 8.1.6 in Windows NT machine. During the creation of the database the system was connected in LAN. But i have created the database in my machine locally. So when i remove my machine for the LAN i am not able to login into my database. The database is in my machine. I am using a laptop. Could u assist me in knowing the problem. It is urgent.
Karthi
Go to your services and check whether there are oracle services, and they had been started. If not start them (like listeners and etc) then make sure that your database is up. Using oradim, start your database instance. then try connecting to the instance. From the sql for a fresh install it would be
sys/change_on_install
system/manager
Try that and let us know what the result is.
Sam
One point I forgot to point out is that on your laptop make sure that you have the tnsnames.ora file configured to look at the new installation on your NT. Then try connecting.
Sam
I tried stopping the database services and starting them again. But still the problem is there. Is that anything to do with the networking part. Please advise...
If you've installed Oracle 8i on your laptop then it has nothing to do with the network. Is the database up..? Pls check the background processes and the alert log for details.
Have you configured your listener.ora ?
Hi,
When i went into the alert log file i get this message.
SHUTDOWN: waiting for logins to complete.
Does this message mean that there are more number of logins that are present.
Karthi
it means that some user is still connected to your Oracle server and is waiting for it to disconnect. Pls kill any sessions which is still connected to your DB. This will bring down the Instance/DB.
Startup again. This should work fine.
Cheers,
One more alternative..#
svrmgrl
connect internal
shutdown abort
Then bring up the DB -
startup
No vinit,
I am the only person who is accessing the database. When i give shutdown it hangs. This is an additional problem. Could u explain this please
Karthi
Pls give shutdown abort as given in my earlier reply.
If you are on the NT, do Ctrl-ALt-Del, ther e choose the taskmanager, then go ahead and kill the tnslsnr.exe dbsnmp.exe, vppdc.exe, jrew.exe, launch.exe and all the other relevent processes. then try starting the database as follows.
startup mount
then
alter database open;
If you are not successfull in that of shuting down, issue
shutdown immediate
or shutdown abort
If you had issued shutdown, it would wait untill the connections are commited and released by the user. So you would want to issue shutdown immediate It will take a few seconds to minute. Then if that goes through, issue startup
.
Other wise issue startup force
Hope this would help you, good luck
sam
Vinit,
I tried Shutdown abort. It worked. Now i am able to shutdown the database only when i login as Internal. And that too i am not able to shutdown normally. I think the problem is with the NT software.
Karthi
I have my doubts..Can you shutdown your DB and get rid of any Oracle related processes which are still in the memory (hanged processes).
As I said earlier, just shutdown would wait for all the connection to be released and it will not indulge in killing the sessions, and it normally would take some time, or would wait untill the user exits. That is why oracle has the shutdown immediate. This would commit the changes to the database and then kill the sessions and shutdown the database. On the other hand when you issue dhutdown abort, the changes are not commited to the database, as a result when you start your database back, you would have to do a recovery to roll back the changes that are yet to be commited.
So normal word is "shutdown immediate"
To start up the database, you can do
startup
startup mount
alter database open;
startup nomount
alter database mount;
alter database open;
If you just want to bounce the server, then you can issue
startup force
Hope this would help you to undestand the diffence in the concepts.
Sam
I think the agent is running..That's why you get this error. Try giving dbsnmp_stop (at the listener prompt) and the shutdown the DB..Then after starting the DB give dbsnmp_start.
SPN