Apply patchset on Sol10-x86

Hi
I have to apply the latest patchset to a system running Sol10-x86 with root on zfs As the usual backout strategy of breaking the root mirror will not work here , I want some opinion on the backout strategy . Particularly I want to know if I create an alternate boot environment with lucreate and then patch the primary boot environment in single user mode , Can the ABE used to boot the system to previous state Basically if I do not want to use luupgrade to apply the patchset ; or using luupgrade in this case is the same as using installpatchset command ?
OR
Will just taking a snapshot of the root pool and keeping it on the same machine work if I need to roll back to original environment
What may be the steps in such roll back
Appreciate any insights on this
TIA and Rgds

Hello
With zfs rpool you have to use LU, and LU will do all work for you, making the most of ZFS advantage doing snapshot, clone on the current BE and then you will be able to patch the newBE create.
there are 3 mains comamnds, lucreate, luupgrade and luactivate (this will activate one newBE or the oldBE)
Check this doc https://community.oracle.com/docs/DOC-887132
If you are in sparc there is a new Boot command that will print the BE that are on the system
boot -L --> then you will be able to choose the one you one, this is the worst case the newBE that you have tried to boot panic or similar
in X86 you will see 2 entries in grub menu.
Regards
Ezequiel

Similar Messages

SQL Developer 1.5.1 failed to start after applying patchset 11.1.0.7

After applying patchset 11.1.0.7 to Oracle 11g (11.1.0.6) running on Windows 2003, when starting SQL Developer 1.5.1 I got an error:
"Unable to find main class. Class specified is: oracle/ide/boot/Launcher".
Any idea? Thanks.

It is possible that the patch has replaced you shortcut with one pointing to the version within the 11g home. Try running sqldeveloper directly from the executable in the 151 directory.

Missing rows / output only one row in a Report after applying patchset 2

Hi.
We use Reports Builder for 10g R2. We had the problem with our AS 10g R2 on windows 2003, that some reports creates duplicate rows when it is a ASCII report (desformat = delimited), see Bug 3340546.
Now we apply Patchset 2 on a local machine, to test the functionality. It fix the problem (look in metalink doc ID 398955.1 under "2.12 Oracle Reports Developer Bugs")-
But now most csv reports creates only one row instead of multiple rows.
We run reports on our local machine with OC4N and local started Form (via Forms Builder) to generate the reports (local started report server) from DevSuite).
When we start the reports with desformat=delimited the txt-file has only the header row and one data row (instead of multiple ones).
And when we generate the same report with desformat=delimiteddata it looks fine and generates all rows as expected.
We found neither here in the forum or in metalink knowledge base nor on the internet.
Have you any suggestions for us how to fix this problem?
Using delimiteddata is now acceptable solution for us, because delimited is easier to use.
Thanks for your help!

Hey folks.
We have solved the problem. :)
We applied PatchSet2 for 10gR2. But we don´t know how the csv-report outputs only 1 data-row instead of several rows.
Than we create a similar report (with the same sql-query) as a new one with the reports builder assistant.
This one works pretty fine. So we looked for the attributes and see the "max. number datasets for each site" and it was in the new one set to 0 and in our old one set to 1.
So we change this and ... the old one works pretty fine! :)
So the problem is, that this attribute does not had any consequences in the old version. But since we update with PatchSet 2 it respect this attribute but we don´t "see" it.
Hope this helps others.

Applying patchset 10.2.0.3 to 10.2.0.1 Oracle client on Linux

Hi folks,
I want to apply patchset 10.2.0.3 to a 10.2.0.1 Oracle "Client" on Linux (both 32bit and 64bit). So, I started with the 64bit Linux.
1. installed the 10.2.0.1 Client,
2. downloaded the patchset 10.2.0.3 (5337014) for 64bit Linux,
3. read the documentation for the 5337014 patchset
I also downloaded the patchset 5601428 (specified in document 412160.1 referenced in the patchset document), and patchsets 4689959 and 5632264 (specified in document 396671.1 - which is Time Zone related).
I understand that if I do apply the 10.2.0.3 patchset to a 10.2.0.1 database server installation, then I need to apply the patchsets 5601428 and 4689959 (or 5632264) but for just applying the patchset 10.2.0.3 (5337014) to a 10.2.0.1 client, do I still need to apply 4689959 and/or 5632264 ?
will simply (only) applying 10.2.0.3 (5337014) will do the job on the Oracle Client ?
I have done this so many times for the Database Server but haven't done it for the Oracle Client - did search the forums and Metalink but did not find anything specific to applying patchsets to Oracle Client installations.
Thank you and Best regards
Zafer

