Error while upgrade oracle database from 9.2.0.6 to 10.2.0.1

updating the correct ORACLE_HOME and PATH variables
and following the Oracle10 R2 upgrade guide,
oracle.xxxxxx: <10.2.0.1/dbs> sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Nov 8 10:53:39 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup upgrade pfile=initCB6ES4.ora
ORA-29702: error occurred in Cluster Group Service operation
SQL>

Verify if the process LMON is active.

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

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

Error while upgrading Oracle Portal to 10.1.4.

While upgrading Oracle Portal to 10.1.4 , I am getting the following error.
Error: Database version 9.0.1.5.1 is not supported
MRUA detected an error at C:\oracleportalupgrade\mrua_051020\mrua\mrua.pl line 212.
Please let me know how can I resolve this issue.

There is no WSRP container created as a part of the AS 10.1.2.0.2 or Portal 10.1.4 setup (that means there is no WSRP directory below $ORACLE_HOME/j2ee by derfault).
You need to create a brand new application server container, either in the same oracle home as portal or (as we are doing according to advice from oracle) create a new AS 10.1.2.0.2 AS oracle home for just J2EE (not portal) and then create a container for your WSRP portlets -- we called ours OC4J_WSRP. This is the step that will create a directory under $ORACLE_HOME/j2ee (in our case $ORACLE_HOME/j2ee/OC4J_WSRP).
After you have your new container (OC4J_WSRP), you need to configure this container to support WSRP. First you need to download the "Java Portlet Container for Standards" from http://www.oracle.com/technology/products/ias/portal/pdk.html (this does not come with the Portal 10.1.4 installation).
Download "Download the Java Portlet Container (JSR 168)":
http://download.oracle.com/otndocs/tech/ias/portal/files/portlet-container.zip
This will get you portlet-container.zip.
Extract this zip file. One of the files you will have is wsrp-install.jar.
Then log into the box where your new OC4J_WSRP container is setup (it is really important that you have not changed the default configuration of this new app server container or deployed any applications before running the next step) and ...
1. copy wsrp-install.jar into $ORACLE_HOME/j2ee/OC4J_WSRP
2. cd $ORACLE_HOME/j2ee/OC4J_WSRP
3. run "java -jar wsrp-install.jar"
4. restart your app server that contains OC4J_WSRP ("opmnctl stopall; opmnctl startall")
Now you have a app server container that you can deploy your JSR-168/WSRP portlets to! Just deploy your ear files to this OC4J_WSRP.

Steps to upgrade Oracle database from 11.2.0.3.8 to 11.2.0.4.0

Hi Support,
Could anyone please provide the steps to upgrade Oracle Database EE from 11.2.0.3.8 to 11.2.0.4.0.
Thanks
Imtiyaz

You will need to install 11.2.0.4 into a new ORACLE_HOME, apply the latest 11.2.0.4 PSU patch to the new ORACLE_HOME (see MOS Doc 1454618.1) and then follow the steps in the Upgrade Guide
http://docs.oracle.com/cd/E11882_01/server.112/e23633/upgrade.htm#UPGRD003
see MOS Doc 1189783.1

Upgrade Oracle Database From Release 11.1.0.6.0 to Release 11.2.0.1.0

Dear Experts ,
I need the procedure to do the upgrade Oracle DB From Release 11.1.0.6.0 to Release 11.2.0.1.0
We have RAC Setup, OS windows 2003 R2 Server Service Pack 2
I have 3 instance Epprod, Epval, Mnlptprod
I am using the Same server as an application server as well.
Server Specification
E5540 @ 2.53GHz
2.53 HGz, 15.9 GB of RAM
Please your help highly appreciated

Hi,
Please refer the following links,which may help you in upgradation:
http://www.oracle.com/technetwork/database/upgrade/best-practices-for-upgrading-11gr2-174946.pdf
http://docs.oracle.com/cd/E14072_01/server.112/e10819/intro.htm#i1008321
http://www.ludatou.com/?p=287
http://www.oracledba.org/upgrade/Upgrade_11gR1_RAC_to_11gR2_RAC.htm

