RMAN-06004: ORACLE recovery catalog database error: ORA-03113: end - of -

Similar Questions

• RMAN-04004: recovery catalog database error: ORA-12170: TNS: connect the ti

  Hello:
  
  Last night ' RMAN backup error: ' RMAN-04004: recovery catalog database error: ORA-12170: TNS: Connect timeout.
  
  I can sqlplus to the target database and the catalog database. The listener is in place. What is the problem? What should I check?
  
  Thanks in advance for your help.

  in the oratest/orapass@rmandb1 CATALOG,.

  rmandb1 is the name of the service. normally the name of the service and the name of db are kept same.

  check rmandb1 tnsping where you try to run ' RMAN TARGET / CATALOG oratest/orapass@rmandb1 "command.

  as optput will get the ip address of the server on which db is resident, no port, Protocol

  as

  ---------

  [Oracle@RAC3 ~] $ tnsping orcl

  AMT Ping utility for Linux: Version 10.2.0.5.0 - Production on December 23, 2011 21:12:20

  Copyright (c) 1997, 2010, Oracle. All rights reserved.

  Use settings files:
  /opt/app/Oracle/product/DB/10.2.1/network/admin/SQLNET.ora

  TNSNAMES adapter used to resolve the alias
  Try to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = rac3.rajesh.com) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl)))
  OK (10 ms)
  -------------------------------

  Here the HOST = rac3.rajesh.com is the present db Server

  Published by: Rajesh.Rathod on December 23, 2011 07:43

• Cannot open the database: error, ora-03113 end of file communication

  Hi guys,.
  
  I am facing a problem with my database
  
  Oracle Linux Tikanga 5 machine
  database: 10.2.0.1
  Error: ora-03113
  
  I tried to move a log file while inserting data...
  
  I restored and tried to get back what she recovers with message media recover full but doesnot allow to open the database
  gives the same error: error: ora-03113 end of file communication
  
  Watch alert_log
  ____________
  
  ALTER database recover if necessary
  beginning
  Start of recovery Media
  ORA - 264 marked during: alter database recover if necessary
  beginning
  ...
  Fri Jan 9 16:20:18 2013
  2048 MB db_recovery_file_dest_size is 40,79% used. It is a
  user-specified limit on the amount of space that will be used by the present
  for the files related to the recovery of databases and does not reflect the amount of
  space available in the underlying file system or ASM diskgroup.
  Fri Jan 9 16:22:02 2013
  change the list of file restore of database data clear
  Fri Jan 9 16:22:02 2013
  Completed: change the clear list of restore of database data file
  Fri Jan 9 16:22:02 2013
  Edit the list of file restore of database data
  1, 2, 3, 4, 5
  Completed: change the list of file restore of database data
  1, 2, 3, 4, 5
  Fri Jan 9 16:22:02 2013
  ALTER database recover if necessary
  beginning
  Start of recovery Media
  ORA - 264 marked during: alter database recover if necessary
  beginning
  ...
  Fri Jan 9 16:22:07 2013
  change the database open
  Fri Jan 9 16:22:07 2013
  LGWR: FROM PROCESS ARCH
  Arc0 started with pid = 16, OS id = 2049
  Fri Jan 9 16:22:07 2013
  Arc0: Started archiving
  Arc1: Started archiving
  LGWR: FROM PROCESS ARCH COMPLETE
  Arc1 started with pid = 17, OS id = 2051
  Fri Jan 9 16:22:07 2013
  Fix half open fully the valve of the thread 1
  Fri Jan 9 16:22:07 2013
  Errors in the /d1/app/oracle/oradata/orcl/bdump/orcl_lgwr_1966.trc file:
  [ORA-00600: internal error code, arguments: [3712], [1], [1], [0], [445262], [0], [445261],]
  Fri Jan 9 16:22:08 2013
  Errors in the /d1/app/oracle/oradata/orcl/bdump/orcl_lgwr_1966.trc file:
  [ORA-00600: internal error code, arguments: [3712], [1], [1], [0], [445262], [0], [445261],]
  LGWR: termination litigation because of the 470 error
  Instance terminated by LGWR, pid = 1966
  
  can you please on the same...
  Thank you

  ORA-00600: internal error code, arguments: [3712].

  ORA-00600 is error internal oracle, you need to check metalink support for this.

• RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target

  Hello
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 2009-03-31 21:59:24
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target not found in the recovery catalog database
  
  
  I get the above error while taking backup RMAN Level0. I am able to connect to the database of the catalogue without any problem.
  
  I already have this registry database command in RMAN prompt. Now I am able to see backup list but I don't know how that DB asking to sign up for today. Until yesterday, the backups were running fine btu today his application to enter the catalog DB.
  
  Here we manually to connect the catalogue in this way
  rman target $ /.
  RMAN > catalog connection rmanuser/password @ < globalcatalogDB >
  connected.
  
  After that if I give this command means...
  
  RMAN > backup from the list of database;
  I get the error I pasted at the earliest.
  
  Thanks in advance.

  If you do not have a catalog, you need not to save the database. Rely you only on the target database controlfile. If you use a catalog, you must save the target database, but only once. If you sometimes use a catalog - and sometimes not--the appropriate command is RESYNC (although in many cases RMAN automatically done).

  Werner

• Error: ORA-03113: end of file on communication channel

  Installing Oracle: 11.2.0.1.0

  Linux: Oracle Linux 6.6

  I get an error after I start the DB.  Please see the screenshot below.  Please advice, if you need more information.

  Thanks for your help.

  

  As already indicated source oraenv should be run as a DBA, not root.

  You seem to face multiple problems. You run a virtual machine? If so, you can run out of physical memory and disk space on your host system.

• RMAN - 06004:ORACLE error in the recovery catalog. ORA-00904: invalid...

  Hello all,.
  
  One of our backups RMAN fails with the following error message. Any suggestions would be greatly appreciated.
  
  ==================================================================================================
  
  From backup 2008-12-30 22:03:47
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 2008-12-30 22:03:47
  RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier
  
  RMAN >
  RMAN > #BACKUP # ARCHIVELOG delete all '% d_bkp_al_ % t_Set % s_Piece %p' entry FORMAT;
  2 >
  3 > # DELETE ARCHIVELOG until ' SYSDATE-7 ";
  4 >
  5 > # check if the database can be restored
  6 > RESTORE DATABASE # VALIDATE;
  7 >
  8 > # check if controlfile can be restored
  9 > #RESTORE # CONTROLFILE to ' / backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
  10 >
  11 > # check if archivelogs for these past two weeks can be restored
  12 > # RESTORE ARCHIVELOG FROM TIME ' SYSDATE-7' VALIDATE ';
  13 >
  14 > #-check all backups on backup media are intact
  15 > # CROSSCHECK BACKUP OF DATABASE;
  16 >
  17 > #-display based on a list of files that need to be stored on the retention
  18 > policy #. For this case study, the files that do not have at least 1 backups
  19 > # will be reported.
  20 > REPORT NEED backup.
  RMAN retention policy apply to the order
  RMAN retention policy is set to 7 days recovery window
  Report of the files whose recovery needs more 7 days of archived newspapers
  Days of files name
  ---- ----- -----------------------------------------------------
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of command report at 2008-12-30 22:03:48
  RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier
  
  RMAN >
  RMAN > #-remove unnecessary backups. This command deletes the backups based on the
  2 > retention policy of #.
  3 > # commented DELETE OBSOLETE - TSM not configured to remove on 68
  4 > #DELETE # OBSOLETE;
  5 >
  6 > #-complete list of the existing backups
  7 > LIST BACKUP;
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the list command at 2008-12-30 22:03:49
  RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier
  
  RMAN >
  RMAN > # end of file.
  2 > * end-of-file *.
  
  RMAN >
  
  Published by: ORA_UMAIR on December 31, 2008 07:51

  No help is possible.
  You publish a file of newspaper only, and can not see the command that failed.
  Also you include, contrary to the recommendation in the post on Forums label, the complete version number of 4-digit.
  This is important because they either has an error in your script that does not find RMAN or you hit a bug.

  -----
  Sybrand Bakker
  Senior Oracle DBA

