Error while accessing DBlink to mysql

Getting following error (trace file content) when querying suing the DB link (select * from "DeviceWindows_Devices"@monolith2.us.oracle.com;)
table: DeviceWindows_Devices
Entered hgopcda at 2012/11/15-18:56:59
Column:1(WindowID): dtype:4 (INTEGER), prc/scl:10/0, nullbl:0, octet:0, sign:1, radix:10
Exiting hgopcda, rc=0 at 2012/11/15-18:56:59
Entered hgopcda at 2012/11/15-18:56:59
Column:2(DeviceID): dtype:4 (INTEGER), prc/scl:10/0, nullbl:0, octet:0, sign:1, radix:10
Exiting hgopcda, rc=0 at 2012/11/15-18:56:59
The hoada for table DeviceWindows_Devices follows...
hgodtab, line 651: Printing hoada @ 0x281a100
MAX:2, ACTUAL:2, BRC:1, WHT=6 (TABLE_DESCRIBE)
DTY NULL-OK LEN MAXBUFLEN PR/SC CST IND MOD NAME
4 INTEGER N 4 4 0/ 0 0 0 0 WindowID
4 INTEGER N 4 4 0/ 0 0 0 0 DeviceID
Exiting hgodtab, rc=0 at 2012/11/15-18:56:59
Entered hgodafr, cursor id 0 at 2012/11/15-18:56:59
Exiting hgodafr, rc=0 at 2012/11/15-18:56:59
Entered hgopars, cursor id 1 at 2012/11/15-18:56:59
type:0
SQL text from hgopars, id=1, len=60 ...
00: 53454C45 43542041 312E5769 6E646F77 [SELECT A1.Window]
10: 49442C41 312E4465 76696365 49442046 [ID,A1.DeviceID F]
20: 524F4D20 44657669 63655769 6E646F77 [ROM DeviceWindow]
30: 735F4465 76696365 73204131 [s_Devices A1]
Exiting hgopars, rc=0 at 2012/11/15-18:56:59
Entered hgoopen, cursor id 1 at 2012/11/15-18:56:59
hgoopen, line 83: NO hoada to print
Exiting hgoopen, rc=0 at 2012/11/15-18:56:59
Entered hgodscr, cursor id 1 at 2012/11/15-18:56:59
Entered hgopcda at 2012/11/15-18:56:59
Column:1(WindowID): dtype:4 (INTEGER), prc/scl:10/0, nullbl:0, octet:0, sign:0, radix:0
Exiting hgopcda, rc=0 at 2012/11/15-18:56:59
Entered hgopcda at 2012/11/15-18:56:59
Column:2(DeviceID): dtype:4 (INTEGER), prc/scl:10/0, nullbl:0, octet:0, sign:0, radix:0
Exiting hgopcda, rc=0 at 2012/11/15-18:56:59
Entered hgopoer at 2012/11/15-18:56:59
hgopoer, line 159: got native error 0 and sqlstate HY092; message follows...
[unixODBC][Driver Manager]Invalid attribute/option identifier
Exiting hgopoer, rc=0 at 2012/11/15-18:56:59
hgodscr, line 456: calling SQLSetStmtAttr got sqlstate HY092
hgodscr, line 506: NO hoada to print
Exiting hgodscr, rc=28500 at 2012/11/15-18:56:59 with error ptr FILE:hgodscr.c LINE:456 FUNCTION:hgodscr() ID:Set array fetch size
Driver : ODBC 5.2(w) Driver
Oracle Database: 11.1.0.7
Mysql Database: 5.5.20
Able to connect from isql and select commands also works fine from there
-bash-3.2$ isql -v monolith_itasmon
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
Please help in resolving this, thanks in advance.
Thanks,
Vani
Edited by: user580543 on Nov 16, 2012 2:10 AM

Hi ,
Sorry for the delay.
Please find the trace file.
Thanks,
Vani
[ODBC][26106][__handles.c][444]
          Exit:[SQL_SUCCESS]
               Environment = 0x532c160
[ODBC][26106][SQLSetEnvAttr.c][182]
          Entry:
               Environment = 0x532c160
               Attribute = SQL_ATTR_ODBC_VERSION
               Value = 0x3
               StrLen = -6
[ODBC][26106][SQLSetEnvAttr.c][349]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLAllocHandle.c][345]
          Entry:
               Handle Type = 2
               Input Handle = 0x532c160
