RMAN: Unable to register database

Hi all,
I have just renamed the db_name, dbid and SID of a database using the DBNEWID Utility.
When I satrt up the database, it seems to start without any errors.
I need to take a backup of this database using RMAN.
But when I try to register the database, I get an error -
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 06/22/2009 15:26:39
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 06/22/2009 15:26:39
ORA-01587: error during control file backup file copy
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 323
Additional information: 1036288
Could anyone please help me resolve this problem?

How do I find out, what path exact path is it trying to access?
When I do a SHOW ALL, all that RMAN does is show the error again.
This is what I get -
RMAN> SHOW ALL;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 06/23/2009 08:16:28
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 06/23/2009 08:16:28
ORA-01587: error during control file backup file copy
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 323
Additional information: 602112
Edited by: user10882764 on Jun 23, 2009 5:21 AM
Edited by: user10882764 on Jun 23, 2009 5:22 AM

Similar Messages

Unable to register database in RMAN - RedHat 6.2 + Oracle 8.1.6

Is this a bug?? pls suggest the way out...
-Balaji
([email protected])
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------

Is this a bug?? pls suggest the way out...
-Balaji
([email protected])
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------

Unable to register database in catalog into emrep

Hello guys,
I have a RMAN catalog in one server that works fine, now I tried to move this catalog to the emrep database (In this database I have the Grid Control), as I can´t use export / import because the original database is 10.1.0.5 and the emrep database is 10.1.0.4, I have created a new catalog into the emrep database.
The problem appear when I try to register one database on it:
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/15/2009 12:10:43
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
So, my first question is: Is possible create a RMAN catalog in the same database of Grid Control?
If this is possible, any suggestions that can help me to resolve this errors?
Thanks.

Hello Damorgan, thanks for your answer.
I follow the steps in a remote database ( BEEVODES ) which I want register into catalog ( tstsuse11-emrep ):
oracle@srvdb01 ~]$ echo $ORACLE_BASE
*/u01/app/oracle*
oracle@srvdb01 ~]$ echo $ORACLE_HOME
*/u01/app/oracle/product/10.1.0/db_1*
oracle@srvdb01 ~]$ export ORACLE_SID=BEEVODES
oracle@srvdb01 ~]$ rman target / catalog rman@tstsuse11-emrep
Recovery Manager: Release 10.1.0.5.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: BEEVODES (DBID=822996874)
recovery catalog database Password:
connected to recovery catalog database
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/16/2009 12:12:49
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
But I continue with the same error.
I supose the instalation of emrep is ok, because the Grid Control ( installed there ) works fine.
Thanks again.

[RMAN] problem with registering database

Hello, we have RAC environment on two nodes. We created rman catalog database and then registered our database with REGISTER DATABASE command. After that we issued command SHOW ALL and encountered an error:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_easy1.f'; # default
this is new catalog database, which is to replace the old one
how to deal with this problem ?

So you are following up on datafile 74 in this other thread :
problem with datafile recovery
Hemant K Chitale

RMAN-can't register database

I'm attempting to register a database that is located on a different server from my rman database. Here's the error:
$ rman target system/manager@PROD rcvcat rman/rman@RMANDB
Recovery Manager: Release 8.1.7.4.0 - Production
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database: ORA-01031: insufficient privileges
Any help would be appreciated!!!

Hi,
Try using "as sysdba" in your string. This should take the insufficient privileges away.
Hope this helps.
Al

Unable to recover database after rman recovery and database open resetlogs

I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
OPA-00600: ORA-00600: internal error code, arguments: ...
The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
I hope I have not dug myself into too deep of a hole here.
Here is the trace from my most recent attempt.
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> list incarnation of database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 08/02/2011 15:49:04
ORA-01507: database not mounted
RMAN> restore controlfile from autobackup;
Starting restore at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /opt/oracle/flash_recovery_area
database name (or database unique name) used for search: LCRSDEV
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 02-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
RMAN> restore database until scn 95676700;
Starting restore at 02-AUG-11
Starting implicit crosscheck backup at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 02-AUG-11
Starting implicit crosscheck copy at 02-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 02-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/02/2011 15:52:04
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> restore database;
Starting restore at 02-AUG-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
Finished restore at 02-AUG-11
RMAN> recover database until scn 95676700;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:16:28
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> recover database;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
unable to find archive log
archive log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:25:04
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701

Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
*1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
*2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
*3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
*4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
*5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
*6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
*7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
*8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
*9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
However if I restore the controlfile to the earlier version I am getting the following output from the process:
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
Starting restore at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 03-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
RMAN> restore database until scn 92348137;
Starting restore at 03-AUG-11
Starting implicit crosscheck backup at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 03-AUG-11
Starting implicit crosscheck copy at 03-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 03-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/03/2011 12:53:19
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Edited by: K Doyle on Aug 3, 2011 10:22 AM

