Error in Upgrade for Workbooks from 3.X to 7.0

Hi guys....i hope somebody could help me with this.....i have my new 7.0 system its an upgrade of 3.X, and i have a very strange problem....when i open workbooks in BEx Analyzer 7.0 a pop up message is shown that said the workbooks will be upgraded to 7.0 i click ok and execute the workbook, then i close the workbook and open again the same workbook i have again the popup for migration.....i see that the modification date didnt change.....this is very strange....and only affects some workbooks....and its not an authorization problem....my user have SAP_ALL .....
Regards

Hello Oscar,
Every workbook that was created with the BW 3.x system, when you open it in the new BI 7 system, the system will prompt that message for migration.
But only after you save the workbook (that you open with BI 7) in the BI 7 Analyzer is the workbook really saved. If you don't save it, it will continue to show that message and you'll continue to have it in version 3.X
Also be aware that after you migrate (save in BI 7 version) the workbook will no longer be executed any more in the BW 3.x version, only in BI 7.
Diogo.

Similar Messages

  • ORA-03113: Error while upgrading the Database from 11.1.0.6 to 11.1.0.7

    Hi,
    I am trying to upgrade the database from 11.1.0.6 to 11.1.0.7 on OEL operating system.
    After applying the patch "6890831" when trying to start the database using "Startup Upgrade" command I am getting the below error.
    ORA-03113: end-of-file on communication channel
    Process ID: 20826
    Session ID: 170 Serial number: 3
    I am getting the same error when trying to create the new database using "DBCA".
    Please provide me the probable outcomes.
    Thanks
    Amith

    Below entries found in alert_orcl.log file
    MMNL started with pid=15, OS id=20571
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = /u01/app/oracle
    Thu Dec 03 20:11:11 2009
    ALTER DATABASE MOUNT
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_mman_20557.trc:
    ORA-27103: internal error
    Linux-x86_64 Error: 11: Resource temporarily unavailable
    Additional information: -1
    Additional information: 1
    MMAN (ospid: 20557): terminating the instance due to error 27103
    Instance terminated by MMAN, pid = 20557
    Below entries found in the Trace file generated
    error 27103 detected in background process
    ORA-27103: internal error
    Linux-x86_64 Error: 11: Resource temporarily unavailable
    Additional information: -1
    Additional information: 1
    *** 2009-12-03 20:11:14.727
    MMAN (ospid: 20557): terminating the instance due to error 27103

  • Error Message "waiting for response from user"

    When some people invite me to chat on Ichat, they get an error message saying "waiting for response from user."  On my end, I never get the invite.  Other people are able to invite me without any problem.  How do I fix this?  Is the problem on my end? 
    Thank you!

    Hi,
    I can see now where the issue is.
    A Jabber Buddy list can only accept Jabber Buddies.
    A Buddy List that Logs into AIM such as your @Me.com name can only add Valid AIM Names to it as Buddies.
    The main problem is that both Jabber IDs and AIM names can have the @symbol on them and look like email addresses.
    Example Jabber IDs
    Example "AIM " Names
    [email protected]
    ralphjonhsr  (No @)
    [email protected]
    [email protected]  (Apple ID type)
    [email protected]
    [email protected] (Apple ID type)
    any Facebook name
    [email protected] (Email registered with AIM)
    So your Jabber Buddy List will find that there is No (@)me.com Jabber server and say the message cannot be delivered.
    The AIM (@Me.com) Buddy never gets the Request for Authorisation for the same reason and the auto response of adding An ID/Name to Send a Message to starts iChat wanting that person to Accept or Decline being a Buddy- which they cannot do - so you get the name with the "Waiting for..." message.
    Either everyone gets a Jabber ID or everyone gets a Valid AIM Name.
    8:39 PM      Friday; October 28, 2011
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb( 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • Error while upgrading SRM portal from 7.01 to 7.02

    Hi All,
    We are in process of upgrading SRM Java from 7.01 to 7.02. While JSPM was running 250GB of trace files (around 29317 files) have been written under D:\usr\sap\SJ7\JC01\j2ee\cluster\server0 and we are forced to stop JSPM and complete SAP instance.
    As soon as we start the instance with minutes 1GB trace files are written. All these files are dev_jrfc_xxxxx.trc.
    All these files have single error repeated continuously, kindly let us know how to resolve this issue.
    Error file opened at 20110706 102426 Eastern Daylight Time Rel 7.01.3 (2008-10-28) [710.234]
    Error thrown [Wed Jul 06
    10:26:12,128]:Error in RequestDispatcher.DispatcherWorker.run() java.lang.UnsatisfiedLinkError: nativeSAP_CMLISTEN
                at com.sap.mw.rfc.driver.CpicDriver.nativeSAP_CMLISTEN(Native Method)
                at com.sap.mw.rfc.driver.CpicDriver.SAP_CMLISTEN(CpicDriver.java:1137)
                at com.sap.mw.rfc.driver.RfcTypeRegisterCpic.waitForRequest(RfcTypeRegisterCpic.java:593)
                at com.sap.mw.rfc.api.RfcApi.RfcWaitForCpicRequest(RfcApi.java:1262)
                at com.sap.mw.jco.MiddlewareJRfc.waitForRequest(MiddlewareJRfc.java:641)
                at com.sap.mw.jco.RequestDispatcher$DispatcherWorker.run(RequestDispatcher.java:159)
                at java.lang.Thread.run(Thread.java:534)
    Regards,
    Siva.

    Hi Siva,
    it seems to me that you have heavy log archiving on the system. You can switch the log severity of all (or at least most) of the locations to the default. In addition, switch off the archiving of old log files:
    In the visual configtool navigate to Server -> Services -> Log Configurator -> Properties tab and set the value of the ArchiveOldLogFiles to "OFF".
    Also, using the Visual Administrator -> Services -> Log Configurator -> restore to default all the trace levels.
    Regards,
    Jonas Cella

  • ECC 6 Upgradation for PM from 4.7?

    Dear SAPINETS,
    My system is going for upgaration from 4.7 to 6.0 and i have to perform testing. I need to know what are the test i should perform to know that upgradation is succesful.
    Regards,

    hi,
    you have to test the entire PM Business Processes.

  • Error while upgrading the patch from RMS 13.1.1.1 to RMS 13.1.1.2

    Hi,
    While upgrading the rms dbschema from 13.1.1.1 to RMS 13.1.1.2 we are getting the following error update ALC_FREIGHT_COST table or view doesnt exist.
    We have checked the data model of rms 13.1.1 and rms 13.1.2 and we couldnt find the table "ALC_FREIGHT_COST."
    So anybody could give suggestions on this.
    Appreciate your help
    Thanks,
    Suresh

    I'd ignore the error for the moment and file an SR with OracleSupport to make them aware of the issue and release a better script - all of this assuming that your 13.1.1 starting point is valid and correctly installed.
    Additionally you can locate the SQL upgrade script that is actually trying to do something on the mentioned table, and grasp what it is trying to achieve and how relevant that is for you.
    The table exists in our 13.0.3 setup. The release notes of 13.1.0 mention a rework of cost component functionality, so seems like it was deprecated in that release.
    Best regards,
    Erik

  • Error while upgrading NW04s ABAP from sp7 to sp8

    Hi,
    I installed NW04s in my system and its ABAP stack is upgraded to sp7. When i was upgrading its SAP_BASIS support package to sp8, i got the following error.
    Error in phase: IMPORT_PROPER
    Reason for error: TP_BUFFER_INCONSISTENCY
    Return code: 0008
    Error message: Pkgs. in queue don"t exist in the tp buffer (e.g. SAPKB70008)
    This phase imports all Repository objects and table entries. It may terminate for the following reasons:
    ○       TP_INTERFACE_FAILURE: The tp interface could not be called.
    ○       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
    ○       TP_STEP_FAILURE: A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import log.
    If a tp step 6, N or S is in the termination message, it is a step independent of the transport request. The corresponding logs are contained in the log overview under the node Import steps not specific to the transport request.
    You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):
    tp step 6: P<YY><MM><DD>.<SID>
    tp step N: N<YY><MM><DD>.<SID>
    tp step S: DS<YY><MM><DD>.<SID>
    To display these files, run report RSPUTPRT or call transaction AL11.
    Can anyone help me to resolve this problem?
    Thanks in advance.

    I have the similar problem to yours with tp_buffer_consistency at the xpra_phase when I was runing SAINT on a SAP R/3 Service Tool (RTCTOOL) with SAPKITAR19.
    Shall you confirm what you have solved your problem are:
    1) You have removed registers from the file /usr/sap/trans/buffer/SID which contains the troubled register, an example SAPKNNNNNN. First make a backup of that file before removing registers.
    2) You have removed registers from the two tables: PAT01 (PATCH=SAPKNNNNNN), and PAT03 (PATCH=SAPKNNNNNN)
    3) Invoke the trx SAINT
    4) Installation package-->load package --> from application server
    5) Select the uploaded SP and click the button Continue.
    6) Anything else.
    Appreciate in hearing from your input.
    Rodolfo

  • Error while Upgrading to PL10 from 2007A

    I got an error at the last database during the 'Pre-Upgrade Check'. The error says...
    Integrity check failed due to non-consecutive TransSeq on OINM for the same document row [SAP Note: 1344231].
    The log file says....
    09/11/2010  14:18:43:154027      UpgradeWizard     Note               I     Technical     ID: 27 # #     MID=-1     BOID=-1     BO=     UserID=     G:\SAP_8.8_Upgrade_Files\88PL10_Upgrade\Wizard\Upgrade.exe     Version=8.80.229     Area=     PID=5296     TID=152     D:\depot\BUSMB_B1\8.8_REL\SBO\8.8_REL\Application\SolutionPatch\Component\Logger.cpp     105
    09/11/2010  14:18:43:154027      UpgradeWizard     Note               I     Technical     Check: OINM integrity check for having same document row with non-consecutive TransSeq in OINM # #     MID=-1     BOID=-1     BO=     UserID=     G:\SAP_8.8_Upgrade_Files\88PL10_Upgrade\Wizard\Upgrade.exe     Version=8.80.229     Area=     PID=5296     TID=152     D:\depot\BUSMB_B1\8.8_REL\SBO\8.8_REL\Application\SolutionPatch\Component\Logger.cpp     105
    09/11/2010  14:18:43:154027      UpgradeWizard     Note               I     Technical     Desc: (27) Check OINM integrity if exists same document line with non-consecutive TransSeq in OINM; SAP Note: 1344231 # #     MID=-1     BOID=-1     BO=     UserID=     G:\SAP_8.8_Upgrade_Files\88PL10_Upgrade\Wizard\Upgrade.exe     Version=8.80.229     Area=     PID=5296     TID=152     D:\depot\BUSMB_B1\8.8_REL\SBO\8.8_REL\Application\SolutionPatch\Component\Logger.cpp     105
    09/11/2010  14:18:43:154027      UpgradeWizard     Note               I     Technical     Begin time: 20101109 2:18:38PM # #     MID=-1     BOID=-1     BO=     UserID=     G:\SAP_8.8_Upgrade_Files\88PL10_Upgrade\Wizard\Upgrade.exe     Version=8.80.229     Area=     PID=5296     TID=152     D:\depot\BUSMB_B1\8.8_REL\SBO\8.8_REL\Application\SolutionPatch\Component\Logger.cpp     105
    09/11/2010  14:18:43:247777      UpgradeWizard     Note               I     Technical     Same document line with non-consecutive TransSeq exist in OINM # #     MID=-1     BOID=-1     BO=     UserID=     G:\SAP_8.8_Upgrade_Files\88PL10_Upgrade\Wizard\Upgrade.exe     Version=8.80.229     Area=     PID=5296     TID=152     D:\depot\BUSMB_B1\8.8_REL\SBO\8.8_REL\Application\SolutionPatch\Component\Logger.cpp     105
    09/11/2010  14:18:43:247777      UpgradeWizard     Note               I     Technical     End time: 20101109 2:18:38PM # #     MID=-1     BOID=-1     BO=     UserID=     G:\SAP_8.8_Upgrade_Files\88PL10_Upgrade\Wizard\Upgrade.exe     Version=8.80.229     Area=     PID=5296     TID=152     D:\depot\BUSMB_B1\8.8_REL\SBO\8.8_REL\Application\SolutionPatch\Component\Logger.cpp     105
    09/11/2010  14:18:43:247777      UpgradeWizard     Note               I     Technical     Test result: Error # #     MID=-1     BOID=-1     BO=     UserID=     G:\SAP_8.8_Upgrade_Files\88PL10_Upgrade\Wizard\Upgrade.exe     Version=8.80.229     Area=     PID=5296     TID=152     D:\depot\BUSMB_B1\8.8_REL\SBO\8.8_REL\Application\SolutionPatch\Component\Logger.cpp     105
    Can anyone help. I tried to look up many places for this SAP note or on the details of the error, but no clue.

    Hi,
    Recommended patch level upgrade is SAP B1 8.8 SP00 PL15. you can read the info from this thread:
    Upgrade from 2007A PL47 to 8.8 PL16
    if you need fast, you can download it and upgrade your 2007A version to the PL. I am not sure if the PL15 can be solved the current upgrade problem but you may try. if not success, you have to log message to SAP support as Gordon's suggested.
    JimM

  • OCI-21500 error when upgrading Oracle database from 10.2 to 11.2

    We have been running some test upgrades from 10.2 to 11.2 before running it on our production server. During one of these tests, the post-upgrade script utlu112s.sql generated the following output:
    Oracle Database 11.2 Post-Upgrade Status Tool 12-12-2011 21:12:54
    Component Status Version HH:MM:SS
    Oracle Server
    . VALID 11.2.0.2.0 00:53:59
    JServer JAVA Virtual Machine
    . VALID 11.2.0.2.0 00:31:25
    Oracle Real Application Clusters
    . INVALID 11.2.0.2.0 00:00:03
    Oracle Enterprise Manager
    . VALID 11.2.0.2.0 00:33:44
    Oracle XDK
    . VALID 11.2.0.2.0 00:13:00
    Oracle Text
    . VALID 11.2.0.2.0 00:05:19
    Oracle XML Database
    . OCI-21500: internal error code, arguments:
    [KODDBG_PUSH_80IMGPTR:dbgecPushPtr
    . failed], [0], [0xFFFFFFFF7FFF55E8], [0xFFFFFFFF7F22E2B8], [1], [], [], []
    . OCI-21500: internal error code, arguments:
    [KODDBG_PUSH_80IMGPTR:dbgecPushPtr
    . failed], [0], [0xFFFFFFFF7FFF55E8], [0xFFFFFFFF7F22E2B8], [1], [], [], []
    . OCI-21500: internal error code, arguments:
    [KODDBG_PUSH_80IMGPTR:dbgecPushPtr
    . failed], [0], [0xFFFFFFFF7FFF55E8], [0xFFFFFFFF7F22E2B8], [1], [], [], []
    . VALID 11.2.0.2.0 00:20:49
    Oracle Database Java Packages
    . VALID 11.2.0.2.0 00:00:53
    Oracle Multimedia
    . VALID 11.2.0.2.0 00:13:00
    Spatial
    . VALID 11.2.0.2.0 00:20:00
    Gathering Statistics
    . 00:24:39
    Total Upgrade Time: 03:37:02
    PL/SQL procedure successfully completed.
    As far as we can tell, everything appears to be up and running, but the OCI-21500 internal errors are troubling. I have not been able to find anything on metalink regarding this error, and I am wondering if anyone else has come across it before. Thanks for your help!
    Simeon

    The OS is Solaris 10 (SunOS 5.10) and the source DB version was 10.2.0.4. We are running the upgrade manually (NOT with DBUA). The upgrade log does not have any ORA-xxxx errors, but it does show a few instances of the same error, such as this example:
    SQL> desc XDB.XDB$RESOURCE_T;
    ERROR: OCI-21500: internal error code, arguments: [KODDBG_PUSH_80IMGPTR:dbgecPushPtr failed], [0], [0xFFFFFFFF7FFF55E8], [0xFFFFFFFF7F22E2B8], [1], [], [], []
    Regards,
    Simeon

  • Timed Out Error while waiting for response from DB Procedure

    Hi Gurus,
    We are encountering a problem in our production environment. The system is implemented using AIA foundation pack 2.5 on SOA suite 10.1.3.4.
    We have a BPEL process A which calls an ESB Service which inturn calls BPEL Process B. In process B, we have a DB procedure call which waits for a response from
    a DB procedure. The procedure doesn't reply on time and Process B remains in waiting state to get the response from DB Procedure wherein Process A errors out by showing as "Timed Out Error".
    This issue is intermittent and we have already increased transaction-time outs in transaction-manager.xml to 7200 and ejb-orion-jar.xml to 3600.
    When we encountered this problem, we found out that there are too many connections open and when we bounced the server, everything was restored to nornal but as it is a production env. we can't do it over and over again.
    We have 2 nodes each having max connections as 100 and min. as 0.
    Is there a limit to max no. of connections or can we do something in DB side to ensure that it doesn't happen again ?
    Please suggest.
    Thanks,
    Vikas Manchanda

    Hi Gurus,
    We are encountering a problem in our production environment. The system is implemented using AIA foundation pack 2.5 on SOA suite 10.1.3.4.
    We have a BPEL process A which calls an ESB Service which inturn calls BPEL Process B. In process B, we have a DB procedure call which waits for a response from
    a DB procedure. The procedure doesn't reply on time and Process B remains in waiting state to get the response from DB Procedure wherein Process A errors out by showing as "Timed Out Error".
    This issue is intermittent and we have already increased transaction-time outs in transaction-manager.xml to 7200 and ejb-orion-jar.xml to 3600.
    When we encountered this problem, we found out that there are too many connections open and when we bounced the server, everything was restored to nornal but as it is a production env. we can't do it over and over again.
    We have 2 nodes each having max connections as 100 and min. as 0.
    Is there a limit to max no. of connections or can we do something in DB side to ensure that it doesn't happen again ?
    Please suggest.
    Thanks,
    Vikas Manchanda

  • Error while upgrading to SP3 from SP1 Exchange 2010

    Here is the error I get when trying to upgrade to SP3, it fails when it gets to the mailbox role.
    Summary: 8 item(s). 5 succeeded, 1 failed.
    Elapsed time: 00:34:21
    Language Files
    Completed
    Elapsed Time: 00:11:05
    Restoring services
    Completed
    Elapsed Time: 00:00:02
    Languages
    Completed
    Elapsed Time: 00:05:08
    Hub Transport Role
    Completed
    Elapsed Time: 00:07:35
    Client Access Role
    Completed
    Elapsed Time: 00:04:56
    Mailbox Role
    Failed
    Error:
    The following error was generated when "$error.Clear(); 
              if ($RoleIsDatacenter -ne $true)
                if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
                  # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
                  get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
                  $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
                  $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
                  $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0) 
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if($dbs.Length -ne 0) 
                      $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                      if ($mbxUser.Length -ne 0) 
                        enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                else
                  write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox. Property Name: Database".
    Database is mandatory on UserMailbox. Property Name: Database
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
    Error:
    The following error was generated when "$error.Clear(); 
              if ($RoleIsDatacenter -ne $true)
                if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
                  # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
                  get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
                  $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
                  $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
                  $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0) 
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if($dbs.Length -ne 0) 
                      $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                      if ($mbxUser.Length -ne 0) 
                        enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                else
                  write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox. Property Name: Database".
    Database is mandatory on UserMailbox. Property Name: Database
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
    Elapsed Time: 00:05:32
    Management Tools
    Cancelled
    Finalizing Setup
    Cancelled

    Hi,
    Glad to know that we have solved the problem.
    Thanks for your sharing.
    Have a nice day : )
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Photoshop Error When Sending for Edit from Bridge or Lighroom

    When I attempt to send an image from Bridge CS5 or Lightroom using the Edit In or Open With commands Photoshop begins to launch but then displays the error message "Adobe Photoshop CS5 has encountered a problem and needs to close." If Photoshop is open and I attempt to open Bridge I get the same error message for Bridge.

    Thanks theFurryOne for your response.
    I do see my source in the data_source view.
    As for the Caused by:
    I see:
    Caused by:java.lang.NullPointerException
    at oracle.dbtools.raptor.navigator.net.DBURLStreamHandlerFactory.fetchSource(DBURLStreamHandlerFactory.java.213)
    ...............................................DBURLfileSystemHelper...
    at oracle.ide.net.URLFileSystem.createReader(URLFileSystem.java:1630)
    at oracle.ide.model.TextNode.createreader(TextNode.java:1680)
    .....................................loadTextBuffer...
    .....................................openImpl....
    ...48 more (these do not appear in the details window due to the number of exceptions prior to the caused by line)
    SQL Developer version
    .....About tab
    Version 2.1.1.64
    Build Main-64.45
    .....Version tab
    Java Platform 1.6.0_11
    Oracle IDE 2.1.1.64.45
    Versioning Support 2.1.1.64.45
    Edited by: amosgreg on Sep 2, 2010 4:58 AM

  • Time Out Error while waiting for response from DB Procedure

    Hi Gurus,
    We are encountering a problem in our production environment. The system is implemented using AIA foundation pack 2.5 on SOA suite 10.1.3.4.
    We have a BPEL process A which calls an ESB Service which inturn calls BPEL Process B. In process B, we have a DB procedure call which waits for a response from
    a DB procedure. The procedure doesn't reply on time and Process B remains in waiting state to get the response from DB Procedure wherein Process A errors out by showing as "Timed Out Error".
    This issue is intermittent and we have already increased transaction-time outs in transaction-manager.xml to 7200 and ejb-orion-jar.xml to 3600.
    When we encountered this problem, we found out that there are too many connections open and when we bounced the server, everything was restored to nornal but as it is a production env. we can't do it over and over again.
    We have 2 nodes each having max connections as 100 and min. as 0.
    Is there a limit to max no. of connections or can we do something in DB side to ensure that it doesn't happen again ?
    Please suggest.
    Thanks,
    Vikas Manchanda

    Hi Anuj,
    I don't think it is a problem with connection reaching to max numbers because this issue is coming on very intermittent basis.we don't have any other processes using
    the same connection pool and this issue is coming even when there is no load on the server. This is recent trace from the production environment. Also i don't have any thing called "abandoned-connection-pool" in my data-sources.xml.
    <2011-07-07 13:09:16,101> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
    com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
    at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:109)
    at sun.reflect.GeneratedMethodAccessor113.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
    at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
    at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
    at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
    at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
    at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
    at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
    at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
    at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
    at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:194)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
    at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:576)
    at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:465)
    at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:134)
    at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java)
    Please suggest.
    Thanks,
    Vikas Manchanda

  • Timeout error (code 6101) for acquisition from MODBUS instrument

    I am experiencing a problem which other users have reported, but for which little useful information has been posted:
    I am trying to acquire data from an instrument using MODBUS RTU protocol.  The code works as desired for a while, but will intermittently stop executing and give a timeout error, code 6101.  This code seems to be associated with the MB Serial Master Query sub VI.  In the past, I was getting this error as a result of RF noise corrupting the signal in the USB connection to the instrument.  Removing the USB cable from the noisy environment eliminated the problem.  I am now having the problem with an RS 485 line in the noisy environment, which should be very stable in noisy environemnts. 
    My question:  is there a coding trick i can use to reconnect in the event that a corrupt signal occurrs (or some other problem which results in the intermittent appearence of the error 6101)?   I've increased the timeout value on the MB Serial Master Query sub vi, but this hasn't helped.  Any input is appreciated.  In case it's useful, I've posted a simple version of code which generates the problem. 
    Thanks,
    Paul   
    Attachments:
    Floating point 1.12.vi ‏24 KB
    timeout error1.JPG ‏31 KB

    Thanks for your input, Ravens Fan.  I am indeed getting a popup error message with the timeout.  I agree that putting the MODBUS read in its own loop would solve the problem.  However, I'm struggling with trying to figure out how to actually do this.  Should I put the read in a case structure or a while loop?  How do I go about looping back to re-execute the read statement?  I think so called "state machine architecture" seems to be where I should be going. Some example code would be greatly appreciated. 
    paul  

  • Error while upgrading 10g AS from 10.1.2.0.2 to 10.1.2.3

    Hi All,
    I am in process of doing 10g AS integration with 11.5.10.2.
    As per documentation i have seen that 10g AS has to upgrade
    My 10g AS version is 10.1.2.0.2
    and my database version is 10.1.0.4.2
    I have downloaded patch p5983622_10123_LINUX.zip
    and first tried to upgrade infrastructure home
    but while upgrading it says
    oracle universal installer has detected that your database is version 10.1.0.4.2 before you can continue you must apply a required database patch set.
    But in documentation i have seen
    Supported Database Releases
    The portal schema may be residing in an OracleAS Metadata Repository, or in a customer database. The database in which the portal schema resides must be one of the following supported releases:
    Oracle Database 10g (10.1.0.4.2) or later
    Please let me know what should i do now
    Thanks in advance
    Regards,
    Bhanu Chander.

    Hi ,
    $ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log
    09/09/24 06:24:21 portal: Max URL _debug value '1'.
    09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Portal Servlet Context Listener destroy started
    09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service destroy started
    09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service Config destroy started
    09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service Config destroy finished, 0 ms
    09/09/24 06:36:34 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service destroy finished, 1003ms
    09/09/24 06:36:34 portal: [module=PortalServletContextListener, thread=Shutdown] Portal Servlet Context Listener destroy finished, 1004ms
    09/09/24 06:36:34 portal: Page Servlet destroy started at 1253788594974 millis
    09/09/24 06:36:34 portal: Page Servlet destroy ended at 1253788594977 millis, duration was 3 millis
    09/09/24 06:36:34 portal: [module=RepositoryServlet, thread=Shutdown] Repository Servlet destroy started
    09/09/24 06:36:34 portal: RepositoryServlet: destroy
    09/09/24 06:36:34 portal: [module=RepositoryServlet, thread=Shutdown] Repository Servlet destroy finished, 0ms
    09/09/24 06:36:34 portal: [module=PortalServlet, thread=Shutdown] Portal Servlet destroy started
    09/09/24 06:36:34 portal: PortalServlet: destroy
    09/09/24 06:36:34 portal: [module=PortalServlet, thread=Shutdown] Portal Servlet destroy finished, 0ms
    09/09/24 06:36:34 portal: Stopped
    09/09/24 06:36:34 Stopped (Shutdown executed by jazn.com/admin from 127.0.0.1 (localhost.localdomain))
    09/09/24 08:35:53 Started
    09/09/24 08:36:13 portal: ServletLogger - Logging level: 2
    09/09/24 08:36:13 portal: [module=PortalServletContextListener, thread=Orion Launcher] Initializing Portal Servlet Context Listener
    09/09/24 08:36:13 portal: jsp: init
    09/09/24 08:36:13 portal: Started
    09/09/24 08:38:37 portal: PortalServlet: init
    09/09/24 08:38:37 portal: ServletLogger - Logging level: 2
    09/09/24 08:38:37 portal: [module=PortalServlet, thread=AJPRequestHandler-ApplicationServerThread-5] Initializing Servlet: PortalServlet
    09/09/24 08:38:38 portal: RepositoryServlet: init
    09/09/24 08:38:38 portal: ServletLogger - Logging level: 2
    09/09/24 08:38:38 portal: [module=RepositoryServlet, thread=AJPRequestHandler-ApplicationServerThread-5] Initializing Servlet: RepositoryServlet
    09/09/24 08:38:39 portal: page: init
    09/09/24 08:38:39 portal: Cache: Cache is enabled.
    09/09/24 08:38:39 portal: Pool: Initialized with the following pools : [oracle.webdb.pool.http.HTTPConnectionKey]
    09/09/24 08:38:39 portal: Created mobileXML to HTML stylesheet object
    09/09/24 08:38:39 portal: PPE version : 10.1.2.0.2 (11082005)
    09/09/24 08:38:39 portal: Tuning parameter values : poolSize(Fetchers)=25[default=25] : minTimeout(MinTimeout)=5s[default=5s] : requesttime(DefaultTimeout)=15s[default=15s] : stall(MaxTimeout)=65s[default=65s] : queueTimeout(QueueTimeout)=10s[default=10s] maxParallelPortlets=20[default=20] maxParallelPagePortlets=10[default=10]
    09/09/24 08:38:39 portal: Max URL _debug value '1'.
    what do you see when you get the error on trying to login.
    Same error
    An error occurred while processing the request. Try refreshing your browser. If the problem persists contact the site administrator

Maybe you are looking for

  • Error while creating a PO - Please select Purchasing Organization from Head

    Hi All, We have recently upgraded to R12 from 11.5.9 in Test environment. Due to upgrade all the purchasing setup which was there in 11.5.9 is now available in R12. We are creating a Standard Purchase Order. I have entered the header level details wi

  • Calling a reentrant sub-vi from a reentrant vi

    I need to communicate with multiple identical instruments on different serial ports simultaneously. I have a set of vis that are the building blocks for communication, and they are all reentrant. I then have a top-level reentrant vi that is called mu

  • Crash at Startup / preferences not loaded

    Hi there, Been having this problem for a week now. Logic's been crashing at startup a lot. Some time though, Logic starts up normally except for an error message at startup saying that the preferences are not loaded completely and advising me not to

  • HT3702 Assistance at apple for allowing card verification

    I can't buy ringtones or download games! There is a problem using my contact! It says for assistance go to apple.com

  • Type Tool/black document window issue.

    When I use the type tool in PS CC, the document goes black and becomes unuseable, what's up? (WIN 8) I found some mention of flickering problems in WIN 7 but no changes in my graphics performance software settings helped...