Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Eventeditor and Timestamp-Format

13 posts in General Discussion Last posting was on 2008-01-25 08:52:47.0Z
Andreas Dorn Posted on 2008-01-21 11:15:22.0Z
From: Andreas Dorn <adornno1@web.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Eventeditor and Timestamp-Format
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 62.152.177.65
X-Original-NNTP-Posting-Host: 62.152.177.65
Message-ID: <47947eca$1@forums-1-dub>
Date: 21 Jan 2008 03:15:22 -0800
X-Trace: forums-1-dub 1200914122 62.152.177.65 (21 Jan 2008 03:15:22 -0800)
X-Original-Trace: 21 Jan 2008 03:15:22 -0800, 62.152.177.65
Lines: 14
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6681
Article PK: 4930

I'm testing a Database on 10.0.1.3619 and the Event Editor
of Sybase Central doesn't work. (I get an error when trying
to view the list of events).
In the Database the timestamp_Format is set to
DD.MM.YYYY HH:NN:SS.SSSSSS
and I think the Cast to Timestamp in the Select that Sybase Central uses
doesn't work.

SELECT
CAST( DB_EXTENDED_PROPERTY( 'NextScheduleTime', E.event_name ) AS
TIMESTAMP)
FROM SYS.SYSEVENT E

Any suggestions?


Chris Keating (Sybase iAnywhere) Posted on 2008-01-21 13:45:25.0Z
From: "Chris Keating (Sybase iAnywhere)" <keating_spam_free@ianywhere.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub>
In-Reply-To: <47947eca$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: keating-d620.sybase.com
X-Original-NNTP-Posting-Host: keating-d620.sybase.com
Message-ID: <4794a1f5$1@forums-1-dub>
Date: 21 Jan 2008 05:45:25 -0800
X-Trace: forums-1-dub 1200923125 10.25.99.145 (21 Jan 2008 05:45:25 -0800)
X-Original-Trace: 21 Jan 2008 05:45:25 -0800, keating-d620.sybase.com
Lines: 18
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6682
Article PK: 4931

Try changing the DATE_ORDER option to 'DMY' to match your timestamp
format order.

Andreas Dorn wrote:
> I'm testing a Database on 10.0.1.3619 and the Event Editor
> of Sybase Central doesn't work. (I get an error when trying
> to view the list of events).
> In the Database the timestamp_Format is set to
> DD.MM.YYYY HH:NN:SS.SSSSSS
> and I think the Cast to Timestamp in the Select that Sybase Central uses
> doesn't work.
>
> SELECT
> CAST( DB_EXTENDED_PROPERTY( 'NextScheduleTime', E.event_name ) AS
> TIMESTAMP)
> FROM SYS.SYSEVENT E
>
> Any suggestions?


Andreas Dorn Posted on 2008-01-21 16:26:54.0Z
From: Andreas Dorn <adornno1@web.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub>
In-Reply-To: <4794a1f5$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 62.152.177.65
X-Original-NNTP-Posting-Host: 62.152.177.65
Message-ID: <4794c7ce$1@forums-1-dub>
Date: 21 Jan 2008 08:26:54 -0800
X-Trace: forums-1-dub 1200932814 62.152.177.65 (21 Jan 2008 08:26:54 -0800)
X-Original-Trace: 21 Jan 2008 08:26:54 -0800, 62.152.177.65
Lines: 12
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6683
Article PK: 4932

Chris Keating (Sybase iAnywhere) schrieb:

>> I'm testing a Database on 10.0.1.3619 and the Event Editor
>> of Sybase Central doesn't work.

> Try changing the DATE_ORDER option to 'DMY' to match your timestamp
> format order.

OK, thanks. With that the Event-Editor works. The clients usually use a
'YYYY-MM-DD' syntax, so I think theoretically I would be able to change
the option globally.
But to be on the safe side maybe I should set the option just temporary
for the connection of SybaseCentral?!?