Error while restoring oracle database by using brrestore command

Dear Experts ,
please check and give me your suggesitions on my issue
now we are trying to restore my oracle database from prd to quality
by using brrestore command
and it is terminated with an error at persent 30 %
error log
BR0278E command output of 'LANG=C dd ibs=64k if=/dev/rmt/ocbn of=/oracle/QAS/sapdata1/sr1_11/sr1.data11';
BR0359E Restore of /oracle/QAS/sapdata1/sr1_11/sr1.data11 from /dev/rmt/ocbn failed due to previous errors
BR0406I End of file restore
BR0404I brrestore terminated with errors
Regards

Ershad Ahmed wrote:
Hi Swathi,
>
> Before performing the restore i would always restore control file from the backup to make sure that restore is working
Hi,
he already restored 30%, so I think we can safely assume at least some stuff did work.
Allthough I agree that since the controlfile is saved last, this is a good test.
Seems to be either a dirty tape (clean drive, repeat) or a faulty backup ( ugh ).
When you retry after cleaning, you can use -f (fillup) to save the restore from retrieving the files it allready got.
Check the initSID.sap for the backup & restore commands and esp. the bs= / ibs= / obs= options.
Volker

Patch Number to Upgrade Oracle Database from 11.1.0.6.0 to 11.1.0.7.0

Hi,
Please let me know the patchset number which can be used to upgrade Oracle Datbase from 11.1.0.6.0 to 11.1.0.7.0
Thanks,
Salih KM

Hi,
I checked the read me of 7631980 and got the information as below.
2.1 Bugs Fixed by This Patch
This patch fixes the following bugs.
h4. 2.1.1 Bugs Fixed for DB 11.1.0.6 Patch 14: 7631980
DB 11.1.0.6 Patch 14 includes all bugs fixed in the 11.1.0.6 patch1 to Patch13. It must be applied on top of the 11.1.0.6 base release or on top of the earlier bundle patch.
For a more descriptive list of the bug fixes included in this bundle patch, refer to Oracle+MetaLink+ Note [560295.1|http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=560295.1].
Please let me know whether 7631980 is the right patch?
Thanks,
Salih KM

Upgrade oracle database from 11.2.0.3 to 11.2.0.4 on RHEL 6

Hello,
There was OS upgrade from RHEL5 to RHEL6 and Oracle 11gR2 ( 11.2.0.3) is running on rhel5, we need to upgrade to 11.2.0.4 on RHEL6.
Do anyone know what are the exact steps to perform this task?
Thanks

Hi Srini,
Thanks for the reply. while i am performing RMAN duplicate target database using active database. I am getting the below errors.
==========================================================================================================
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 08/06/2014 11:48:22
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 20877
Session ID: 1 Serial number: 5
==============================================================================================================
Source database is on RHEL5 and Oracle 11.2.0.3
Target database is on RHEL6 and Oracle 11.2.0.4.
I tried to start the startup the database with upgrade option but i am getting media recovery error.
SQL> startup upgrade;
ORACLE instance started.
Total System Global Area 1603411968 bytes
Fixed Size                  2253664 bytes
Variable Size             603983008 bytes
Database Buffers          989855744 bytes
Redo Buffers                7319552 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u02/oradata/NBFDEV1/system01.dbf'
It would be great if you can help me to fix the issue.
Thanks

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

Error while calling oracle reports from another report

Hello everyone,
I have a problem running oracle reports. In one report I have a button
that calls another report. There is a button for each row of the result
in the first report , and i have used Srw.run_report to call the second
report.
My problem is, when I run the report, at the first time i can push the
button and the second report opens and works correctly. But if i close
the second report and come back to the first one, when i push the
button for a different row ,the second report starts to run but then I
get some oracle errors like table does not exist or... while the first
time the report worked correctly.
It seems that when i close the second report and go back to the first
one, sth happens that changes my session or connection. I don't know
what can be the problem.
By the way, when I log in with the user that owns the tables and has
all the privileges, I don't get this problem. It only occurs when I
use other users ( which have all privileges on all of the tables
needed in the report )
I am using Report Builder 6.0.5 and the DB is Oracle Database 10g.
Can anyone please help me with this problem?
Thanx in Advance.
Maryam.

