As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Well, what can I say? If you want to use Oracle as if it were MSSQL then I'd advise to port the Oracle db to MSSQL. You just simply can't compare the two with respect to how to work with them. They are two very different database engiens, and that diference is reflected in the way you have to work with them. If you stick to using master files then you can still simply say TABLE FILE xxx, the connection info is stored in the access file. But if you go native, well then you have to abide by the rules that govern that specific db engine.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
James, You are connecting to Oracle with one user and running a query against another user's table. Oracle does not know which user's table "xxxx" you want to query.
There are at least two ways to do this: 1) Log into Oracle as the dbwork user.
2) Use synonyms on each object so you don't need to use the explicit "owner.object" reference. (Oracle does not have a default setting for this. There are public synonyms that apply for all users, but you still need to create one for every object/table.) "Create synonym xxxx for dbwork.xxxx;" Run this while logged in as the user you will be connecting with, not while logged in as dbwork.
3) I would suggest that you not connect as system. This is a DBA user with full permissions to the database. Depending on your data security concerns, you may not want to connect as dbwork either. We usually use another proxy ID just for reporting connections. This user will need the grants for read access and any synonyms that you want.