Proxy table creation error.

[Former Member]

DBMS is ASA 9.0.2.3951 on SuSe Linux 10.1 32-bit host. I'm using a master in Sybase Central for create proxy table of Oracle 10g database table. I've got an error with SQLCODE -667 "Could not access column information for the table '%1'". Documentation says that prabable couse may by "Column information for the table could not be accessed. Check privileges for the table". I can't understand what does it mean. I have SELECT privilege on this table(view) in Oracle database. What i must to do to avoid this error?

Update:

I'm using an Oracle WP Driver.

There is a part from odbc.ini

[ODBC Data Sources]
OraSRC=iAnywhere Solutions 9 - Oracle Wire Protocol Driver

[OraSRC]
Driver=/opt/sybase/SYBSsa9/drivers/lib/wqora19.so
Description=iAnywhere Solutions 9 - Oracle Wire Protocol
ApplicationUsingThreads=1
ArraySize=60000
CachedCursorLimit=32
CachedDescriptionLimit=0
CatalogIncludesSynonyms=1
CatalogOptions=1
DefaultLongDataBuffLen=1024
DescribeAtPrepare=1
EnableDescribeParam=1
EnableNcharSupport=0
EnableScrollableCursors=1
EnableStaticCursorsForLongData=1
EnableTimestampWithTimeZone=0
HostName= here the fqdn of the oracle db host
LocalTimeZoneOffset=
LockTimeOut=5
LogonID= here the username of oracle user
Password= user password
PortNumber=1521
ProcedureRetResults=1
SID=B
UseCurrentSchema=0

I put the OraSRC to connection parameters when creating the remote server in Sybase Central. Remote server was sucessfully created. Then i tried to create a proxy table, peek the db name and choose table name from list and go on.

[reimer_pods]

It would be helpfull if you specify more details: which connection parameters and which driver are you using to connect with the Oracle db?

[graeme_perrow]

If you need to add more details, please edit your question rather than add an answer. Answers should only be for actual answers to the question. I've done this for you here.

[Former Member]

Sybase Central is probably calling dbo.sp_remote_columns() which is failing for some strange reason. Try issuing the CREATE EXISTING TABLE statement directly in DBISQL and see if that works or gives you more details as to why the column information is not coming back.

[Former Member]

I tried CREATE EXISTING TABLE statement in DBISQL with column defition and without. The result is the same. No more information just the error message.

[VolkerBarth]

Does the following work when issued via DBISQL (assumption: SRV_ORA is the server name as specified in the CREATE SERVER statement):

FORWARD TO SRV_ORA;
SELECT * FROM <your native Oracle table schema and name>;
FORWARD TO;

(That's just a test whether the ASA user can access the remote table when the select is sent as a native command to the remote server.)

[Former Member]

Yes, it works.