Somebody replied my query on Metalink telling me applying the patchset is the same as the server and to follow the installation manual instructions :) Oracle patchset installation help file (document) could be clearer for the Client installation (as they did include explicit sections for RAC's, etc in the same doc).
Edited by: zaferaktan on Jul 2, 2009 5:31 PM

Error while applying patchset 11.1.0.7 to 11.1.0.6

Hi, I am a new DBA and would appreciate any help on this.
I am in the process of upgrading my database from 10.2.0.4 to 11.1.0.7. I installed 11.1.0.6 and was applying the 11.1.0.7 patch. I installed the 11g patchset successfully and was working on 'Upgrading Oracle Database 11g Release 11.1.0.6 to Oracle Database 11g Release 11.1.0.7' - Section 9.2 of the readme of the 11.1.0.7 patchset. After starting the dbua and selecting the 11g home that needed to be upgraded, the dbua gave the error -
The upgrade Assistant failed in bringing up the database proddb1. Oracle Home /opt/oracle/product/11.1.0/dev obtained from file /etc/oratab was used to connect to the database. Either the database is not running from Oracle Home /opt/oracle/product/11.1.0/dev or the pfile /oravol00/oracle/product/11.1.0/dev/dbs/init.ora used is incorrect. Correct the error and run the Upgrade Assistant again.
Here are some more details about my system - I have a 10g dev instance and a 10g production instance also running on the same box. The 11g instance location is /oravol00/opt/oracle/product/11.1.0/dev and has a soft link to /opt/oracle/product/11.1.0/dev.
I read another thread on the OTN where another person had the same problem and was asked to start the database in the upgrade mode from sqlplus and then try the dbua again. I tried that - started the databse in startup upgrade mode and it gave me this error -
SQL> startup upgrade;
ORACLE instance started.
Total System Global Area 1.0088E+10 bytes
Fixed Size 2162320 bytes
Variable Size 5502927216 bytes
Database Buffers 4563402752 bytes
Redo Buffers 19697664 bytes
ORA-03113: end-of-file on communication channel
Process ID: 19677
Session ID: 170 Serial number: 3
Can someone please give me some clue on what I did wrong here and how to correct it? Any help is appreciated.
Edited by: user12158503 on Mar 12, 2010 7:47 PM

I checked my alert log and see errors from the day I installed the 11g instance. When DBUA said the installation is complete, I thought everything went fine. But now I see alert log had errors since then. I created the database on March 12th and tried to install the 11.1.0.7 patch on March 14th by around 3pm. Here is more clarification on the upgrade. I am trying to upgrade my dev environment. I plan to upgrade using export/import. For this I created the 11g instance and am applying the 11.1.07 patch. Next, I need to apply the PSU patch and then do the upgrade.
I am pasting the alert log errors here. Please advice on what I need to do.
I see these errors from the day I created the database -
alter database "progdev" open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 844220
Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_ora_29547.trc:
z00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oravol00/oradata/progdev/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
2010-03-11 14:23:24.757000 -06:00
Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_ora_29547.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oravol00/oradata/progdev/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
2010-03-11 14:23:27.729000 -06:00
And these from when I tried to do the patch install -
Shutting down instance (immediate)
License high water mark = 71
ORA-1089 : opidrv aborting process unknown ospid (1452_47151230037104)
2010-03-12 16:20:31.653000 -06:00
All dispatchers and shared servers shutdown
2010-03-12 16:20:33.732000 -06:00
ALTER DATABASE CLOSE NORMAL
SMON: disabling tx recovery
SMON: disabling cache recovery
2010-03-12 16:20:34.730000 -06:00
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 4
Successful close of redo thread 1
2010-03-12 16:20:48.060000 -06:00
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
2010-03-12 16:20:49.267000 -06:00
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Stopping background process VKTM:
2010-03-12 16:20:58.416000 -06:00
System State dumped to trace file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_ora_10281.trc
2010-03-12 16:20:59.757000 -06:00
Instance shutdown complete
2010-03-12 17:03:02.814000 -06:00
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Starting ORACLE instance (normal)
2010-03-12 17:03:04.837000 -06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 3
2010-03-12 17:03:08.261000 -06:00
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
System parameters with non-default values:
processes = 150
memory_target = 9664M
control_files = "/oravol00/oradata/progdev/control01.ctl"
control_files = "/oravol00/oradata/progdev/control02.ctl"
control_files = "/oravol00/oradata/progdev/control03.ctl"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
audit_file_dest = "/opt/oracle/admin/progdev/adump"
audit_trail = "DB"
db_name = "progdev"
open_cursors = 300
diagnostic_dest = "/opt/oracle"
PMON started with pid=2, OS id=26304
VKTM started with pid=3, OS id=26306 at elevated priority
VKTM running at (20)ms precision
DIAG started with pid=4, OS id=26310
DBRM started with pid=5, OS id=26312
PSP0 started with pid=6, OS id=26314
DIA0 started with pid=7, OS id=26316
MMAN started with pid=8, OS id=26318
DBW0 started with pid=9, OS id=26320
DBW1 started with pid=10, OS id=26322
LGWR started with pid=11, OS id=26324
CKPT started with pid=12, OS id=26326
SMON started with pid=13, OS id=26328
RECO started with pid=14, OS id=26330
MMON started with pid=15, OS id=26332
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=16, OS id=26334
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
ALTER DATABASE MOUNT
2010-03-12 17:03:12.994000 -06:00
Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_26318.trc:
ORA-27103: internal error
Linux-x86_64 Error: 17: File exists
Additional information: -1
Additional information: 1
MMAN (ospid: 26318): terminating the instance due to error 27103
ORA-1092 : opitsk aborting process
Instance terminated by MMAN, pid = 26318
2010-03-12 17:12:46.811000 -06:00
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Starting ORACLE instance (normal)
2010-03-12 17:12:48.769000 -06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
2010-03-12 17:12:51.909000 -06:00
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
System parameters with non-default values:
processes = 150
memory_target = 9664M
control_files = "/oravol00/oradata/progdev/control01.ctl"
control_files = "/oravol00/oradata/progdev/control02.ctl"
control_files = "/oravol00/oradata/progdev/control03.ctl"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
audit_file_dest = "/opt/oracle/admin/progdev/adump"
audit_trail = "DB"
db_name = "progdev"
open_cursors = 300
diagnostic_dest = "/opt/oracle"
PMON started with pid=2, OS id=28723
VKTM started with pid=3, OS id=28725 at elevated priority
VKTM running at (20)ms precision
DIAG started with pid=4, OS id=28729
DBRM started with pid=5, OS id=28731
PSP0 started with pid=6, OS id=28733
DIA0 started with pid=7, OS id=28735
MMAN started with pid=8, OS id=28737
DBW0 started with pid=9, OS id=28739
DBW1 started with pid=10, OS id=28741
LGWR started with pid=11, OS id=28743
CKPT started with pid=12, OS id=28745
SMON started with pid=13, OS id=28747
RECO started with pid=14, OS id=28749
MMON started with pid=15, OS id=28751
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=16, OS id=28753
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
ALTER DATABASE MOUNT
2010-03-12 17:12:55.989000 -06:00
Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_28737.trc:
ORA-27103: internal error
Linux-x86_64 Error: 17: File exists
Additional information: -1
Additional information: 1
MMAN (ospid: 28737): terminating the instance due to error 27103
ORA-1092 : opitsk aborting process
Instance terminated by MMAN, pid = 28737
2010-03-12 21:09:24.016000 -06:00
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Starting ORACLE instance (normal)
2010-03-12 21:09:25.986000 -06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
2010-03-12 21:09:29.084000 -06:00
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
System parameters with non-default values:
processes = 150
memory_target = 9664M
control_files = "/oravol00/oradata/progdev/control01.ctl"
control_files = "/oravol00/oradata/progdev/control02.ctl"
control_files = "/oravol00/oradata/progdev/control03.ctl"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
audit_file_dest = "/opt/oracle/admin/progdev/adump"
audit_trail = "DB"
db_name = "progdev"
open_cursors = 300
diagnostic_dest = "/opt/oracle"
PMON started with pid=2, OS id=19640
VKTM started with pid=3, OS id=19642 at elevated priority
VKTM running at (20)ms precision
DIAG started with pid=4, OS id=19646
DBRM started with pid=5, OS id=19648
PSP0 started with pid=6, OS id=19650
DIA0 started with pid=7, OS id=19652
MMAN started with pid=8, OS id=19654
DBW0 started with pid=9, OS id=19657
DBW1 started with pid=10, OS id=19659
LGWR started with pid=11, OS id=19661
CKPT started with pid=12, OS id=19663
SMON started with pid=13, OS id=19665
RECO started with pid=14, OS id=19667
MMON started with pid=15, OS id=19669
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=16, OS id=19671
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
ALTER DATABASE MOUNT
2010-03-12 21:09:33.214000 -06:00
Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_19654.trc:
ORA-27103: internal error
Linux-x86_64 Error: 17: File exists
Additional information: -1
Additional information: 1
MMAN (ospid: 19654): terminating the instance due to error 27103
2010-03-12 21:09:34.222000 -06:00
Instance terminated by MMAN, pid = 19654
2010-03-12 21:10:15.072000 -06:00
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Starting ORACLE instance (normal)
2010-03-12 21:10:17.067000 -06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
2010-03-12 21:10:20.227000 -06:00
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
System parameters with non-default values:
processes = 150
memory_target = 9664M
control_files = "/oravol00/oradata/progdev/control01.ctl"
control_files = "/oravol00/oradata/progdev/control02.ctl"
control_files = "/oravol00/oradata/progdev/control03.ctl"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
audit_file_dest = "/opt/oracle/admin/progdev/adump"
audit_trail = "DB"
db_name = "progdev"
open_cursors = 300
diagnostic_dest = "/opt/oracle"
PMON started with pid=2, OS id=20310
VKTM started with pid=3, OS id=20312 at elevated priority
VKTM running at (20)ms precision
DIAG started with pid=4, OS id=20316
DBRM started with pid=5, OS id=20318
PSP0 started with pid=6, OS id=20320
DIA0 started with pid=7, OS id=20322
MMAN started with pid=8, OS id=20324
DBW0 started with pid=9, OS id=20326
DBW1 started with pid=10, OS id=20328
LGWR started with pid=11, OS id=20330
CKPT started with pid=12, OS id=20332
SMON started with pid=13, OS id=20334
RECO started with pid=14, OS id=20336
MMON started with pid=15, OS id=20338
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=16, OS id=20340
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
ALTER DATABASE MOUNT
2010-03-12 21:10:24.263000 -06:00
Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_20324.trc:
ORA-27103: internal error
Linux-x86_64 Error: 17: File exists
Additional information: -1
Additional information: 1
MMAN (ospid: 20324): terminating the instance due to error 27103
ORA-1092 : opitsk aborting process
Instance terminated by MMAN, pid = 20324
2010-03-12 22:02:04.524000 -06:00
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Starting ORACLE instance (normal)
2010-03-12 22:02:06.715000 -06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
2010-03-12 22:02:10.003000 -06:00
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
System parameters with non-default values:
processes = 150
memory_target = 9664M
control_files = "/oravol00/oradata/progdev/control01.ctl"
control_files = "/oravol00/oradata/progdev/control02.ctl"
control_files = "/oravol00/oradata/progdev/control03.ctl"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
audit_file_dest = "/opt/oracle/admin/progdev/adump"
audit_trail = "DB"
db_name = "progdev"
open_cursors = 300
diagnostic_dest = "/opt/oracle"
PMON started with pid=2, OS id=32493
VKTM started with pid=3, OS id=32495 at elevated priority
VKTM running at (20)ms precision
DIAG started with pid=4, OS id=32499
DBRM started with pid=5, OS id=32501
PSP0 started with pid=6, OS id=32503
DIA0 started with pid=7, OS id=32505
MMAN started with pid=8, OS id=32507
DBW0 started with pid=9, OS id=32509
DBW1 started with pid=10, OS id=32511
LGWR started with pid=11, OS id=32513
CKPT started with pid=12, OS id=32515
SMON started with pid=13, OS id=32517
RECO started with pid=14, OS id=32519
MMON started with pid=15, OS id=32521
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=16, OS id=32523
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
2010-03-12 22:02:11.216000 -06:00
ALTER DATABASE MOUNT
2010-03-12 22:02:14.385000 -06:00
Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_32507.trc:
ORA-27103: internal error
Linux-x86_64 Error: 17: File exists
Additional information: -1
Additional information: 1
MMAN (ospid: 32507): terminating the instance due to error 27103
ORA-1092 : opitsk aborting process
Instance terminated by MMAN, pid = 32507
oracle@<progdev>:/home/oracle $
Thanks,
Anu

Applying patchset 10.2.0.3 ::known issues:: need clarification

Hello all,
i am planning to apply the patchset 10.2.0.3 on my 2 node 10.2.0.2 RAC on Solaris 10.
In the readme.html, under the known issues its mentioned
11.8 Memory Access Mode not Supported in Oracle RAC
In an Oracle RAC set up, if database instances are not running on the same node as Oracle Enterprise Manager Management Service, then monitoring in memory access mode does not display performance chart data.
This issue is tracked with Oracle bug 5559618.Now how do i know whether oracle has some fix for bug 5559618 .
I did search in th metalink, but could not find any patch or anything.
Is this bug fixed in this patchset or will oracle provide some other one off patches for this bug ??
any idea ??
TIA,
JJ

Somebody replied my query on Metalink telling me applying the patchset is the same as the server and to follow the installation manual instructions :) Oracle patchset installation help file (document) could be clearer for the Client installation (as they did include explicit sections for RAC's, etc in the same doc).
Edited by: zaferaktan on Jul 2, 2009 5:31 PM

10.2.0.1 to 10.2.0.3 patchset for Solaris x86 64-bit

I'm having difficulty in locating the patch (or patchset) to upgrade my 10.2.0.1 database to 10.2.0.3
This is for the Solaris x86 64-bit platform.
I'm using the metalink patches area but am baffled on how to find what I need.
Any thoughts ?
Thanks in advance
Mark
EDIT... I believe I found what I was looking for ... Patchset 5337014 ... took me a while but I believe this is the one.
Edited by: markhooper on Aug 13, 2009 10:05 AM

Yes. You found it. ;)

