• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Getting OpenDBFile2 error is Unable to communicate with database driver process (99).

 1 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
simmons2112
New Member Send Private Message
Posts: 1
New Member
10/18/2011 2:20 PM
Our hardware dept. was messing with DNS settings and now the environment won't start.  I get

OpenDBFile2 error is Unable to communicate with database driver process (99).
  Additional information is 1167.

I know it's a database communication issue but when I got to start the listener I get:  lsnrctl:  File cannot be found

In $ORACLE_HOME/bin, lsnrctl is not present like it is on our other app server.

Am I looking in the wrong place?

Lawson is taking forever to get back to me.

Thanks in advance.
Tomwise
Advanced Member Send Private Message
Posts: 32
Advanced Member
10/19/2011 5:47 PM
the command to start the default listerner is:

lsnrctl start

The files it looks at are in $ORACLE_HOME/network/admin

There should be a listerner.ora and tnsnames.ora file located in that directory (unless you're not using a tnsnames.ora file and using a names server).

If the files are there and your listener starts (could already be running) type

tnsping service_name and see what it returns.

e.g.

LAW9PROD>tnsping law9prod.world

TNS Ping Utility for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Production o
n 19-OCT-2011 14:46:29

Copyright (c) 1997, 2005, Oracle. All rights reserved.

Used parameter files:
/oracle/app/oracle/product/10.2.0/network/admin/sqlnet.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
(HOST = 10.0.64.118)(PORT = 1526))) (CONNECT_DATA = (SID = law9)))
OK (20 msec)
LAW9PROD>

It should return your database connection and ip address.