Can anyone answer the actual question? Here it is... Is the following "E" level message something separate, or is it associated with the "W" warning? All the rest of the stuff is background... this is NOT a question about the Oracle long-running transaction problem, it is a question about an "E" level message appearing that may or may not be related to the warning. The reason it is important is this: folks tend to worry about "E" level messages, and a shop that does not care about the Oracle long-running transaction problem needs to know if this "E" level message can be ignored along with the "W" warning. Thanks! E. 2010-11-03 17:21:47. [-10002] Consolidated database server or ODBC error: ODBC: [Sybase][iAnywhere Solutions - Oracle][Oracle]ORA-00942: table or view does not exist (ODBC State = 42S02, Native error code = 942) W. 2010-11-03 17:21:58. [10075] Unable to access ORACLE table 'gv$transaction'. Access is needed to ensure no data is missed if using timestamp-based downloads Here's the context... I. 2010-11-03 17:21:44. SQL Anywhere MobiLink Server Version 12.0.0.2483 I. 2010-11-03 17:21:44. I. 2010-11-03 17:21:44. Copyright Š 2001-2010, iAnywhere Solutions, Inc. I. 2010-11-03 17:21:44. Portions copyright Š 1988-2010, Sybase, Inc. All rights reserved. I. 2010-11-03 17:21:44. Use of this software is governed by the Sybase License Agreement. I. 2010-11-03 17:21:44. Refer to http://www.sybase.com/softwarelicenses. I. 2010-11-03 17:21:44. I. 2010-11-03 17:21:44. This server is licensed to: I. 2010-11-03 17:21:44. Developer Edition I. 2010-11-03 17:21:44. Restricted Use I. 2010-11-03 17:21:44. Running Windows XP Build 2600 Service Pack 3 on X86 (X86_64) I. 2010-11-03 17:21:44. Server built for X86 processor architecture I. 2010-11-03 17:21:44. Option 1: -c I. 2010-11-03 17:21:44. Option 2: DSN=xxx;UID=xxx;pwd=********; I. 2010-11-03 17:21:44. Option 3: -zs I. 2010-11-03 17:21:44. Option 4: xxx I. 2010-11-03 17:21:44. Option 5: -vcnrs I. 2010-11-03 17:21:44. Option 6: -ot I. 2010-11-03 17:21:44. Option 7: ml.txt I. 2010-11-03 17:21:44. Option 8: -x I. 2010-11-03 17:21:44. Option 9: tcpip(port=2439) I. 2010-11-03 17:21:44. Verbose logging: show upload row values I. 2010-11-03 17:21:44. Verbose logging: show download row values I. 2010-11-03 17:21:44. Verbose logging: show script names when invoked I. 2010-11-03 17:21:44. Verbose logging: show script contents when invoked I. 2010-11-03 17:21:44. Verbose logging: show rowcount values I. 2010-11-03 17:21:44. Cache size: 52428800 bytes I. 2010-11-03 17:21:44. Download cache directory size: 10485760 bytes I. 2010-11-03 17:21:44. Local file for remote synchronization logs: 'mlsrv.mle' I. 2010-11-03 17:21:44. Individual database connections will be closed after synchronization errors I. 2010-11-03 17:21:44. Maximum number of BLOB bytes to compare: 4294967295 I. 2010-11-03 17:21:44. Maximum number of database connections: 5 I. 2010-11-03 17:21:44. Maximum number of deadlock retries: 10 I. 2010-11-03 17:21:44. Timeout for inactive database connections: 60 minutes I. 2010-11-03 17:21:44. Maximum delay between retries after deadlock: 30 seconds I. 2010-11-03 17:21:44. Rowset size: 10 I. 2010-11-03 17:21:44. Number of database worker threads: 5 I. 2010-11-03 17:21:44. Maximum number of threads uploading concurrently: 5 I. 2010-11-03 17:21:44. Unknown users will be rejected (when there is no authenticate_user script) I. 2010-11-03 17:21:46. Shared administrative connection connected I. 2010-11-03 17:21:46. ODBC DBMS Name: Oracle I. 2010-11-03 17:21:46. ODBC DBMS Version: 10.02.0000 I. 2010-11-03 17:21:46. ODBC DBMS Driver Version: 12.00.0000 I. 2010-11-03 17:21:46. ODBC Version supported by the driver: 3.51 I. 2010-11-03 17:21:46. ODBC DBMS Type: ORACLE RAC I. 2010-11-03 17:21:46. ODBC isolation set to: Read Committed E. 2010-11-03 17:21:47. [-10002] Consolidated database server or ODBC error: ODBC: [Sybase][iAnywhere Solutions - Oracle][Oracle]ORA-00942: table or view does not exist (ODBC State = 42S02, Native error code = 942) W. 2010-11-03 17:21:58. [10075] Unable to access ORACLE table 'gv$transaction'. Access is needed to ensure no data is missed if using timestamp-based downloads I. 2010-11-03 17:21:58. This software is using security technology from Certicom Corp. I. 2010-11-03 17:21:58. MobiLink server started I. 2010-11-03 17:21:58. Notifier stage connection connected I. 2010-11-03 17:21:58. ODBC isolation set to: Read Committed I. 2010-11-03 17:21:58. Started RTNotifier 'RTNotifier1' asked 03 Nov '10, 21:47 Breck Carter |
I "think" I remember there is an error in the documentation. The line of code below is what I have cataloged as the proper statement. Notice the underscore, which does not appear in the docs. GRANT SELECT ON SYS.GV_$TRANSACTION TO user_name; I say "think" because our wonderful, extremely smart Oracle DBA would often "correct" my mistakes without telling me. But I believe the underscore makes the difference between the base table and a view, and the one with the underscore is what we needed. answered 03 Nov '10, 23:15 Bill Aumen Comment Text Removed
1
You're correct. Permission has to be granted on GV_$TRANSACTION to access GV$TRANSACTION. The documentation has been updated for the next release. Comment Text Removed
|
More of a wild guess, but do both errors/warnings disappear when you follow the requirements to grant the needed permissions, e.g. on gv_$transaction, as described in the docs? answered 03 Nov '10, 22:06 Volker Barth Comment Text Removed
I may never know, since most Oracle sites won't do that. What I want to know, is the "E" message just part of the same warning, or is it a real error message? @Breck: Sorry, that's something I cannot clarify - because I'm lacking both ML/Oracle knowledge and an Oracle DB (and don't miss that)... Comment Text Removed
We are almost positive that the two messages are for the same problem. They could tell for certain by adding 'e' to the verbosity switch, eg. -vcenrs. Note that without assigning that permission, some changes on the consolidated might never be downloaded! Also, if any Oracle sites are leery of granting permission to that view, they can see the SQL that accesses it with -ve vebosity. All it's doing is getting the earliest start time of open transactions. For more info, see this old document: http://www.sybase.com/detail?id=1034585 |