Server restarted when applying patchset...

Hi,
Db version:10.2.0.1
OS=RHEL 4AS
I was applying 10.2.0.4 patchset on my databse . 80% of installation completed. that time server was rebooted. how to complete my installation?
Thanks,

I would recommend that you restore the database from backup and re-do the upgrade.
HTH
Srini

Dataguard 11gR2 - Apply Patchset Max Availability

Hello All,
I would like to apply the April PSU to single instance with a 1 physical standby.
When I try to switch off the log transport I get the error ORA-16627.
My question is whether I need to temporarily change the protection mode to max performance for the primary while I shutdown and apply the patchset to the standby?
I am using the note : *How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]*
Thanks in advance for your help.
Jan S.
ENV
=============
Primary : 11.2.0.3
Standby: 11.2.0.3 Physical
Protection: Max Availability

I would like to apply the April PSU to single instance with a 1 physical standby.
When I try to switch off the log transport I get the error ORA-16627.
My question is whether I need to temporarily change the protection mode to max performance for the primary while I shutdown and apply the patchset to the standby?check this link http://blog.grid-it.nl/index.php/2011/05/24/how-is-data-guard-maximum-protection-mode-protecting-your-data/
Please read below completely.
ORA-16627:
     operation disallowed since no standby databases would remain to support protection mode
