Moving from oracle express to a production server

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
Posts: 2
Joined: Fri 10 Apr 2009 16:59

Moving from oracle express to a production server

Post by Arthurdent510 » Tue 21 Apr 2009 18:46

I have my app working against a local copy of oracle express just fine, but I need to deploy my webapp to the web farm and hit the production oracle database. The table structure is the same, but I keep getting an error saying that the table or view does not exist. Looking through the context file, I noticed that it listed all my tables as "SYSTEM.table name". I updated those to be (and forgive me, I'm new to oracle so I may have the wrong term here) my database name.table name, so now it looks like "NAS.table name". The other thing I wasn't sure about was the linq mapping name. Previously it was set as "SYSTEM", and I wasn't sure what that needs to be changed to... Thanks for the help!

Devart Team
Posts: 8033
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Wed 22 Apr 2009 07:20

The schema name precedes the object name (e.g., the table name) in Oracle database. The schema name is an account name that is used when connecting and working with your database. When you were generating the context file on your local database you used the SYSTEM account name. Probably, you have created a schema with a different account at your production server. So please replace the SYSTEM account name with your current account name that you are using to connect to your database at the production server. As an alternative, you can remove the schema name that precedes the database object name from the context file without pointing your current schema name (the schema name will be set implicitly from the connection string).

Post Reply