[ODBC][26106][SQLAllocHandle.c][463]
          Exit:[SQL_SUCCESS]
               Output Handle = 0x5361780
[ODBC][26106][SQLSetConnectAttr.c][318]
          Entry:
               Connection = 0x5361780
               Attribute = SQL_ATTR_AUTOCOMMIT
               Value = (nil)
               StrLen = -5
[ODBC][26106][SQLSetConnectAttr.c][500]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLDriverConnect.c][678]
          Entry:
               Connection = 0x5361780
               Window Hdl = (nil)
               Str In = [DSN=MONOLITH_ITASMON;UID=itasmon;PWD=********][length = 45]
               Str Out = 0x5363848
               Str Out Max = 1024
               Str Out Ptr = 0x7fffe146fe44
               Completion = 0
          UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE'
[ODBC][26106][SQLDriverConnect.c][1487]
          Exit:[SQL_SUCCESS]
               Connection Out [[DSN=MONOLITH_ITASMON;UID=itasmon;PWD=********][length = 45 (SQL_NTS)]]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_DRIVER_NAME (6)
               Info Value = 0x7fffe146fb20
               Buffer Length = 512
               StrLen = 0x7fffe146fe48
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_DRIVER_VER (7)
               Info Value = 0x7fffe146fb20
               Buffer Length = 512
               StrLen = 0x7fffe146fe48
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_DBMS_NAME (17)
               Info Value = 0x7fffe146fb20
               Buffer Length = 512
               StrLen = 0x7fffe146fe48
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_DBMS_VER (18)
               Info Value = 0x7fffe146fb20
               Buffer Length = 512
               StrLen = 0x7fffe146fe48
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_CATALOG_NAME (10003)
               Info Value = 0x7fffe146fe90
               Buffer Length = 512
               StrLen = 0x7fffe1470124
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_IDENTIFIER_QUOTE_CHAR (29)
               Info Value = 0x7fffe146fd60
               Buffer Length = 512
               StrLen = 0x7fffe147021c
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_COLUMN_ALIAS (87)
               Info Value = 0x7fffe146fd60
               Buffer Length = 512
               StrLen = 0x7fffe147021c
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_NO_DATA]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_INTEGER
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_SMALLINT
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_NO_DATA]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_SMALLINT
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_VARBINARY
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_NO_DATA]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_BIGINT
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_NO_DATA]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_BIGINT
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_TINYINT
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_NO_DATA]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_TINYINT
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_LONGVARCHAR
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetTypeInfo.c][164]
          Entry:
               Statement = 0x538ae20
               Data Type = SQL_LONGVARBINARY
[ODBC][26106][SQLGetTypeInfo.c][314]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 2
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLEndTran.c][315]
          Entry:
               Connection = 0x5361780
               Completion Type = 0
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_CURSOR_COMMIT_BEHAVIOR (23)
               Info Value = 0x7fffe14700de
               Buffer Length = 8
               StrLen = 0x7fffe14700dc
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLEndTran.c][488]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_TXN_CAPABLE (46)
               Info Value = 0x7fffe1470274
               Buffer Length = 2
               StrLen = 0x7fffe1470278
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLGetInfo.c][214]
          Entry:
               Connection = 0x5361780
               Info Type = SQL_TXN_ISOLATION_OPTION (72)
               Info Value = 0x7fffe1470270
               Buffer Length = 4
               StrLen = 0x7fffe1470278
[ODBC][26106][SQLGetInfo.c][528]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLSetConnectAttr.c][318]
          Entry:
               Connection = 0x5361780
               Attribute = SQL_ATTR_TXN_ISOLATION
               Value = 0x2
               StrLen = -5
[ODBC][26106][SQLSetConnectAttr.c][671]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeHandle.c][365]
          Entry:
               Handle Type = 3
               Input Handle = 0x538ae20
[ODBC][26106][SQLFreeHandle.c][462]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLAllocHandle.c][510]
          Entry:
               Handle Type = 3
               Input Handle = 0x5361780
