Hello Anthony -
On Wed, 25 Aug 1999, Anthony Chan wrote:
> Hi Mike,
>
> I encountered two problems of using Oracle 8. The first one is Oracle
> core dump and the second one is about the Oracle efficiency.
>
> For the first problem, after I use the Oracle as session database, the
> Oracle server always core dump. From the reply of Oracle support, there
> is a bug in Oracle 8 that the core dump is due to the existence of null
> variables inside the SQL statements. However, they don't have a patch
> for our server. So, we have to avoid null variables. From the logfile, I
> found that there is always a null variable, servicetype, inside the
> insert sql statement, i.e. insert into RADONLINE (USERNAME,
> NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS,
> NASPORTTYPE,SERVICETYPE) values ('lawkei', '207.176.112.154', 20109,
> '295908866', 935519065,
> '208.151.66.123', 'Async', '').
>
> The workaround for this problem is to replace all null variables using a
> space. Can you do me a favour to tell me how to change the source code
> for the make it work?
>
You don't need to change the source code - all you need to do is change the
AddQuery definition in the SessionDatabase declaration:
<SessionDatabase SQL>
DBSource ....
DBUsername ....
DBAuth ....
AddQuery .......
.....
</SessionDatabase>
See Section 6.6 in the Radiator 2.14.1 reference manual for further details.
> The second problem is that, from the DBA of the Oracle, the Radiator is
> now using hardcored SQL statement to the session database. It would
> decrease the efficiency of the Oracle. If the frequency of delete and
> insert statements are very frequent, it would cause memory leak or even
> ora error: 4031. The dba suggest to use variable binding of the SQL
> statement.
>
> For the variable binding of SQL statements, it would consist of
> ora_login, ora_open, & ora_bind. I checked the source code, SessSQL.pm
> and SqlDb.pm, that they don't exist. How's your suggestion about it? Is
> that possible you can provide us with the variable binding SQL
> statements?
>
Because we use the DBI/DBD libraries, you will not see the Oracle-specific
routines in the Radiator source code. For the above problem you might be better
served with a Stored-Procedure inside Oracle, and use the SessionDatabase
AddQuery statement above to call it.
> Thank you for your attention.
>
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
