Program in v$session

"Phil Kaufman" wrote in
newsQDMa.169$We4.23047256@mantis.golden.net:

> Hi folks.
>
> I have two 8.1.7 environments, one local, one remote. I noticed in
> v$session, the program column is populated on connection by our
> application on local db, yet on the remote database, it does not. Can
> anyone point me in the direction as to the possible difference in
> environment that would explain this? Our application runs on Windows
> 98 or better at our client's site.
>
> Many thanks.
>
> Phil
>
>
>
There were quite a few issues with sqlnet versions and a database being
at 8.1.7 not having a populated program name in v$session. A search on
metalink should give you exact versions.

Scott Gamble wrote in message news:...
> "Phil Kaufman" wrote in
> newsQDMa.169$We4.23047256@mantis.golden.net:
>
> > Hi folks.
> >
> > I have two 8.1.7 environments, one local, one remote. I noticed in
> > v$session, the program column is populated on connection by our
> > application on local db, yet on the remote database, it does not. Can
> > anyone point me in the direction as to the possible difference in
> > environment that would explain this? Our application runs on Windows
> > 98 or better at our client's site.
> >

I can't tell you what causes this. However, DBMS_APPLICATION_INFO.SET_MODULE()
is a rather effective workaround. The values that you plug into set_module()
will show up in v$session as the module & action columns

> > Many thanks.
> >
> > Phil
> >
> >
> >
> There were quite a few issues with sqlnet versions and a database being
> at 8.1.7 not having a populated program name in v$session. A search on
> metalink should give you exact versions.