Cause:      This status is returned in the following situations:
- The broker rejects an attempt to change the configuration's overall protection mode since it could not find any online, enabled standby databases that support the proposed protection mode.
- The broker rejects an attempt to enable the configuration if it determines there are no online, enabled standby databases that support the overall protection mode.
- The broker rejects an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that can support the configuration's overall protection mode.
- The broker rejects an attempt to set the configuration offline if doing so would violate the configuration's overall protection mode.
- The broker rejects an attempt to set a standby database offline if doing so would violate the configuration's overall protection mode.
- The broker rejects a switchover attempt if doing so would violate the configuration's overall protection mode.
- The broker returns this error during a health check.
Action:      - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode.
- For enable failures, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.
- For delete and disable failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode.
- For state change failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If setting the configuration OFFLINE you may have to downgrade the protection mode setting to maximum performance beforehand.
- For switchover failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If your configuration contains a primary database and a single standby database, ensure that the LogXptMode configuration property established for the primary database supports the overall protection mode. After the switchover, the old primary database will become the standby database and its LogXptMode configuration property setting must support the overall protection mode.
- For health check error, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.

Should i shutdown other DBs while applying patchsets?

I have a 10.2.0.1.0 and an 11g DB running on a machine. I need a third database which should be of version 10.2.0.4.0 .
For that, i've installed 10.2.0.1.0 on a separate ORACLE_HOME(a software only installation) and i am going to apply the 10.2.0.4.0 patchset. But in the patchset documentation's pre-requisite bit it says
+8.6 Shut Down Oracle Databases+
Shut down any existing Oracle Database instances with normal or immediate priority. On Oracle RAC systems, shut down all instances on each node.
If Automatic Storage Management (ASM) is running, shut down all databases that use ASM, then shut down the ASM instance on each node of the cluster.
Does this mean i have to shutdown all other databases in this machine due to the patchset installation?

