Skip to content

Archive for

Netezza – ERROR [08S02] Unexpected protocol character/message

Issue:
You may face below error message when you are trying to create external table in Netezza appliance.

ERROR [08S02] Unexpected protocol character/message

CAUSE:
This error may occure when you try to create a external table.

CREATE EXTERNAL TABLE ‘c:\testtest.csv’ USING (DELIMITER ‘,’ REMOTESOURCE ‘odbc’ FILLRECORD ‘true’ DATEDELIM
‘/’ DATESTYLE ‘YMD’ QUOTEDVALUE ‘yes’ TIMEDELIM ‘:’ TIMESTYLE ’12HOUR’)
as ……

You will also see something like below in postgres logs
26499] ERROR: found delim ‘,’ in a data field, specify escapeChar ‘\’ option in the external table definition

RESOLUTION:
Make sure to specify escapeChar ‘\’ option in the create external table syntax and rerun your query.

CREATE EXTERNAL TABLE ‘c:\testtest.csv’ USING (DELIMITER ‘,’ REMOTESOURCE ‘odbc’ FILLRECORD ‘true’ DATEDELIM
‘/’ DATESTYLE ‘YMD’ QUOTEDVALUE ‘yes’ TIMEDELIM ‘:’ TIMESTYLE ’12HOUR’ escapeChar ‘\’)
as ……

SQL Server database restarting every couple of minutes

ISSUE:

You may face an issue when your database is just restarting every couple of minutes and you can see check DB is running at same frequency under same spid, when you look into the SQL Server error log. But users are able to connect to database without any issues.

Below is the error message that you will find in SQL Server error log stating that database is starting:

Date                         6/6/2013 10:10:43 AM

Log                            SQL Server (Current – 6/6/2013 10:10:00 AM)

Source                     spid69

Message

Starting up database ‘WW_Testing’.

Below is the error message that you will find in SQL Server error log stating that checkdb is running on this database:

Date                         6/6/2013 10:10:43 AM

Log                            SQL Server (Current – 6/6/2013 10:10:00 AM)

Source                     spid69

Message

CHECKDB for database ‘WW_Testing’ finished without errors on 2013-06-01 11:00:24.160 (local time). This is an informational message only; no user action is required.

CAUSE:

Regarding database restart, this will happen because you have set auto close database setting to enabled. So, your database is closed as soon as the last connection to this database is closed, but DB again restarts as soon as a new request to connect to database comes to SQL Server instance.

You can run below query to find if it is enabled or not. If output is 1 then its enabled If 0 then its disabled.

select is_auto_close_on from sys.databases

where name='DBNAME'

Now regarding checkDB running at same frequency, This is not a issue. SQL Server always performs checkDB whenever any database is started. This is to make sure a consistent copy of database is available before coming online. You will notice that this message comes every time after the Starting database message.

RESOLUTION:

Only thing you need to do is to disable database auto close parameter by running below query in master database or by changing that by going to SSMS –> Databases –> DBNAME –> Right Click –> Properties –> Options –> Auto Close and set it to FALSE.

USE [master]

GO

ALTER DATABASE [Test] SET AUTO_CLOSE ON WITH NO_WAIT

GO