• RMAN-20001: target not found in the recovery catalog database

  I'm practicing the loss of all control files. I have backups of catalog rman configured for controlfile autobackup. So far, I did this.
  
  
  RMAN > startup nomount;
  Oracle instance started
  
  Total System Global Area 209715200 bytes
  
  Bytes of size 1272864 fixed
  155190240 variable size bytes
  Buffers 50331648 database bytes
  Redo buffers 2920448 bytes
  
  
  RMAN > restore controlfile autobackup.
  
  From restoration to SEPT. 08.-10
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 156 devtype = DISK
  
  field of recovery destination: / u02/flash_recovery
  name of database (or unique name of database) used for research: TEST
  channel ORA_DISK_1: autobackup found in the recovery area
  channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
  channel ORA_DISK_1: restore full automatic backup of control file
  output filename=/u02/control_files/TEST/control02.ctl
  output filename=/u03/oradata/TEST/control03.ctl
  Restoration finished in 08-SEVEN.-10
  
  RMAN > change the editing of the database;
  
  mounted database
  output channel: ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure to modify the order db at 08/09/2010 14:54:50
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target not found in the recovery catalog database
  
  
  I guess it has something to do with the DBID but... I don't have and I do not know how to find.

  Hello
  Try this
  RMAN > Connect target /.
  RMAN > Connect catalog rman/rman@test
  RMAN > startup nomount;
  RMAN > list backup of controlfile;

• RMAN-06004: error recovery catalog database ORACLE

  Hi all
  
  I'm new to the RMAN module, please help me solve the error below.
  

  Recovery Manager: Release 9.2.0.6.0 - Production
  
  Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.
  
  connected to target database: DB96 (DBID=2450380394)
  connected to recovery catalog database
  
  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '\\10.101.22.80\Backup\Rman\Prologs\DB96/DB96_FULL_%T_%U.rman' MAXPIECESIZE 4 G; 
  2> CONFIGURE CONTROLFILE AUTOBACKUP ON; 
  3> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '\\10.101.22.80\Backup\Rman\Prologs\DB96/DB96_ctlfile_%F'; 
  4> CONFIGURE RETENTION POLICY TO REDUNDANCY 1; 
  5> shutdown immediate; 
  6> startup mount; 
  7> backup database; 
  8> CROSSCHECK BACKUP; 
  9> DELETE NOPROMPT OBSOLETE; 
  10> alter database open; 
  11> list backup summary; 
  12> exit;
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of configure command at 06/20/2011 11:31:55
  RMAN-06004: ORACLE error from recovery catalog database:
   
  RMAN-20001: target database not found in recovery catalog
  Recovery Manager complete.

  Please do the neeful.
  
  Kind regards
  Jame

  Jame,

  connect to retrieve catalog owner user (RMAN) using SQLPLUS on the catalog database and run the following query.

  SQL> select * from rc_database;
  

  Another thing is, check, if your catalog is accidentally created in the target database or you sure sound in a separate database (possibly on a separate server).

  Thank you
  RANA

  Published by: RANA June 20, 2011 17:08

  Published by: RANA June 20, 2011 17:41

