========================================================================
Applies to:
Weblogic: 10.3.6 and later
========================================================================
Problem Summary:
Application requires a XA data source to be configured on weblogic for DB connection and they have provided default SYS(admin) user for data source creation.
Data Source configuration test is failing with ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
Error:
Connection test failed.ORA-28009: connection as SYS should be as SYSDBA or SYSOPER <br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)<br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)<br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)<br/>oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:689)<br/>oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:452)<br/>oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)<br/>oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)<br/>oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:384)<br/>oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:811)<br/>oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411)<br/>oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)<br/>oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)<br/>oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)<br/>oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)<br/>oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:404)<br/>oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:674)<br/>oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:267)<br/>oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:134)<br/>weblogic.jdbc.common.internal.DataSourceUtil.testConnection(DataSourceUtil.java:314)<br/>com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:734)<br/>...
========================================================================
Root Cause:
We can use SYS user only as a SYSDBA or SYSOPER. We can't use SYS as normal user.
SYS is the super user in Oracle database which is needed for many critical activity and we shouldn't use SYS schema for Data Source.
The error is generated becuase of the parameter O7_DICTIONARY_ACCESSIBILITY is set to FALSE. O7_DICTIONARY_ACCESSIBILITY controls restrictions on SYSTEM privileges.The default setting of false ensures that system privileges that allow access to objects in "any schema" do not allow access to objects in the SYS schema.
SQL> show parameter O7_DICTIONARY_ACCESSIBILITY
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
O7_DICTIONARY_ACCESSIBILITY boolean FALSE
========================================================================
Resolution:
1. Login to DB and create user/schema specific to application with required privileges and use same for data source creation.
2. To create user use below commands,
create user user_name identified by password;
grant connect, resource to user_name identified by password;
Applies to:
Weblogic: 10.3.6 and later
========================================================================
Problem Summary:
Application requires a XA data source to be configured on weblogic for DB connection and they have provided default SYS(admin) user for data source creation.
Data Source configuration test is failing with ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
Error:
Connection test failed.ORA-28009: connection as SYS should be as SYSDBA or SYSOPER <br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)<br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)<br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)<br/>oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:689)<br/>oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:452)<br/>oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)<br/>oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)<br/>oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:384)<br/>oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:811)<br/>oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411)<br/>oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)<br/>oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)<br/>oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)<br/>oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)<br/>oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:404)<br/>oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:674)<br/>oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:267)<br/>oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:134)<br/>weblogic.jdbc.common.internal.DataSourceUtil.testConnection(DataSourceUtil.java:314)<br/>com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:734)<br/>...
========================================================================
Root Cause:
We can use SYS user only as a SYSDBA or SYSOPER. We can't use SYS as normal user.
SYS is the super user in Oracle database which is needed for many critical activity and we shouldn't use SYS schema for Data Source.
The error is generated becuase of the parameter O7_DICTIONARY_ACCESSIBILITY is set to FALSE. O7_DICTIONARY_ACCESSIBILITY controls restrictions on SYSTEM privileges.The default setting of false ensures that system privileges that allow access to objects in "any schema" do not allow access to objects in the SYS schema.
SQL> show parameter O7_DICTIONARY_ACCESSIBILITY
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
O7_DICTIONARY_ACCESSIBILITY boolean FALSE
========================================================================
Resolution:
1. Login to DB and create user/schema specific to application with required privileges and use same for data source creation.
2. To create user use below commands,
create user user_name identified by password;
grant connect, resource to user_name identified by password;
No comments:
Post a Comment