Register Database error in Rman

Hi
I have been trying to register a database in RMAN . Here are the steps I took on OS linux Mandrake 8.1 using ORACLE version 9.2.0.1.0
SQL:
CONNECT sys/password@ora AS SYSDBA
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
rman catalog=rman/rman@ora
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
rman catalog=rman/rman@ora target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ora (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
This is returning the error message
RMAN-00571:
RMAN-00569:
RMAN-00571:
RMAN-03002:failure of register command at 07/16/03 12:56
RMAN-03014:implicit resyncof recovery catalog failed
RMAN-03009:failure of full resync command on default channel at 07/16/03
ORA01001- cursor not valide

Hi,
Change the name of your tablespace RMAN to CATTBS. I believe RMAN is a reserved word in oracle.

Register database problem (oracle 8.1.6) on Linux 6.2

I'm unable to register my database using RMAN. I'm using Oracle 8.1.6 on Redhat Linux 6.2 (glibc - 2.2.14-5.0). Is there any known bug in Oracle 8.1.6 / rman on Linux 6.2.
These are the steps I followed:
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------
Actually I followed the same steps in my own PC with Oracle 8.1.7 on Win2k, It worked!!

Hello,
Narender,you have to include DISPLAY in your .bash_profile and set to your hostname, somewhat like this DISPLAY=hostname:0.0
or read the installation guides, installation of Oracle 8.1.6 in RHL 6.2 is straight forward.

How can i do a RMAN backup of my database from the network ?

i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.

Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus

Error while registering database

Hi,
I get "RMAN-03008: error while performing automatic resync of recovery catalog" while registering a database which is located on my server.
Following is the procedure i have done to register it.
C:\Documents and Settings\yogeshn.RITPL>rman target=sys/sys@oracle10 catalog=rman/rman@rman_db
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Dec 12 12:23:02 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is
not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not cur
rent
connected to target database: ORACLE10 (DBID=2437633359)
connected to recovery catalog database
RMAN> connect target;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06167: already connected
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
RMAN>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not currentIt seems the rman version (10.2.0.3) is higher than the target database version, this is not supported. Make sure rman executable and target database are on the same level.

Unable to create database entry in the directory service. - TNS-04

We run into this error when we tried to register an Oracle 10.2.0.4 database with OID server (10.1.4.3):
Unable to create database entry in the directory service. - TNS-04409: Directory service error
We use Oracle DBCA to register to the OID. Both Oracle database and OID server are all running under Sun Solaris environment.
In the meantime, I found these errors in the oid logs:
oidldapd01.log:
2009/07/13:21:15:47 * DispatcherListener:2 * ERROR : gslsflAcceptConnAndSend : OS 2 : Unable to accept New TCP
connection
Any ideas?
Thanks
Naiying

Hi,
Thanks for update.
No, didn't find DSCC agent logs get updated when I have the pop up.
C:\dsee7\var\dcc\agent\logs
In the glassfish server log, I didn't find new transaction when I hit the issue
C:\glassfish3\glassfish\domains\domain1\logs

Un register and register database again in the same catalog

Dear All,
I've a requirement to Un-register the existing database from the catalog by removing all its information, and immediately registering the same database in the same catalog.
Please advice How to unregister and register again by retaining the backup files that are on tape.
Immeidate reply is highly appreciated.
Thanks

http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrepos.htm#442604
Unregistering a Target Database from the Recovery Catalog
RMAN can unregister a database as well as register it. Make sure this procedure is what you intend, because if you make a mistake, then must reregister the database. In this case, you lose any metadata that is older than the CONTROLFILE_RECORD_KEEP_TIME setting in the target database control file.
To unregister a database:
   1. Start RMAN and connect to the target database. Note down the DBID value that is displayed when you use RMAN to connect to the target database. For example, enter:
% rman TARGET / CATALOG rman/cat@catdb
connected to target database: RDBMS (DBID=1237603294)
connected to recovery catalog database
   2. List the copies and backup sets recorded in the repository (refer to "Listing RMAN Backups, Copies, and Database Incarnations"). For example, enter:
LIST BACKUP SUMMARY;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Tag
19      B A A DISK        08-FEB-02       1       1       TAG20020208T155239
20      B F A DISK        08-FEB-02       1       1       TAG20020208T155242
21      B A A DISK        08-FEB-02       1       1       TAG20020208T155331
22      B A A DISK        08-FEB-02       1       1       TAG20020208T155604
   3. Run DELETE statements to delete all existing physical backups (refer to "Deleting Backups and Copies"). For example:
DELETE BACKUP DEVICE TYPE sbt;
DELETE BACKUP DEVICE TYPE DISK;
      RMAN will list the backups that it intends to delete and prompt for confirmation before deleting them.
   4. Use SQL*Plus to connect to the recovery catalog database as the catalog owner, then execute the following query in the recovery catalog to find the correct row of the DB table, setting DB_ID equal to the value you obtained from step 1. For example, enter:
% sqlplus rman/cat@catdb
SQL> SELECT DB_KEY, DB_ID FROM DB WHERE DB_ID = 1237603294;
      This query should return exactly one row.
DB_KEY     DB_ID
         1 1237603294
1 row selected.
   5. While still connected to the recovery catalog, enter the following, where DB_KEY and DB_ID are the corresponding columns from the row you got from the query in step 4:
SQL> EXECUTE dbms_rcvcat.unregisterdatabase(db_key, db_id)
      For example, enter:
SQL> EXECUTE dbms_rcvcat.unregisterdatabase(1, 1237603294)Aron

Unable to register my data warehouse in Service Manager

I have been trying to register my data warehouse but keep getting the same error message each time - "Invalid URI: the hostname could
not be parsed." I know the issue is on the ServiceManager database side of things, but there is not a lot of information related to this error message and the info I do find is unrelated to ServiceManager. I have gone as far as building a
brand new data warehouse server and reinstalling all of the data warehouse databases from scratch. It doesn't matter if I tried to register with the original data warehouse environment or the new environment, I get the same error message. I also
received a powershell command from Microsoft Support to help clean up any residual entries in the ServiceManager database that might be left over. At this point I'm at a loss on how to proceed. Anyone ever run into this issue?
Here's the event log message:
Unable to register Service Manager installation with Data Warehouse installation.
Data Warehouse Server: DW_SCSM
Service Manager Management Server: FlowSMRC
Exception: Microsoft.EnterpriseManagement.UI.Core.Shared.PowerShell.PSServiceException: Invalid URI: The hostname could not be parsed.
at Microsoft.EnterpriseManagement.UI.Core.Shared.PowerShell.PSHostService.executeHelper(String cmd, Object[] input)
at Microsoft.EnterpriseManagement.UI.Core.Shared.PowerShell.PSHostService.Invoke(String cmd, Object[] input)
at Microsoft.EnterpriseManagement.ServiceManager.UI.Administration.DWRegistration.Registration.DWRegistrationHelper.AcceptChanges(WizardMode wizardMode)
Also, I tried registering the data warehouse using powershell Add-SCDWMgmtGroup and get an error saying that Cannot associate Service Manager installation on scsm_server with Service Manager Data Warehouse installation on dw_server.

Just got additional information about this error. If you run the following query in SQL pointing to the ServiceManager database you should see the name of the Management Server. The query is:
select * from MT_Microsoft$SystemCenter$ResourceAccessLayer$SdkResourceStore
There is a column named Server_<some GUID> that should contain the Management Sever NetBIOS name. If it has some other name, run an update query to ensure the column has the NetBIOS name of the Management Server. Restart the SCSM Console
and retry the Database Registration again and it should succeed.
Microsoft has said that this is normally caused by either moving the database or database server to another server and the value is never updated.
Try registering the DW Server again and see if you have better luck.

MSDTC connection manager is unable to register with RPC

HI
I am using the Windowserver 2012. We mount a WCF application , the server is working fine.. sundenly this error occurred in production environment. what might be the reason. What should i check in my server? how to fix this ? I navigate to components
and click distributed coordianator nothing comes in the list like LOCAL DTC. I am very confused. it is not happening in any other sites. This server is database server for my application
Thank you.
Log Name:      Application
Source:        Microsoft-Windows-MSDTC
Date:          9/20/2014 9:00:41 AM
Event ID:      4358
Task Category: MSDTC Proxy
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      IO-DB1
Description:
The MS DTC Connection Manager is unable to register with RPC to use one of LRPC, TCP/IP, or UDP/IP.
Please ensure that RPC is configured properly. If "ServerTcpPort"
registry key is configured(DWORD value under the HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC for local DTC instance or under cluster
hive for clustered DTC instance), please verify if the configured port is valid and the port is not already in use by a different component.
Error Specifics:hr = 0x8007000e, com\complus\dtc\dtc\cm\src\iomgrsrv.cpp:2597, CmdLine: "C:\Windows\system32\mmc.exe"
"C:\Windows\system32\comexp.msc" , Pid: 956
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-MSDTC" Guid="{719BE4ED-E9BC-4DD8-A7CF-C85CE8E4975D}" EventSourceName="MSDTC" />
    <EventID Qualifiers="49152">4358</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>10</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-20T02:00:41.000000000Z" />
    <EventRecordID>19391</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>IO-DB1</Computer>
    <Security />
</System>
<EventData>
    <Data Name="param1">hr = 0x8007000e, com\complus\dtc\dtc\cm\src\iomgrsrv.cpp:2597, CmdLine: "C:\Windows\system32\mmc.exe" "C:\Windows\system32\comexp.msc" , Pid: 956</Data>
    <Binary>4D005300440054004300</Binary>
</EventData>
</Event>
Thanks & Regards Manoj

Hi Partner,
Thank you for your post.
From your description, I see that the current issue is you notice Event ID 4358 error (source: Microsoft-Windows-MSDTC) logged in Application log.
Please let me know if I misunderstand anything or you have any additional information.
Firstly, could you help clarify that what operation you are performing while the issue occur? It would be nice if you can provide a GUI error message if any.
Currently, based on the error message and my research, some incorrect register key about RPC dynamic port resulting in MSDTC behaves unexpectedly might cause such symptom.
If that is the case, let's take the following steps to check our issue.
[Note: As the operation is related to the registry key components, I suggest we backup the entries firstly before performing the steps]
1. Delete all the register keys about RPC dynamic port you inserted manually.
2. Configure the ports via UI.
3. Reboot the server.
Please let me know if there is any update. Thank you for your time.
Best Regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Warning: skgmdetach - Unable to register unmap, error 4210

Can anyone infer from the alert log message found in production database. If I have connect as normal user the database hangs. Find the alert log message below
ksvcreate: Process(q001) creation failed
Tue Apr 03 21:42:07 2007
ksvcreate: Process(q001) creation failed
Wed Apr 04 00:01:05 2007
Thread 1 advanced to log sequence 3812
Current log# 2 seq# 3812 mem# 0: C:\db1\LOG\REDO02.LOG
Wed Apr 04 00:25:17 2007
Warning: skgmdetach - Unable to register unmap, error 4210
Wed Apr 04 01:29:47 2007
Warning: skgmdetach - Unable to register unmap, error 4210
Wed Apr 04 02:20:45 2007
Thread 1 advanced to log sequence 3813
Current log# 3 seq# 3813 mem# 0: C:\db1\LOG\REDO03.LOG
Wed Apr 04 02:29:44 2007
Warning: skgmdetach - Unable to register unmap, error 4210
Wed Apr 04 02:35:29 2007
Warning: skgmdetach - Unable to register unmap, error 4210
Wed Apr 04 02:55:28 2007
Warning: skgmdetach - Unable to register unmap, error 4210
Wed Apr 04 08:52:07 2007
Warning: skgmdetach - Unable to register unmap, error 4210
Wed Apr 04 10:08:46 2007
Thread 1 advanced to log sequence 3814
Current log# 4 seq# 3814 mem# 0: C:\db1\LOG\REDO04.LOG

Joshi,
Check SAP Note 1289691 - ORA-610: INTERNAL ERROR CODE if not enough resources
Metalink:-
https://metalink.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocTitle=%3Cb%3EORA-00610%3C/b%3E%20AND%20"unable%20to%20spawn%20jobq%20slave%20process%20"%20IN%20THE%20ALERT%20LOG.&viewingMode=1143&bmDocID=416244.1&from=BOOKMARK&bmDocType=PROBLEM&bmDocDsrc=KB))
https://metalink.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocTitle=Process%20J000%20died,%20kkjcre1p:%20unable%20to%20spawn%20jobq%20slave%20process&viewingMode=1143&bmDocID=833613.1&from=BOOKMARK&bmDocType=PROBLEM&bmDocDsrc=KB))
Check you DB parameter setting according to SAP Note 830576 - Parameter recommendations for Oracle 10g
SAP Note 1171650 -Automated Oracle DB parameter check
Also try by restarting server once.
Hope this helps
Thanks
Sushil

RMAN: Unable to register database

Similar Messages

Maybe you are looking for