LogDigger Connector 3.0 released

31 views
Skip to first unread message

Radomir M

unread,
Feb 22, 2012, 3:06:50 AM2/22/12
to logdigger-connector
We're pleased to announce new major release of LogDigger Connector.
Here's what's new in v3.0:

- Built-in web UI to review error logs. No need for an external
service any more - your error reports and logs stay with you!
- Track user actions and have the recent usage history included with
the error report.
- Improved email notifier.
- Collect error notifications using RSS.
- Greatly improved documentation and examples (http://docs.bugsio.com/
display/logdigger/)

Standard edition is FREE for commercial use and distribution.

LogDigger Connector is available at http://logdigger.com

As always, we appreciate your feedback.

Regards,
Radomir
LogDigger Team

Prabhat Mishra

unread,
Nov 11, 2013, 11:25:19 PM11/11/13
to logdigger...@googlegroups.com
Hi,

Can someone from logdigger team please help me configuring store with oracle db. I am getting below error and have posted the same in your side but not getting any answer.

Please let me know if oracle is supported or not.
CREATE
TABLE "logdigger_errorlog" ("id" VARCHAR2(255) PRIMARY KEY NOT NULL ,
"time" TIMESTAMP NOT NULL , "prj" VARCHAR2(255) , "host" VARCHAR2(255) ,
"url" LONG , "err" INTEGER , "type" VARCHAR2(255) , "message" LONG ,
"st" LONG , "user" VARCHAR2(255) , "snip" LONG , "applog" LONG RAW ,
"ctx" LONG RAW , "cv0" VARCHAR2(255) , "cs0" VARCHAR2(255) , "cv1"
VARCHAR2(255) , "cs1" VARCHAR2(255) , "cv2" VARCHAR2(255) , "cs2"
VARCHAR2(255) , "cv3" VARCHAR2(255) , "cs3" VARCHAR2(255) , "cv4"
VARCHAR2(255) , "cs4" VARCHAR2(255) , PRIMARY KEY ("id") )
Error at Command Line:3 Column:203
Error report:
SQL Error: ORA-01754: a table may contain only one column of type LONG
01754. 00000 - "a table may contain only one column of type LONG"
*Cause: An attempt was made to add a LONG column to a table which already
had a LONG column. Note that even if the LONG column currently
in the table has already been marked unused, another LONG column
may not be added until the unused columns are dropped.
*Action: Remove the LONG column currently in the table by using the ALTER
TABLE command.

Thanks
Prabhat

Radomir Mladenovic

unread,
Nov 12, 2013, 2:37:40 AM11/12/13
to logdigger...@googlegroups.com
Try creating the table manually and using LOB instead of LONG.


Hope this helps.

Regards,
Radomir



--
You received this message because you are subscribed to the Google Groups "logdigger-connector" group.
To unsubscribe from this group and stop receiving emails from it, send an email to logdigger-conne...@googlegroups.com.
To post to this group, send email to logdigger...@googlegroups.com.
Visit this group at http://groups.google.com/group/logdigger-connector.
For more options, visit https://groups.google.com/groups/opt_out.

Reply all
Reply to author
Forward
0 new messages