6.0.5 is not certified against 10g database, so I suggest to upgrade to 6.0.8.26 (6i patch 17) first to see if the problem is gone.

Error while upgrading Oracle SOA 10.1.3.3 to 10.1.3.5

Hi,
Iam trying to upgrade Oracle SOA ver.10.1.3.3 to 10.1.3.5 on a windows server.The following steps were followed.
1. SOA was stopped. Back up of the SOA folder was taken.
2. SOA uses the default Olite database. Connected to the BPEL schema and run the upgrade_10133_10135_olite.sql script.
It errored out in the upgrade process of 10.1.3.3 to 10.1.3.4.
The esb schema upgrade script executed without error. Have any one faced similar issue? or aware of the reason? Please help me out. Thanks in advance.
The following is the log:
SQL> @E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\upgrade_10133_10135_olite.sql
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL> @@upgrade_10133_10134_olite.sql
SQL> Rem
SQL> Rem $Header: bpel/everest/src/modules/server/database/scripts/upgrade_10133_10134_olite.sql /st_pcbpel_10.1.3.1/11 2009/06/03 00:37:24 nverma Exp $
SQL> Rem
SQL> Rem upgrade_10133_10134_olite.sql
SQL> Rem
SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
SQL> Rem All rights reserved.
SQL> Rem
SQL> Rem NAME
SQL> Rem upgrade_10133_10134_olite.sql - <one-line expansion of the name>
SQL> Rem
SQL> Rem DESCRIPTION
SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
SQL> Rem
SQL> Rem NOTES
SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
SQL> Rem
SQL> Rem MODIFIED (MM/DD/YY)
SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
SQL> Rem nverma 04/14/09 - Backport nverma_bug-7171739 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem ramisra 06/05/08 -
SQL> Rem ralmuell 03/28/08 - Sensor schema change for 6819678
SQL> Rem ramisra 03/17/08 - Backport ramisra_bug-6845586 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem atam 03/06/08 - update version
SQL> Rem nverma 01/29/08 - Upgrade script (10.1.3.3.0 to 10.1.3.4.0) for orabpel schema on olite
SQL> Rem database.
SQL> Rem nverma 01/29/08 - Created
SQL> Rem
SQL> SET ECHO ON
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL> ALTER TABLE DLV_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
Table altered
SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
Table altered
SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (CONV_ID VARCHAR2(256))
Table altered
SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
Table altered
SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
Internal Error:thinExecute: Result Communication Failed
SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (MASTER_CONV_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (CONVERSATION_ID VARCHAR2(1000))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (NATIVE_CORRELATION_ID VARCHAR2(1000))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE CUBE_INSTANCE MODIFY (CONVERSATION_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE TASK MODIFY (CONVERSATION_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE WORK_ITEM MODIFY (CUSTOM_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (SUBSCRIBER_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_MESSAGE MODIFY (RES_SUBSCRIBER VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX DDMR_DOCKEY ON DOCUMENT_DLV_MSG_REF(DOCKEY)
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX CI_CUSTOM4 ON CUBE_INSTANCE (MODIFY_DATE)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE WFUserTaskViewGrant ADD ( granteeType VARCHAR2(20), applicationContext VARCHAR2(200) )
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table cube_instance add ( at_count_id integer, at_event_id integer, at_detail_id integer )
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values add error_message_temp clob
Internal Error:AllocStatement: Request Communication Failed
SQL> update activity_sensor_values set error_message_temp=error_message
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop column error_message
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values add error_message clob
Internal Error:AllocStatement: Request Communication Failed
SQL> update activity_sensor_values set error_message=error_message_temp
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop column error_message_temp
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop column error_message_temp
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table fault_sensor_values drop primary key
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values drop primary key
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop primary key cascade
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values add constraint activity_sensor_pk primary key(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values add constraint variable_sensor_pk primary key(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values add constraint variable_sensor_fk1 foreign key(activity_sensor_id, process_instance_id) references activity_sensor_values(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table fault_sensor_values add constraint fault_sensor_pk primary key(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values modify constraint activity_sensor_pk enable
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values modify constraint variable_sensor_pk enable
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values modify constraint variable_sensor_fk1 enable
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table fault_sensor_values modify constraint fault_sensor_pk enable
Internal Error:AllocStatement: Request Communication Failed
SQL> drop index activity_sensor_values_indx
Internal Error:AllocStatement: Request Communication Failed
SQL> create index activity_sensor_values_indx on activity_sensor_values(process_instance_id, sensor_name, action_name)
Internal Error:AllocStatement: Request Communication Failed
SQL> update version set guid = '10.1.3.4.0'
Internal Error:AllocStatement: Request Communication Failed
SQL> update version_server set guid = '10.1.3.4.0'
Internal Error:AllocStatement: Request Communication Failed
SQL> COMMIT
Internal Error:AllocStatement: Request Communication Failed
SQL> @@upgrade_10134_10135_olite.sql
SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
SQL> Rem All rights reserved.
SQL> Rem
SQL> Rem NAME
SQL> Rem
SQL> Rem DESCRIPTION
SQL> Rem
SQL> Rem NOTES
SQL> Rem <other useful comments, qualifications, etc.>
SQL> Rem
SQL> Rem MODIFIED (MM/DD/YY)
SQL> Rem vnanjund 07/09/09 - Backport vnanjund_bug-8655721 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mchinnan 07/07/09 - Backport mchinnan_bug-8636836 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem vnanjund 07/06/09 - olite fix
SQL> Rem mchmiele 07/02/09 - Backport mchmiele_bug-8613538 from
SQL> Rem mchmiele 07/01/09 - Backport mchmiele_bug-8613538 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mchmiele 06/30/09 - Migrating processes with correlation sets
SQL> Rem mchmiele 06/30/09 - Backport mchmiele_bug-8613538 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mchmiele 06/29/09 - Olite resource tables
SQL> Rem mchmiele 06/29/09 - Backport mchmiele_bug-8613538 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem ramisra 05/11/09 - Backport ramisra_bug-8498498 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mnanal 03/09/09 - Backport mnanal_bug-7286083 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mnanal 02/10/09 - RFI bug 7022475
SQL> Rem ramisra 01/02/09 - Backport ramisra_bug-7577303 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem ramisra 09/17/08 - Created
SQL> Rem
SQL> SET ECHO ON
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL> -- Update version
SQL> --
SQL> update version set guid = '10.1.3.5.0' where dbtype = 'olite'
Internal Error:AllocStatement: Request Communication Failed
SQL> commit
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE table temp_attachment ( key varchar2( 50 ), bin blob )
Internal Error:AllocStatement: Request Communication Failed
SQL> INSERT into temp_attachment (key,bin) SELECT key, bin FROM attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP table attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE table attachment ( key varchar2( 50 ), content_type varchar2( 50 ), bin blob, constraint att_pk primary key( key ) )
Internal Error:AllocStatement: Request Communication Failed
SQL> INSERT into attachment (key,bin) SELECT key, bin FROM temp_attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP table temp_attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> DELETE FROM WFRoutingSlip rs WHERE NOT EXISTS (SELECT 1 FROM WFTask t WHERE t.taskid = rs.taskid)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE WFRoutingSlip ADD CONSTRAINT RoutingSlipTaskConstraint FOREIGN KEY (taskId) REFERENCES WFTask (taskId) ON DELETE CASCADE
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE process_descriptor ADD (last_change_time NUMBER(38))
Internal Error:AllocStatement: Request Communication Failed
SQL> UPDATE process_descriptor SET last_change_time=(SELECT (SYSDATE - TO_DATE('01-01-1970','DD-MM-YYYY')) * (24*60*60*1000) FROM DUAL)
Internal Error:AllocStatement: Request Communication Failed
SQL> create index WFTaskTaskGroupId_I on WFTask(taskGroupId)
Internal Error:AllocStatement: Request Communication Failed
SQL> create index WFTaskWorkflowPattern_I on WFTask(workflowPattern)
Internal Error:AllocStatement: Request Communication Failed
SQL> DELETE FROM domain_properties WHERE prop_id IN ( 'dspMinThreads' , 'dspMaxThreads', 'dspInvokeAllocFactor' )
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription ADD ( partner_link VARCHAR2(256) )
Internal Error:AllocStatement: Request Communication Failed
SQL> UPDATE VERSION SET guid = '10.1.3.5.0'
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table WFTaskTimer add key varchar(100)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table WFAttachment modify (encoding varchar(100))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription DROP CONSTRAINT ds_pk
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription ADD CONSTRAINT ds_pk PRIMARY KEY (subscriber_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP INDEX ds_conversation
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX ds_conversation ON dlv_subscription( conv_id )
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP INDEX ds_operation
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX ds_operation ON dlv_subscription( process_id, operation_name )
Internal Error:AllocStatement: Request Communication Failed
SQL> drop table cx_resource
Internal Error:AllocStatement: Request Communication Failed
SQL> create table cx_resource ( id integer, pid integer, name varchar(64), kind char(1), modify_date timestamp default sysdate, constraint cx_resource_pk primary key( id ), constraint cx_resource_no_dups_pk unique (pid,name) )
Internal Error:AllocStatement: Request Communication Failed
SQL> create index cx_resource_name_idx on cx_resource (name)
Internal Error:AllocStatement: Request Communication Failed
SQL> create index cx_resource_pid_idx on cx_resource (pid)
Internal Error:AllocStatement: Request Communication Failed
SQL> drop table cx_content
Internal Error:AllocStatement: Request Communication Failed
SQL> create table cx_content ( id integer, /* id of the resource content, pointing to Resource.id */ content blob, /* the content as a blob */ constraint cx_content_pk primary key( id ) )
Internal Error:AllocStatement: Request Communication Failed
SQL> -- Add debugger tables
SQL> --
SQL> @@debugger_olite.ddl
E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\debugger_olite.ddl (The system cannot find the file specified)
SQL> ALTER TABLE work_item ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE ci_indexes ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE wi_exception ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE wi_fault ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE document_ci_ref ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE audit_trail ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE audit_details ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE cube_scope ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE attachment ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE attachment_ref ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE document_dlv_msg_ref ADD (dlv_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE xml_document ADD (doc_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> create or replace view admin_list_cx as select ci.cikey, domain_ref as ci_domain_ref, process_id, revision_tag, creation_date ci_creation_date, creator ci_creator, modify_date ci_modify_date, modifier ci_modifier, state ci_state, priority ci_priority, title, status, stage, conversation_id, metadata, root_id, parent_id, test_run_id, index_1, index_2, index_3, index_4, index_5, index_6, ci.test_run_id from cube_instance ci, ci_indexes cx where ci.cikey = cx.cikey (+)
Internal Error:AllocStatement: Request Communication Failed
SQL> COMMIT
Internal Error:AllocStatement: Request Communication Failed

Hi,
IF ORACLE DATABASE HAS ALREADY HAS ORABPEL AND ORAESB USERS, I don't know password.:
My remarks. If you upgrade a SOA suite to a higher version, you always need to known the passwords of the Oracle dehydration store (orabpel/orawsm/oraesb). If you do not know that, call your DBA. Otherwise try: the same password as the user name or try 'welcome1'. You could also force to change the password via the system user; alter user <user> identified by <password>;
IS IT A GOOD IDEA TO UPGRADE Oracle SOA 10.1.3.1.0 to Oracle SOA 10.1.3.4.0?
Yes! 10.1.3.4 is the succeeder of 10.1.3.3, in the beginning of next year 10.1.3.5 (with WLS 10.3) will come out. Note if you use 10.1.3.4 download also the latest patchset from metalink.
Marc
http://oroasoa.blogspot.com

Errors while installind Oracle Database 11gR2

At the step "Oracle Database Configuration Assistant i got the following error: link
And i don't know why, and what to do. Can you help me?
Thanks!
Edited by: Roger22 on 14.07.2010 20:25

Wed Jul 14 20:38:54 2010
AUD: OS Error = 1502 encountered while writing audit record
AUD: OS Error = 1502 encountered while writing audit record
Starting ORACLE instance (normal)
Wed Jul 14 20:39:13 2010
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as D:\oracle\product\11.2.0\dbhome_1\RDBMS
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in client-side pfile D:\ORACLE\PRODUCT\11.2.0\APP\SORIN\ADMIN\ORCL\PFILE\INIT.ORA on machine ROGER
System parameters with non-default values:
processes                = 150
nls_language             = "ROMANIAN"
nls_territory            = "ROMANIA"
memory_target            = 816M
control_files            = "D:\ORACLE\PRODUCT\11.2.0\APP\SORIN\ORADATA\ORCL\CONTROL01.CTL"
control_files            = "D:\ORACLE\PRODUCT\11.2.0\APP\SORIN\ORADATA\ORCL\CONTROL02.CTL"
db_block_size            = 8192
compatible               = "11.2.0.0.0"
undo_tablespace          = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain                = ""
dispatchers              = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
audit_file_dest          = "D:\ORACLE\PRODUCT\11.2.0\APP\SORIN\ADMIN\ORCL\ADUMP"
audit_trail              = "DB"
db_name                  = "orcl"
open_cursors             = 300
diagnostic_dest          = "D:\ORACLE\PRODUCT\11.2.0\APP\SORIN"
Wed Jul 14 20:39:18 2010
PMON started with pid=2, OS id=5252
Wed Jul 14 20:39:18 2010
VKTM started with pid=3, OS id=4052 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Jul 14 20:39:18 2010
GEN0 started with pid=4, OS id=4392
Wed Jul 14 20:39:18 2010
DIAG started with pid=5, OS id=4924
Wed Jul 14 20:39:18 2010
DBRM started with pid=6, OS id=5692
Wed Jul 14 20:39:18 2010
PSP0 started with pid=7, OS id=5120
Wed Jul 14 20:39:18 2010
DIA0 started with pid=8, OS id=3532
Wed Jul 14 20:39:19 2010
MMAN started with pid=9, OS id=4196
Wed Jul 14 20:39:19 2010
DBW0 started with pid=10, OS id=504
Wed Jul 14 20:39:19 2010
LGWR started with pid=11, OS id=1252
Wed Jul 14 20:39:19 2010
CKPT started with pid=12, OS id=3776
Wed Jul 14 20:39:19 2010
SMON started with pid=13, OS id=5408
Wed Jul 14 20:39:19 2010
RECO started with pid=14, OS id=4776
Wed Jul 14 20:39:19 2010
MMON started with pid=15, OS id=4980
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Wed Jul 14 20:39:19 2010
MMNL started with pid=16, OS id=752
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\oracle\product\11.2.0\app\Sorin
Wed Jul 14 20:39:19 2010
AUD: OS Error = 1502 encountered while writing audit record
Wed Jul 14 20:43:13 2010
AUD: OS Error = 1502 encountered while writing audit record
AUD: OS Error = 1502 encountered while writing audit record
Wed Jul 14 20:48:34 2010
alter database open
ORA-1507 signalled during: alter database open...
alter database mount
Wed Jul 14 20:48:41 2010
ORA-00210: nu se poate deschide fisierul de control specificat
ORA-00202: fisier de control: 'D:\ORACLE\PRODUCT\11.2.0\APP\SORIN\ORADATA\ORCL\CONTROL02.CTL'
ORA-27041: fisierul nu a putut fi deschis
OSD-04002: fişierul nu a putut fi deschis
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00210: nu se poate deschide fisierul de control specificat
ORA-00202: fisier de control: 'D:\ORACLE\PRODUCT\11.2.0\APP\SORIN\ORADATA\ORCL\CONTROL01.CTL'
ORA-27041: fisierul nu a putut fi deschis
OSD-04002: fişierul nu a putut fi deschis
O/S-Error: (OS 2) The system cannot find the file specified.
Wed Jul 14 20:48:43 2010
Checker run found 2 new persistent data failures
ORA-205 signalled during: alter database mount
...This is what that file contains
Roger..

Upgrading Oracle Database from 10.2.0.3 to 10.2.0.4 on Windows XP

Hi,
My moto is to install Oracle DB 10.2.0.4 but i didn't find that vesion of DB. so i installed 10.2.0.3 and now wanted to upgrade it to 10.2.0.4. Please redirect me to proper documentation or patch that will help me.
Is there 10.2.0.4 setup directly insted of upgrading from previous version??

Hi,
Case 1) On top of Oracle Database 10.2.0.3 directly install and apply the patch for Oracle database 10.2.0.4 provided with Database ORACLE_HOME and SYS password parameters at the patch installation time.
Case 2) If you installed only Database software from 10.2.0.3 to 10.2.0.4, using dbua utility you can upgrade the database version.
Thanks,
Ajay Babu Pentela

Error While Creating Essbase Database From Hyperion Planning

Hi,
While creating the Essbase Database From the 'Manage Database' in Hyperion Planning, I am getting the following error:
com.hyperion.planning.olap.EssbaseException: Account (1060000)
It gets stuck at Adding Dimensions.
I have tried reconfiguring Planning, but no luck.
My Relation Repository is MS SQL Server 2005 and the Essbase and Shared Services are on a Linux box.
I am getting the following error in the Planning log
[12-Nov-2009 10:50:41]: Propegating external event[ FROM_ID: 68b6dbf1 Class: class com.hyperion.planning.sql.HspLock Object Type: -1 Primary Key: 50001 ]
[12-Nov-2009 10:50:41]: Processing cube: Plan1
[12-Nov-2009 10:50:41]: Setting System CFG properties for Attribute Dimensions
[12-Nov-2009 10:50:41]: Adding dimension: Account
[12-Nov-2009 10:50:41]: Closing outlines
com.hyperion.planning.olap.EssbaseException: Account (1060000)
     at com.hyperion.planning.olap.HspEssbaseOutlineAPI.EssAddMemberEx(Native Method)
     at com.hyperion.planning.olap.HspCubeRefreshTask.addDimension(Unknown Source)
     at com.hyperion.planning.olap.HspCubeRefreshTask.addDimensionsAndMembers(Unknown Source)
     at com.hyperion.planning.olap.HspCubeRefreshTask.buildOutlines(Unknown Source)
     at com.hyperion.planning.olap.HspCubeRefreshTask.run(Unknown Source)
     at com.hyperion.planning.HspJSImpl.runCubeRefresh(Unknown Source)
     at com.hyperion.planning.HyperionPlanningBean.runCubeRefresh(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
     at sun.rmi.transport.Transport$1.run(Transport.java:153)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
     at java.lang.Thread.run(Thread.java:595)
Thanks for your help.
Edited by: user524093 on Nov 12, 2009 4:38 PM

Have you tried restarting the services and giving it a try?
Which version of Essbase/Planning are you on?
If your Essbase server name has more than 30 characters, please use NODENAME with short server name.

Error while upgrade oracle database from 9.2.0.6 to 10.2.0.1

Similar Messages

Maybe you are looking for