I also implemented logon trigger to for audit purposes, and from trace files output and analysis from Oracle support, the problem was triggered before the logon trigger was fired.
Trace file extract :-
The statment is the same in all trace files
SELECT VALUE FROM NLS_INSTANCE_PARAMETERS WHERE PARAMETER ='NLS_DATE_FORMAT'
The error is a NLS date issue that can be caused by the jdbc version.
8000000100000010 2D303720 6C696E6B 65722063 6F6D6D61 [-07 linker comma]
8000000100000020 6E642073 3830302E 73677320 63727430 [nd s800.sgs crt0]
8000000100000030 2E6F2042 2E31312E 34332050 424F2030 [.o
B.11.43 PBO 0]
8000000100000040 35303132 34202400 63727430 3A206E75 [50124 $.crt0: nu]
8000000100000050 6D626572 20746F6F 206C6172 67652000 [mber too large .]
=> Logon trigger code followed.....
On 11/15/05, Radoulov, Dimitre <email@example.com> wrote:
>>> use logon triggers and see if you can spot then in module from v$session
As far as I know the v$session.module column is populated after a logon trigger is fired, so this is not possible.