After I published the packaged to IIS7,  the exception occurred below.

Connection is already part of a local or a distributed transaction

referring to the article  the problem is resolved.

https://forums.oracle.com/forums/thread.jspa?threadID=2263095

or  http://forums.devart.com/viewtopic.php?t=20844

1. Switch to the File View of your LightSwitch Solution.
2. Select the "Server" Project and add a reference to "System.Transactions".
3. Open the Code for your Data Source (Right-Click on your Data Source --> Show/View Code)
4. Declare a using for System.Transactions:
using System.Transactions;
5. Enter following code snippet:

      private TransactionScope _tscope;

        partial void SaveChanges_Executing()
        {
            _tscope = new TransactionScope(TransactionScopeOption.Required,
                new TransactionOptions
                {
                    IsolationLevel = System.Transactions.IsolationLevel.ReadCommitted
                });
        }

        partial void SaveChanges_Executed()
        {
            _tscope.Complete();
            _tscope.Dispose();
        }

if user forms authentication is checked,  we need to input MS SQL connection when we deploy a package.

=>not possible to deploy with Oracle DB server

so check : Do not enable authentication, then we can deploy a package without MS SQL connection information.

Create a package on disk, select the directory the package should be created.

click publish ! We can see the package in the directory.

move the files including the package to a directory in Server computer.

1. ODAC for Oracle should be installed in server environment.

2. should install deploy 3.0 through web platform installer 4.5

deploy 3.0 download link :  http://www.iis.net/downloads/microsoft/web-deploy

3. Deploy the package with deploy : load the application

When  I don't use bind variance , the response time is acceptable.

query.Where(e => e.CUST_LOT == "AAA");

But  with a bind variance , obviously it spends too much time, which occurred time out error.

string Lotid = "AAA" ;

query.Where(e => e.CUST_LOT == Lotid );

I look into the query with Query tool, the plan is OK.

But When I check the session, there is a direct path read problem(Full path read).

I found a solution in the article below. use EntityFunctions.AsNonUnicode!

string Lotid = "AAA" ;

query.Where(e => e.CUST_LOT == EntityFunctions.AsNonUnicode(Lotid));

https://forums.oracle.com/forums/thread.jspa?messageID=10723648

[ the cause of this problem]

Because .NET string is Unicode, by default NVARCHAR2 is used in parameter binding for a string variable.
In WHERE clause, when one side is N type and the other side is not N type, data conversion occurs.
That may cause full table scan instead of using index.

EntityFunctions.AsNonUnicode() tells ODP.NET to treat a string as non Unicode. In this case, VARCHAR2
is used for the parameter binding. Because both sides are not N type, no more data conversion and
no more full table scan.