Hello,

I'm trying out 24x7 and am close to purchasing a
couple of copies. Very good looking product!

I can connect to the database and DatabaseExport
works good, but DatabaseImport fails.

Here is the line from pbtrace.log that shows the
problem:

(a8e0130):
Error -1305 (rc -1) : SQLSTATE = S0002
[Microsoft][ODBC Microsoft Access Driver] The
Microsoft Jet database engine cannot find the input
table or query 'pbcattbl'. Make sure it exists and
that its name is spelled correctly.

Thanks for any help or pointers.

Paul Breneman

Locate PBODB70.INI in 24x7 installation directory and rename this file to PBODB70.BAK.

Please let me know if this doesn't help.

: Hello,

: I'm trying out 24x7 and am close to purchasing a
: couple of copies. Very good looking product!

: I can connect to the database and DatabaseExport
: works good, but DatabaseImport fails.

: Here is the line from pbtrace.log that shows the
: problem: (a8e0130): Error -1305 (rc -1) : SQLSTATE = S0002
: [Microsoft][ODBC Microsoft Access Driver] The
: Microsoft Jet database engine cannot find the input
: table or query 'pbcattbl'. Make sure it exists and
: that its name is spelled correctly.

: Thanks for any help or pointers.

: Paul Breneman

: Locate PBODB70.INI in 24x7 installation directory and rename this file to
: PBODB70.BAK.

: Please let me know if this doesn't help.

It still had the same error.

I'm scheduled to install this at a client's site
tomorrow so any quick help would be appreciated
(and guarantee the sale).

You quoted that from a trace file. Do you get this error in the job log? Does the import fail because of that error?
If not then what do you see in the job log?

PS. Can you post the complete trace file here?

: It still had the same error.

: I'm scheduled to install this at a client's site
: tomorrow so any quick help would be appreciated
: (and guarantee the sale).

: You quoted that from a trace file. Do you get this error in the job log? Does
: the import fail because of that error?
: If not then what do you see in the job log?

: PS. Can you post the complete trace file here?

I don't get any error in the job log file. The
DatabaseImport just returns zero rows imported.

/*---------------------------------------------------*/
/* 6/29/2004 14:50 */
/*---------------------------------------------------*/
(6740b48): LOGIN: (0 MilliSeconds)
(6740b48): CONNECT TO TRACE ODBC:
(6740b48): DATABASE=SigFarm1
(6740b48): LOGID=Admin
(6740b48): LOCK=Read Committed
(6740b48): DBPARM=ConnectString='DSN=SigFarm1;UID=Admin;PWD=',DelimitIdentifier='No'
(6740b48): SERVER=ACCESS (0 MilliSeconds)
(6740b48): PREPARE: (0 MilliSeconds)
(6740b48): PREPARE:
(6740b48): SELECT * FROM DataCol (0 MilliSeconds)
(6740b48): DESCRIBE: (0 MilliSeconds)
(6740b48): name=id,len=44,type=LONG,pbt=5,dbt=4,ct=0,prec=10,scale=0
(6740b48): name=scaleid,len=51,type=VCHAR,pbt=2,dbt=12,ct=0,prec=50,scale=0
(6740b48): name=group,len=2,type=VCHAR,pbt=2,dbt=12,ct=0,prec=1,scale=0
(6740b48): name=reading,len=51,type=VCHAR,pbt=2,dbt=12,ct=0,prec=50,scale=0
(6740b48): name=time,len=30,type=DATETIME,pbt=9,dbt=11,ct=0,prec=19,scale=0
(6740b48): name=date,len=30,type=DATETIME,pbt=9,dbt=11,ct=0,prec=19,scale=0
(6740b48): name=tagid,len=51,type=VCHAR,pbt=2,dbt=12,ct=0,prec=50,scale=0
(6740b48): GET EXTENDED ATTRIBUTES: TABLE=DataCol OWNER=admin (0 MilliSeconds)
(6740b48):
Error -1305 (rc -1) : SQLSTATE = S0002
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot find the input table or query 'pbcattbl'. Make sure it exists and that its name is spelled correctly.
(6740b48): UNIQUE KEY CHECK: TABLE=DataCol OWNER=admin USER=admin (0 MilliSeconds)
(6740b48): YES, unique key found
(6740b48): COMMIT: (0 MilliSeconds)
(6740b48): DISCONNECT: (47 MilliSeconds)
(6740b48): SHUTDOWN DATABASE INTERFACE: (0 MilliSeconds)

