Skip to main content

Oracle E-Business Suite Schema Type

Oracle E-Business Suite Schema:

Type 1. Schemas that exist in every Oracle database - SYS, SYSTEM.
Type 2. A small set of critical core schemas used by shared components of Oracle E-Business Suite - APPLSYSPUB, APPLSYS, APPS, APPS_NE.
APPYSYSPUB schema:
  • It is public account, and has only Read-Only privileges on a few tables and views for signing on to Applications.
  • The password for this account can be seen from the OS in the environment variable or logical GWYUID.
  • It was pointless to change it before the security patch that allowed the APPLSYSPUB password to be encrypted.
  • Warning: The APPLSYSPUB password is unique in that it must be maintained as an uppercase password. This means that if you opt to change the APPLSYSPUB password in Oracle Database 11g, you must enter the new password in all uppercase to preserve system functionality.
  • Oracle recommend that the APPLSYSPUB password should be changed on all Release 12.x systems, using either AFPASSWD or FNDCPASS. AutoConfig should be run after changing the password, to synchronize all the application tier files.
Type 3. A large set of schemas provided by individual Oracle E-Business Suite products, ranging (using product short names) from ABM through to ZX.
4. A set of schemas that belong to optional database features or third party products.
These fall into three sub-categories:
 a. Schemas that are both used by and patched with Oracle EBS - CTXSYS.
 b. Schemas that are used by Oracle EBS but patched only with the database - MDSYS, ORDSYS.
Schemas that are not used by Oracle EBS - SCOTT.
All these types of schema are used during runtime operations of Oracle E-Business Suite.
The schemas of types 2, 3 and 4-1 above are accessed during initial installation and patching.
Note: None of the Oracle EBS schemas relate to a particular Oracle EBS user. The Oracle database schemas and passwords are used to connect to the database, while application usernames and passwords are used to access Oracle EBS.

Three passwords are especially significant in Oracle EBS schema usage, so should be chosen with particular care:

1. A password for APPLSYSPUB (also known as the GATEWAY user).
2. A password shared between APPLSYS, APPS, and APPS_NE.
3. A password for all of the product-specific base schemas (type 3).

Installation process automatically registers Oracle EBS ORACLE schemas.
Register an ORACLE schema with Oracle EBS, if you create a custom application using Oracle Application Object Library.
Refer Document 1577707.1, "Creating a Custom Application in Oracle E-Business Suite Release 12.2."
Add in custom initialization SQL code to be executed when a database session starts up or when it is re-initialized.
Code is executed by FND_GLOBAL.INITIALIZE and APPS_INITIALIZE immediately after initializing global variables, profiles, and the contents of client_info on session startup.
Using the profile option Initialization SQL Statement - Custom, you can add sitespecific initialization code, such as optimizer settings.
Oracle EBS allows the system administrator to assign individual Oracle EBS users to resource consumer groups.
In addition, concurrent programs and concurrent managers can be assigned to resource consumer groups.
Note: These resource consumer groups apply to CPU resources only.
Labels:

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

MySQL 5.7 Install | Configure MySQL | Configure MySQL Replication | Configure systemd for single instance

Install MySQL 5.7 Community Edition on Linux: #yum install mysql80-community-release-el7-1.noarch.rpm #yum install mysql-community-server #yum install perl-DBD-MySQL-4.023-6.el7.x86_64.rpm #yum install percona-release-0.1-4.noarch.rpm Increase no. of open files: Edit file /etc/security/limits.conf and includes as follows, which will increase no of open files for mysql user to 65535 from 1024 which is default. excute ulimit -a after sudo to mysql, if you are logged in exit and login again then and then only you will be able to see it. mysql              soft     nofile           65535 mysql             hard     nofile           65535 Ref.: https://dev.mysql.com/doc/refman/8.0/en/linux-installation-yum-repo.html https://jinyuwang.weebly.co...
1 comment
Read more

Create MySQL database with hyphen

Create MySQL database with hyphen: If you are trying to create MySQL database with hyphen " - " in the name such as test-db and get error  " your MySQL server version for the right syntax to use near '-db' at line" then you might be wondering how to get it done as your business require MySQL database name with hyphen " - "  Here is the fix, use escape character " ` " before and after database name such as `test-db` and you will be able to create database with hyphen. CREATE DATABASE `test-db`; 
Post a Comment
Read more