Patch activity

During patch applying using adpatch utility why it is not asking patch driver u11737539.drv?
[prod1@UAT1 appshome]$ cd 11737539/
[prod1@UAT1 11737539]$ adpatch
                     Copyright (c) 2002 Oracle Corporation
                        Redwood Shores, California, USA
                         Oracle Applications AutoPatch
                                 Version 12.0.0
NOTE: You may not use this utility for custom development
      unless you have written permission from Oracle Corporation.
Attention: AutoPatch no longer checks for unapplied pre-requisite patches.
You must use OAM Patch Wizard for this feature. Alternatively, you can
review the README for pre-requisite information.
Your default directory is '/appshome/PROD/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?
AutoPatch records your AutoPatch session in a text file
you specify.  Enter your AutoPatch log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adpatch.log] : 11737539c.log
Backing up restart files, if any......Done.
Your previous AutoPatch session did not run to completion.
Do you wish to continue with your previous AutoPatch session [Yes] ?
You are about to apply a patch to the installation of Oracle Applications
in your ORACLE database 'UAT'
using ORACLE executables in '/appshome/PROD/apps/tech_st/10.1.2'.
Is this the correct database [Yes] ?
Already asked for the ORACLE username and password
of Application Object Library.
(The given username/password was: APPLSYS/*****)
The status of various features in this run of AutoPatch is:
                                           <-Feature version in->
Feature                          Active?   APPLTOP    Data model    Flags
CHECKFILE                        Yes       1          1             Y N N Y N Y
PREREQ                           Yes       6          6             Y N N Y N Y
CONCURRENT_SESSIONS              No        2          2             Y Y N Y Y N
PATCH_TIMING                     Yes       2          2             Y N N Y N Y
PATCH_HIST_IN_DB                 Yes       6          6             Y N N Y N Y
SCHEMA_SWAP                      Yes       1          1             Y N N Y Y Y
JAVA_WORKER                      Yes       1          1             Y N N Y N Y
CODELEVEL                        Yes       1          1             Y N N Y N Y
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
AutoPatch warning:
Product Data File
/appshome/PROD/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product "zfa".
This product is registered in the database but the
above file does not exist in APPL_TOP.  The product
will be ignored without error.
AutoPatch warning:
Product Data File
/appshome/PROD/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product "zsa".
This product is registered in the database but the
above file does not exist in APPL_TOP.  The product
will be ignored without error.
AutoPatch warning:
Product Data File
/appshome/PROD/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product "jts".
This product is registered in the database but the
above file does not exist in APPL_TOP.  The product
will be ignored without error.
Currently, the following language is installed:
Code   Language                                Status
US     American English                        Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
AD code level : [A.4]
AutoPatch error:
You must be in Maintenance Mode to apply patches.
You can use the AD Administration Utility to set Maintenance Mode.
You should check the file
/appshome/PROD/apps/apps_st/appl/admin/UAT/log/11737539c.log
for errors.
[prod1@UAT1 11737539]$

You must be in Maintenance Mode to apply patches.You need to enable via adadmin before applying the patch or apply the patch using options=hotpatch.
http://forums.oracle.com/forums/search.jspa?threadID=&q=Maintenance+AND+Mode&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
http://forums.oracle.com/forums/search.jspa?threadID=&q=hotpatch&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Please search the forum before posting such questions -- http://forums.oracle.com/forums/search.jspa?threadID=&q=%22You+must+be+in+Maintenance+Mode+to+apply+patches%22&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Similar Messages

  • Need to place the SCOM agents in Maintenance Mode automatically during Patching activity

    Hi,
    I have a requirement to place the SCOM agent servers in MM automatically during shceduled patching every month. I have gone through few blogs but could not find an apt solution for SCOM 2012 R2 environment.
    I think the process should be..
     1. Create a management pack to monitor all servers for event 1074 (or/and 22), which gets triggere during the patching
     2. Write some powershell to put a machine into maintenance mode.
     3. Trigger the powershell script to run when needed.
    Any suggestions please?
    Thanks

    Where doing this in our environment. We have a SCOM monitor looking for Reboot events (ID 1074) where the event contains Shutdown Type: Reboot. the monitor creates an Informational alert which Orchestrator picks up and then sets the machine in MM for 30
    minutes. So its any time the machine is intentionally rebooted. You can have it look for CcmExec in the Event description (assuming you're using SCCM) if you only want it to work when being patched. 
    - Slow is smooth and smooth is fast.

  • Step for Active/Passive RAC Patching (CPU Patch )

    Hi
    I know how to patch active /active configuration patching done in RAC.
    I need to patch (CPU) for acitve/passive , how to i proceed ,is it the same ? i.e i can open passive node any how and the patch one by one .
    Please suggest the step

    Hi,
    1) Will the 9.2.0.8 upgrade patching modified the SYSTEM tablespace and corresponding SYSTEM datafilesYes it will modify the SYSTEM tablespace and corresponding datafiles.
    If I upgrade my active primary database first, will I be still able to upgrade the passive primary database without error laterYes u can upgrade passive primary database without error later
    I shall be patching the database after failover the passive DB to become activecan u elaborate this further.
    I suggest u to create a formal service request at MyoracoleSupport
    Regards,
    X A H E E R

  • Best practice to secure database during patching/upgrade-Vault disabled

    I have a highly confidential system and to protect the data in the DB, I intend to use Oracle Vault. In my company, we have centralized services and therefore, the oracle Unix owner and sysdba are owned by this group, not the application dba that "knows" the system (me).
    The problem I have is what would be the best way to protect my data from the sysdba user during the window that Vault is disabled?
    I thougth maybe I could un-mount and file protect the tablespace from the Unix oracle user during the upgrade process, but the tablespace could be outdated when I remount it after the patch. I am not sure how I might patch it seperatley. I am thinking I might export and drop the schema during the patching, then load it back in when vault is enabled again. This will work for a year or so, but I envision the databases getting too large to do this efficiently.
    Does anyone have any thoughts on how I might protect the data in this scenario?
    Edited by: user4714217 on Oct 20, 2008 11:06 AM for clarity

    Hi,
    I did not understood your question properly, but the thing which I understood is like you do not want any other user to access the database when your security vault is disabled.
    At that time you can
    1) Start the database in restrict mode (only a sysdba can do it).
    2) Change the password/lock the user till the time your patching activity is going (any user with dba role can do it, so might be not so useful)
    Regards
    Anurag Tibrewal

  • How to backout a Recommended Patch cluster deployment in Solstice disksuite

    Hello Admin's,
    I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
    concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
    1) Will shutdown the applications and the databases on the server:
    2) Will capture the output of the following commands :
    df -k
    ifconfig -a
    contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
    metastat -p
    netstat -rn
    prtvtoc /dev/rdsk/c1t0d0s0
    prtvtoc /dev/rdsk/c1t1d0s0
    3) We bring the system to the ok prompt
    4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
    =======================================================================================
    user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
    /dev/dsk
    Filesystem kbytes used avail capacity Mounted on
    /dev/md/dsk/d10 8258597 3435895 4740117 43% /
    lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
    lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
    bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
    d10: Mirror
    Submirror 0: d11
    State: Okay
    Submirror 1: d12
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 16779312 blocks
    d11: Submirror of d10
    State: Okay
    Size: 16779312 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s0 0 No Okay
    d12: Submirror of d10
    State: Okay
    Size: 16779312 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s0 0 No Okay
    user1@myserver>
    ===================================================================================
    ok nvalias backup_root <disk path>
    Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
    ok printenv boot-device
    boot-device= disk net
    ok setenv boot-device disk backup_root net
    boot-device= disk backup_root net
    In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
    ok boot backup_root
    user1@myserver>metadb -i
    flags first blk block count
    a m p luo 16 1034 /dev/dsk/c1t0d0s7
    a p luo 1050 1034 /dev/dsk/c1t0d0s7
    a p luo 2084 1034 /dev/dsk/c1t0d0s7
    a p luo 16 1034 /dev/dsk/c1t1d0s7
    a p luo 1050 1034 /dev/dsk/c1t1d0s7
    a p luo 2084 1034 /dev/dsk/c1t1d0s7
    o - replica active prior to last mddb configuration change
    u - replica is up to date
    l - locator for this replica was read successfully
    c - replica's location was in /etc/lvm/mddb.cf
    p - replica's location was patched in kernel
    m - replica is master, this is replica selected as input
    W - replica has device write errors
    a - replica is active, commits are occurring to this replica
    M - replica had problem with master blocks
    D - replica had problem with data blocks
    F - replica had format problems
    S - replica is too small to hold current data base
    R - replica had device read errors
    user1@myserver>df -k
    Filesystem kbytes used avail capacity Mounted on
    /dev/md/dsk/d10 8258597 3435896 4740116 43% /
    /dev/md/dsk/d40 2053605 929873 1062124 47% /usr
    /proc 0 0 0 0% /proc
    fd 0 0 0 0% /dev/fd
    mnttab 0 0 0 0% /etc/mnttab
    /dev/md/dsk/d30 2053605 937231 1054766 48% /var
    swap 2606008 24 2605984 1% /var/run
    swap 6102504 3496520 2605984 58% /tmp
    /dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
    /dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
    user1@myserver>metastat d40
    d40: Mirror
    Submirror 0: d41
    State: Okay
    Submirror 1: d42
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194828 blocks
    d41: Submirror of d40
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s4 0 No Okay
    d42: Submirror of d40
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s4 0 No Okay
    user1@myserver>metastat d30
    d30: Mirror
    Submirror 0: d31
    State: Okay
    Submirror 1: d32
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194828 blocks
    d31: Submirror of d30
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s3 0 No Okay
    d32: Submirror of d30
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s3 0 No Okay
    user1@myserver>metastat d50
    d50: Mirror
    Submirror 0: d51
    State: Okay
    Submirror 1: d52
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 10487070 blocks
    d51: Submirror of d50
    State: Okay
    Size: 10487070 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s5 0 No Okay
    d52: Submirror of d50
    State: Okay
    Size: 10487070 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s5 0 No Okay
    user1@myserver>metastat -p
    d10 -m d11 d12 1
    d11 1 1 c1t0d0s0
    d12 1 1 c1t1d0s0
    d20 -m d21 d22 1
    d21 1 1 c1t0d0s1
    d22 1 1 c1t1d0s1
    d30 -m d31 d32 1
    d31 1 1 c1t0d0s3
    d32 1 1 c1t1d0s3
    d40 -m d41 d42 1
    d41 1 1 c1t0d0s4
    d42 1 1 c1t1d0s4
    d50 -m d51 d52 1
    d51 1 1 c1t0d0s5
    d52 1 1 c1t1d0s5
    d60 -m d61 d62 1
    d61 1 1 c1t0d0s6
    d62 1 1 c1t1d0s6
    user1@myserver>pkginfo -l SUNWmdg
    PKGINST: SUNWmdg
    NAME: Solstice DiskSuite Tool
    CATEGORY: system
    ARCH: sparc
    VERSION: 4.2.1,REV=1999.11.04.18.29
    BASEDIR: /
    VENDOR: Sun Microsystems, Inc.
    DESC: Solstice DiskSuite Tool
    PSTAMP: 11/04/99-18:32:06
    INSTDATE: Apr 16 2004 11:10
    VSTOCK: 258-6252-11
    HOTLINE: Please contact your local service provider
    STATUS: completely installed
    FILES: 150 installed pathnames
    6 shared pathnames
    19 directories
    1 executables
    7327 blocks used (approx)
    user1@myserver>
    =======================================================================================
    5) After successfully testing the above we will bring the system to the single user mode
    # reboot -- -s
    6) Detach the following sub-mirrors :
    # metadetach -f d10 d12
    #metadetach -f d30 d32
    #metadetach -f d40 d42
    #metadetach -f d50 d52
    # metastat =====> (to check if the submirror�s are successfully detached)
    7) Applying patch on the server
    After patch installation is complete will be rebooting the server to single user mode
    # reboot -- -s
    confirming if patch installation was successful (uname �a) .
    8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
    Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
    # metattach d12 d10
    # metattach d30 d32
    #metattach d40 d42
    # metattach d50 d52
    # metastat d10 =====> (to check the submirror is successfully reattached)
    user1@myserver>uname -a ; cat /etc/release ; date
    SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
    Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
    Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
    Assembled 12 December 2002
    Mon Apr 14 17:10:09 BST 2008
    -----------------------------------------------------------------------------------------------------------------------------

    Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
    I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
    They try to generate those every 6 months, but the schedule often slips.
    The two most recent were sol10 11/06 and sol10 8/07.

  • How to apply 3 RPC (Recommended Patch Collection)

    Dear,
    I am fresher in the field of Oracle EBS R12. As per recurrence of the create accounting issues on PAYABLE module: the Metalink representative recommends to apply the following patch collection:
    We strongly recommends to apply the following 3 RPC (Recommended Patch Collection):
    Patch 13563472:R12.AP.B
    Patch 13563481:R12.AP.B
    Patch 13563489:R12.AP.B
    So I want to know how to apply these patches, one by one or collectively. I shall be very thankful if you share all steps to apply these patches with me.
    Stay blessed.
    Best Regards,
    Ahmed.

    I have corrected some of you steps and made below:-
    1. Stop applicaiton services.
    2. Stop Database Services or bring database in hot backup mode.
    3. Take backup(both apps and DB).
    4) Start Database or bring database out of backup mode.
    6) Bring application in maintenance mode.
    7) Extract the patch into a folder.
    8)Follow readme document of the patch.
    9) use adpatch utility to apply the patch.
    10) disable maintenance mode
    11) start application services and test the application functionality.
    I need your help at step # 5. In this scenario, will i take cold backup of data files only or whole backup of DB Tier & Application Tier. Whole backup of DB and apps Tier.
    And Please also tell me if i want to reverse the patch operation, what do i need ? only restore the data files. Please tell me step by step. I shall be very thank full to you. Your posts are always helpful for us.restore complete db and apps tier.
    If you have taken cold backup prior to patching activity then to undo a patch use below steps:-
    1)Stop apps and db tier.
    2)Clear all apps and db mount points.
    3) Restore backup taken prior to patching activity.
    4) Start database and listener.
    5) Start application.
    If you have taken hot backup then after step 3 you need to recover the database and rest all steps remain same.
    Also check below metalink note:-
    How to uninstall backout rollback an Oracle Applications 11i or R12 Patch [ID 343987.1]
    Thanks,
    JD
    Thanks,
    JD

  • Pfile missing after vtm patch

    Hi,
    we have applied vtm patch for the database, changing the o_h from 11.2.02_Q311 to 11.2.0.2_Q112 (311--3rd quarter 2011, 112-- 1st quarter 2012), the patch went fine and the database was up and running. The pfile was located in different folder and we use to create the softlinks for accessing the pfile from o_h/dbs.
    Now my teammates reported that the pfile is not there for this database and the database is up and running. I'm not in office now, so I cant work on my desktop. Is there any way to create pfile from the running database. the database which was started after vtm patch is running now. but I cant find the pfile. so I wanted to create it.
    1) we are not using SP file, we are using only pfile.
    2) the softlink in the new o_h is still there.
    3) is there any bug that causes this issue after vtm patch activity?
    Thanks and Regards
    Venkata Sudheer

    Good to hear that you got it solved.
    Furthermore... you also can use the alertlog file to retreive all non default initialisation parameters of your instance and recreate the pfile from it (regardless Oracle version)
    Only, and very handy, the 'create pfile from memory' is only available from 11g.
    Regards,
    Thierry

  • Applying RPM while running patch

    Hi
    we are using oracle 12.1.1 on OEL 5.4
    I want to enable telnet service i need to aaply rpm but other side patch is running and it is taking time.
    my question here is it possible to apply rpm while running NLS patch activity?
    Thanks
    With Regards
    OH

    Hi OH;
    I want to enable telnet service i need to aaply rpm but other side patch is running and it is taking time.
    my question here is it possible to apply rpm while running NLS patch activity?I belive yes you can, rpm installation is not related with patching activity
    Regard
    Helios

  • Patch installation does not end

    Hi All,
    I was succesful in installing a BI_CONT 703 add-on on Solution Manager 4.0 . I was updating the patches to patchlevel 2. The Process is still running since 3 hours and is stuck in Main import finished with returncode 4. It is not giving any error or not even finishing the update. Please advice what should i do.
    Any help will be appreciated.
    Thanks,
    Fahad

    Is there any activity in SM50 related to this patch activity?
    If not,go to se38 and run RDDIMPDP,RDDNEWPP and RDDPUTPP .
    and check in SM50 again.see the slog,plog in /usr/sap/trans/log directory,you will get some idea abt whats going on.

  • Invoices Issue After applying patches of 11i Extended Support

    Platform: Windows 2003 R2 32-bit
    EBS: 11.5.10.2 (with 11i Extended Support Patches)
    DB: 10.2.0.4
    After completing the 11i Extended Support Patching activity we are receiving a complain from users' side that:
    while user run autoinvoice program, auto invoice validation report shows following error
    Please define all periods in which revenue is to be recognized
    I have also check period in GL as well as receivable period is open status.

    1.
    Metalink Note:550572.1 says:
    Specifically, the parameter btree_bitmap_plans should be set to False
    And parameter is alreadt set as per note.
    2.
    Metalink Note:369437.1 says:
    FYI: One-off Patch 4587470 on top of 11.5.AR.O is available
    Which contains following file version:
    ar patch/115/sql ARTECMMB.pls 115.67.15104.2
    and we are already on version
    ar patch/115/sql ARTECMMB.pls 115.67.15104.8
    above AR.O.

  • Patching on PRD system and thereafter moving the logs to DR ?

    Patching on PRD system and thereafter moving the logs to DR, will the patches take effect in DR ?
    We have patched our PRD system to the latest APPL patch levels, we have a DR system in place, the link for which was disabled before we started our patching process. The DR system was successfully patched before taking up the activity on PRD.
    The link between the PRD and DR is still not restored.
    Now, that our PRD system is on the latest patch levels, my idea is restoring a full offline database backup of PRD on the DR system should make the DR system exactly identical to the PRD and the link between the two restored to allow for dynamic syncing thereafter.
    Is my above view correct ?
    Moreover, from my understanding, Patches are a bunch of SAP notes, SAP notes in-turn are basically code corrections for some objects, which ultimately means some entries are either written or deleted from database tables. My colleagues are of the view that instead of patching the DR server separately we could have actually restored the link and transferred the logs to the DR and the patches should have taken effect in the DR SERVER, is this alright ?
    From my past experience I am aware that once you restore an offline database backup onto any system, the patch level in the target system would become similar to the source system(the system whose offline backup is actually being restored).
    Thereby request the experts on the forum to give their views on the above.
    Many Thanks in advance

    when we take up any patching activity, can we just do it on the PRD and then move on the logs to the DR and the DR should also be on the same patch levels as PRD. ?
    Yes, its a normal patching process for Primary-->Secondary setups.
    You have to apply the application patches only on Production, then sync process takes care on DR (No need to apply the pathces here, infact you don't need to touch your exisiting DR system).
    As a best practice - Just perform a Quality refresh before performing patching activity, then you can perform your test Patching/Upgrade activity in your Quality system itself (Not on DR).
    Regards,
    Nick Loy

  • Client Stop reporting in WSUS after Approval patches

    Hi Team,
    Recently i faced lot of issue in my wsus server during patching activity,  After approving patches certain client stop reporting in wsus . I have tried all the troubleshooting but no one help.
    can any one help me and provide troubleshooting steps which required in this type of cases
    Regards, Triyambak

    I am facing same issue in one of server ,  here is the log file
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING: SOAP Fault: 0x00012c
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING:     faultstring:Fault occurred
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING:     ErrorCode:ServerChanged(4)
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING:     Message:Server rolled back since last call to GetCookie
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING:     ID:2f956ab6-fac3-4e68-bffa-48557d580e88
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING: PTError: 0x80244015
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING: GetCookie_WithRecovery failed : 0x80244015
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING: RefreshCookie failed: 0x80244015
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING: RefreshPTState failed: 0x80244015
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING: Sync of Updates: 0x80244015
    2014-06-24 02:56:11:066
    852 c18
    PT WARNING: Cached cookie has expired or new PID is available
    2014-06-24 02:56:11:066
    852 c18
    PT Initializing simple targeting cookie, clientId = 60adbf7d-5194-4cd9-90c7-e00efccedcb7, target group = WSUS 2003 x32 Prod Group 1, DNS name = lpsjcmwbp13.sumcweb.com
    2014-06-24 02:56:11:066
    852 c18
    PT  Server URL = http://lpchweb-wsus.sumcweb.com/SimpleAuthWebService/SimpleAuth.asmx
    2014-06-24 02:56:30:488
    852 c18
    Agent  * WARNING: Failed to synchronize, error = 0x80244015
    2014-06-24 02:56:30:504
    852 c18
    Report CWERReporter finishing event handling. (00000000)
    2014-06-24 02:56:30:504
    852 c18
    DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
    2014-06-24 02:56:30:504
    852 c18
    Agent Server changed and need resyncing with server
    2014-06-24 02:56:30:895
    852 c18
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-06-24 02:56:30:895
    852 c18
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
    2014-06-24 02:56:35:692
    852 c18
    PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-06-24 02:56:35:692
    852 c18
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
    an AU detection already in progress
    2014-06-24 01:35:37:030
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:37:030
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:37:077
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:37:077
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:37:296
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:37:296
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:37:562
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:37:562
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:37:655
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:37:655
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:37:968
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:37:968
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:38:015
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:38:015
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:38:343
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:38:343
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:38:515
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:38:515
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:38:655
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:38:655
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:38:937
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:38:937
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:38:999
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:38:999
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:39:421
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:39:421
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:39:421
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:39:421
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:39:640
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:39:640
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:39:859
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:39:859
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:39:968
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:39:968
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:40:312
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:40:312
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:40:374
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:40:374
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:40:609
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:40:609
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:40:859
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:40:859
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:41:030
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:41:030
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:41:202
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:41:202
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:41:374
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:41:374
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:41:515
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:41:515
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:41:796
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:41:796
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:41:952
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:41:952
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:42:077
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:42:077
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:42:374
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:42:374
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:42:499
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:42:499
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:42:671
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:42:671
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:42:952
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:42:952
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:43:062
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:43:062
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:43:327
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:43:327
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:43:499
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:43:499
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:43:624
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:43:624
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:43:859
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:43:859
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:43:984
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:43:984
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:44:218
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:44:218
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:44:343
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:44:343
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:44:687
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:44:687
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:44:859
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:44:859
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:44:984
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:44:984
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:45:281
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:45:281
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:45:343
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:45:343
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:45:749
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:45:749
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:45:749
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:45:749
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:45:984
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:45:984
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:46:281
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:46:281
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:46:452
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:46:452
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:46:593
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:46:593
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:46:765
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:46:765
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:46:968
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:46:968
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:47:124
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:47:124
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:47:343
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:47:343
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:47:515
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:47:515
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:47:734
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:47:734
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:48:015
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:48:015
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:48:109
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:48:109
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:48:327
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:48:327
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:48:499
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:48:499
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:48:702
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:48:702
    832 1378
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:48:906
    832 700
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:48:906
    832 700
    AU Piggybacking on an AU detection already in progress
    2014-06-24 01:35:49:234
    832 1378
    AU Triggering AU detection through DetectNow API
    2014-06-24 01:35:49:234
    832 1378
    AU Piggybacking on an AU detection already
    Regards, Triyambak

  • Applications Addon ST-PI 2008_1_640 and ST-A/PI 01L_ECC500

    Dear All ,
    We are using ecc5  release  640.
    I am facing the problem in Service Tools for Applications Addon ST-PI 2008_1_640 and ST-A/PI 01L_ECC500
    Mu current  sp level is
    ST-A/PI     01J_ECC500     0          -     Application Servicetools for ECC 500
    ST-PI     2005_1_640     3     SAPKITLQH3     SAP Solution Tools Plug-In
    After running the RTCCTOOL report I am getting and error .I  have some queries
    1 as suggest I can go directly 01J_ECC500 to 01L_ECC500 same for 2005_1_640 to  ST-PI 2008_1_640.
    2 Do I have to upgrades before SAINT version 6.40/0019.
    3. As per note 69455  Note: As of 28th Nov. 2008 a new release 01L* of addon ST-A/PI has become available. The previous release 01K* will still be sufficient forservice preparation until 31th December 2008.
    Regards,
    kumar

    For the dependencies and pre-requisites, just read the Notes recommended by the RTCCTOOL run. when you downloads the ST-PI or ST-A//PI or even any patch, it's information file is always there with it in marketplace which tell what pre-requisites should met before that particular patch can be applied successful. For 'pre-requisites', here means, the support pack/patch level which should already be there before applying the current one in question.
    And, like if we do not have any SP of ST-PI or ST-A/PI already in our SAP system, then to install them for the 'first time', we need to download the 'installation files'. If you already have some patch level of ST-API or ST-PI in the system, then we need to downlaod the 'delta upgrade' files for each of them. Read those notes, everything mentioned.
    For normal precaution, just make sure that /usr/sap/trans filesystem has enough space and do this patch activity in less user load time, however st-pi and st-api woudn't be affected much even with user loads.

  • Backup  oracle database - pre post steps

    I want to do cold backup of 10g database. Do I need to shutdown Oracle Application server and listeners before doing cold backup and start them again after backup done.

    for taking cold backup then its better to shutdown the apps server as well
    database.I would recommend to you whenver you are going to take cold
    backup for db then its better for you to take apps cold backup too if
    the cold backup goes after you applied any patch ,within E-Biz tech the
    patch activity affect apps files too.
    Khurram

  • OEM 10g - Job Status - Suspended on Agent Unreachable

    Hi,
    I have checked out a few post on this forum which is similar to my problem.
    But could not get the exact workaround.
    The scheduled backup is not getting failed / successful since 29th January 2010.
    We have not made any changes on the database level. But there was a patching activity at application level.
    and as soon as I try to schedule a backup it shows the same status "suspended on agent unreachable"
    I have checked the emctl status and dbconsole status.
    E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.6.0
    OMS Version : 10.1.0.6.0
    Protocol Version : 10.1.0.2.0
    Agent Home : e:\oracle\product\10.2.0\db_1\content.mydomain.de_aeb
    Agent binaries : e:\oracle\product\10.2.0\db_1
    Agent Process ID : 6104
    Agent URL : http://content.mydomain.de:3938/emd/main
    Started at : 2010-02-01 21:55:19
    Started by user : SYSTEM
    Last Reload : 2010-02-01 21:55:19
    Last successful upload : 2010-02-17 06:12:10
    Last attempted upload : 2010-02-17 06:12:25
    Total Megabytes of XML files uploaded so far : 323.40
    Number of XML files pending upload : 1
    Size of XML files pending upload(MB) : 0.01
    Available disk space on upload filesystem : 9.36%
    Agent is Running and Ready
    E:\oracle\product\10.2.0\db_1\BIN>emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    http://content.mydomain.de:1158/em/console/aboutApplication
    Oracle Enterprise Manager 10g is running.
    Logs are generated in directory e:\oracle\product\10.2.0\db_1/scontent.mydomain.de_AEB/sysman/log
    Upload also seems to be working fine.
    E:\oracle\product\10.2.0\db_1\BIN>emctl upload
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD upload completed successfully
    What should I do ? Will restarting the agent help ? Will restarting the agent have any adverse effect on DB ?
    Any help would be a great help.
    Rushabh

    Hi,
    This is urgent.. Please help..
    I am not able to start the emctl...
    Below is the error that I am getting..
    E:\oracle\product\10.2.0\db_1\BIN>emctl stop agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    This will stop the Oracle Enterprise Manager 10g Database Control process. Conti
    nue [y/n] :y
    The OracleDBConsoleaeb service is stopping..........
    The OracleDBConsoleaeb service was stopped successfully.
    E:\oracle\product\10.2.0\db_1\BIN>emctl clearstate agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD clearstate completed successfully
    E:\oracle\product\10.2.0\db_1\BIN>emctl secure agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Enter Agent Registration password :
    Agent is already stopped... Done.
    Securing agent... Started.
    Requesting an HTTPS Upload URL from the OMS... Failed.
    The OMS is not set up for Enterprise Manager Security.
    E:\oracle\product\10.2.0\db_1\BIN>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    When I try to secure agent it is asking for a password, but it is already saved I think..
    When I press enter it is showing the above error.
    What should I do now ?
    Regards,
    Rushabh
    Edited by: user650383 on Feb 16, 2010 10:44 PM

Maybe you are looking for