Timestamp format for SQL Server data

Hi all,
I put this question on the PL/SQL forum but got no answer yet. Could anyone help me with the timestamp format for a timestamp data from SQL Server? I have this in the xml from SQL server,
2006-06-20T00:00:00-05:00
and I need to make it a date or timestamp data type in Oralce. I have looked at the docs and could not find the correct format for this. Please note there is a T in the middle and I don't know why it is there and what it is for.
Thanks.
Ben

Actually the date is in the only form that is valid in the XML Schema spec and the RFC that the datetime formats are allowed to be in per the XML schema spec...
The way to decode is to a timestamp with timezone
SQL> select to_timestamp_Tz('2006-06-20T00:00:00-05:00','YYYY-MM-DD"T":HH24:MI:SSTZH:TZM') from dual;
TO_TIMESTAMP_TZ('2006-06-20T00:00:00-05:00','YYYY-MM-DD"T":HH24:MI:SSTZH:TZ
20-JUN-06 12.00.00.000000000 AM -05:00
SQL>

Similar Messages

How to convert MS SQL Server data to XML data using Java

Hi all!
How do I generate XML document for SQL Server data using java / jsp.
Thanks in advance

http://www.fdsapi.com

Sql server data tools - Business intelligence

Hi,
Please assist, i need to know if i require a licence for SQL Server Data tools - Business Intelligence.
L.M

Hi Lebohang,
As per my understanding, you don't have to make all users have CAL. You can install SQL Server Data Tools - Business Intelligence for Visual Studio 2013 as a standalone business intelligence authoring environment or side-by-side with an existing SQL Server
Data Tools installed with SQL Server.
Reference:
Install SQL Server Data Tools - Business Intelligence for Visual Studio 2013
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu

Do we need to format data and log files with 64k cluster size for sql server 2012?

Do we need to format data and log files with 64k cluster size for sql server 2012?
Does this best practice still applies to sql server 2012 & 2014?

Yes. The extent size of SQL Server data files, and the max log block size have not changed with the new versions, so the guidance should remain the same.
Microsoft SQL Server Storage Engine PM

Date formats for SQL statements used by recordset object

Hi,
Date formatting appears to be quite problematic for Business One. I did a forum search for date issues and I don't think I saw any of them with an "answered" status. I have an issue with formatting a date for the creation of an SQL statement that the DI sends to SQL Server 2005. I need to format a date so that the localization parameters don't matter for either the client machine or SQL Server's machine. We don't have a problem as long as our machines are localized as USA.
I have PL 22 and I have a form - ours - where I use the Today() function to fill a date field. So this is a date that is not entered by the user. The result of this function is consistent with the localization parameters on my machine. We have two other date fields on the form where the user must type in the date.
As a test, I changed my machine to the UK parameters. I then set up the language parameters of Business One for English(United Kingdom). I changed the date format specifications in Business One so that its format is dd/mm/yy. I then brought up the form and the field that is formatted by the above function arrived in the form's field as dd/mm/yy. I then typed in the two other dates in the same format and added the record to the database. The form's table is user-defined.
I dismissed the form then brought it back up loaded with the new record. The date that was entered by the function appeared in USA format (mm/dd/yy). The dates that were typed in appeared in the Business One format (dd/mm/yy). This of course is not consistent.
When I looked at what got into the database, the formats were the opposite. Weird! To make matters really confusing, I run an SQL statement within SQL Server Mgt Studio, and use the WHERE clause to filter on the date that was based on the function. It didnt matter what format I used for the WHERE clause, the record came up. Does anyone have any idea about how I can ensure that I always use the correct date format for SQL statements passed by Business One to SQL Server regardless of where in the world the application is being run?
Thanks,
Mike

Ian,
Here's what I'm concerned about: Im using the date in a WHERE clause.
Assume the date is Aug 3, 2007.
"SELECT * FROM Table WHERE StartDate > 8/3/2007"
OR
"SELECT * FROM Table WHERE StartDate > 3/8/2007"
If the client machine is set up as USA, the today function will provide the date as formatted in the first query. If the database server is setup as lets say the UK, I believe that SQL Server query parser will interpret the date as Mar 8, 2007.
If the client machine is set up as UK, the today function will provide the date as formatted in the second query. If the database server is setup as lets say USA, I believe that SQL Server query parser will also interpret the date as Mar 8, 2007.
In both cases it would be wrong.
I know I could use the DATEPART function to get the three parts and this will make the code indifferent to the localization specs of the client machine. I need to then be able to concatenate those date parts for the WHERE clause so that the localization specifications of the database server dont matter.
Thanks,
Mike

Wrong Date format in SQL Server

Hello All,
I have an asp page with a hidden field that holds
<%=Date()%>. Because the
Session.LCID is set to UK this value today would be
12/03/2007 (UK format).
When this hidden field is fed into an INSERT Stored Procedure
in SQL Server
in my testing environment, the date format that is inserted
into the
database is the same as the value in the hidden field eg
12/03/2007, which
is what I want.
Now though, the site has moved to a production web server
with SQL Server.
When I perform this exact insert using the same webpages and
(from what I
can see) the same SQL Server configuration, the date inserts
as 03/12/2007,
US format. This is causing me big problems as the website is
complete but
the wrong dateformat is producing some undesirable results.
The whole site
is set up to expect the original format and I cannot see why
this is
happening.
Does anyone have any suggestions and more importantly how I
can change this
please.

There is a real issue here and it has nothing to do with the
way that data
is formatted on the way out.
msSQL does seem to always assume that numbers entered in the
format of
00/00/00 follow the pattern of MM/DD/YY which is American
format. So the 8th
of March entered in UK format of 08/03/2007 ends up being
intrepreted by SQL
as 3rd August. However it only does this up to the 12th of
each month. If
you enter the 13th of March as 13/03/2007 SQL stores it
correctly.
The workaround does seem to enter the number in the
YYYY-MM-DD format as
Julian has suggested.
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver
Valleybiz Internet Design
www.valleybiz.net
"Lionstone" <[email protected]> wrote in
message
news:[email protected]...
> SQL Server does not store dates in any format. They are
simply numbers,
> with the integer part representing date and the
fractional part
> representing time. If you do not format dates on the way
out, then you're
> leaving things up to your web server (and depending on
when the dates
> become strings, it might be the ADO provider and not ASP
that does the
> formatting).
>
> The only way to reliably format dates the way you want
is to do so
> explicitly. You may use CONVERT for SQL Server and
specify a format
> option (
http://msdn2.microsoft.com/en-us/library/aa226054(SQL.80).aspx),
> or you may use the FormatDateTime function in your ASP
page.
> FormatDateTime is locale-aware when it formats dates.
All you have to do
> is make sure the locale is set properly (which you seem
to have done).
>
>
>
> "TTal" <[email protected]> wrote in message
> news:[email protected]...
>> Hello All,
>>
>> I have an asp page with a hidden field that holds
<%=Date()%>. Because
>> the Session.LCID is set to UK this value today would
be 12/03/2007 (UK
>> format).
>>
>> When this hidden field is fed into an INSERT Stored
Procedure in SQL
>> Server in my testing environment, the date format
that is inserted into
>> the database is the same as the value in the hidden
field eg 12/03/2007,
>> which is what I want.
>>
>> Now though, the site has moved to a production web
server with SQL
>> Server. When I perform this exact insert using the
same webpages and
>> (from what I can see) the same SQL Server
configuration, the date inserts
>> as 03/12/2007, US format. This is causing me big
problems as the website
>> is complete but the wrong dateformat is producing
some undesirable
>> results. The whole site is set up to expect the
original format and I
>> cannot see why this is happening.
>>
>> Does anyone have any suggestions and more
importantly how I can change
>> this please.
>>
>
>

Will Cumulative Update 12 for SQL Server 2008R2 SP2 fix: Warning: Unable to Verify TimeStamp for Path\ProgramName?

Hello,
I had a server crash recently and our outsource hosting tech support suggested applying Cumulative Upade 12 for SQL server 2008R2 SP2 to fix the issue. The exception from our dump file "Warning: Unable to Verify TimeStamp for Path\ProgramName"
is not in the list of hotfixes for this CU. Do you know if this will fix this issue? The CU warns not to apply the CU if your issue id not addressed by the CU. Here is a portion of the dump file with the relevant error:
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(7e8.2ab4): Unknown exception - code 000042ac (first/second chance not available)
ntdll!NtWaitForSingleObject+0xa:
00000000`777412fa c3 ret
0:240> .sympath srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols;
Symbol search path is: srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
0:240> .reload /f
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlservr.exe
..........Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlos.dll
...............Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for opends60.dll
.......Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BatchParser.dll
....Unable to load image C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for instapi10.dll
*** ERROR: Module load completed but symbols could not be loaded for instapi10.dll
..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlevn70.rll
*** ERROR: Module load completed but symbols could not be loaded for sqlevn70.rll
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.................Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ftimport.dll
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\msfte.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for msfte.dll
*** ERROR: Module load completed but symbols could not be loaded for msfte.dll
...........Unable to load image C:\Windows\System32\sqlncli10.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlncli10.dll
...Unable to load image C:\Windows\System32\1033\SQLNCLIR10.RLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SQLNCLIR10.RLL
*** ERROR: Module load completed but symbols could not be loaded for SQLNCLIR10.RLL
..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpsqlbot.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xpsqlbot.dll
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\XPStar.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for XPStar.DLL
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlscm.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlscm.dll
...*** ERROR: Module load completed but symbols could not be loaded for odbcint.dll
...Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\XPStar.RLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for XPStar.RLL
Thank you,
Steve -

The error message appears to be related to a debug session and not come from the actual crash.
So all I know is that you hade a server crash. I don't even know exactly what that means. Did Windows bite the dust? Or was it only SQL Server?
Assuming the latter, I would expect the SQL Server errorlog to have some information (and that would be ERRORLOG.1 or earlier, since the server have been restarted), but if SQL Server died the output may be incomplete.
There may be also dump files, but as I rarely look into these, I am not sure how to interpret them. But I am quite confident that "Unable to verify TimeStamp..." is not the reason SQL Server went down.
I would suggest the following course:
* If the server is not critical, do nothing. As long as it has onlyl happened once, it has only happened once.
* If the server is critical, open a case with Microsoft if you are not able to figure out the reason yourself. The key here is "Unknown exception - code 000042ac".
* If it happens again, you should absolutely open a case. An important thing here is whether the stack dump is identical or something different. If the stack dumps are identical, you may have hit a bug in SQL Server or the OS, and applying CUs or OS
fixes could help if it is a known issue. If the stack dump is something else, you have ghosts in the machine - that is, bad hardware.
Erland Sommarskog, SQL Server MVP, [email protected]

SQL Server Data Tools – Business Intelligence for Visual Studio 2013 (SSDT BI) and SSIS on SQL Server 2012

This great blog entry titled
SQL Server Data Tools - Business Intelligence for Visual Studio 2013 (SSDT BI), link below, highlights the lack of support for SSIS projects using SQL Server 2012, VS 2013 and SSDT BI for VS 2013. I see there is a new version
on SSDT BI for VS 2013 (12.0.2430.0, File Name: SSDTBI_x86_ENU.exe, Date Published: 10/27/2014) link below.
Does this version support SSIS projects using SQL Server 2012 using VS 2013 and SSDT BI for VS 2013?
http://blogs.msdn.com/b/analysisservices/archive/2014/04/02/sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi.aspx
http://www.microsoft.com/en-us/download/details.aspx?id=42313

Hi cjrinpdx,
According to the picture, it seems that we can use SSIS 2012 support is not included in SSDT-BI for VS 2013. And based on the previous versions, SSIS always different from SSRS, SSAS.
SSDT-BI for Visual Studio 2012 supports versions of SQL Server as follows:
SSAS project can target SQL 2012 or lower
SSRS project can target SQL 2012 or lower
SSIS project can target only SQL 2012
The following blog is for your reference:
http://blogs.technet.com/b/dataplatforminsider/archive/2013/11/13/microsoft-sql-server-data-tools-update.aspx
Since I have no environment to test this at this moment,
I recommend you that submit the feedback at
https://connect.microsoft.com/SQLServer/.
Thank you for your understanding.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

The February 2015 release of SQL Server Data Tools is now available for download

We'd like to announce the availability of the latest February 2015 release of SQL Server Data Tools.
This update is now available for Visual Studio 2012 and 2013. For Visual Studio 2012, use the SQL > Check for Updates tool inside Visual Studio. For Visual Studio 2013, check the Visual Studio update channel (Tools > Extensions and Updates > Updates)
for this update. Alternatively, administrative installs are available via the link below.
Get it here:
http://msdn.microsoft.com/en-us/data/hh297027
What’s New?
Support for the latest Azure SQL Database V12 features
Improved Cross-Platform Schema Comparison
New advanced publish options
Fixes for customer reported issues
For more details, see the SQL Server Data Tools team blog:
http://blogs.msdn.com/b/ssdt/archive/2015/03/03/sql-server-data-tools-and-data-tier-application-framework-update-for-february-2015.aspx

While we are investigating this issue, you can revert to the November release with the links below. You will need to uninstall your current SSDT.MSI and then run the installer from these ISOs.
Visual Studio 2012 versions:
SSDT_11.1.41025.0_BR.iso
SSDT_11.1.41025.0_CN.iso
SSDT_11.1.41025.0_DE.iso
SSDT_11.1.41025.0_EN.iso
SSDT_11.1.41025.0_ES.iso
SSDT_11.1.41025.0_FR.iso
SSDT_11.1.41025.0_IT.iso
SSDT_11.1.41025.0_JA.iso
SSDT_11.1.41025.0_KO.iso
SSDT_11.1.41025.0_RU.iso
SSDT_11.1.41025.0_TW.iso
Visual Studio 2013 versions:
SSDT_12.0.41025.0_BR.iso
SSDT_12.0.41025.0_CN.iso
SSDT_12.0.41025.0_DE.iso
SSDT_12.0.41025.0_EN.iso
SSDT_12.0.41025.0_ES.iso
SSDT_12.0.41025.0_FR.iso
SSDT_12.0.41025.0_IT.iso
SSDT_12.0.41025.0_JA.iso
SSDT_12.0.41025.0_KO.iso
SSDT_12.0.41025.0_RU.iso
SSDT_12.0.41025.0_TW.iso

SQL Server Data Tools for SQL 2014 setup

Hello,
I have been using SQL server 2008 with Visual Studio 2008 to perform the ETL processes.
I have recently got SQL 2014 and realized that Business Intelligence Development Studio does not come with it so I have to download SQL Server Data Tools for Visual Basics 2012 or 2013 from:
https://msdn.microsoft.com/en-us/data/hh297027
Can someone advise what exactly I have to do if I want to start using SQL 2014 with SSDT? I still have VB 2008 installed and all my packages were created with that version.
Do I need to download VB 2012 or 2013 plus SSDT and then SSDT? Do I also uninstall VB2008?
Thanks in advnce

Hello,
If you want to keep developing packages for SQL Server 2008 then you need to use BIDS 2008, you cannot use SSDT.
If you want to upgrade BIDS projects to SSDT, then you can use Integration Services Project Conversion Wizard from Visual
Studio or SSIS Package Upgrade Wizard from SQL Server Management Studio (SSMS).
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server Data Tools - for visual studio 2013

Hi
I have recently installed Visual Studio 2013 and need to install the SQL Server Data Tools too, as I have done in Visual Studio 2012, but I can not find the software, where can I get it?
thanks
MsdnMezzo

Hi,
I hope you serve.Regards
SQL Server Data Tools for Visual Studio 2013 - 12.0.40403.0
Portuguese (Brazil)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/BR/SSDTSetup.exe
Chinese (PRC)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/CN/SSDTSetup.exe
German
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/DE/SSDTSetup.exe
English (United States)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/EN/SSDTSetup.exe
Spanish
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/ES/SSDTSetup.exe
French
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/FR/SSDTSetup.exe
Italian
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/IT/SSDTSetup.exe
Japanese
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/JA/SSDTSetup.exe
Korean
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/KO/SSDTSetup.exe
Russian
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/RU/SSDTSetup.exe
Chinese (Taiwan)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/TW/SSDTSetup.exe

SQL Server date format

Hi all,
I realize that this may be a little bit out of the scope of this forum, but I thought I'd ask anyway.
I'm trying to figure out how to select a date in the format mm/dd/yyyy from a SQL Server date/time field. I've browsed the internet on this but haven't found any quick/easy way to do this. Can anyone please help me out here?
Thanks!
-Stephen Spalding
Web Developer
Graybar

Hi Stephen,
You can use the convert function in sql to change the format of the date time field.
select convert(varchar(13),getdate(),101) gives u the current date in mm/dd/yyyy format.
If you want that in java you can use the SimpleDateFormat class to change the format.
import java.text.Format;
import java.text.SimpleDateFormat;
import java.util.Date;
Date currentDate = null;
Format formatter = null;
String date = "";
currentDate = new Date();
formatter = new SimpleDateFormat("MM/dd/yyyy");
date = formatter.format(currentDate);
This should give in the mm/dd/yyyy format.
But both the results will be in String Format and not datetime.
Hope this will be useful to you.
Regards
Prakash

Error installing SQL Server Data Tools - Business Intelligence for Visual Studio 2013

Hi
I am trying to install SQL Server Data Tools - Business Intelligence for Visual Studio 2013 and am getting the following error
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
I am running
Windows 8.1 x64
SQL Server 2014 Developer Edition x64
Visual Studio 2013 Professional
Any help would be appreciated.
Thanks
Biztalk Developer

Could you please check if Windows Installer service is running and is in automatic startup mode.
The other thing is, if you’re running an x64-based SQL instance (64-bit), make sure to select “New Instance” on the Installation Type page, and NOT “Add features to an existing instance”.
http://stackoverflow.com/questions/24989187/64-bit-microsoft-sql-server-data-tools

SQL Developer 2.1.0.63 - Export Data menu missing for SQL Server databases

Hi
The Export Data menu only appears for Oracle databases in this version, it does not appear for SQL server databases.
To demonstrate:
Press F9 to run query
Right click on Query Result data
For Oracle an Export Data sub menu appears
For SQL server no Export Data sub menu appears
This worked in previous versions.
Is this functionality going to reappear?
Thanks
Dave

Hi,
Looks like this is exactly the same problem for third party connections as I have the exact same issue for mySQL.
I had to apply 1.5.5 version to fix it.
Hope we're going to have this solved !
Thanks,
JP

OGG for SQL Server - Extract stops capturing - Bug?

Hi, all,
I've found a problem with OGG for SQL Server where the Extract stops capturing data after the transaction log is backed up. I've looked for ways to reconfigure OGG to avoid the problem but couldn't find any reference to options to workaround this problem. It seems to be a bug to me.
My Extract configuration is as follows:
EXTRACT ext1
SOURCEDB mssql1
TRANLOGOPTIONS NOMANAGESECONDARYTRUNCATIONPOINT
EOFDELAY 60
EXTTRAIL dirdat/e1
TABLE dbo.TestTable;
I'm using the EOFDELAY parameter for testing purposes only, since it's easy to reproduce the scenario that causes the issue when the extract polling is configured with longer intervals.
When the Transaction Log backup runs, SQL Server marks all the virtual logs that are older than the primary and secondary truncation points as inactive (status = 0). These virtual logs can then be reused if required. They still contain change records, though, and OGG can read from then if required, before they are overwritten. This situation will never occur if we are not using SQL Replication and have the Extract configured with the parameter MANAGESECONDARYTRUNCATIONPOINT.
However, I'm trying to simulate a scenario where OGG is used along SQL Replication and the extract is configured with the NOMANAGESECONDARYTRUNCATIONPOINT option. The situation that I've reproduced and caused the Extract to stop capturing is the follow sequence of events:
1. Extract reads transaction log and capture change up to LSN X
2. More change are made to the database and the LSN is incremented
3. Log Reader reads Transaction Log, captures changes up to LSN X+Y and advances the secondary truncation point to that LSN
4. A transaction log occurs, backs up all the active virtual logs, advances the primary truncation point to a LSN greater than LSN X+Y, and marks all the virtual logs with LSNs <= X+Y as inactive (status = 0)
5. Changes continue to happen in the database consuming all the available inactive virtual logs and overwriting them.
6. The extract wakes up again to capture more changes.
At this point, the changes between LSNs X and X+Y are not in the Transaction Log anymore, but are available in the backups. From what I understood in the documentation the Extract should detect that situation and retrieve the changes from the Transaction Log backups. This, however, is not happening and the Extract becomes stuck. It still pools the transaction log at the configured interval query the log state with DBCC LOGINFO, but doesn't move forward anymore.
If I stop and restart the Extract I can see from the trace that it does the right thing upon startup. It realises that it requires information that's missing from the logs, query MSDB for the available backups, and mine the backups to get the required LSNs.
I would've thought the Extract should do the same during normal operation, without the need for a restart.
Is this a bug or the normal operation of the Extract? Is there a way to configure it to avoid this situation without using NOMANAGESECONDARYTRUNCATIONPOINT?
The following is the state of the Extract once it gets stuck. The last replicated change occurred at 2012-07-09 12:46:50.370000. All the changes after that, and there are many, were not captured until I restarted the Extract.
GGSCI> info extract ext1, showch
EXTRACT EXT1 Last Started 2012-07-09 12:32 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:54 ago)
VAM Read Checkpoint 2012-07-09 12:46:50.370000
LSN: 0x0000073d:00000aff:0001, Tran: 0000:000bd922
Current Checkpoint Detail:
Read Checkpoint #1
VAM External Interface
Startup Checkpoint (starting position in the data source):
Timestamp: 2012-07-09 11:41:06.036666
LSN: 0x00000460:00000198:0004, Tran: 0000:00089b02
Recovery Checkpoint (position of oldest unprocessed transaction in the data so
urce):
Timestamp: 2012-07-09 12:46:50.370000
LSN: 0x0000073d:00000afd:0004, Tran: 0000:000bd921
Current Checkpoint (position of last record read in the data source):
Timestamp: 2012-07-09 12:46:50.370000
LSN: 0x0000073d:00000aff:0001, Tran: 0000:000bd922
Write Checkpoint #1
GGS Log Trail
Current Checkpoint (current write position):
Sequence #: 14
RBA: 28531192
Timestamp: 2012-07-09 12:50:02.409000
Extract Trail: dirdat/e1
CSN state information:
CRC: D2-B6-9F-B0
CSN: Not available
Header:
Version = 2
Record Source = A
Type = 8
# Input Checkpoints = 1
# Output Checkpoints = 1
File Information:
Block Size = 2048
Max Blocks = 100
Record Length = 20480
Current Offset = 0
Configuration:
Data Source = 5
Transaction Integrity = 1
Task Type = 0
Status:
Start Time = 2012-07-09 12:32:29
Last Update Time = 2012-07-09 12:50:02
Stop Status = A
Last Result = 400
Thanks!
Andre

It might be something simple (or maybe not); but the best/fastest way to troubleshoot this would be to have Oracle (GoldenGate) support review your configuration. There are a number of critical steps required to allow GG to interoperate with MS's capture API. (I doubt this is it, but is your TranLogOptions on one line? It looks like you have it on two , the way it's formatted here.)
Anyway, GG support has seen it all, and can probably wrap this up quickly. (And if it was something simple -- or even a bug -- do post back here & maybe someone else can benefit from the solution.)
Perhaps someone else will be able to provide a better answer, but for the most part troubleshooting this (ie, sql server) via forum tends to be a bit like doing brain surgery blindfolded.

Timestamp format for SQL Server data

Similar Messages

Maybe you are looking for