• RMAN-04006: auxiliary database error: ORA-12504: TNS:listener has not been

  HIII...
  
  I was doing my dataguard configuration, my primary side is a 2 node RAC and my stand by is a single node.
  IM using the database and 11 GR 2 grid infrastructure.
  
  When I try to connect to the rating system standy priamry using RMAN im getting the following error.
  
  [*[*Oracle@Rac2 ~] rman target $ / auxiliary sys / sys@to_std *.
  
  Recovery Manager: release 11.2.0.1.0 - Production on Thu Sep 29 20:39:04 2011
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
  
  connected to target database: RAC (DBID = 2346715690)
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-04006: auxiliary database error: ORA-12504: TNS:listener did not have the SERVICE_NAME in CONNECT_DATA
  
  
  My tnsnames.ora file is as follows
  
  to_std =
  (DESCRIPTION_LIST =
  (DESCRIPTION =
  (ADDRESS = (PROTOCOL = tcp (PORT = 9999))(HOST=datagrd))
  )
  (CONNECT_DATA =
  (SERVICE_NAME = STB.msftpnq.com)
  )
  )
  
  
  and my listsner.ora file is as follows
  
  list_std =
  (DESCRIPTION_LIST =
  (DESCRIPTION =
  (ADDRESS = (PROTOCOL = tcp (PORT = 9999))(HOST=datagrd))
  )
  )
  SID_LIST_list_std =
  (SID_LIST =
  (SID_DESC =
  (GLOBAL_DBNAME = STB.msftpnq.com)
  (SID_NAME = STB)
  (ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)
  )
  )
  
  
  Please can someone help me to solve the issue.
  
  
  Thanks in advance.

  change the string Service_name in the tnsnames.ora file in the following and try again

  (SERVICE_NAME = STB) will be replaced by (SERVICE_NAME = STB.msftpnq.com)

• RMAN-04005: target database error: ORA-01031: insufficient privileges

  Try to duplicate db
  I checked the orapwd file looks ok.
  
  Oracle: tulpcorpadb03$ rman TARGET sys/***@wcmp AUXILIARY.
  
  Release of Recovery Manager: 9.2.0.8.0 - 64 bit Production
  
  Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-04005: target database error:
  ORA-01031: insufficient privileges
  
  I findout, this is prod db and not allowed to bounce to change, any other solution do rman duplicate work without changing it?
  
  SQL > show parameter password
  
  VALUE OF TYPE NAME
  -----------
  Remote_login_passwordfile string NONE
  
  SQL > connect virtue sysdba;
  Connected.
  SQL > select * from v$ pwfile_users;
  
  no selected line

  The auxiliary node must always have access to the backupset.

• Database does not start... ALTER database open; change the database open * ERROR at line 1: ORA-03113: end of file on the channel of communication process ID: 10400 Session ID: 418 serial number: 3 -.

  HI during startup of the database of the following errors is. Please help solve the problem.

  SQL > alter database open;

  change the database open * ERROR at line 1: ORA-03113: end of file on the channel of communication process ID: 10400 Session ID: 418 serial number: 3 -.

  ============================================================

  Please see the alerts log entries

  --------------------------------------------------------------------------------------------------------------------------------

  Commissioning:

  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production

  With the options of partitioning, OLAP, Data Mining and Real Application Testing.

  Using parameters in spfile D:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEATTNDPRD server-side. ORA

  Parameters of the system with default values:

  process = 400

  sessions = 624

  memory_target = 4G

  control_files = 'D:\ORACLE\ORADATA\ATTNDPRD\CONTROLFILE\O1_MF_8LRQYB0M_. CTL.

  control_files = 'C:\ORACLE\ORADATA\ATTNDPRD\CONTROLFILE\O1_MF_8LRQYB13_. CTL.

  DB_BLOCK_SIZE = 8192

  compatible = "11.2.0.0.0."

  log_archive_format = "ARC%S_%R.%T."

  db_create_file_dest = 'D:\oracle\oradata. '

  db_create_online_log_dest_1 = "D:\oracle\oradata".

  db_create_online_log_dest_2 = "C:\oracle\oradata".

  db_recovery_file_dest = 'C:\oracle\oradata\flash_area. '

  db_recovery_file_dest_size = 8G

  undo_tablespace = 'UNDOTBS1.

  Remote_login_passwordfile = "EXCLUSIVE."

  db_domain = «»

  dispatchers = "(PROTOCOL=TCP) (SERVICE = ATTNDPRDXDB)" "

  audit_file_dest = "D:\APP\ADMINISTRATOR\ADMIN\ATTNDPRD\ADUMP".

  AUDIT_TRAIL = 'DB '.

  db_name = "ATTNDPRD".

  open_cursors = 300

  diagnostic_dest = "D:\APP\ADMINISTRATOR".

  Sun 24 May 13:43:09 2015

  PMON started with pid = 2, OS id = 5792

  Sun 24 May 13:43:09 2015

  VKTM started with pid = 3, OS id = 6500 high priority

  VKTM clocked at (10) precision of milliseconds with DBRM quantum (100) ms

  Sun 24 May 13:43:09 2015

  GEN0 started with pid = 4, OS id = 13072

  Sun 24 May 13:43:09 2015

  DIAG started with pid = 5, OS id = 1424

  Sun 24 May 13:43:09 2015

  DBRM started with pid = 6, OS id = 8240

  Sun 24 May 13:43:09 2015

  PSP0 started with pid = 7, OS id = 2980

  Sun 24 May 13:43:09 2015

  DIA0 started with pid = 8, OS id = 12956

  Sun 24 May 13:43:09 2015

  MA started with pid = 9, OS id = 13356

  Sun 24 May 13:43:09 2015

  DBW0 started with pid = 10, OS id = 14248

  Sun 24 May 13:43:09 2015

  DBW1 started with pid = 11, OS id = 17900

  Sun 24 May 13:43:09 2015

  LGWR started with pid = 12, OS id = 5564

  Sun 24 May 13:43:09 2015

  CKPT started with pid = 13, OS id = 16736

  Sun 24 May 13:43:09 2015

  SMON started with pid = 14, OS id = 14068

  Sun 24 May 13:43:09 2015

  RECCE has started with pid = 15, OS id = 16288

  Sun 24 May 13:43:09 2015

  MMON started with pid = 16, OS id = 10884

  commissioning 1 dispatcher (s) for '(ADDRESS =(PARTIAL=YES) (PROTOCOL = TCP))' network address...

  commissioning or shared server 1...

  Environment ORACLE_BASE = D:\app\Administrator

  Sun 24 May 13:43:09 2015

  ALTER DATABASE MOUNT

  Sun 24 May 13:43:09 2015

  MMNL started with pid = 17, OS id = 16128

  Mount of redo thread 1, with mount id 3325657453

  Database mounted in exclusive Mode

  Disabled lost write protect

  Completed: ALTER DATABASE MOUNT

  Sun 24 May 13:43:23 2015

  change the database open

  Sun 24 May 13:43:23 2015

  LGWR: FROM PROCESS ARCH

  Sun 24 May 13:43:23 2015

  Arc0 started with pid = 21, OS id = 10084

  Arc0: Started archiving

  LGWR: FROM PROCESS ARCH COMPLETE

  ARC0: FROM PROCESS ARCH

  Sun 24 May 13:43:24 2015

  Arc1 started with pid = 22, OS id = 18400

  Sun 24 May 13:43:24 2015

  ARC2 started with pid = 23, OS id = 17280

  Arc1: Started archiving

  ARC2: Started archiving

  Arc1: become the "no FAL' ARCH

  Arc1: become the "no SRL" ARCH

  ARC2: Become the heartbeat ARCH

  Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_ora_10400.trc file:

  ORA-19815: WARNING: db_recovery_file_dest_size 8589934592 bytes is 100.00% used and has 0 bytes remaining available.

  ************************************************************************

  You have choice to free up space in the recovery area:

  1 consider changing STRATEGY OF RETENTION of RMAN. If you are using Data Guard

  then consider changing POLICY of DELETE ARCHIVELOG RMAN.

  2 back up files on a tertiary device such as a tape with RMAN

  SAFEGUARDING RECOVERY AREA command.

  3. Add space drive and increase the db_recovery_file_dest_size setting to

  reflect the new space.

  4 remove the unnecessary files using the RMAN DELETE command. If a service

  the system control has been used to remove the files, and then use the RMAN DUPLICATION and

  Commands DELETE has EXPIRED.

  ************************************************************************

  Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_ora_10400.trc file:

  ORA-19809: limit exceeded for file recovery

  ORA-19804: cannot recover disk 44571136 bytes limit 8589934592 space

  ARCH: 19809 error creating archive log file to ' C:\ORACLE\ORADATA\FLASH_AREA\ATTNDPRD\ARCHIVELOG\2015_05_24\O1_MF_1_10343_%U_. ARC'

  Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_ora_10400.trc file:

  ORA-16038: log 2 # 10343 sequence can be archived

  ORA-19809: limit exceeded for file recovery

  ORA-00312: wire 2 1 online journal: ' D:\ORACLE\ORADATA\ATTNDPRD\ONLINELOG\O1_MF_2_8LRQYD8B_. JOURNAL"

  ORA-00312: wire 2 1 online journal: ' C:\ORACLE\ORADATA\ATTNDPRD\ONLINELOG\O1_MF_2_8LRQYDF6_. JOURNAL"

  USER (ospid: 10400): put an end to litigation because of the error 16038

  Sun 24 May 13:43:24 2015

  ARC3 started with pid = 24, OS id = 2188

  Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_arc2_17280.trc file:

  ORA-19815: WARNING: db_recovery_file_dest_size 8589934592 bytes is 100.00% used and has 0 bytes remaining available.

  ************************************************************************

  You have choice to free up space in the recovery area:

  1 consider changing STRATEGY OF RETENTION of RMAN. If you are using Data Guard

  then consider changing POLICY of DELETE ARCHIVELOG RMAN.

  2 back up files on a tertiary device such as a tape with RMAN

  SAFEGUARDING RECOVERY AREA command.

  3. Add space drive and increase the db_recovery_file_dest_size setting to

  reflect the new space.

  4 remove the unnecessary files using the RMAN DELETE command. If a service

  the system control has been used to remove the files, and then use the RMAN DUPLICATION and

  Commands DELETE has EXPIRED.

  ************************************************************************

  Instance of stopped by USER, pid = 10400

  --------------------------------------------------------------------------------------------------------------------------

  Regarding

  Ngoyi

  Hello

  Now it works very well... with following

  --------------------------------------------------

  using sqlplus

  • Startup mount
  • ALTER database noarchivelog;
  • ALTER database open;

  -------------------------------------------------------------------------------

  Concerning

  Ngoyi

  -------------------------------------------------

• RMAN-04017: description of the startup error: ORA-32004: obsolete parameters or obsolete er (s) specified for the instance of RDBMS

  Dear all,

  While making the cloning of RMAN using the command duplicate in 11.2.0.3 database with ebs.

  We receive the error below

  connected to the auxiliary database (not started)

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of Db in dual at 03/07/2015 15:12:07

  RMAN-06403: could not get a fully authorized session

  RMAN-04006: auxiliary database error: ORA-24327: need explicit attach befor

  e a user authentication

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-04014: failed to start: ORA-03113: end of file on communication channel

  RMAN-04017: description of the startup error: ORA-32004: outdated or obsolete parameters

  ER (s) specified for the instance of RDBMS

  Kind regards

  Villi Kumar

  Dear all,

  We have corrected the problems.

  Solution:

  To the bottom of the database

  Comment this parameter and re try

  =====================================

  oratest@ctsst $ grep-i local initerptest.ora

  #local_listener = erptest_LOCAL

  oratest@ctsst $

  Test the issue again.

  Concerning

  Villi Kumar

• Connection to the PROD database error: ORA-20

  Salvation of DBA
  
  When running custom reports, I get the following error.
  
  Connection to the PROD database error: ORA-20
  
  When I run the same report again, it works fine.
  
  Please tell me why it behaves like this? and advice me please how to fix this.
  
  Best regards

  Suresh,

  Follow the recommendations of the following note to set the initialization of the PROCESS parameter correctly.

  Note: 216205,1 - parameters to initialize database for Oracle Applications Release 11i
  https://metalink2.Oracle.com/MetaLink/PLSQL/ml2_documents.showDocument?p_database_id=not&P_ID=216205.1

  Another possible solution is to give your opinion on tune your custom code.

• ORA-03113 end of file on communication channel error

  Hello

  I am trying to create a table that looks like the following:

  create table test as
  with a as
  (
  ..
  ),
  b as
  (
  ..),
  ab_percentage as
  (
  ..
  ),
  c as
  (
  ..
  ),
  d as
  (
  ..),
  cd_percentage as
  (
  ..
  ),
  e as
  (
  select * from ab_percentage UNION cd_percentage
  )
  select * from e;
  
  

  When I run the script, I get the following error:

  Oracle error: ORA-03113

  end of file on communication channel

  Cause: The connection between the Client and the process server was broken.

  Action: There was a communication error that requires further investigation. First, check for network problems and review the SQL * Net configuration. In addition, review the file alert.log for possible errors. Finally, a test to see if the server process is dead and if a trace file has been generated at the time of the failure.

  I use:

  TOAD for Oracle Base 11.5.1.2

  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production

  PL/SQL Release 11.2.0.1.0 - Production

  CORE 11.2.0.1.0 Production

  AMT for Linux: Version 11.2.0.1.0 - Production

  NLSRTL Version 11.2.0.1.0 - Production

  Please help me understand this!

  Thank you!

  Hello

  2632048 wrote:

  Hello

  I am trying to create a table that looks like the following:

  1. create the test table
  2. with one also
  3. (
  4. ..
  5. ),
  6. b as
  7. (
  8. ..),
  9. ab_percentage as
  10. (
  11. ..
  12. ),
  13. c as
  14. (
  15. ..
  16. ),
  17. d as
  18. (
  19. ..),
  20. cd_percentage as
  21. (
  22. ..
  23. ),
  24. e as
  25. (
  26. Select * from ab_percentage UNION cd_percentage
  27. )
  28. Select * e;

  That has nothing to do with the problem of the ORA-03113, but what value is Sub question e add?

  Why can't let you the lines 23, 24, 25, 27 and 28 above, so that the request ends

  cd_percentage as

  (

  ...

  )

  Select * from ab_percentage UNION select * from cd_percentage;

  ?

• ORA-03113: end of file on communication channel: delivered Oracle SQL

  Hello
  We have a SQL comes in an application engine that throws the below error:
  
  1. SELECT DISTINCT ELG. EMPLID, ELG. EMPL_RCD, '99', ((ABS1. EFFDT)
  2 + (1)), SYSDATE, EVT. GPDE_DV_EE_STATUS, EVT. GPDE_AL_FREQUENCY, "FM_CG_0811".
  3 PS_GPDE_DV_ELIG_MO ELO, ELG, PS_GPDE_DV_FLT_ABS ABS1 PS_GPDE_DV_ELIG_MO
  4, PS_GPDE_DV_EVTDFN EVT WHERE ELG. CAL_RUN_ID = "FM_CG_0811" AND ELG. EMPLID =
  5 ELO. EMPLID AND ELG. EMPL_RCD = ELO. EMPL_RCD AND EVT. GPDE_DV_EVT_TYPE = '99' AND
  6 ELG. GPDE_DV_SV_CODE <>' 0000' AND ELG. GPDE_DV_ACTIVE IN ('2 ', ' 3') AND
  7 ELO. GPDE_AL_SEQNUM = ELG. GPDE_AL_SEQNUM - 1 AND ELO. GPDE_RP_SIGRS_ANLZ = 0.00
  8 AND ELO. GPDE_RP_SIDAYS = 0.00 AND (ELG. GPDE_RP_SIGRS_ANLZ > 0.00 OR
  9 ELG. GPDE_RP_SIDAYS > 0) AND ABS1. EMPLID = ELG. EMPLID AND ABS1. EMPL_RCD =
  10 ELG. EMPL_RCD AND ABS1. CAL_RUN_ID = "FM_CG_0811" AND ABS1. ABS_BGN_DT < =.
  11 ELG. PRD_END_DT AND ABS1. GPDE_DV_AB_CODE = ' A ' AND ABS1.» GP_UNIT IN (4,5,6) AND
  12 EXISTS (SELECT 'X' FROM PS_GPDE_DV_TRIGGER WHERE TRIG TRIG.) EMPLID = ELG. EMPLID
  13 AND TRIG. EMPL_RCD = ELG. EMPL_RCD AND TRIG. GPDE_DV_EVT_TYPE IN
  14 ('09', '31', '32,' 33', 34') AND TRIG. GPDE_DV_EVT_EFFDT < = ABS1. ABS_END_DT AND
  15 TRIG. GPDE_DV_EVT_EFFDT > = ELG. GPDE_AL_BGN_DT AND TRIG. GPDE_DV_EVT_EFFDT =)
  16. SELECT MAX (TRIG2. GPDE_DV_EVT_EFFDT) OF PS_GPDE_DV_TRIGGER TRIG2 WHERE
  17 TRIG2. EMPLID = ELG. EMPLID AND TRIG2. EMPL_RCD = ELG. EMPL_RCD AND
  18 TRIG2. GPDE_DV_EE_STATUS <>' n AND TRIG2. GPDE_DV_EVT_TYPE NOT LIKE 2% ' AND
  19 TRIG2. GPDE_DV_EVT_EFFDT < ABS1. EFFDT)) AND ((ABS1. EFFDT) +.
  20 (1)) > = ELG. GPDE_AL_BGN_DT AND ((ABS1. EFFDT) (1)) > (SELECT MIN (E3. PRD_END_DT)
  21. OF PS_GPDE_DV_ELIG_MO E3 WHERE E3. EMPLID = ELG. EMPLID AND
  22 * E3. EMPL_RCD = ELG. EMPL_RCD AND E3. CAL_RUN_ID = "FM_CG_0811")
  SQL > /.
  SELECT DISTINCT TASKS. EMPLID, ELG. EMPL_RCD, '99', ((ABS1. EFFDT)
  *
  ERROR on line 1:
  ORA-03113: end of file on communication channel
  
  
  above sql is passed a statement selection-insert inline, however, as we see, the select query has a problem.
  
  The interesting part is that if I change AND TRIG. GPDE_DV_EVT_TYPE IN ('09', '31', '32', '33', 34')
  to AND TRIG. GPDE_DV_EVT_TYPE = '31'
  
  so, it works!
  
  Suggestions please!
  
  Thank you
  Vikas

  According to the Metalink3 #654658.1, is not always past in 10.2.0.2, which means that it happens.
  The Oracle suggested patch is #5128368 or a workaround is to cut the SQL into small pieces to avoid in.

  You could also start an SR to your Oracle support (no support Peoplesoft) to use them for the patch and/or workaround solution to apply.

  Finally and not at least, it seems that Peopletools 8.49 are not supported on Oracle 10.2.0.2 (obligatorily 10.2.0.3 or 10.2.0.4).

  Nicolas.