RE: snort and oralce (snort 1.90)

["Kreimendahl, Chad J" <Chad.Kreimendahl () umb com>]

For Oracle, the answer is one of two things:  
 You should probably defined a default setting for the LAST_CID (should
probably also be done in the contrib sql file).  
AND
 The current version of spo_database does not work with oracle.  I
recommend you cvs back to version 1.55.  Some of the changes made to
move to DB Schema 106 will cause oracle errors, filling up your syslog
in a big hurry.  

        -----Original Message-----
        From: gongya [mailto:yu () dhcp-243-81 gongya net] 
        Sent: Friday, October 25, 2002 6:02 PM
        To: roman () danyliw com
        Cc: snort-users () lists sourceforge net
        Subject: [Snort-users] snort and oralce (snort 1.90)
        
        
        Hi, anyone knows why for the following messages ?
         
        snort -i hme0 -l ./log -c etc/snort.conf 
         
        ...............................
        database: compiled support for ( oracle )
        database: configured to use oracle
        database:          user = snort
        database: password is set
        database: database name = ocean
        database:   sensor name = 192.168.1.23
        database: oracle_error: ORA-01403: no data found
         
        database: oracle_error: ORA-01400: cannot insert NULL into
("SNORT"."SENSOR"."LAST_CID")
         
        database: oracle_error: ORA-01403: no data found
         
        database: Problem obtaining SENSOR ID (sid) from ocean->sensor
         
         When this plugin starts, a SELECT query is run to find the
sensor id for the
         currently running sensor. If the sensor id is not found, the
plugin will run
         an INSERT query to insert the proper data and generate a new
sensor id. Then a
         SELECT query is run to get the newly allocated sensor id. If
that fails then
         this error message is generated.
         
         Some possible causes for this error are:
          * the user does not have proper INSERT or SELECT privileges
          * the sensor table does not exist
         
         If you are _absolutely_ certain that you have the proper
privileges set and
         that your database structure is built properly please let me
know if you
         continue to get this error. You can contact me at
(roman () danyliw com).
         
        Fatal Error, Quitting..
        
        Note:
        1. Sensor is created.
        2. Have all the privileges for snort .
         
        thanks !!!
         
        Gongya Yu