oracle 9i over hp us 11.11

[rahul s_1]

PLS GO THROUGH THE BELOW 2 OUTPUTS OF COMMAND "lsnrctl status" ...................

FIRST OUTPUT IS WHEN EVERYTHING IS OK & SECOND OUTPUT IS WHEN USER CAN'T LOGIN TO THE APPLICATION...... ....

I WANT HELP ON THE SECOND OUTPUT TO KNOW WHAT IS PROBLEM AND HOW TO RECTIFY IT....

$ lsnrctl status

LSNRCTL for HPUX: Version 9.2.0.1.0 - Production on 30-MAY-2007 12:30:18

Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=patna-pr)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for HPUX: Version 9.2.0.1.0 - Production
Start Date 20-MAY-2007 21:25:03
Uptime 9 days 15 hr. 5 min. 20 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /oracle/product/902/network/admin/listener.ora
Listener Log File /oracle/product/902/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=patna-pr)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "dotsoft" has 1 instance(s).
Instance "dot1", status READY, has 1 handler(s) for this service...
The command completed successfully



$ lsnrctl status

LSNRCTL for HPUX: Version 9.2.0.1.0 - Production on 30-MAY-2007 12:30:25

Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=patna-se)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for HPUX: Version 9.2.0.1.0 - Production
Start Date 30-MAY-2007 12:02:08
Uptime 0 days 0 hr. 28 min. 16 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /oracle/product/902/network/admin/listener.ora
Listener Log File /oracle/product/902/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=patna-se)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

[Piergiacomo Perini]

Hi Rahul and welcome to ITRC Forums,

the only difference from two log is :

Service "dotsoft" has 1 instance(s).
Instance "dot1", status READY, has 1 handler(s) for this service...

So, in my opinion your tnsnames.ora has been changed.
How your tnsnames.ora is ?

best regards
pg

And as Peter Godron says

Please also read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33
on how to reward any useful answers given to your questions.

[rahul s_1]

hello ,

Thanks for ur reply .... u r right about the difference in both the outputs . and this problem happening now a days frequently. May u suggest me wht to do..

Regards,

Rahul Singh

[Piergiacomo Perini]

Hi again,

in your "tnsnames.ora" there is a reference to "dotsoft" or to "dot1" ?
how is your "tnsnames.ora"?

regards
pg

[Ben Dehner]

As pointed out, the working version shows service "dotsoft" with instance "dot1"; in the non-working version, this entry isn't there. However, this has nothing to do with the tnsnames file.

First of all, look at the listener.ora file in $ORACLE_HOME/network/admin. It may or may not have a static entry for this particular instance. In general, it's better if you do not have a such an entry, so the system is using dynamic service registration.

With dynamic registration, when the instance is started up, it connects to the listener and registers itself. According to your "working" output, the instance name is "dot1", and the service name is "dotsoff". This data comes from the INSTANCE_NAME and SERVICE_NAMES init.ora parameters, respectively.

While you are having a problem, there is no service registration data. The clients are probably getting the error ORA-12154: TNS could not resolve service name. This error means that the client is talking to the listener, but the listener doesn't know about the particular instance. This could happen for two reasons: 1) the listener got goofed up and "lost" the service registration, or 2) the instance has crashed and been de-registered by the listener. Either way, check the listener log file (typically found in $ORACLE_HOME/network/log) for possible errors.

If the problem is (1), then this can be addressed by adding an entry to the listener.ora file, so that instance is permanently registered. If the problem is (2), then you need to restart the instance and find out why it crashed.

Also, I see in the output that you are running Oracle 9.2.0.1. The current version is 9.2.0.8, I'd recommend that you update to a more recent patch set. I'm sure there are many bugs that could cause either of the problems mentioned above.

[Ben Dehner]

Oops. I just noticed a mistake in my previous reply I wanted to correct. I stated that your client should be getting an error

ORA-12154: TNS: could not resolve service name.

This is incorrect. The 12154 error indicates that the client could not resolve the connection string to find the (IP, Port, SERVCIE_NAME | SID) it needed to connect to the database. This error should not happen unless there is a mis-configured client, regardless of the state of database or listener. If you are getting this error, you need to check the TNSNAMES file. The error that I would expect is

ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect
descriptor

In this case, the client is connecting to the listener, but the target instance is not registered with the listener. This was the condition I was describing in the original reply.