"Frank Ploessel" <fpl... Posted on 2008-01-21 17:40:35.0Z
Subject: Re: Eventeditor and Timestamp-Format
From: "Frank Ploessel" <fpl...@d_e.i_m_s_h_e_a_l_t_h.c_o_m>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <4794c7ce$1@forums-1-dub>
Content-Transfer-Encoding: 7bit
Message-ID: <op.t5ajdxyij0bybf@bonw00164.internal.imsglobal.com>
User-Agent: Opera Mail/9.21 (Win32)
NNTP-Posting-Host: mail.taskarena-software-engineering.net
X-Original-NNTP-Posting-Host: mail.taskarena-software-engineering.net
Date: 21 Jan 2008 09:40:35 -0800
X-Trace: forums-1-dub 1200937235 217.76.101.130 (21 Jan 2008 09:40:35 -0800)
X-Original-Trace: 21 Jan 2008 09:40:35 -0800, mail.taskarena-software-engineering.net
Lines: 22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6685
Article PK: 4935

Andreas,

I just would set it at the same level where you change timestamp_format to
keep them in sync.

Frank

On Mon, 21 Jan 2008 17:26:54 +0100, Andreas Dorn <adornno1@web.de> wrote:

> Chris Keating (Sybase iAnywhere) schrieb:
>>> I'm testing a Database on 10.0.1.3619 and the Event Editor
>>> of Sybase Central doesn't work.
>
>> Try changing the DATE_ORDER option to 'DMY' to match your timestamp
>> format order.
>
> OK, thanks. With that the Event-Editor works. The clients usually use a
> 'YYYY-MM-DD' syntax, so I think theoretically I would be able to change
> the option globally.
> But to be on the safe side maybe I should set the option just temporary
> for the connection of SybaseCentral?!?


Andreas Dorn Posted on 2008-01-22 07:44:44.0Z
From: Andreas Dorn <adornno1@web.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <4794c7ce$1@forums-1-dub> <op.t5ajdxyij0bybf@bonw00164.internal.imsglobal.com>
In-Reply-To: <op.t5ajdxyij0bybf@bonw00164.internal.imsglobal.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 62.152.177.65
X-Original-NNTP-Posting-Host: 62.152.177.65
Message-ID: <47959eec$1@forums-1-dub>
Date: 21 Jan 2008 23:44:44 -0800
X-Trace: forums-1-dub 1200987884 62.152.177.65 (21 Jan 2008 23:44:44 -0800)
X-Original-Trace: 21 Jan 2008 23:44:44 -0800, 62.152.177.65
Lines: 26
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6686
Article PK: 4934


Frank Ploessel wrote:
> On Mon, 21 Jan 2008 17:26:54 +0100, Andreas Dorn <adornno1@web.de> wrote:
>> Chris Keating (Sybase iAnywhere) schrieb:
>>> Try changing the DATE_ORDER option to 'DMY' to match your timestamp
>>> format order.
>>
>> OK, thanks. With that the Event-Editor works. The clients usually use
>> a 'YYYY-MM-DD' syntax, so I think theoretically I would be able to change
>> the option globally.
>> But to be on the safe side maybe I should set the option just temporary
>> for the connection of SybaseCentral?!?
>

> I just would set it at the same level where you change
> timestamp_format to keep them in sync.

I'd really like to change the database options, but I'm trying to
migrate from a 9.02 database. And setting the options to different
values than the 9.02 database had could be a problem for some
client application.

Changing the DMY option really sounds best, but if it's just the
event editor that needs that I think I'd prefere to set a temporary
option whenever I need the event editor...

--
Andreas


Breck Carter [Team iAnywhere] Posted on 2008-01-22 14:37:25.0Z
From: "Breck Carter [Team iAnywhere]" <NOSPAM__bcarter@risingroad.com>
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
Organization: RisingRoad Professional Services
Reply-To: NOSPAM__bcarter@risingroad.com
Message-ID: <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com>
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.640
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: bcarter.sentex.ca
X-Original-NNTP-Posting-Host: bcarter.sentex.ca
Date: 22 Jan 2008 06:37:25 -0800
X-Trace: forums-1-dub 1201012645 64.7.134.118 (22 Jan 2008 06:37:25 -0800)
X-Original-Trace: 22 Jan 2008 06:37:25 -0800, bcarter.sentex.ca
Lines: 63
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6687
Article PK: 4936

This is an *interesting* problem, because (in my opinion) an
*internal* function (PROPERTY, etc) that *always* returns a character
string should not have its return value profoundly influenced by
database options that are documented to affect only *input/output*
operations. Especially without documenting that fact.

It is my opinion that PROPERTY and the like, when returning strings
containing dates and timestamps, should use the standard ISO format.
That format can be converted to date and timestamp datatypes
regardless of the input/output option settings (see example below).

