Mediabin error messages

Rubix

Hi,

We're getting a bunch of error messages in our DB.logfile (we've enabled database logging).

Here is a snippet:
-------------------------------------------------------------------
State1C00,Native:0,Origin:[Oracle][ODBC]
State:IM006,Native:0,Origin:[Microsoft][ODBC Driver Manager]

04/21/09 22:28:21 [1F8] OdbcConnection:pen m_hDbc:AB3AD0
04/21/09 22:28:21 [1F8] executeQuery() - select c.id from ContainerTree ct, containers c where ct.parentid = ? and c.id = ct.id and c.isSearchable = 0 order by depth desc, {FCDB6651-6CD3-4C3E-B83E-3A913D5797A4}
04/21/09 22:28:21 [1F8] executeQuery() - 0 ms
04/21/09 22:28:21 [1F8] Rows returned: 0 - 0 ms
04/21/09 22:28:21 SQL_SUCCESS_WITH_INFO: Driver not capable.
Driver's SQLSetConnectAttr failed

State1C00,Native:0,Origin:[Oracle][ODBC]
State:IM006,Native:0,Origin:[Microsoft][ODBC Driver Manager]

04/21/09 22:28:21 [1F8] OdbcConnection:pen m_hDbc:AB3AD0
04/21/09 22:28:21 [1F8] executeQuery() - SELECT r.id, r.parentid, r.name o1 FROM assetrefs r WHERE r.isContainer = 1 AND r.parentid IN ( SELECT id FROM ContainerTree WHERE parentid = ? AND depth = 1 ) ORDER BY o1, {FCDB6651-6CD3-4C3E-B83E-3A913D5797A4}
04/21/09 22:28:21 [1F8] executeQuery() - 15 ms
04/21/09 22:28:21 [1F8] Rows returned: 0 - 15 ms
04/21/09 22:28:21 SQL_SUCCESS_WITH_INFO: Driver not capable.
Driver's SQLSetConnectAttr failed

State1C00,Native:0,Origin:[Oracle][ODBC]
State:IM006,Native:0,Origin:[Microsoft][ODBC Driver Manager]

04/21/09 22:28:21 [162C] OdbcConnection:pen m_hDbc:AB3AD0
04/21/09 22:28:21 Log message too long: [162C] executeQuery() - SELECT r.id, r.parentid, r.name, r.isOriginal, r.jobid, a.id, a.sid, a.username, v.id, datediff(second, '1/1/1970', v.modified), v.revision, v.assettype, v.layercount, d.factoryid, md.datatype, md.filesize, md.datavalue1, md.datavalue2, md.datavalue3, md.datavalue4, md.datafile FROM assetrefs r INNER JOIN assets a ON r.baseid = a.id INNER JOIN revisions v ON a.id = v.baseid AND a.maxrevision = v.revision LEFT OUTER JOIN metadata d ON v.id = d.revisionid LEFT OUTER JOIN metadata md ON v.id = md.revisionid AND d.factoryid = md.factoryid AND md.factoryid IN ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) WHERE r.id IN ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) ORDER BY r.id, {43154AE9-0199-4F99-B11C-8B1B95CF55F5}, {545D58B7-8B17-4019-BBB6-4D44C653711D}, {50835A72-A77C-423C-B8B6-15B3C3D408FC}, {03F8DE50-7E66-4425-82AE-F42255AC3A2B}, {00E81843-6ABF-4997-86D3-757D7272D129}, {78108DCD-02C4-47DD-AC43-53ED976D548C}, {7D58EB02-9822-4D4E-A1EC-9E6E7BA6F1F1}, {5BE195E0-0726-11D3-9DDE-0060081F836F}, {4510D310-E6BB-11D2-BF95-00A024DB7160}, {E68D4990-FC14-11D2-B883-0000C07E5BB8}, {5C15B93B-EFB8-4702-81C7-4CFB3B36C862}, {0CDBE02E-1FBB-44F0-8779-C7228D563393}, {BF23DD2A-218E-4B78-8CE1-24E4F08CFC5A}, {4D52B90B-B0AF-4593-8F4E-27CEC01068A6}, {6868E63D-20E1-4A78-ADDF-092C494801FC}, {4EE43EDC-B2EA-45A4-A603-5BDCDD1A977C}, {99D9BA63-0E72-4C36-A037-144191FFA075}, {4ABB13DC-3156-4565-A2B7-586D56BB9A06}, {0915E657-0140-4ED8-9F28-F7FA83E7630C}, {A1F3510E-9A66-4238-B5BD-5938024433F4}, {F6112CD0-0B72-4954-AE1A-689E02B647F7}, {2CDCB008-B048-4227-99B5-8EA8D5AA9215}, {8F4C6C9B-3FE7-408A-AB37-C8FC2544DC0A}, {05F1FF51-C20C-417C-AB83-D022F4728067}, {7E08844E-B0E5-4824-A90F-C659242C8A72}, {42D17E81-2C8E-4DCB-9655-A4861EE94939}, {533B0DB9-B012-4451-A618-221BFBBFD17B}, {CAC5A8AC-AA98-4D89-80C5-3E241241D307},
04/21/09 22:28:21 [162C] executeQuery() - 32 ms
04/21/09 22:28:22 [162C] Multiple Rows returned: 4528 - 1532 ms
-------------------------------------------------------------------

From a user perspective, it seems MediaBin is functioning properly, however these driver errors concern us. Is it safe for us to ignore these errors, or is there some steps we can take to resolve them?

System configuration:
Mediabin Windows Server 2003 R2 SP2 running MediaBin 4.6.1.7, connecting to another Windows server in the same network segment running Oracle 10.2

lyman

I can confirm that these are harmless. I know we really should make an effort to suppress them but we try to minimize "database aware" code paths. We apologize for any confusion.

Cheers,

Lyman Hurd