Bootstrap process failure

Hi Everybody,
Database Version:Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
Os:Windows Xp.
When I am trying to startup the Database it giving me the following error..
SQL> startup
ORACLE instance started.
Total System Global Area  113246208 bytes
Fixed Size                  1247588 bytes
Variable Size              58721948 bytes
Database Buffers           50331648 bytes
Redo Buffers                2945024 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forcedWhen i looked into the alert log file it showing me the follwoing error's
Fri Oct 17 15:47:22 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\udump\primary_ora_3812.trc:
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 16 bytes of shared memory ("shared pool","select o.owner#,o.name,o.nam...","sql area","kggsmInitCompact:offsetVec")
Fri Oct 17 15:47:22 2008
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
ARC2 started with pid=16, OS id=3024
Fri Oct 17 15:47:22 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_lns1_872.trc:
ORA-00704: bootstrap process failure
Fri Oct 17 15:47:22 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_reco_3120.trc:
ORA-00704: bootstrap process failure
Fri Oct 17 15:47:22 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_pmon_2652.trc:
ORA-00704: bootstrap process failure
Fri Oct 17 15:47:23 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_ckpt_928.trc:
ORA-00704: bootstrap process failure
Fri Oct 17 15:47:23 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_lgwr_3332.trc:
ORA-00704: bootstrap process failure
Fri Oct 17 15:47:23 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_dbw0_1696.trc:
ORA-00704: bootstrap process failure
Fri Oct 17 15:47:23 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_mman_1724.trc:
ORA-00704: bootstrap process failure
Fri Oct 17 15:47:24 2008
Errors in file d:\oracle\product\10.2.0\admin\primary\bdump\primary_psp0_2464.trc:
ORA-00704: bootstrap process failure
Instance terminated by USER, pid = 3812
ORA-1092 signalled during: ALTER DATABASE OPEN...even i looked into the trace files mentioned in the alert log but no definite information is provided out there.....
How to overcome this Bootstrap process failure error.......
Any Help Appreciated..
Regards,
Prosenjit Mukherjee.

Recommended action for ORA-00704 is to contact Oracle support.
Just out of curiosity, whats the machine configuration?