In other words, this whole thread came as a complete surprise to me,
and I would have bet money that Chris' original response was wrong.
That means I owe Chris a Beer Voucher.

Breck

BEGIN
DECLARE @s1 LONG VARCHAR;
DECLARE @s2 LONG VARCHAR;
DECLARE @t1 TIMESTAMP;
DECLARE @t2 TIMESTAMP;

SET @s1 = '2001-12-28 23:59:01'; -- standard format always works
SET @s2 = '12-29-2001 23:59:01'; -- otherwise must agree with
DATE_ORDER

SET TEMPORARY OPTION DATE_ORDER = 'MDY';
SET TEMPORARY OPTION TIMESTAMP_FORMAT = 'MM.DD.YYYY HH NN SS.SSS';
SET @t1 = CAST ( @s1 AS TIMESTAMP );
SET @t2 = CAST ( @s2 AS TIMESTAMP );

SELECT @t1, @t2;
END;

On 21 Jan 2008 05:45:25 -0800, "Chris Keating (Sybase iAnywhere)"

<keating_spam_free@ianywhere.com> wrote:

>Try changing the DATE_ORDER option to 'DMY' to match your timestamp
>format order.
>
>Andreas Dorn wrote:
>> I'm testing a Database on 10.0.1.3619 and the Event Editor
>> of Sybase Central doesn't work. (I get an error when trying
>> to view the list of events).
>> In the Database the timestamp_Format is set to
>> DD.MM.YYYY HH:NN:SS.SSSSSS
>> and I think the Cast to Timestamp in the Select that Sybase Central uses
>> doesn't work.
>>
>> SELECT
>> CAST( DB_EXTENDED_PROPERTY( 'NextScheduleTime', E.event_name ) AS
>> TIMESTAMP)
>> FROM SYS.SYSEVENT E
>>
>> Any suggestions?

--
Breck Carter [Team iAnywhere]
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
The book: http://www.risingroad.com/SQL_Anywhere_Studio_9_Developers_Guide.html
breck.carter@risingroad.com


Andreas Dorn Posted on 2008-01-24 15:35:27.0Z
From: Andreas Dorn <adornno1@web.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com>
In-Reply-To: <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4798b03f$1@forums-1-dub>
Date: 24 Jan 2008 07:35:27 -0800
X-Trace: forums-1-dub 1201188927 10.22.241.152 (24 Jan 2008 07:35:27 -0800)
X-Original-Trace: 24 Jan 2008 07:35:27 -0800, vip152.sybase.com
Lines: 69
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6691
Article PK: 4940

Sadly the problems today got even more interesting because today
the Database crashed several times.

Where should I send the mini_cores and crash_logs to?

Breck Carter [Team iAnywhere] schrieb:

> This is an *interesting* problem, because (in my opinion) an
> *internal* function (PROPERTY, etc) that *always* returns a character
> string should not have its return value profoundly influenced by
> database options that are documented to affect only *input/output*
> operations. Especially without documenting that fact.
>
> It is my opinion that PROPERTY and the like, when returning strings
> containing dates and timestamps, should use the standard ISO format.
> That format can be converted to date and timestamp datatypes
> regardless of the input/output option settings (see example below).
>
> In other words, this whole thread came as a complete surprise to me,
> and I would have bet money that Chris' original response was wrong.
> That means I owe Chris a Beer Voucher.
>
> Breck
>
> BEGIN
> DECLARE @s1 LONG VARCHAR;
> DECLARE @s2 LONG VARCHAR;
> DECLARE @t1 TIMESTAMP;
> DECLARE @t2 TIMESTAMP;
>
> SET @s1 = '2001-12-28 23:59:01'; -- standard format always works
> SET @s2 = '12-29-2001 23:59:01'; -- otherwise must agree with
> DATE_ORDER
>
> SET TEMPORARY OPTION DATE_ORDER = 'MDY';
> SET TEMPORARY OPTION TIMESTAMP_FORMAT = 'MM.DD.YYYY HH NN SS.SSS';
> SET @t1 = CAST ( @s1 AS TIMESTAMP );
> SET @t2 = CAST ( @s2 AS TIMESTAMP );
>
> SELECT @t1, @t2;
> END;
>
> On 21 Jan 2008 05:45:25 -0800, "Chris Keating (Sybase iAnywhere)"
> <keating_spam_free@ianywhere.com> wrote:
>
>> Try changing the DATE_ORDER option to 'DMY' to match your timestamp
>> format order.
>>
>> Andreas Dorn wrote:
>>> I'm testing a Database on 10.0.1.3619 and the Event Editor
>>> of Sybase Central doesn't work. (I get an error when trying
>>> to view the list of events).
>>> In the Database the timestamp_Format is set to
>>> DD.MM.YYYY HH:NN:SS.SSSSSS
>>> and I think the Cast to Timestamp in the Select that Sybase Central uses
>>> doesn't work.
>>>
>>> SELECT
>>> CAST( DB_EXTENDED_PROPERTY( 'NextScheduleTime', E.event_name ) AS
>>> TIMESTAMP)
>>> FROM SYS.SYSEVENT E
>>>
>>> Any suggestions?
>
> --
> Breck Carter [Team iAnywhere]
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com
> The book: http://www.risingroad.com/SQL_Anywhere_Studio_9_Developers_Guide.html
> breck.carter@risingroad.com


