APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Configuring Workspace on runtime environment

ct.rodriguezaleApr 10 2019 — edited Apr 11 2019

I need to automate the installation of APEX 5.1 using only the runtime environment to configure the application.

I made some scripts that install and configure the application using the ADMIN user as the INTERNAL administrator, but when I create my Workspace, this is created without a user manager and I can not log in. How can I create the work area with an administrator or create a user and convert it into Administrator from my WS?

This is my code.. It is the same code that indicates the official documentation

ALTER SESSION SET CURRENT_SCHEMA = APEX_050100;
BEGIN
    APEX_INSTANCE_ADMIN.ADD_WORKSPACE (
        p_workspace_id => 100000,
        p_workspace => 'MY_WKS',
        p_primary_schema => 'WS',
        p_additional_schemas => 'HF' );
END;
/

dvohra21

It is documented.

"The Oracle.connect() method defaults to a false setting of the auto-commit flag. However, it also has signatures to set it explicitly. In the Oracle JDBC implementation, the auto-commit flag defaults to true."

Key Programming Considerations

kdario

Well, this is documentation for sqlj and first sentence just confirms what I said(that auto-commit by default should be false)

Just to clarify my original post:

When you retrieve jdbc connection in adf application(for example, in app module impl class), that connection already has autocommit=false (because framework will set this property)

Difference between adf 11.x and 12.x is in setting db proxy user (by using conn.openProxySession() ) :

In 11.x (which uses ojdbc6 driver) invocation of openProxySession() method will preserve autocommit=false

In 12.x (which uses ojdbc7 driver) invocation of openProxySession() method will reset autocommit to true (and adf app will not work correctly with this setting)

Dario

dvohra21

ojdbc7.jar is based on JDBC 4.1 and JDBC 4.1 still sets auto-commit to true by default.

"The default is for auto-commit mode to be enabled when the Connection object is

created."

http://download.oracle.com/otn-pub/jcp/jdbc-4_1-mrel-spec/jdbc4.1-fr-spec.pdf?AuthParam=1404073866_5e28356fa3b11ea367d6b…

Could auto commit be false for the PROXYTYPE_USER_NAME specified?

OracleConnection (Oracle Database JDBC Java API Reference)

dvohra21

CONNECTION_PROPERTY_AUTOCOMMIT_DEFAULT is true in both 11g and 12c.

http://docs.oracle.com/cd/E18283_01/appdev.112/e13995/constant-values.html#oracle_jdbc_OracleConnection_CONNECTION_PROPERTY_AUTOCOMMIT_DEFAULT

http://docs.oracle.com/cd/E16655_01/appdev.121/e17663/constant-values.html#oracle_jdbc_OracleConnection_CONNECTION_PROPERTY_AUTOCOMMIT_DEFAULT