Simply ignore that message. It can be seen in the trace file but it is not the cause of the problem. This error message indicates that some catalog table cannot be found. That's it.

The likely reason why the data cannot be imported is that the import file has invalid format, for example number of columns in the file do not match number of columns in the table, or the data types do not match or something else like that.

: I don't get any error in the job log file. The
: DatabaseImport just returns zero rows imported.

: /*---------------------------------------------------*/
: /* 6/29/2004 14:50 */
: /*---------------------------------------------------*/
: (6740b48): LOGIN: (0 MilliSeconds)
: (6740b48): CONNECT TO TRACE ODBC: (6740b48): DATABASE=SigFarm1
: (6740b48): LOGID=Admin
: (6740b48): LOCK=Read Committed
: (6740b48):
: DBPARM=ConnectString='DSN=SigFarm1;UID=Admin;PWD=',DelimitIdentifier='No'
: (6740b48): SERVER=ACCESS (0 MilliSeconds)
: (6740b48): PREPARE: (0 MilliSeconds)
: (6740b48): PREPARE: (6740b48): SELECT * FROM DataCol (0 MilliSeconds)
: (6740b48): DESCRIBE: (0 MilliSeconds)
: (6740b48): name=id,len=44,type=LONG,pbt=5,dbt=4,ct=0,prec=10,scale=0
: (6740b48): name=scaleid,len=51,type=VCHAR,pbt=2,dbt=12,ct=0,prec=50,scale=0
: (6740b48): name=group,len=2,type=VCHAR,pbt=2,dbt=12,ct=0,prec=1,scale=0
: (6740b48): name=reading,len=51,type=VCHAR,pbt=2,dbt=12,ct=0,prec=50,scale=0
: (6740b48): name=time,len=30,type=DATETIME,pbt=9,dbt=11,ct=0,prec=19,scale=0
: (6740b48): name=date,len=30,type=DATETIME,pbt=9,dbt=11,ct=0,prec=19,scale=0
: (6740b48): name=tagid,len=51,type=VCHAR,pbt=2,dbt=12,ct=0,prec=50,scale=0
: (6740b48): GET EXTENDED ATTRIBUTES: TABLE=DataCol OWNER=admin (0
: MilliSeconds)
: (6740b48): Error -1305 (rc -1) : SQLSTATE = S0002
: [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine
: cannot find the input table or query 'pbcattbl'. Make sure it exists and
: that its name is spelled correctly.
: (6740b48): UNIQUE KEY CHECK: TABLE=DataCol OWNER=admin USER=admin (0
: MilliSeconds)
: (6740b48): YES, unique key found
: (6740b48): COMMIT: (0 MilliSeconds)
: (6740b48): DISCONNECT: (47 MilliSeconds)
: (6740b48): SHUTDOWN DATABASE INTERFACE: (0 MilliSeconds)

: Simply ignore that message. It can be seen in the trace file but it is not
: the cause of the problem. This error message indicates that some catalog
: table cannot be found. That's it.

: The likely reason why the data cannot be imported is that the import file has
: invalid format, for example number of columns in the file do not match
: number of columns in the table, or the data types do not match or
: something else like that.

Thanks for looking into this. Since I'm not getting
any errors in the job file nor the log file, is there
any other way to troubleshoot this better than just
trying different CSV file formats? I've even tried
the same exact file generated by DatabaseExport but
that didn't work either (after deleting all of the
records).

Would the ODBC trace help?

Thanks for your help.

: Thanks for looking into this. Since I'm not getting
: any errors in the job file nor the log file, is there
: any other way to troubleshoot this better than just
: trying different CSV file formats? I've even tried
: the same exact file generated by DatabaseExport but
: that didn't work either (after deleting all of the
: records).

: Would the ODBC trace help?

: Thanks for your help.

After reading your previous post I figured out that you are trying to import a CSV file. DatabaseImport only supports tab-separated files at this time.

I guess you are trying to import a file created using DatabaseSave statement with CSV option. Instead try exporting files using DatabaseExport statement and then importing them back using DatabaseImport.

: After reading your previous post I figured out that you are trying to import
: a CSV file. DatabaseImport only supports tab-separated files at this time.

: I guess you are trying to import a file created using DatabaseSave statement
: with CSV option. Instead try exporting files using DatabaseExport
: statement and then importing them back using DatabaseImport.

I did get DatabaseExport to work. After clearing the
records from the database, DatabaseImport using the
same file (tab-delimited) did not work.

The client will probably switch from Access to their
in-house SQL Server so I have confidence that will
work better.