Hi Hemant,

Thanks for your earlier reply. 

I will not lock APPS, APPLSYS and APPLSYSPUB accounts as these accounts are
needed for the HR patches. 

In my company, we do have in-house applications which use client-server
forms/reports to access (read-only privilege) the HR tables. We created user
accounts for these applications. The last time when I applied HR patches, I
encountered deadlock despite shutting down the concurrent manager, forms
server, report server , apache server, web db 2.5 server etc.  I suspected
some of my users were accessing the HR tables via sqlplus/client-server
forms/reports, thereby causing deadlocks.

This time round, I will lock the user accounts which use client-server
forms/reports to access (read-only privilege) the HR tables. 

Hope it helps. 

Regds,
Catherine
                -----Original Message-----
                From:   [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
                Sent:   Wednesday, February 20, 2002 4:44 PM
                To:     CHAN Chor Ling Catherine (CSC)
                Cc:     [EMAIL PROTECTED]
                Subject:        RE: Disable certain users from login to
database while applying H


                Catherine

                Which database accounts will you lock ?  You can't lock
APPS, APPLSYS and
                APPLSYSPUB
                as APPLSYSPUB and APPS will be used by all users and APPS
and APPLSYS will
                be used by the patch.

                Hemant K Chitale
                Principal DBA
                Chartered Semiconductor Manufacturing Ltd


                "CHAN Chor Ling Catherine (CSC)" <[EMAIL PROTECTED]>
19/02/2002 05:23 PM
                Sent by: [EMAIL PROTECTED]




                Hi Gurus,

                Thanks for replying to my qn.

                "Startup Database in Restricted mode" will not work (for
more details, pls
                refer to the email below).

                The following solutions :
                1.  Database ON LOGON Trigger => don't know whether it will
work
                2.  Lock Database Account => I am going to use this
solution.
                3.  Change Database Account Password => I believe it will
work

                In our Oracle HR, we also support oracle client-server
forms/reports, so
                I've to disable their accounts so that they do not access
the HR database
                using sqlplus/forms/reports while I am applying patches.


                Regds,
                Catherine
                                     -----Original Message-----
                                     From:
[EMAIL PROTECTED]
                [mailto:[EMAIL PROTECTED]]
                                     Sent:          Tuesday, February 19,
2002 2:13 PM
                                     To:       Multiple recipients of list
ORACLE-L
                                     Subject:       Re: Disable certain
users from login to
                database while applying Human


                                     As you are talking of Oracle Apps, NONE
of the
                suggested
                solutions :
                                     1.  Database ON LOGON Trigger
                                     2.  Lock Database Account
                                     3.  Change Database Account Password
                                     4.  Startup Database in Restricted mode
                                     would work.

                                     The users connect to the Database in
the APPS schema
                -- this
                is the
                                     "universal"
                                     schema that Oracle Apps uses.  The
Patch requires APPS
                so
                Restricted
                                     doesn't
                                     help (unless you grant Restricted to
APPS in which
                case all
                the users can
                                     logon).
                                     Ditto about locking, changing password
or writing a
                trigger
                on the APPS
                                     schema.

                                     What you can do are :
                                     1. Shutdown the Apache server for the
Self-Service
                Modules
                                     2. Shutdown the Forms server for the
Forms Module
                                     3. Shutdown the Concurrent Managers.

                                     All of the above would affect ALL
users.

                                     Alternatively, login to the Application
as the System
                Administrator user
                                     and
                                     change the Application User Passwords
for the users
                whom you
                want disabled.
                                     Change the passwords back to a default
(WELCOME)
                later.

                                     However, what you SHOULD do, per Oracle
Support, is 1.
                Shutdown 2. Shutdown
                                     3. Shutdown
                                     as I have listed above.
                                     If you are familiar with Oracle
Applications Patching
                and
                are comfortable
                                     with reading
                                     the Patch drivers, you can figure out
what database
                objects
                are being
                                     modified/updated/created
                                     and what Forms/Reports/HTML etc files
are being
                modified/created by the
                                     patch.
                                     Then you can take an intelligent
decision .... should
                you
                allow users to
                                     logon when
                                     applying the patch ?

                                     Hemant K Chitale
                                     Principal DBA
                                     Chartered Semiconductor Manufacturing
Ltd


                                     "CHAN Chor Ling Catherine (CSC)"
<[EMAIL PROTECTED]>
                18/02/2002 03:28 PM
                                     Sent by: [EMAIL PROTECTED]

                                     Please respond to ORACLE-L


                                                  To: Multiple recipients of
list ORACLE-L
                <[EMAIL PROTECTED]>
                                                  cc: (bcc: CHITALE Hemant
                Krishnarao/IT/CHRT/ST
                Group)
                                                  Subject: Disable certain
users from login
                to
                database while applying
                                                  Human












                                     Hi Gurus,

                                     I need to disable certain users from
login to database
                while
                I apply the
                                     Human Resources Patches for our Oracle
HR 11i
                Applications.
                                     Which is the best way to do it ? Should
I write
                on-logon
                trigger to disable
                                     or should I take away their privileges
to logon to
                report/forms/sqlplus ?
                                     What about the rest of the DBA
Applications
                administrator ?
                What do U guys
                                     do to solve the dead-lock problem (If
my users access
                the HR
                tables while I
                                     apply the patches, I will encounter
dead-lock problem)
                ?

                                     Please advise. Thanks.

                                     Regds,
                                     New Bee
                                     --
                                     Please see the official ORACLE-L FAQ:
                http://www.orafaq.com
                                     --
                                     Author: CHAN Chor Ling Catherine (CSC)
                                       INET: [EMAIL PROTECTED]

                                     Fat City Network Services    -- (858)
538-5051  FAX:
                (858)
                538-5051
                                     San Diego, California        -- Public
Internet access
                /
                Mailing Lists

        
--------------------------------------------------------------------
                                     To REMOVE yourself from this mailing
list, send an
                E-Mail
                message
                                     to: [EMAIL PROTECTED] (note EXACT
spelling of
                'ListGuru')
                and in
                                     the message BODY, include a line
containing: UNSUB
                ORACLE-L
                                     (or the name of mailing list you want
to be removed
                from).
                You may
                                     also send the HELP command for other
information (like
                subscribing).





                                     --
                                     Please see the official ORACLE-L FAQ:
                http://www.orafaq.com
                                     --
                                     Author:
                                       INET: [EMAIL PROTECTED]

                                     Fat City Network Services    -- (858)
538-5051  FAX:
                (858)
                538-5051
                                     San Diego, California        -- Public
Internet access
                /
                Mailing Lists

        
--------------------------------------------------------------------
                                     To REMOVE yourself from this mailing
list, send an
                E-Mail
                message
                                     to: [EMAIL PROTECTED] (note EXACT
spelling of
                'ListGuru')
                and in
                                     the message BODY, include a line
containing: UNSUB
                ORACLE-L
                                     (or the name of mailing list you want
to be removed
                from).
                You may
                                     also send the HELP command for other
information (like
                subscribing).
                --
                Please see the official ORACLE-L FAQ: http://www.orafaq.com
                --
                Author: CHAN Chor Ling Catherine (CSC)
                  INET: [EMAIL PROTECTED]

                Fat City Network Services    -- (858) 538-5051  FAX: (858)
538-5051
                San Diego, California        -- Public Internet access /
Mailing Lists
        
--------------------------------------------------------------------
                To REMOVE yourself from this mailing list, send an E-Mail
message
                to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru')
and in
                the message BODY, include a line containing: UNSUB ORACLE-L
                (or the name of mailing list you want to be removed from).
You may
                also send the HELP command for other information (like
subscribing).



                
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: CHAN Chor Ling Catherine (CSC)
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to