[ODBC][26106][SQLAllocHandle.c][872]
          Exit:[SQL_SUCCESS]
               Output Handle = 0x538ae20
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 4
               Target Type = 1 SQL_CHAR
               Target Value = 0x7fffe1470028
               Buffer Length = 124
               StrLen Or Ind = 0x7fffe1470110
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 5
               Target Type = -15 SQL_C_SSHORT
               Target Value = 0x7fffe14701c0
               Buffer Length = 0
               StrLen Or Ind = (nil)
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 6
               Target Type = 1 SQL_CHAR
               Target Value = 0x7fffe146ffb0
               Buffer Length = 120
               StrLen Or Ind = 0x7fffe1470108
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 7
               Target Type = -16 SQL_C_SLONG
               Target Value = 0x7fffe14701a8
               Buffer Length = 0
               StrLen Or Ind = 0x7fffe1470130
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 9
               Target Type = -15 SQL_C_SSHORT
               Target Value = 0x7fffe14701cc
               Buffer Length = 0
               StrLen Or Ind = 0x7fffe1470128
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 10
               Target Type = -15 SQL_C_SSHORT
               Target Value = 0x7fffe14701c4
               Buffer Length = 0
               StrLen Or Ind = 0x7fffe1470120
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 11
               Target Type = -15 SQL_C_SSHORT
               Target Value = 0x7fffe14701c8
               Buffer Length = 0
               StrLen Or Ind = (nil)
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLBindCol.c][165]
          Entry:
               Statement = 0x538ae20
               Column Number = 16
               Target Type = -16 SQL_C_SLONG
               Target Value = 0x7fffe14701a4
               Buffer Length = 0
               StrLen Or Ind = 0x7fffe1470118
[ODBC][26106][SQLBindCol.c][251]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLColumns.c][208]
          Entry:
               Statement = 0x538ae20
               Catalog Name = [NULL]
               Schema Name = [itasmon][length = 7]
               Table Name = [DeviceWindows_Devices][length = 21]
               Column Type = [NULL]
[ODBC][26106][SQLColumns.c][405]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFetch.c][158]
          Entry:
               Statement = 0x538ae20
[ODBC][26106][SQLFetch.c][340]
          Exit:[SQL_NO_DATA]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 0
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLFreeStmt.c][140]
          Entry:
               Statement = 0x538ae20
               Option = 2
[ODBC][26106][SQLFreeStmt.c][246]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLAllocHandle.c][510]
          Entry:
               Handle Type = 3
               Input Handle = 0x5361780
[ODBC][26106][SQLAllocHandle.c][872]
          Exit:[SQL_SUCCESS]
               Output Handle = 0x53bdd30
[ODBC][26106][SQLPrepare.c][189]
          Entry:
               Statement = 0x53bdd30
               SQL = [SELECT A1.WindowID,A1.DeviceID FROM DeviceWindows_Devices A1][length = 60]
[ODBC][26106][SQLPrepare.c][364]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLNumResultCols.c][149]
          Entry:
               Statement = 0x53bdd30
               Column Count = 0x532c880
[ODBC][26106][SQLNumResultCols.c][234]
          Exit:[SQL_SUCCESS]
               Count = 0x532c880 -> 2
[ODBC][26106][SQLExecute.c][183]
          Entry:
               Statement = 0x53bdd30
[ODBC][26106][SQLExecute.c][344]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLDescribeCol.c][231]
          Entry:
               Statement = 0x53bdd30
               Column Number = 1
               Column Name = 0x7fffe146ff00
               Buffer Length = 30
               Name Length = 0x7fffe1470044
               Data Type = 0x7fffe1470040
               Column Size = 0x7fffe146ffe8
               Decimal Digits = 0x7fffe147003c
               Nullable = 0x7fffe1470038
[ODBC][26106][SQLDescribeCol.c][474]
          Exit:[SQL_SUCCESS]
               Column Name = [WindowID]
               Data Type = 0x7fffe1470040 -> 4
               Column Size = 0x7fffe146ffe8 -> 10
               Decimal Digits = 0x7fffe147003c -> 0
               Nullable = 0x7fffe1470038 -> 0
[ODBC][26106][SQLColAttribute.c][277]
          Entry:
               Statement = 0x53bdd30
               Column Number = 1
               Field Identifier = SQL_DESC_UNSIGNED
               Character Attr = (nil)
               Buffer Length = 0
               String Length = (nil)
               Numeric Attribute = 0x7fffe146fff0