Similar Messages

  • 32bit Primary to 64bit Standby-"ORA-00704: bootstrap process failure"

    Hello All,
    As per the Doc ID 414043.1 it is possible to use mixed word size primary-standby configurations since 10g and better in 11g.
    So i created my test env:-
    OS: Linux 5.5 64bit
    DB Name: TEST
    Primary  - TEST32 on 32bit Oracle Home
    Standby-  TEST64 on 64bit Oracle Home
    I could apply TEST32's archive logs(manually) on TEST64 without any problem, but when i tried to migrate to 64bit it kept failed with "ORA-00704: bootstrap process failure ORA-39700: database must be opened with UPGRADE option"
    What i did on TEST64 is:
    1) Activate physical standby
    2) Startup Upgrade
    3)@?/rdbms/admin/utlirp.sql
    4)@?/rdbms/admin/utlrp.sql
    5)Shutdown
    6)Startup
    When i issue startup(step 6); it fails with
    <pre>
    SQL> startup;
    ORACLE instance started.
    Total System Global Area 1670221824 bytes
    Fixed Size 2227072 bytes
    Variable Size 419431552 bytes
    Database Buffers 1241513984 bytes
    Redo Buffers 7049216 bytes
    Database mounted.
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Process ID: 22712
    Session ID: 126 Serial number: 5
    SQL> exit
    ＜/pre＞
    Did i go wrong somewhere ?
    TIA,
    JJ

    What i did on TEST64 is:
    1) Activate physical standby
    2) Startup Upgrade
    3)@?/rdbms/admin/utlirp.sql
    4)@?/rdbms/admin/utlrp.sql
    5)Shutdown
    6)Startup
    SQL> startup;
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Process ID: 22712
    Session ID: 126 Serial number: 5SQL> Startup upgrade.

  • ORA-00704: bootstrap process failure and SYSTEM datafile corrupt

    We have an Oracle 10g Express database that is getting the following error on startup.
    ORA-00704: bootstrap process failure
    It is also showing that the SYSTEM datafile is corrupt. And unfortunately the backups are gone. Is there any way to recover from this without a backup? Maybe some hidden undocumented parameter???
    We do have some full database exports from a couple weeks ago so it is not a complete loss but would really like a full recover.

    Windows XP
    We have tried allowresetlogs_corruption and allowread_only_corruption and no luck so far.
    ALTER DATABASE MOUNT
    Thu Aug 09 08:49:28 2012
    Setting recovery target incarnation to 2
    Thu Aug 09 08:49:28 2012
    Successful mount of redo thread 1, with mount id 2672004948
    Thu Aug 09 08:49:28 2012
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Thu Aug 09 08:49:50 2012
    alter database open upgrade
    Thu Aug 09 08:49:50 2012
    Beginning crash recovery of 1 threads
    Thu Aug 09 08:49:50 2012
    Started redo scan
    Thu Aug 09 08:49:50 2012
    Completed redo scan
    0 redo blocks read, 0 data blocks need recovery
    Thu Aug 09 08:49:50 2012
    Started redo application at
    Thread 1: logseq 84298, block 3, scn 10745981851
    Thu Aug 09 08:49:50 2012
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 84298 Reading mem 0
    Mem# 0 errs 0: D:\DATA\ORACLE\ORADATA\XE\REDO04A.LOG
    Mem# 1 errs 0: D:\DATA\ORACLE\ORADATA\XE\REDO04B.LOG
    Thu Aug 09 08:49:50 2012
    Completed redo application
    Thu Aug 09 08:49:50 2012
    Completed crash recovery at
    Thread 1: logseq 84298, block 3, scn 10746001852
    0 data blocks read, 0 data blocks written, 0 redo blocks read
    Thu Aug 09 08:49:51 2012
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=18, OS id=2524
    Thu Aug 09 08:49:51 2012
    ARC0: Archival started
    ARC1 started with pid=20, OS id=2956
    Thu Aug 09 08:49:52 2012
    ARC1: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    Thread 1 advanced to log sequence 84299
    Thread 1 opened at log sequence 84299
    Current log# 2 seq# 84299 mem# 0: D:\DATA\ORACLE\ORADATA\XE\REDO02A.LOG
    Current log# 2 seq# 84299 mem# 1: D:\DATA\ORACLE\ORADATA\XE\REDO02B.LOG
    Successful open of redo thread 1
    Thu Aug 09 08:49:52 2012
    ARC1: STARTING ARCH PROCESSES
    Thu Aug 09 08:49:52 2012
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    Thu Aug 09 08:49:52 2012
    SMON: enabling cache recovery
    Thu Aug 09 08:49:52 2012
    ARC2: Archival started
    Thu Aug 09 08:49:52 2012
    ARC1: STARTING ARCH PROCESSES COMPLETE
    ARC1: Becoming the heartbeat ARCH
    ARC2 started with pid=21, OS id=3916
    Thu Aug 09 08:49:54 2012
    Successfully onlined Undo Tablespace 1.
    Thu Aug 09 08:49:54 2012
    SMON: enabling tx recovery
    Thu Aug 09 08:49:54 2012
    Database Characterset is WE8MSWIN1252
    Thu Aug 09 08:49:56 2012
    Hex dump of (file 1, block 39) in trace file c:\oraclexe\app\oracle\admin\xe\bdump\xe_smon_876.trc
    Corrupt block relative dba: 0x00400027 (file 1, block 39)
    Bad check value found during buffer read
    Data in bad block:
    type: 6 format: 2 rdba: 0x00400027
    last change scn: 0x0002.7fee0b69 seq: 0x1 flg: 0x06
    spare1: 0x0 spare2: 0x0 spare3: 0x0
    consistency value in tail: 0x0b690601
    check value in block header: 0x8f6c
    computed block checksum: 0x1000
    Reread of rdba: 0x00400027 (file 1, block 39) found same corrupted data
    Thu Aug 09 08:49:56 2012
    Stopping background process MMNL
    Thu Aug 09 08:49:56 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_smon_876.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 39)
    ORA-01110: data file 1: 'D:\DATA\ORACLE\ORADATA\XE\SYSTEM.DBF'
    Thu Aug 09 08:49:57 2012
    Stopping background process MMON
    Starting background process MMON
    Starting background process MMNL
    MMON started with pid=11, OS id=1012
    Thu Aug 09 08:49:58 2012
    ALTER SYSTEM enable restricted session;
    MMNL started with pid=12, OS id=3584
    Thu Aug 09 08:49:58 2012
    ALTER SYSTEM SET systemtrig_enabled=FALSE SCOPE=MEMORY;
    Thu Aug 09 08:49:58 2012
    ALTER SYSTEM SET aq_tm_processes=0 SCOPE=MEMORY;
    Thu Aug 09 08:49:58 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_324.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 39)
    ORA-01110: data file 1: 'D:\DATA\ORACLE\ORADATA\XE\SYSTEM.DBF'
    Thu Aug 09 08:49:58 2012
    Error 604 happened during db open, shutting down database
    USER: terminating instance due to error 604
    Thu Aug 09 08:49:59 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_pmon_3120.trc:
    ORA-00604: error occurred at recursive SQL level
    Thu Aug 09 08:49:59 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_psp0_3444.trc:
    ORA-00604: error occurred at recursive SQL level
    Thu Aug 09 08:49:59 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_mman_2592.trc:
    ORA-00604: error occurred at recursive SQL level
    Thu Aug 09 08:49:59 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_dbw0_932.trc:
    ORA-00604: error occurred at recursive SQL level
    Thu Aug 09 08:49:59 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_ckpt_1156.trc:
    ORA-00604: error occurred at recursive SQL level
    Thu Aug 09 08:50:00 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_lgwr_1508.trc:
    ORA-00604: error occurred at recursive SQL level
    Thu Aug 09 08:50:00 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_reco_2700.trc:
    ORA-00604: error occurred at recursive SQL level
    Thu Aug 09 08:50:00 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_smon_876.trc:
    ORA-00604: error occurred at recursive SQL level

  • Process Failure when communicating over MODBUS using LabVIEW 2011 and DSC

    I'm currently trying to read from a PLC's holding registers using MODBUS/TCP. I've confirmed that the PLC is updating the values and responding to MODBUS communication correctly using a third party program called Modbus Poll. However, when I try to poll the PLC using LabVIEW's shared variable engine, I am unable to read any values from the same addresses that I'm viewing with Modbus Poll.
    My setup simply consists of a PC connected directly to the PLC over Ethernet, with no router in between. I am using LabVIEW 2011 SP1 with the DSC module.
    I opened the NI Distributed Systems Manager to view the status of all shared variables in the Modbus library that I created and I've noticed that the CommFail bit is permanently set to "true". All other variables with a "read" access mode report "Process Failure". I've tried restarting the process as well as stopping and starting the local variable engine with no success. I've also restarted my computer several times to see if any services were failing, but this does not seem to have fixed the problem.
    I finally resorted to monitoring communications over the network card that I have the PLC plugged into via Ethernet using Wireshark and I've found that while Modbus Poll is communicating with the PLC, many MODBUS and TCP packets are sent and received. However, when solely using LabVIEW or the NI DSM to communicate with the PLC, there does not appear to be any communication over the network card.
    Something that may be worth noting is that I was able to communicate with the PLC and read values from it with the DSM on just one occasion, when I first figured out which addresses I should be reading from. It all stopped working shortly thereafter. Prior to this, "CommFail" was not usually set to "true" with my current configuration. Thinking that it was my firewall, I have since turned my firewall off, but this seems to have had no effect on the problem either.
    Any help on this matter would be appreciated.
    Solved!
    Go to Solution.

    Just a thought but I think the  register addresses used by LabVIEW are one off of the actual register #.  I was using a CRIO as a modbus IO Server and had to shift the register addresses by 1 to get things to work correctly (can;t recall if it was +1 or -1).  This is documented somewhere on ni.com but can;t seem to find it now.  But here is another  link that may help:
    http://zone.ni.com/reference/en-XX/help/371618E-01/lvmve/dsc_modbus_using/
    Dan

  • Soap fault: SOAP processing failure, error id = 1018

    Hello,
    if I try to call a web service exposed via XI, i have this error message:
    soap fault: SOAP processing failure, error id = 1018
    Can someone help me to solve this problem?
    Thank you

    The following OSS note talks of 1018 error, see if it helps.
    [946658|https://service.sap.com/sap/support/notes/946658]

  • SOAP processing failure, error id = 112

    Hi,
    i call a web service and get the following error message:
    - <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    - <soap-env:Body>
    - <soap-env:Fault>
      <faultcode>soap-env:Server</faultcode>
      <faultstring xml:lang="en">SOAP processing failure, error id = 112</faultstring>
      </soap-env:Fault>
      </soap-env:Body>
      </soap-env:Envelope>
    I have no answer find in the forum.
    Any ideas?
    regards

    does the connection test work in SM59??
    I think you got to involve a basis guy. unless I can't see your proxy settings, your dev_traces and so on I can#t diagnose your problem correctly.
    the unallowed XML-Tag error could arise in the following situation:
    you call a service, but your proxy doesn't forward the request due to authentication or other problems and returns you something like
    <html><body><h1>A proxy error occured. Call your admin.</h1></body></html>
    this is because the proxy assumes you use a browser and therefore returns a 'nicely formatted answer'(i.e. one in HTML, which you could easily understand if you used a browser).
    If its not the proxy your webserver could return for instance a 401-Forbidden, which also often comes nicely formatted to be rendered with a browser.
    Your proxy runtime on the other side expects no other answer than one starting with
    <xml ... > ....
    since yours starts with
    <html>...
    it says 'unnallowed XML tag'.
    This way there can be numerous errors and I can only advice you to use all debugging tools available and inspect the communication carefully.
    anton
    Message was edited by:
            Anton Wenzelhuemer

  • SOAP processing failure, error id = 1001

    Hi,
    I am trying to implement the yahoo widgets usingthe following blog:
    BI Data Widget - Weblog Series & Pre-requisites
    I am stuck at STEP 14. I am getting the error :
    "An error has occurred. Maybe the request is not accepted by the server:
    SOAP processing failure, error id = 1001"
    Any idea how to rectify this. I have activated the service in SE80 also.
    Thanks,

    Hi Avihai,
    I exposed custom RFC as a webservice and the url specified in the reciever adapter is http://pdcntwr.wipro.com:8000/sap/bc/srt/rfc/sap/Z_Get_Transport_Request?sap-client=100.
    Please let me know if anything needs to be done.
    Please find the dump.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: SOAP processing failure, error id = 1001</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • How to Configure alert for process failures

    Hi Friends.
    How to Configure alert for process failures due to any reasons like mapping, runtime exceptions .
    I am devloping one scenario which is file to flatfile. In this scenario I am also using mail adapter for sending mail daily to admin that tells about record size and no of records parallely. I am not using BPM in this scenario.
    I am having very little experience in XI.
    Please answer this with clear steps so that I can do it.

    hi,
    check the links below for all the details and help on configuring alerts
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9418d690-0201-0010-85bb-e9b2c1af895b - How to setup alerts for monitoring in XI 3.0
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/003de490-0201-0010-68a4-bf7a1e1fd3a5 - Monitoring in XI 3.0
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - XI: Alerts configuration - Step by step
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - XI: Alerts - Troubleshooting guide
    /people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
    /people/community.user/blog/2006/10/16/simple-steps-to-get-descriptive-alerts-from-bpm-in-xi

  • SOAP processing failure

    Hello All , I have installed Java and ABAP sneak preview on the same machine . I have also created a service from an existing BAPI 'BAPI_FLBOOKING_GETLIST' and released the service . When I am trying to test this new service from ZICF transaction then I get following error :
    'SOAP processing failure, error id = 112' .
    Has any one faced and resolved the same error ? Any help would be greatly appreciated .
    Thanks
    Rajesh

    Hi Avihai,
    I exposed custom RFC as a webservice and the url specified in the reciever adapter is http://pdcntwr.wipro.com:8000/sap/bc/srt/rfc/sap/Z_Get_Transport_Request?sap-client=100.
    Please let me know if anything needs to be done.
    Please find the dump.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: SOAP processing failure, error id = 1001</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • Batch processing Failure

    hey,
    please help me regarding the batch processing failure issue,
    The file is placed in appropriate folder but in am getting an error when i execute it.
    The error is
    ORA-02291-integrity constraint
    Please help Me Out

    What is in the user error log? (Toos > View Error Log). This is going to be a bit difficult to troubleshoot over the discussion forum, you may want to open a Service Request to allow an FDM analyst to view the files, users error logs, etc.

  • SQL30082N  Security processing failed with reason "15" (PROCESSING FAILURE)

    Hi all.
    I'm managing the following error during a system copy:
    <b>SQL30082N  Security processing failed with reason "15" ("PROCESSING FAILURE").
    SQLSTATE=08001</b>
    Inside the db2diag.log, i have the following message:
    <b>2007-10-15-16.44.56.793439+120 I718413554A270     LEVEL: Warning
    PID     : 483450               TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 64 bytes
    Password validation for user sapr3 failed with rc = -2146500315</b>
    Can anyone help?
    Thanks and regards,
    Marco.

    Hi,
    check if the files
    $INSTHOME/sqllib/security/db2c?pw
    have the correct permissions. They need a SUID bit to root.
    If the SUID bit is not set, you can do a
    <db2_install_dir>/instance/db2iupdt db2<dbname>
    as user root to update your DB2 instance. This will set the permissions correctly.
    Regards
                   Frank

  • Group Policy processing failure on 2008 when MIX Domain 2003 with DC 2008

    Dear I try to add additional Windows 2008 Domain to My Domain controller 2003  and I ma Receiving Group policy error in DC 2008  With Event ID 1055
    The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
    a) Name Resolution failure on the current domain controller. 
    b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" /> 
      <EventID>1055</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Opcode>1</Opcode> 
      <Keywords>0x8000000000000000</Keywords> 
      <TimeCreated SystemTime="2014-03-06T14:36:44.411955300Z" /> 
      <EventRecordID>3859</EventRecordID> 
      <Correlation ActivityID="{28DAD258-26D0-4C1E-A4B7-F37DEE04C8F1}" /> 
      <Execution ProcessID="952" ThreadID="3276" /> 
      <Channel>System</Channel> 
      <Computer>PRIMARYDC.Qtit.com</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="SupportInfo1">1</Data> 
      <Data Name="SupportInfo2">1632</Data> 
      <Data Name="ProcessingMode">0</Data> 
      <Data Name="ProcessingTimeInMilliseconds">1578</Data> 
      <Data Name="ErrorCode">5</Data> 
      <Data Name="ErrorDescription">Access is denied.</Data> 
      </EventData>
      </Event>
    I install See KB939820 for a hotfix applicable to Microsoft DC 2003 regrading to he KRBTGT account 
    Refer Url : http://support.microsoft.com/kb/939820 
    I run dcdiag /v on  and repadmin /showrepl at DC 2008
    the dcdiag /v result
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine PRIMARYDC, is a Directory Server. 
       Home Server = PRIMARYDC
       * Connecting to directory service on server PRIMARYDC.
       * Identified AD Forest. 
       Collecting AD specific global data 
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded 
       Iterating through the sites 
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers 
       Getting information for the server CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       Getting information for the server CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity 
             * Active Directory RPC Services Check
             ......................... PRIMARYDC passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Advertising
             The DC PRIMARYDC is advertising itself as a DC and having a DS.
             The DC PRIMARYDC is advertising as an LDAP server
             The DC PRIMARYDC is advertising as having a writeable directory
             The DC PRIMARYDC is advertising as a Key Distribution Center
             The DC PRIMARYDC is advertising as a time server
             The DS PRIMARYDC is advertising as a GC.
             ......................... PRIMARYDC passed test Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Starting test: FrsEvent
             * The File Replication Service Event log test 
             There are warning or error events within the last 24 hours after the
             SYSVOL has been shared.  Failing SYSVOL replication problems may cause
             Group Policy problems. 
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:18:56
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:53:21
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             ......................... PRIMARYDC passed test FrsEvent
          Starting test: DFSREvent
             The DFS Replication Event Log. 
             Skip the test because the server is running FRS.
             ......................... PRIMARYDC passed test DFSREvent
          Starting test: SysVolCheck
             * The File Replication Service SYSVOL ready test 
             File Replication Service's SYSVOL is ready 
             ......................... PRIMARYDC passed test SysVolCheck
          Starting test: KccEvent
             * The KCC Event log test
             Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
             ......................... PRIMARYDC passed test KccEvent
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Domain Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role PDC Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Rid Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             ......................... PRIMARYDC passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             Checking machine account for DC PRIMARYDC on DC PRIMARYDC.
             * SPN found :LDAP/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :LDAP/PRIMARYDC.Qtit.com
             * SPN found :LDAP/PRIMARYDC
             * SPN found :LDAP/PRIMARYDC.Qtit.com/QTIT
             * SPN found :LDAP/e3d8c76c-1b59-4de6-9f7f-c438df9a2863._msdcs.Qtit.com
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/e3d8c76c-1b59-4de6-9f7f-c438df9a2863/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com
             * SPN found :HOST/PRIMARYDC
             * SPN found :HOST/PRIMARYDC.Qtit.com/QTIT
             * SPN found :GC/PRIMARYDC.Qtit.com/Qtit.com
             ......................... PRIMARYDC passed test MachineAccount
          Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC PRIMARYDC.
             The forest is not ready for RODC. Will skip checking ERODC ACEs.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               DC=DomainDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=DomainDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=Qtit,DC=com
                (Schema,Version 3)
             * Security Permissions Check for
               CN=Configuration,DC=Qtit,DC=com
                (Configuration,Version 3)
             * Security Permissions Check for
               DC=Qtit,DC=com
                (Domain,Version 3)
             ......................... PRIMARYDC failed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             Verified share \\PRIMARYDC\netlogon
             Verified share \\PRIMARYDC\sysvol
             ......................... PRIMARYDC passed test NetLogons
          Starting test: ObjectsReplicated
             PRIMARYDC is in domain DC=Qtit,DC=com
             Checking for CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com in domain DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com in domain CN=Configuration,DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             ......................... PRIMARYDC passed test ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
                DC=ForestDnsZones,DC=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                DC=DomainDnsZones,DC=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                CN=Schema,CN=Configuration,DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                CN=Configuration,DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
             * Replication Site Latency Check 
             ......................... PRIMARYDC passed test Replications
          Starting test: RidManager
             * Available RID Pool for the Domain is 14607 to 1073741823
             * SecondAD.Qtit.com is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 14107 to 14606
             * rIDPreviousAllocationPool is 14107 to 14606
             * rIDNextRID: 14124
             ......................... PRIMARYDC passed test RidManager
          Starting test: Services
             * Checking Service: EventSystem
             * Checking Service: RpcSs
             * Checking Service: NTDS
             * Checking Service: DnsCache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... PRIMARYDC passed test Services
          Starting test: SystemLog
             * The System Event log test
             A warning event occurred.  EventID: 0x0000A001
                Time Generated: 03/06/2014   16:04:05
                Event String:
                The Security System could not establish a secured connection with the server ldap/PRIMARYDC.Qtit.com/[email protected]. No authentication protocol was available.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:06:35
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:11:36
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:16:38
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:21:39
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:26:41
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:46
                Event String:
                Driver TOSHIBA e-STUDIO16/20/25 PCL 6 required for printer TOSHIBA e-STUDIO16/20/25 PCL 6 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:48
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:49
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:14
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver WebEx Document Loader required for printer WebEx Document Loader is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:31:42
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             ......................... PRIMARYDC failed test SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Starting test: VerifyReferences
             The system object reference (serverReference)
             CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com and backlink on
             CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (serverReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on
             CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (frsComputerReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com are
             correct. 
             ......................... PRIMARYDC passed test VerifyReferences
          Test omitted by user request: VerifyReplicas
          Test omitted by user request: DNS
          Test omitted by user request: DNS
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : Qtit
          Starting test: CheckSDRefDom
             ......................... Qtit passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Qtit passed test CrossRefValidation
       Running enterprise tests on : Qtit.com
          Test omitted by user request: DNS
          Test omitted by user request: DNS
          Starting test: LocatorCheck
             GC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             PDC Name: \\SecondAD.Qtit.com
             Locator Flags: 0xe00001bd
             Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             Preferred Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             KDC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             ......................... Qtit.com passed test LocatorCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope
             provided by the command line arguments provided. 
             ......................... Qtit.com passed test Intersite
    repadmin /showrepl Result
    ******************************8
    ==== INBOUND NEIGHBORS ===================================
    DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:04 was successful.
    CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:39 was successful.
    CN=Schema,CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    DC=DomainDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:27:31 was successful.
    DC=ForestDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    I try to down the DC 2003 and access \\Qtit.com it success open the syslog on DC 2008
    Any help or advice 

    Hi,
    Were there other error codes logged in Event Viewer?
    Regarding Event ID 1055, the following article can be referred to for troubleshooting.
    Event ID 1055 — Group Policy Preprocessing (Security)
    http://technet.microsoft.com/en-us/library/cc727272(v=ws.10).aspx
    Based on the report you posted, this issue may be related to FRS replication service. As a result, we can use ntfrsutl tool to check whether the replication service is healthy.
    Regarding this point, the following articles can be referred to for more information.
    Troubleshooting File Replication Service
    http://technet.microsoft.com/en-us/library/bb727056.aspx
    Ntfrsutl
    http://technet.microsoft.com/en-us/library/hh875636.aspx
    In addition, we can also try doing a non-authoritative Sysvol restore on Windows Server 2008 DC to see whether the issue persists.
    Using the BurFlags registry key to reinitialize File Replication Service replica sets
    http://support.microsoft.com/kb/290762/en-us
    Hope it helps.
    Best regards,
    Frank Shen

  • Automated detect on a process failure

    Hi,
    I was using SQL developer to execute a pl/sql code, my version is 1.5.3. the code is actually running a program to recover a failure of a process, when the process fail, i need to recover manually by enter the date of the process fail and the last day of recovery. My question, is there any method or way to automatic recover the process or job when it failed? Did sql developer provide some function that can detect the process had failed?
    Thanks

    create or replace PACKAGE BODY Ewaste_Inventory_Recovery AS
         PROCEDURE Inventory_Recovery (vFromDate VARCHAR2, vToDate VARCHAR2) IS     
              dLoopDay     DATE;
              dFromDate     DATE;
              dToDate          DATE;
         BEGIN
         /* this will loop from failed date up to current date + 1 */
              dLoopDay     := TO_DATE(vFromDate, 'DD-MON-YY');
              dFromDate     := TO_DATE(vFromDate, 'DD-MON-YY');
              dToDate      := TO_DATE(vToDate, 'DD-MON-YY');
              WHILE dLoopDay <= dToDate + 1
        LOOP
                   IF dLoopDay < dToDate + 1 THEN
                        Inventory_Calculation(dLoopDay,'Yes');
                   ELSE
                        Inventory_Calculation(dLoopDay, 'No');
                   END IF;
                   dLoopDay := dLoopDay + 1;
              END LOOP;     
         COMMIT;     
         END Inventory_Recovery;
         PROCEDURE Inventory_Calculation (dInDate DATE, vInsertFlag VARCHAR2) IS
              rDayBeforeInvRec      Wste_Waste_Inventory%ROWTYPE;
              rInDateInvRec           Wste_Waste_Inventory%ROWTYPE;
              fInDateReceiveQty      FLOAT;
              fInDateShipoutQty      FLOAT;
              fInDateOnHandQty       FLOAT;
              fInDateOpeningQty      FLOAT;
              nComponentId     NUMBER(25);
              vCompDept     VARCHAR2(20);
              vCompName     VARCHAR2(80);
              vWasteType     VARCHAR2(2);
              nGroupId     NUMBER(25);
              vComponentName     VARCHAR2(80);
              CURSOR Day_Before_Fail_Inv_Bal IS
                   SELECT * FROM wste_waste_inventory
                   WHERE wwin_date = dInDate -1;
              CURSOR InDate_Rec_Exist IS
                   SELECT * FROM wste_waste_inventory
                   WHERE wwin_date = dInDate
                   AND wwin_wwco_id = nComponentId
                   AND wwin_comp_dept = vCompDept
                   AND wwin_waste_type = vWasteType
                   AND wwin_wwgr_id = nGroupId
                   AND wwin_component_name = vComponentName;
         BEGIN
              OPEN Day_Before_Fail_Inv_Bal;
                   LOOP
                        FETCH Day_Before_Fail_Inv_Bal INTO rDayBeforeInvRec;
                        nComponentId     := rDayBeforeInvRec.wwin_wwco_id;
                        vCompDept     := rDayBeforeInvRec.wwin_comp_dept;
                        vCompName     := rDayBeforeInvRec.wwin_comp_name;
                        vWasteType     := rDayBeforeInvRec.wwin_waste_type;
                        nGroupId     := rDayBeforeInvRec.wwin_wwgr_id;
                        vComponentName     := rDayBeforeInvRec.wwin_component_name;
                        OPEN InDate_Rec_Exist;
                             FETCH InDate_Rec_Exist INTO rInDateInvRec;
                             IF InDate_Rec_Exist%FOUND THEN
                                  fInDateOpeningQty      := rDayBeforeInvRec.wwin_onhand;
                                  fInDateOnHandQty      := rDayBeforeInvRec.wwin_onhand - rInDateInvRec.wwin_ship_out + rInDateInvRec.wwin_receive;
                                  UPDATE wste_waste_inventory SET
                                       WWIN_OPENING = fInDateOpeningQty,
                                       WWIN_ONHAND  = fInDateOnHandQty                              
                                  WHERE wwin_date = dInDate
                                  AND wwin_wwco_id = nComponentId
                                  AND wwin_comp_dept = vCompDept
                                  AND wwin_waste_type = vWasteType
                                  AND wwin_wwgr_id = nGroupId
                                  AND wwin_component_name = vComponentName;                              
                             ELSE          
                                  --IF vInsertFlag = 'Yes' THEN
                                       fInDateOpeningQty      := rDayBeforeInvRec.wwin_onhand;
                                       fInDateOnHandQty      := rDayBeforeInvRec.wwin_onhand;
                                       INSERT INTO wste_waste_inventory (
                                            WWIN_ID,
                                            WWIN_WWCO_ID,
                                            WWIN_RECEIVE,
                                            WWIN_SHIP_OUT,
                                            WWIN_ONHAND,
                                            WWIN_OPENING,
                                            WWIN_DATE,
                                            WWIN_COMP_DEPT,
                                            WWIN_COMP_NAME,
                                            WWIN_WASTE_TYPE,
                                            WWIN_WWGR_ID,
                                            WWIN_COMPONENT_NAME )
                                       VALUES (
                                            SAPP_SEQ.nextval,
                                            nComponentId,
                                            0,
                                            0,
                                            fInDateOpeningQty,
                                            fInDateOnHandQty,
                                            TO_DATE(dInDate, 'DD-MON-YY'),
                                            vCompDept,
                                            vCompName,
                                            vWasteType,
                                            nGroupId,
                                            vComponentName );     
                                  --END IF;
                             END IF;               
                        CLOSE InDate_Rec_Exist;
                        EXIT WHEN Day_Before_Fail_Inv_Bal%NOTFOUND;
                   END LOOP;
              CLOSE Day_Before_Fail_Inv_Bal;
         COMMIT;          
         END Inventory_Calculation;
    END Ewaste_Inventory_Recovery;
    -K- said
    What exactly do you want to automate? The program can automatically detect failure when the process fail, as you see my code, i need to manually key in the parameter date for Inventory_Recovery (vFromDate VARCHAR2, vToDate VARCHAR2) when i recover the job.
    What do you mean by recovering?Recover the inventory because the process/job has downtime or something.....

  • PSADELETE process failure due to Internal Session Terminated.

    Hi,
    We have a PSADELETE process in Process chain which failed because of Internal Session Terminated error.
    Now when i am trying to Repeat the process it is giving message Cannot activate job BI_PROCESS_PSADELETE (return code 8)
    and the process is not starting again.
    Please guide me the solution.
    Thanks
    Singh

    Can you check for more details in SM37 for the cancelled job log .
    Do you have authorization to run 'repeat step ' ?
    or display psadelete variant - identify the infopack/psa tables->  u can delete manually psa requests
    Edited by: Srinivas on Jul 18, 2010 5:22 PM

  • Silent ARCH process failure

    Our production OLTP (10.1.0.3) has two archivelog destinations, one of which is on a remote physical standby. This afternoon as ARC1 was finishing writing a log to the standby destination, the standby server suffered a hardware emergency and rebooted itself.
    When the standby came back I restarted replication and the archivelog it had started applying before the reboot continued, finished, and then logfile application stopped. Investigation showed that the primary had stopped shipping archivelogs over to the remote destination. In fact, all archival activity had stopped on the primary.
    I was able to force log switches, and checkpoints were being reported in the alert log, but no archivelogs were being created. log_archive_min_succeed_dest is set to 1, so this behavior was blatantly illegal. Stranger yet, both ARC0 and ARC1 were still sitting in the process list. No errors or trace files were ever reported in the alert log. I added some redo logs as a temporary fix and to give the netops people time to bring the website down gracefully, and then I bounced the database.
    The database hung while dismounting. I noticed ARC1 hanging out there in the process list so I killed it, after which the shutdown proceeded normally. Upon startup, the missing archivelogs were created during instance recovery and both ARCH processes resumed normal activities.
    It's a little frightening that an essential service like ARCH could die without any errors being reported, and if I had not just happened to be poking around the redo logs could easily have filled up and brought the website to its knees. Has anyone else ever witnessed such bizarre behavior? My best guess is that the hardware event on the standby "did something" to ARC1 and shut it down, but I don't see how ARC0 could have been affected by that as well.

    Since you can see the panel, the web client process is running on remote computer. The "X" and error message mean the communication between the web client and the server process has problem. This may be the networking problem, or the configuration problem.
    Take a look at this KB. Do you get the same error message? Try to ping the server machine from the web client machine.
    http://digital.ni.com/public.nsf/allkb/DFF87FABEE7393B586256945007961FA?OpenDocument
    Also refer to this KB.
    http://digital.ni.com/public.nsf/websearch/93D8E67CDB4F930686256F990067B3ED?OpenDocument
    Is there a firewall on your computer?
    By the way, you can develop both server process and client process on the same machine and test the communication. But you can't run the web client on the same machine, because Lookout webclient player can't be installed with Lookout dev/runtime server at the same time. So, the web client has to be running on remote machine.
    The web server can be on the same machine with Lookout server.
    Ryan Shi
    National Instruments

Maybe you are looking for