[rt-users] Failed To Record Message

[Joop van de Wege]

Varun wrote:
> Hello All
> 
>  
> 
> I have problem with my RT we were previously running RT on oracle 9i. 
> Now we have shift it to oracle 10g . Now we are facing a strange problem 
> that we can access RT and can see our tickets but we are not been able 
> update any ticket or insert any comment or even insert any ticket also. 
> When I have looked at my logs it shows me like this
> 
>  
> 
> [Fri Jul 17 15:44:25 2009] [debug]: Guessed encoding: utf8 
> (/opt/rt3/lib/RT/I18N.pm:399)
> 
> [Fri Jul 17 15:44:25 2009] [debug]: Guessed encoding: ascii 
> (/opt/rt3/lib/RT/I18N.pm:399)
> 
> [Fri Jul 17 15:44:25 2009] [debug]: Guessed encoding: utf8 
> (/opt/rt3/lib/RT/I18N.pm:399)
> 
> [Fri Jul 17 15:44:25 2009] [debug]: Guessed encoding: ascii 
> (/opt/rt3/lib/RT/I18N.pm:399)
> 
> [Fri Jul 17 15:44:25 2009] [crit]: RT::Attachment->Create couldn't, as 
> you didn't specify a transaction (/opt/rt3/lib/RT/Attachment_Overlay.pm:145)
> 
> [Fri Jul 17 15:44:25 2009] [debug]: About to think about scrips for 
> transaction # (/opt/rt3/lib/RT/Transaction_Overlay.pm:165)
> 
> [Fri Jul 17 15:44:25 2009] [debug]: About to prepare scrips for 
> transaction # (/opt/rt3/lib/RT/Transaction_Overlay.pm:169)
> 
> [Fri Jul 17 15:44:25 2009] [debug]: Found 4 scrips 
> (/opt/rt3/lib/RT/Scrips_Overlay.pm:363)
> 
> [Fri Jul 17 15:44:25 2009] [debug]: About to commit scrips for 
> transaction # (/opt/rt3/lib/RT/Transaction_Overlay.pm:178)
> 
> [Fri Jul 17 15:44:25 2009] [warning]: Transaction Created 
> (/opt/rt3/lib/RT/Record.pm:1464)
> 
> [Fri Jul 17 15:44:25 2009] [err]: This is 
> transcation:RT::Transaction=HASH(0xad9da74) 
> (/opt/rt3/lib/RT/Ticket_Overlay.pm:2448)
> 
> [Fri Jul 17 15:44:25 2009] [err]: RT::Ticket=HASH(0xad74d48) couldn't 
> init a transaction Transaction Created 
> (/opt/rt3/lib/RT/Ticket_Overlay.pm:2451)

Since you're using separate servers for web and database you can run 
wireshark to sniff the sql that is created and what the error is that 
Oracle returns. That error should show up in the logs but it looks like 
it didn't in the logs that you posted. Is there nothing in 
rt.log/apache_error.log/syslog??
If not go the sniffing route and you should be able to find the error 
returned.

Regards,

Joop