[ODBC][26106][SQLColAttribute.c][648]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLDescribeCol.c][231]
          Entry:
               Statement = 0x53bdd30
               Column Number = 2
               Column Name = 0x7fffe146ff00
               Buffer Length = 30
               Name Length = 0x7fffe1470044
               Data Type = 0x7fffe1470040
               Column Size = 0x7fffe146ffe8
               Decimal Digits = 0x7fffe147003c
               Nullable = 0x7fffe1470038
[ODBC][26106][SQLDescribeCol.c][474]
          Exit:[SQL_SUCCESS]
               Column Name = [DeviceID]
               Data Type = 0x7fffe1470040 -> 4
               Column Size = 0x7fffe146ffe8 -> 10
               Decimal Digits = 0x7fffe147003c -> 0
               Nullable = 0x7fffe1470038 -> 0
[ODBC][26106][SQLColAttribute.c][277]
          Entry:
               Statement = 0x53bdd30
               Column Number = 2
               Field Identifier = SQL_DESC_UNSIGNED
               Character Attr = (nil)
               Buffer Length = 0
               String Length = (nil)
               Numeric Attribute = 0x7fffe146fff0
[ODBC][26106][SQLColAttribute.c][648]
          Exit:[SQL_SUCCESS]
[ODBC][26106][SQLSetStmtAttr.c][243]
          Entry:
               Statement = 0x53bdd30
               Attribute = SQL_ATTR_ROW_ARRAY_SIZE
               Value = 0x1
               StrLen = 0
[ODBC][26106][SQLSetStmtAttr.c][636]Error: HY092
[ODBC][26106][SQLGetDiagRec.c][710]
          Entry:
               Statement = 0x53bdd30
               Rec Number = 1
               SQLState = 0x7fffe146fe48
               Native = 0x7fffe146fec0
               Message Text = 0x7fffe146fc30
               Buffer Length = 510
               Text Len Ptr = 0x7fffe146fec4
[ODBC][26106][SQLGetDiagRec.c][747]
          Exit:[SQL_SUCCESS]
               SQLState = HY092
               Native = 0x7fffe146fec0 -> 0
               Message Text = [[unixODBC][Driver Manager]Invalid attribute/option identifier]
[ODBC][26106][SQLGetDiagRec.c][710]
          Entry:
               Statement = 0x53bdd30
               Rec Number = 2
               SQLState = 0x7fffe146fe48
               Native = 0x7fffe146fec0
               Message Text = 0x7fffe146fc30
               Buffer Length = 510
               Text Len Ptr = 0x7fffe146fec4
[ODBC][26106][SQLGetDiagRec.c][747]
          Exit:[SQL_NO_DATA]