I just noticed that two threads were created by me for the same issue. This was mistake because of intermittent internet connection problem here. Sorry for the duplicate thread.

Applying patchset needs migration ?

Hi all,
I'm applying the patchset to change my Oracle version from 9.2.0.1 to 9.2.0.6.
Do I need migrate my database 9.2.0.1 ? If so, does this mean that the patchset 9.2.0.6 do change in Oracle catalog ?
Yang
ps. My database is used only for storing tables and index of Oracle. No any others functionnality nor options.

Do I need migrate my database 9.2.0.1 ?
If so, does this mean that the patchset 9.2.0.6 do change in Oracle catalog ?Yes to both of questions.
Applying of patchset consist of two steps and these both steps must be done.
1. patching the software
2. patching of database (catalog) - during this step database must be in "migrate" mode.

Applied patchset 10.2.0.4

Hi,
I applied 10.2.0.4 patch set to 10.2.0.3 grid control on solaris sparc(64bit) 5.8 successfully with out any errors.The thing I want to know is it didn't ask to run root.sh!!
But when I applied the patch set to agent,it asked to run the root.sh.
Is that any problem?
Thanks.

Thnks for the reply.
I have one more quesn.
The EM agents on other hosts which are of 10.2.0.3 version are showing the below msg when I check the status of agent.
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.4.0
Protocol Version : 10.2.0.2.0
Do they have to show
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0
instead of 10.2.0.3.0,becoz my grid control is 10.2.0.4.0 now
Do I need to clear anything?
Thanks

