Previous | Next | Contents | Index | Navigation | Glossary | Library |
The installation process always registers your ORACLE username, so you need not register it unless you create a custom application using Oracle Application Object Library, or if you wish to associate an additional ORACLE username with Oracle Applications.
When you register and enable an ORACLE username, you submit a concurrent request to set up the necessary database privileges between your ORACLE username and the Oracle Application Object Library database tables.
If you register an ORACLE username as a "restricted" ORACLE username, you submit a concurrent request to set up read-only privileges to the Oracle Application Object Library tables. An "enabled" ORACLE username has all privileges to those tables. A "disabled" ORACLE username has no privileges to those tables.
If you do not register and enable your ORACLE username or if you disable a registered ORACLE username, your user cannot use Oracle Application Object Library features such as menus and flexfields.
You should not change the registration of any ORACLE usernames that the installation process registers, other than changing the passwords.
If you are registering a change to an existing ORACLE password, make the password change in the database immediately AFTER you register the password change in Oracle Applications. Until you register the password changes in Oracle Applications and implement them in the database, responsibilities using this ORACLE username cannot connect to the database.
Your password must follow the guidelines for creating passwords discussed in the Oracle 7 Server SQL Language Reference Manual. Remember that if you use non-character values in your password, you may need to use quotation marks around your password when changing it in the database.
Warning: If you are changing the password to the applsys ORACLE username, which contains the Oracle Application Object Library tables, you must not change the passwords to any other ORACLE usernames at the same time.
Attention: Until you have both registered the changes in Oracle Applications and then implemented them in the database, responsibilities using your ORACLE username cannot connect to the database.
Until you register the password changes in Oracle Applications and implement them in the database, responsibilities using this ORACLE username cannot connect to the database.
Warning: If you are changing the password to the applsys ORACLE username, which contains the Oracle Application Object Library tables), you must not change the passwords to any other ORACLE usernames at the same time.
The default value for this field is Enabled.
Overview of Oracle Applications Security
Oracle Applications Installation Manual for your operating system
Install Group
Enter the value of the installation group associated with your ORACLE username. Install group numbers should be consecutive whole numbers, where 1 represents the first set of books (or first set of product installations), 2 is the second set of books, 3 is the third set of books, and so on. Install group number 0 represents products that need only single installations.
Attention: Since the installation process does not affect ORACLE usernames (also known as "schemas") for custom applications, this value is for your reference only and is currently not used.
See: Oracle Applications Installation Manual for your operating system
Registering an ORACLE username
Previous | Next | Contents | Index | Navigation | Glossary | Library |