Similar Messages

  • Error while accessing Oracle E-Business Suite 11i from Linux/firefox

    error while accessing Oracle E-Business Suite 11i from Linux/firefox
    OS: SUSE Linux Desktop 11(SLED11)
    Web browser: firefox 3.x
    Java versions:
    # rpm -qa |grep java
    java-1_6_0-sun-plugin-1.6.0.u18-0.1.1
    java-1_6_0-sun-1.6.0.u18-0.1.1
    # java -version
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Server VM (build 16.0-b13, mixed mode)
    when I access the url firefox says
    "Additional plugins are required to display all the media on this page"
    then I clicked on "Install Missing Plugin" button
    then I got the following message
    No Suitable Plugins were found
    Unknown Plugin (application/x-java-applet;jpi-version=1.4.1)
    please help/suggest
    Regards

    Hi user;
    Its not certified to login EBS from linux client
    Please check:
    Linux-cleint (ebs) certification
    pluggins
    Hope it helps
    Regard
    Helios

  • Error while accessing discver report

    Hi,
    I am getting error while accessing a shared report from my colleague.
    1)Item "Project Overview Project Type" used by the workbook is missing. Would you like to continue
    2)Item dependency "not found in the EUL. Attempt to open workbook failed.
    Could you please give my the workaround for this.
    Thanks

    hi,
    the link is:
    Discoverer
    Regards
    Cosimo

  • Error while accessing secure store

    Hi Team,
    We are on EP 7.0 on SQL server 2005 . Iam facing one problem , in sometimemy IRJ pOrtal site stops giving error " Java iView Runtime " .At this time what happens that in my usr/sap drive , the sap folder is not shown as shared its share goes away and that time when i connect to visual admin tool the authentication fails and that time config tool gives error
    #1.5#00188B417A01007E0160B338000008FC00045DE876A4C303#1229152911187#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl##com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#Guest#2####f168def0c8c411dd9a2100188b417a01#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured while creating ManagedConnection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
    musaprd
    sapmnt
    PWC
    SYS
    global
    security
    data
    SecStore.properties" does not exist although it should..#
    #1.5#00188B417A010085015AAAF5000008FC00045DE876A4C207#1229152911187#com.sap.sql.connect.OpenSQLDataSourceImpl##com.sap.sql.connect.OpenSQLDataSourceImpl#Guest#2####09e36ed0c8c711dd93b200188b417a01#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Database/sql/connect#Java#com.sap.sql_0019##Exception of type com.sap.sql.log.OpenSQLException caught: Error while accessing secure store: File
    When i check in this path SecStore.properties is there , also i have checked the permissions .....................please revert the reason of this error  . 
    Main part of this all is that after taking a reboot everything becomes fine , this happens every few days .
    Please revert to this .
    Regards,
    Somya

    Hi,
    This error crops up when the the folder usr/sap folder sharing is lost .  We  have recently faced this problem this is Windows OS level problem you can ask your OS admin. Applying a security patch will do.
    Regards,
    Vamshi.

  • Error while accessing secure store: File "SecStore.properties" does not exi

    Hi ,
    I have a java desktop application, and i am trying to get a connection from a datasource deployed on one SAP AS Java, I can get the datasource succsfullly but when i try to get a connection from the DS, it throughs this exception, I put the secstore..properties file in the classpath even after that it is not happy,
    any solution/hint/light please!!!!
    com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "SecStore.properties" does not exist although it should..
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
         at com.sap.customcode.ConflictingActionFixture.(ConflictingActionFixture.java:53)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
         at java.lang.reflect.Constructor.newInstance(Unknown Source)
         at java.lang.Class.newInstance0(Unknown Source)
         at java.lang.Class.newInstance(Unknown Source)
         at fit.FixtureClass.newInstance(Unknown Source)
         at fit.FixtureLoader.instantiateFixture(Unknown Source)
         at fit.FixtureLoader.instantiateFirstValidFixtureClass(Unknown Source)
         at fit.FixtureLoader.disgraceThenLoad(Unknown Source)
         at fit.Fixture.loadFixture(Unknown Source)
         at fit.Fixture.getLinkedFixtureWithArgs(Unknown Source)
         at fit.Fixture.doTables(Unknown Source)
         at fit.FitServer.process(Unknown Source)
         at fit.FitServer.run(Unknown Source)
         at fit.FitServer.main(Unknown Source)
    Caused by: com.sap.security.core.server.secstorefs.FileMissingException: File "SecStore.properties" does not exist although it should.
         at com.sap.security.core.server.secstorefs.StorageHandler.openExistingStore(StorageHandler.java:372)
         at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1946)
         at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
         at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
         ... 18 more
    caused by

    the SecStore.key file was not there, I changed the passwd and checked the 'Encryption' on, after that my sever instance is not starting.
    Any idea?
    -Puneet

  • Error while accessing table from procedure but no error from anonymous plsq

    Hi All,
    I am getting a strange error while accessing a table from a different schema.
    In that concerned schema OWBSYS, i executed the following:
    grant Select on wb_rt_audit to ods;In Ods schema i executed:
    CREATE OR REPLACE SYNONYM wb_rt_audit FOR OWBSYS.wb_rt_audit;In ODS schema, when i execute:
    create or replace
    procedure pp_test as
    lv_owb_reject number := 0;
    lv_filename_1 varchar2(200):= 'asda';
    begin
        SELECT MAX(aud.rta_iid) into lv_owb_reject
                              FROM   wb_rt_audit aud
                              WHERE  aud.rta_lob_name LIKE Upper(lv_filename_1)
    end;
    /I get the error:
    Warning: execution completed with warning
    procedure Compiled.
    ORA-00942 - TABLE OR VIEW DOES NOT EXISTHowever, when i execute as an anonymous plsql the same code:
    declare
    lv_owb_reject number := 0;
    lv_filename_1 varchar2(200):= 'asda';
    begin
        SELECT MAX(aud.rta_iid) lv_owb_reject
                              FROM   wb_rt_audit aud
                              WHERE  aud.rta_lob_name LIKE Upper(lv_filename_1)
    end;
    anonymous block completedthere is no issue.
    Can someone help me understand what I might be missing:
    Edited by: Chaitanya on Feb 28, 2012 12:31 AM

    Check if have some other steps.
    SQL>conn scott1/tiger
    Connected.
    SQL>create table wb_rt_audit (rta_iid number);
    Table created.
    SQL>insert into wb_rt_audit values (100);
    1 row created.
    SQL>insert into wb_rt_audit values (200);
    1 row created.
    SQL>commit;
    Commit complete.
    SQL>grant select  on wb_rt_audit to scott2;
    Grant succeeded.
    SQL>conn scott2/tiger
    Connected.
    SQL>create synonym wb_rt_audit for scott1.wb_rt_audit;
    Synonym created.
    SQL>create or replace procedure pp_test as
        l_number number(10);
        begin
            SELECT MAX(rta_iid) into l_number
                                  FROM   wb_rt_audit;
      end pp_test;
    Procedure created.

  • Access Denied Error while accessing "Site Settings Access requests and invitations"

    Hi,
    I am getting Access Denied Error while accessing "Site Settings > Access requests and invitations" in SharePoint  2013 online. Currently I am the owner of the site and have "FULL CONTROL" access. I am able to access using
    site collection account. So, what permission I have to give my regular account to access this page?
    Thanks, Pal

    Hello,
    Have you recently changed the Owners group of the site collection or removed the user from the original owners group? 
    The reason I am asking is when the Access requests and invitations list are created, the permissions are given only to the default owners group at the time that the Access Request list was created.  If this "regular account" is not part of that owners
    group, the user will receive access denied.  Site Collection Admins always have permissions for the Access Request List.
    A workaround for the Access Denied issue is listed in the KB article http://support.microsoft.com/kb/2911390/en-us.  By giving the correct group or user the permissions to this list, the users will not receive
    the Access Denied issue anymore.  
    Preferably, in order to grant the user the full permissions ( you will see features like resending invitations may still fail after implementing the above workaround) there is one other workaround that may be required depending on what the original issue
    was.  Below are additional steps to restore full functionality.
    1)Access the /_layouts/15/permsetup.aspx of the site collection, make sure the default Owners Group
    is set correctly.  (There is a group selected)
    2) Add user to that Owners Group.  (Issue may be resolved at this step if the site collection Owners
    Group was never changed, if not continue to next step.)
    3) Implement workaround on http://support.microsoft.com/kb/2911390/en-us, by adding that owners
    group as Full control on Access Request list Permissions.
    Let me know how this works out for you.
    - Shpendi Jashari

  • Error while accessing public holiday calendar

    Friends,
    Well when creating a work schedule for the year 2008 (practice mode - at home) i am getting the below message..
    I checked all the configurations and no where i mention about 2009. Any tips and suggestions.
    Error while accessing public holiday calendar
    The function module HOLIDAY_CHECK_AND_GET)INFO has generated an error

    friends the problem still exists..
    i created a new calender, new dws, pws, bws.. but again the same error comes in play.
    Friends,
    Well when creating a work schedule for the year 2008 (practice mode - at home) i am getting the below message..
    I checked all the configurations and no where i mention about 2009. Any tips and suggestions.
    Error while accessing public holiday calendar on 20090101
    The function module HOLIDAY_CHECK_AND_GET)INFO has generated an error

  • Error while accessing public holiday calendar on 20120101

    Dear All,
    When I'm posting PL(Personnel Leave) against 31.12.2011 it is working fine but If I'm posting a Sick Leave against 31.12.2011 or CB the error is coming like "Error while accessing public holiday calendar on 20120101".
    Please suggest what to do.

    Dear All,
    When I'm posting PL(Personnel Leave) against 31.12.2011
    it is working fine but If I'm posting a Sick Leave against 31.12.2011 or
    CB the error is coming like "Error while accessing public holiday calendar on 20120101".
    Please suggest what to do.
    the error clearly saying that you dont have holiday calendar for 01.01.2012,, so please change it using PT02 to avoid the error.
    then you check what exactly system is doing.
    you have to create a wsr with one month extra validity than the exact periods required to avoid the future errors as you are getting now.
    system always takes one month extra validity it is standard functionality.
    regards,
    mohammed

  • Error while accessing public holiday calendar on 20100101

    Dear Gurus.
    When i was created Work Schedule TC-PT01
    Error Showing
    "Error while accessing public holiday calendar on 20100101"
    Message no. P2518
    Diagnosis
    The function module HOLIDAY_CHECK_AND_GET_INFO has generated an error.
    Please Advised
    Regards
    MHPO

    Hi
    As Surisetti told that, that public holiday might not created in that year. So check the same in SCAL and again re-generate the work schedule.
    Thanks & Regards
    Bharathi

  • InvalidSecurity Error while accessing Webservice

    Hi,
    I am getting an "*InvalidSecurity*" error while accessing webservice.
    Below is the error, which I got while invoking the webservice :
    <env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body>
    <env:Fault
    xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <faultcode>ns0:InvalidSecurity</faultcode>
    <faultstring>InvalidSecurity : error in processing the WS-Security security header</faultstring>
    <faultactor/>
    </env:Fault>
    </env:Body>
    </env:Envelope>
    Thanks
    Abheek
    Edited by: 1005832 on May 14, 2013 6:16 AM

    The error was generated on the endpoint and indicates that the SOAP request message had incorrect WS-Security information in its headers. The SOAP response message you included doesn't contain specific information about what is wrong (we wouldn't want to reveal too much to hackers, of course!).
    Without seeing the SOAP request message and the WS-SecurityPolicy that the endpoint requires, it's impossible to tell what's wrong.
    Other important information:
    - what version of WLS are you running?
    - is the endpoint a WLS JAX-WS or a WLS JAX-RPC web service?
    - is WS-Security configured using native WLS WS-Security (e.g. @Policy) or using OWSM WS-Security (i.e. @SecurityPolicy)?
    - what specific policy is being used to enforce security at the endpoint (the advertised WSDL for the endpoint should contain this)

  • "Error while accessing porting layer for ORACLE database via getSessionId()

    Hi,
    My ejb3.0 Entity is created from Emp table in scott/tiger schema of an Oracle 10g database. I am guessing I made some mistake creating the datasource or uploading the driver, because when I run my application, I get a long exception stack trace. The bottom-most entry in the stack trace is:
    Caused by: com.sap.sql.log.OpenSQLException: Error while accessing porting layer for ORACLE database via getSessionId().
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:148)
         at com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:527)
         at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:158)
         at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:118)
         at com.sap.sql.connect.factory.PooledConnectionFactory.createPooledConnection(PooledConnectionFactory.java:119)
         at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:38)
         at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:685)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.matchPool(DBDataSourcePoolImpl.java:1081)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.matchPooledConnection(DBDataSourcePoolImpl.java:919)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.getConnection(DBDataSourcePoolImpl.java:67)
         at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnection(DatabaseDataSourceImpl.java:36)
         at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:123)
         ... 90 more

    Actually, now (after the GRANT described in my reply before) the Exception has changed to:
    Caused by: com.sap.sql.log.OpenSQLException: Error while
    accessing porting layer for ORACLE database via
    <b>getDatabaseHost</b>().
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException
    (Syslog.java:148)
         at com.sap.sql.jdbc.direct.DirectConnectionFactory.
    createPooledConnection(DirectConnectionFactory.java:527)
         at com.sap.sql.jdbc.direct.DirectConnectionFactory.
    createDirectPooledConnection(DirectConnectionFactory.java:158)
         at com.sap.sql.jdbc.direct.DirectConnectionFactory.
    createDirectPooledConnection(DirectConnectionFactory.java:118)
         at com.sap.sql.connect.factory.PooledConnectionFactory.
    createPooledConnection(PooledConnectionFactory.java:119)
         at com.sap.sql.connect.factory.DriverPooledConnectionFactory.
    getPooledConnection(DriverPooledConnectionFactory.java:38)
         at com.sap.sql.connect.datasource.DBDataSourceImpl.
    createPooledConnection(DBDataSourceImpl.java:685)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.
    matchPool(DBDataSourcePoolImpl.java:1081)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.
    matchPooledConnection(DBDataSourcePoolImpl.java:919)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.
    getConnection(DBDataSourcePoolImpl.java:67)
         at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.
    getConnection(DatabaseDataSourceImpl.java:36)
         at com.sap.engine.services.dbpool.spi.
    ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:123)
         ... 90 more

  • Getting Error while accessing the data using odata service

    Hi All,
    Iam new to SAP FIORI. 
    Iam getting the below error while accessing the data using odata service.
    "Failed to load resource: the server responded with a status of 404 (Not found)"
    "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin "
    i have tried all the solutions like changing the url pattern "proxy/htttp".
    and disabled - security in chrome (Chrome is Updated version).
    i tried with IE still got the same problem.
    And installed all the required software in eclipse
    While installing GWPA plugin i got the following error.
    let me know if any one have idea.
    Thanks in advance.

    > Do you want to add and/or update the data in the already existing tables or do you want to replace the content completely?
    >
    > so in that way :
    > bot the options are fine what ever take less time.
    Sorry mate, but YOU have to know what you want here.
    I gave you an easy to follow set of steps.
    As you don't seam to mind the outcome, just might just use them...
    > I wanted to know weathe i can use the  loadercli for thie export import or not? if yes then is there any new steps to do before i do the export import?
    We had this discussion before...
    >
    > For that the easiest option would be just to drop the tables of SAPR3 and run the import again.
    >
    > For ease of use you could also just do:
    > - logon as superdba
    > - drop user SAPR3
    > - create user SAPR3 password SOMEPW not exclusive dba
    >
    > After these steps you can easily pump the data into the database again.
    >
    > So here in th above given steps , i am creating a new SAPR3 user and why it is not exclusive dba ?
    >  i already have that user SAPR3 can i use the same.
    Yes, you do have the SAPR3 user.
    But you don't seem to like to read documentation or learn about how the tools work or anything like that.
    Therefore I gave you s simple way to reach your goal.
    Of course it's possible to reuse the user.
    But then you would have to deal with already existing tables, already existing data etc.
    You don't seem to be able to do that. So, the easy steps might be better suited for your needs.
    regards,
    Lars

  • Error  while accessing the application server file

    Hello,
    When I try to load the data from CSV file to PSA , I am getting following error message
    "Error  while accessing the application server file"
    "Errors in source system"
    I gave the right file path
    I am not sure about this error message.
    Thanks,

    Hi ram,
    if you have more than one application server running in your BI system (see at transaction SM51) be aware that your infopackage will be executed on the right one. Each application server has its own file system and your job need to run on the server your file is stored on.
    Also check if the os user of the SAP system itself (<sid>adm on Unix) has rights to read that file.
    Bye
    Frank

  • Getting Portal Runtime Error while accessing one link in Portal Page.

    Hi,
    Can anyone tell why I am getting below error while accessing one of the portal page link:
    " Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 01:19_27/02/09_0046_16441150
    Refer to the log file for details about this exception. "
    Also please let me know how to get rid of this if possible.
    Thanks in Advance
    Vaibhav Srivastava

    Thank you for your prompt reply.
    Could you please elaborate the same.
    I am getting Portal runtime error while I am acessing an iveiw in E-recruiting. We have setup the role and user in both portal and Backend. But still the error. Could you pls send me the setting you have done.
    Portal runtime ERROR
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 02:27_27/04/09_0042_113148050
    Refer to the log file for details about this exception.
    regards
    Justin

Maybe you are looking for

  • Converting Acid Apple Loops -great App.!!!

    Sample Manager does this perfectly! Once your Acid .wav files are converted to 44.1kHz aif Apple Loops with correct tempo & beat information, you can then load the files into the Apple Loops Utility for batch or individual tagging (genre/Instrument e

  • How to download a text file using classes

    Hi Guys I want to download a text file using classes. Any idea how to do it ? Thanks Sameer

  • Book with I Photo 9.6 problem with yosemite

    I did some books with I Photo 9.6 in the past and it was working perfectly. Then I installed Yosemite and now when I tried to do a new book and try to use the disposition button and the function Personnelize ( choice of 2, 3 , 4 and more photos in a

  • Configuration Page Garbled on WRT54G V5

    Hi, When I access my router via 192.168.1.1 the page is garbled. ie links are missing and there are bits missing on the page. This happens if i access the router from my PC or remotely from my laptop. Laptop is on Xp and PC is on Vista. I guess reloa

  • Application timeout on ACE

    Hi , I need some advice on how to start troubleshooting on one the issue on ACE. I am new to ACE/Load balancers. The application if is bypassed ACE , it works fine . When it is accessed through the ACE the application timeouts. Any help will be appre