This content has been marked as final. Show 10 replies
Why are you making so complex to RPD to access tables, it always good to go with a user who have access to both schemas.
Try to go for more or less as APPS user as in ebs.
If you still wants to go with your own approach then try to see possible options using Connection Pool->Connection Pool Scripts tab.
If helps mark
As srini suggested why you are making RPD more complex,Just create a one schema and import all the tables what all u need in that and give that schema credentials in one connectiion pool.
Mark as correct,if it is helpful.
Thanks for your reply.
I should not create single schema and have all the tables from two schema.
It always good to go with a user who have access to both schemas. Sorry I did not get any clue. Please elaborate.
Ex: I have scott schema and sh schema how can I have both schemas in a single user?
Then use system or sys or sysdba user instead of mentioned users.
Have fun :)
Edited by: Srini VEERAVALLI on Feb 13, 2013 12:43 AM
Ya that will be the last option
No other way we can do it?
Create another super user as system or sys and use that.
Just do it, looks like you spent more than 24hrs for this!!
Appreciate if you mark
My main motive was to join the tables from two schema's that I did through Manage-> Joins.. So I got it now
Thanks for your suggestions all the time.
Appreciate it :)
Appreciate if you mark and close the post.1 person found this helpful
If need send me email for issues.
I thought that the solution for this problem is we have one option is there in connection pool i.e "Required fully qualified table names" . we have to check this option.Then we can onnect to the multiple schemas using a single connection pool.
I dont think fully qualified names will not work here please correct if I am wrong. Rather shared logon guess should work but did not in my case.
The fully qualified names are based on the physical object names in the repository. If you are querying the same tables from which the physical layer metadata was imported, you can safely check the option. If you have migrated your repository from one physical database to another physical database that has different database and schema names, the fully qualified names would be invalid in the newly migrated database. In this case, if you do not select this option, the queries will succeed against the new database objects.
For some data sources, fully qualified names might be safer because they guarantee that the queries are directed to the desired tables in the desired database. For example, if the RDBMS supports a master database concept, a query against a table named foo first looks for that table in the master database, and then looks for it in the specified database. If the table named foo exists in the master database, that table is queried, not the table named foo in the specified database.