The Bentley Map version would be helpful .
So to test this, I guess you have 2 different Oracle users. One had the connect and select roles and the other has the connect, select, update, delete and insert roles,
If you are using the same TNS connection, but with different users, then I see no problem with this.
Some reasons for this error can be:
Since you do have Oracle spatial installed, are you trying to connect to the database via the Spatial Connection or through the regular database connection method ?? If through the Oralce Spatial method, then the tables need to be spatial tables, with the correct columns, indexes, etc to work correctly. This is explained in the Bentley Map docs.
HTH
Jerry
MicroStation version 8.11.5.17
Bentley Map version 8.11.5.49
Oracle client version 11.1.0
The test was done using the same Oracle user, with CONNECT, SELECT, UPDATE, DELETE, and INSERT privs. SInce the same "user" was able to connect read-only and not read/write to the same Oracle instance, it would (I think) resolve any issues with the TNS stuff (even though that's the error message that Bentley Map returns). There are multiple versions of the Oracle client installed on the PC, but I have specified the MS_ORACLE_HOME for the MAP workspace being used to ensure the appropriate Oracle client is being used. The Oracle user schema account is "empty" - i.e. there are no existing Oracle Spatial tables. There ARE Oracle spatial tables (SDO_GEOMETRY, and spatial indexes) in other schemas and access (SELECT) has been granted to the test user account. The connection being attempted is via the Interoperability dialog. not the "standard" MicroStation way requiring the MSCATALOG table. I am able to connect using "plain" MicroStation via an ODBC connection to the Oracle database in question. Interestingly, I am unable to connect in plain MicroStation using the "Oracle" tab of the "Connect to Database" dialog (again, using the same parameters used to successfully establish a read-only Oracle connectino in the Interoperability dialog).
Any other thoughts/ideas ?
Bruce
I'd check to ensure that the Oracle Database Server version is supported. The BMAP readme should outline this.
If you happen to be connecting on the server itself, using a 64 bit client, you may instead try connecting from a seperate machine using 32 bit drivers.