Jeff Albion (Sybase iAnywhere) Posted on 2008-01-24 16:01:17.0Z
From: "Jeff Albion (Sybase iAnywhere)" <firstname.lastname@ianywhere.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com> <4798b03f$1@forums-1-dub>
In-Reply-To: <4798b03f$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4798b64d$1@forums-1-dub>
Date: 24 Jan 2008 08:01:17 -0800
X-Trace: forums-1-dub 1201190477 10.22.241.152 (24 Jan 2008 08:01:17 -0800)
X-Original-Trace: 24 Jan 2008 08:01:17 -0800, vip152.sybase.com
Lines: 28
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6692
Article PK: 4941


Andreas Dorn wrote:
> Sadly the problems today got even more interesting because today
> the Database crashed several times.
>
> Where should I send the mini_cores and crash_logs to?

Which version did it crash on? I notice that you were testing on
10.0.1.3619 - is this the correct version? Which OS is this - Windows?

If you have a technical support contract or if you have an urgent need
for this to be resolved immediately, please open a Technical Support
case. ( http://www.ianywhere.com/support/support.html )

If not, did the dbsupport tool log a crash and submit it already?
(dbsupport -ls) Is there a submission outstanding? (dbsupport -lc). If
it's outstanding, please submit it and our engineers will examine it
further. (dbsupport -sa).

Regards,

--
Jeff Albion, Product Support Analyst
Sybase iAnywhere

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs :
http://downloads.sybase.com/swd/summary.do?baseprod=144&client=ianywhere&timeframe=0


Andreas Dorn Posted on 2008-01-24 16:43:05.0Z
From: Andreas Dorn <adornno1@web.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com> <4798b03f$1@forums-1-dub> <4798b64d$1@forums-1-dub>
In-Reply-To: <4798b64d$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4798c019$1@forums-1-dub>
Date: 24 Jan 2008 08:43:05 -0800
X-Trace: forums-1-dub 1201192985 10.22.241.152 (24 Jan 2008 08:43:05 -0800)
X-Original-Trace: 24 Jan 2008 08:43:05 -0800, vip152.sybase.com
Lines: 84
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6693
Article PK: 4942

Jeff Albion (Sybase iAnywhere) schrieb:

> Andreas Dorn wrote:
>> Sadly the problems today got even more interesting because today
>> the Database crashed several times.
>>
>> Where should I send the mini_cores and crash_logs to?
>
> Which version did it crash on? I notice that you were testing on
> 10.0.1.3619 - is this the correct version? Which OS is this - Windows?

Yes, 10.0.1.3619. There were 2 crashes on a Windows 2003 Server, and
later one on a Windows XP machine.

> If you have a technical support contract or if you have an urgent need
> for this to be resolved immediately, please open a Technical Support
> case. ( http://www.ianywhere.com/support/support.html )

I don't have a support contract, I'll look into that...

> If not, did the dbsupport tool log a crash and submit it already?
> (dbsupport -ls) Is there a submission outstanding? (dbsupport -lc). If
> it's outstanding, please submit it and our engineers will examine it
> further. (dbsupport -sa).

The reports aren't submitted yet - the servers don't have a direct
internet-connection. I'll have to copy the files and send them from
elsewhere.

I guess dbsupport will need the following files:
sadiags.xml
*.crash_log
*.mini_core
?!?

I'll add two of the crash_logs below:

VERSION=10.0.1.3619
FILENAME=C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\SQL
Anywhere 10\diagnostics\SA10_20080124_142415_856.crash_log
OS=Windows XP Build 2600 Service Pack 2
PROCESSOR=X86_64
EXEC_ARCH=X86
EXEC_PATH=C:\Programme\SQL Anywhere 10\win32\dbsrv10.exe
MODULE_PATH=C:\Programme\SQL Anywhere 10\win32\dbserv10.dll
EXCEPTION_PTR=028CFA48
EXCEPTION_CODE=3221225477
EXCEPTION_FLAGS=0
EXCEPTION_RECORD=00000000
EXCEPTION_ADDRESS=005B2F31
EXCEPTION_NumParameters=2
EXCEPTION_Param0=00000000
EXCEPTION_Param1=5C84B000
TRYING_TO_SAVE_MINI_DUMP C:\Dokumente und Einstellungen\All
Users\Anwendungsdaten\SQL Anywhere
10\diagnostics\SA10_20080124_142415_856.mini_core
DUMPLEVEL 0
SAVING_MINI_DUMP_COMPLETED
CRASH_LOG_COMPLETE
ATTEMPTING_TO_SUBMIT_MINIDUMP...


VERSION=10.0.1.3619
FILENAME=C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\SQL
Anywhere 10\diagnostics\SA10_20080124_084214_1172.crash_log
OS=Windows 2003 Build 3790 Service Pack 2
PROCESSOR=X86_64
EXEC_ARCH=X86
EXEC_PATH=C:\Programme\SQL Anywhere 10\win32\dbsrv10.exe
MODULE_PATH=C:\Programme\SQL Anywhere 10\win32\dbserv10.dll
EXCEPTION_PTR=0B2EFA50
EXCEPTION_CODE=3221225477
EXCEPTION_FLAGS=0
EXCEPTION_RECORD=00000000
EXCEPTION_ADDRESS=005B2F31
EXCEPTION_NumParameters=2
EXCEPTION_Param0=00000000
EXCEPTION_Param1=01FF900F
TRYING_TO_SAVE_MINI_DUMP C:\Dokumente und Einstellungen\All
Users\Anwendungsdaten\SQL Anywhere
10\diagnostics\SA10_20080124_084214_1172.mini_core
DUMPLEVEL 0
SAVING_MINI_DUMP_COMPLETED
CRASH_LOG_COMPLETE
ATTEMPTING_TO_SUBMIT_MINIDUMP...


Jeff Albion (Sybase iAnywhere) Posted on 2008-01-24 21:51:34.0Z
From: "Jeff Albion (Sybase iAnywhere)" <firstname.lastname@ianywhere.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com> <4798b03f$1@forums-1-dub> <4798b64d$1@forums-1-dub> <4798c019$1@forums-1-dub>
In-Reply-To: <4798c019$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47990866$1@forums-1-dub>
Date: 24 Jan 2008 13:51:34 -0800
X-Trace: forums-1-dub 1201211494 10.22.241.152 (24 Jan 2008 13:51:34 -0800)
X-Original-Trace: 24 Jan 2008 13:51:34 -0800, vip152.sybase.com
Lines: 21
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6694
Article PK: 4943


Andreas Dorn wrote:
> I guess dbsupport will need the following files:
> sadiags.xml
> *.crash_log
> *.mini_core
> ?!?

Probably the easiest thing to do would be to install SQL Anywhere 10 on
a computer that is connected to the internet (Developer edition would
do), then copy the C:\Documents and Settings\All Users\Application
Data\SQL Anywhere 10\diagnostics directory over. You should be able to
do the "dbsupport -sa" command at that point.

--
Jeff Albion, Product Support Analyst
Sybase iAnywhere

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs :
http://downloads.sybase.com/swd/summary.do?baseprod=144&client=ianywhere&timeframe=0


Andreas Dorn Posted on 2008-01-25 07:52:50.0Z
From: Andreas Dorn <adornno1@web.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com> <4798b03f$1@forums-1-dub> <4798b64d$1@forums-1-dub> <4798c019$1@forums-1-dub> <47990866$1@forums-1-dub>
In-Reply-To: <47990866$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47999552$1@forums-1-dub>
Date: 24 Jan 2008 23:52:50 -0800
X-Trace: forums-1-dub 1201247570 10.22.241.152 (24 Jan 2008 23:52:50 -0800)
X-Original-Trace: 24 Jan 2008 23:52:50 -0800, vip152.sybase.com
Lines: 25
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6695
Article PK: 4944

Jeff Albion (Sybase iAnywhere) schrieb:

> Andreas Dorn wrote:
>> I guess dbsupport will need the following files:
>> sadiags.xml
>> *.crash_log
>> *.mini_core
>> ?!?
>
> Probably the easiest thing to do would be to install SQL Anywhere 10 on
> a computer that is connected to the internet (Developer edition would
> do), then copy the C:\Documents and Settings\All Users\Application
> Data\SQL Anywhere 10\diagnostics directory over. You should be able to
> do the "dbsupport -sa" command at that point.

OK, I did that (yesterday). And I cleaned the diagnostics directory
before I copied the logs from the second machine.

One thing that was strange was that I have seen only 2 crashes on the
Win2003 server, but the diagnostics directory in fact contained more
dumps (three pretty regularly every 63 minutes)?!?

Now the database is running with date_order = 'DMY' and timestamp_format
= 'DD.MM.YYYY HH:NN:SS.SSSSSS', and I really hope that the problem was
related to the options. (The timestamps of the dumps all have their
minutes divisible by 3).


Andreas Dorn Posted on 2008-01-25 08:52:47.0Z
From: Andreas Dorn <adornno1@web.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Eventeditor and Timestamp-Format
References: <47947eca$1@forums-1-dub> <4794a1f5$1@forums-1-dub> <usvbp396gkk7tn3obdd0p3c6q6lqgu7psk@4ax.com> <4798b03f$1@forums-1-dub> <4798b64d$1@forums-1-dub> <4798c019$1@forums-1-dub> <47990866$1@forums-1-dub> <47999552$1@forums-1-dub>
In-Reply-To: <47999552$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4799a35f$1@forums-1-dub>
Date: 25 Jan 2008 00:52:47 -0800
X-Trace: forums-1-dub 1201251167 10.22.241.152 (25 Jan 2008 00:52:47 -0800)
X-Original-Trace: 25 Jan 2008 00:52:47 -0800, vip152.sybase.com
Lines: 7
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6696
Article PK: 4945

Andreas Dorn schrieb:

> Now the database is running with date_order = 'DMY' and timestamp_format
> = 'DD.MM.YYYY HH:NN:SS.SSSSSS', and I really hope that the problem was
> related to the options.

Bad luck, the database is still running, but in the diagnostics
directory I already found a dump from 2008-01-25 07:08.


"Frank Ploessel" <fpl... Posted on 2008-01-21 17:23:54.0Z
Subject: Re: Eventeditor and Timestamp-Format
From: "Frank Ploessel" <fpl...@d_e.i_m_s_h_e_a_l_t_h.c_o_m>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
References: <47947eca$1@forums-1-dub>
Content-Transfer-Encoding: 7bit
Message-ID: <op.t5ail0yij0bybf@bonw00164.internal.imsglobal.com>
User-Agent: Opera Mail/9.21 (Win32)
NNTP-Posting-Host: mail.taskarena-software-engineering.net
X-Original-NNTP-Posting-Host: mail.taskarena-software-engineering.net
Date: 21 Jan 2008 09:23:54 -0800
X-Trace: forums-1-dub 1200936234 217.76.101.130 (21 Jan 2008 09:23:54 -0800)
X-Original-Trace: 21 Jan 2008 09:23:54 -0800, mail.taskarena-software-engineering.net
Lines: 24
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6684
Article PK: 4933

Andreas,

I am not sure if this helps, but have you tried setting the date_order
option to 'DMY'?

Frank

On Mon, 21 Jan 2008 12:15:22 +0100, Andreas Dorn <adornno1@web.de> wrote:

> I'm testing a Database on 10.0.1.3619 and the Event Editor
> of Sybase Central doesn't work. (I get an error when trying
> to view the list of events).
> In the Database the timestamp_Format is set to
> DD.MM.YYYY HH:NN:SS.SSSSSS
> and I think the Cast to Timestamp in the Select that Sybase Central uses
> doesn't work.
>
> SELECT
> CAST( DB_EXTENDED_PROPERTY( 'NextScheduleTime', E.event_name ) AS
> TIMESTAMP)
> FROM SYS.SYSEVENT E
>
> Any suggestions?