" /> Confserv / dbserver on Oracle - where does dbserver get the ORACLE_HOME value? - Genesys CTI User Forum

Author Topic: Confserv / dbserver on Oracle - where does dbserver get the ORACLE_HOME value?  (Read 10918 times)

Offline mark

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Advertisement
The issue is with outbound dialling, starting the config layer is fine, everything works except outbound.



Offline Sylvainsjc

  • Full Member
  • ***
  • Posts: 137
  • Karma: 2
Hello Mark,
René provided again the correct answer with lca. I was also asking me how SCI could start applications with necessary environment variables on Unix.

I found this on DBserver User's Guide :

[i]Note that when you start the DB Server through the Management Layer, the server inherits environment variables from the Local Control Agent (LCA) component, which executes the startup command. That means you must also set the environment variables required for DB Server for the account that runs LCA. See Chapter 2, “DBMS Environment Settings,” on page 19 for more information.[/i]

Was this your problem ?

Offline mark

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Nope, it's a completely unrelated problem.
Oddly, starting the dbserver from command line also gave the same ORACLE_HOME, which is where our confusion laid.

The actual resolution to the main issue has still not been solved and chances are we will need to perform the 10g upgrade again in our prod environment just to see if we can replicate the issue!
Nightmare.

Mark

AsT

  • Guest
Mark, could you post your .profile so we can take a look?  I used to do a lot of unix and our Oracle DBA hid his information in a file used by the .profile.  So if you look at the .profile you never would see the Oracle reference.  But if you looked close you could see the reference.

thanks,
AsT

Offline mark

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Issue was actually nothing to do with the oracle profile!
installing another instance of dbserver for outbound (which is out of scope..) solved the issue.

Weird!