Problem applying patches on Sol10

I must be doing something guffy but can't figure out what...
I am trying to apply patch on Sol 10x86 box. patchadd is failing siliently with no indication on what might be the problem. I tried on two different machines with identical results. Any ideas on what might be the problem or how to debug it.
Thanks,
/Oleg
# patchadd -g 118344-07
Patches Validation...
Loading patches installed on the system...
Done.
Loading patches requested to install.
Done.
Checking patches requested to install.
Done.
Approved patches will be installed in this order:
118344-07
Checking installed patches...
Patchadd is terminating.

I am assuming you want to only apply this patch in a specific Zone? If that is the case you would want to use -G instead of -g as the option.
"Add patch(es) to packages in the current zone only. When used in the global zone, the patch is added to packages in the global zone only and is not propagated to pack-ages in any existing or yet-to-be-created non-global zone. When used in a non-global zone, the patch is added to packages in the non-global zone only."
DP

Backing up oracle before applying patchset

I am about to patch an Oracle database from 9.2.0.1 to 9.2.0.6. The readme doc which comes with this patchset, suggests to 'backup the oracle installation'. There are no more details about this. By oracle installation, I must assume it's referring to the binaries of the oracle rdbms, right? If so, which directories i must backup? Is $ORACLE_HOME enough?
thanks
james

Oracle_home backup
and
Oracle Database Backup
because after running installer u have to run script on database.
Thanks
Kuljeet

About Apply patchset 10.2.0.2

Guys,
In order to apply the patch set 10.2.0.2, I need to create other ORACLE_HOME?
Currently My ORACLE_HOME is 10.2.
Thank you

Ok, I read the previous links and I applied the patch set.
But yet I'm not performed the DBUA from currently 10.2.0.2 in order to upgrade my database
Then I run the opatch utility and its show me:
Installed Products
Oracle Database 10g 10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 1 10.2.0.2.0My question is:
I should apply the p5490846_10201_LINUX.zip (CPU patch October) before or after the DBUA ?
Tanks for all.

Apply patchset on Sol10-x86

Similar Messages

Maybe you are looking for